94
Build Systems, Not Stuff Presented by @Abby_the_ia 1

Build Systems, Not Stuff

Embed Size (px)

DESCRIPTION

This presentation is for anyone who has had technical, strategic and/or budgetary constraints influence what was built vs. what was imagined. We will dig into how to use systems-based thinking to understand how things influence one another and learn techniques to discover constraints sooner. We will learn how to start creating efficiencies of digital process, infrastructure and communication in pursuit of better user experiences.

Citation preview

Page 1: Build Systems, Not Stuff

Build Systems, Not Stuff

Presented by @Abby_the_ia

1

Page 2: Build Systems, Not Stuff

2

Page 3: Build Systems, Not Stuff

I Make the unclear, clear for people who use and make

things.

3

Page 4: Build Systems, Not Stuff

4

4

Page 5: Build Systems, Not Stuff

Most recently I Have helped

• Change the audience for Sharpie from a office supply consumer to teenagers looking for a self expression tool

• Grow a 150,000 member Facebook fan base for JELL-O over the weekend.

• Pilot a revolutionary diet for people with Type 2 diabetes• Analyze and strategically prioritize digital marketing efforts

and improvements for Herman Miller in support of their movement into the B to C market

5

Page 6: Build Systems, Not Stuff

I hear a lot of the same things over and over...

Our current digital marketing is:

6

A) Embarrassingly out of date

B) Not flexible enough to support needs

C) Not able to be affected quickly because of politics and the bureaucracy

D) All of the Above (Eeeeekk)

6

Page 7: Build Systems, Not Stuff

The behavior of the system cannot be known just by knowing the elements

- Donella Meadows

7

7

Page 8: Build Systems, Not Stuff

Meet the Blind men of digital marketing

8

“I post on social media and send emails”

“I manage the Websites”

“I design the marketing”

“I control the money”

8

Page 9: Build Systems, Not Stuff

9

Observation:Its always the same issues affecting the same parts of the same systems

9

Page 10: Build Systems, Not Stuff

10

We need to build systems, not just stuff.

10

Page 11: Build Systems, Not Stuff

When Stuff is king...

11

11

Page 12: Build Systems, Not Stuff

Spray-n-Pray is common wisdom

12

12

Page 13: Build Systems, Not Stuff

Corporate Underpants start to show

13

13

Page 14: Build Systems, Not Stuff

Shiny, dusty objects accumulate

14

14

Page 15: Build Systems, Not Stuff

Trends win out over needs

15

15

Page 16: Build Systems, Not Stuff

“Skunkworks” projects used to achieve tactical goals

16

16

Page 17: Build Systems, Not Stuff

Everyone feels rushed and underserved

17

17

Page 18: Build Systems, Not Stuff

vs.We need a Facebook page

We need a Digital

Recruitment engine

We ask for more stuff

18

Page 19: Build Systems, Not Stuff

Sound familiar?

19

19

Page 20: Build Systems, Not Stuff

There has to be a better way

20

20

Page 21: Build Systems, Not Stuff

But we arent in manufacturing!

21

21

Page 22: Build Systems, Not Stuff

isnt Creativity meant to be messy?

22

22

Page 23: Build Systems, Not Stuff

23

One important (and easy) question:

How should we spend our finite creative energy?

23

Page 24: Build Systems, Not Stuff

24

By analyzing the system, maybe we can improve the User experience of working in digital marketing

24

Page 25: Build Systems, Not Stuff

Systems-based thinking

the process of understanding how things influence one another. 

viewing "problems" as parts of an overall system, rather than reacting to specific part.

focusing on cyclical rather than linear cause and effect.

25

25

Page 26: Build Systems, Not Stuff

When System is king...

26

• Effectiveness becomes measurable• Solutions have longevity and reuse• Entities are able to remain in sync while

operating independently• Adequate time and budget is allocated• People feel like things just work

26

Page 27: Build Systems, Not Stuff

Reinventing the WheelRepeatable Magic

27

27

Page 28: Build Systems, Not Stuff

Systems Thinking 101

28

28

Page 29: Build Systems, Not Stuff

A system is a set of stocks and flows that is interconnected in

a way that it produces a predictable pattern.

29

29

Page 30: Build Systems, Not Stuff

30

STocks:Assets within your

organization that are able to be measured

for example:

• Knowledge of industry trends• Marketing Budget• Creative Talent

30

Page 31: Build Systems, Not Stuff

31

Flows:Process that affects and

connects stocksfor example:

• How insights become strategy• How designers are briefed on

architectural decisions• How code is accepted in development

31

Page 32: Build Systems, Not Stuff

Cold hard Facts about systems

32

1. Levels of stock are only able to be affected by manipulating flows

2. Stocks take time to change, because flows take time to flow

32

Page 33: Build Systems, Not Stuff

33

another fact: Digital Marketing is a system

33

Page 34: Build Systems, Not Stuff

34

34

Page 35: Build Systems, Not Stuff

35

Digital Marketing: A common system

35

Page 36: Build Systems, Not Stuff

36

Digital Marketing: A common system

36

Page 37: Build Systems, Not Stuff

37

If you are doing it right, you start here

37

Page 38: Build Systems, Not Stuff

38

Digital Marketing: A common system

38

Page 39: Build Systems, Not Stuff

39

But, a lot of people start here...

39

Page 40: Build Systems, Not Stuff

40

Digital Marketing: A common system

40

Page 41: Build Systems, Not Stuff

41

And even here... eek!

41

Page 42: Build Systems, Not Stuff

42

Digital Marketing: A common system

42

Page 43: Build Systems, Not Stuff

43

A lot of people stop here.

43

Page 44: Build Systems, Not Stuff

44

Digital Marketing: A common system

44

Page 45: Build Systems, Not Stuff

45

and This part is almost always ignored or weak

45

Page 46: Build Systems, Not Stuff

46

there are shared lessons that all organizations can learn from

46

Page 47: Build Systems, Not Stuff

47

Five common system failures

47

Page 48: Build Systems, Not Stuff

48

48

Page 49: Build Systems, Not Stuff

49

What’s supposed

to happen

49

Page 50: Build Systems, Not Stuff

50

What can also

happen

50

Page 51: Build Systems, Not Stuff

51

Symptoms

• brittle feeling interactions• Not knowing all the

incarnations of the experience• Not being able to defend cost

of improvement

51

Page 52: Build Systems, Not Stuff

52

Diagnosis: Low Awareness of how something works today

leads to bad strategy

You need to work on research.

52

Page 53: Build Systems, Not Stuff

53

Idea to Combat:

Measure quality of existing systems:

1. Heuristically2. Analytically

3. With real users

53

Page 54: Build Systems, Not Stuff

54

54

Page 55: Build Systems, Not Stuff

55

Lets try to find a way to apply

online55

Page 56: Build Systems, Not Stuff

56

56

Page 57: Build Systems, Not Stuff

57

57

Page 58: Build Systems, Not Stuff

58

58

Page 59: Build Systems, Not Stuff

59

Symptoms

• All the content is there and nothing can be found

• No research has been done into what users want

• Low conversion and roi

59

Page 60: Build Systems, Not Stuff

60

Diagnosis: Lack of clear goals and key performance indicators leads to confounding experience

You need to work on goal setting

60

Page 61: Build Systems, Not Stuff

61

Idea To Combat:

Define S.M.A.R.T Goals and a plan to measure against them

q Specificq Measurableq Achievableq Relevantq Time bound

61

Page 62: Build Systems, Not Stuff

62

62

Page 63: Build Systems, Not Stuff

63

63

Page 64: Build Systems, Not Stuff

64

Symptoms

• Content feels forced into boxes it doesnt fit into

• things are jimmied together• Creative production always

costs more than expected and often assets are reused inappropriately

64

Page 65: Build Systems, Not Stuff

65

Diagnosis: silo-ed decisions on content degrade quality of

experience offered

You need to work on architecting

65

Page 66: Build Systems, Not Stuff

66

Idea to COmbat:

Let the users make the call when content organization

challenges arise. Card sorting, contextual inquiry and

collaborative design can all be used for this.

66

Page 67: Build Systems, Not Stuff

67

67

Page 68: Build Systems, Not Stuff

68

68

Page 69: Build Systems, Not Stuff

69

69

Page 70: Build Systems, Not Stuff

70

Symptoms

• Devices and tools are devised to assist people in understanding the marketing material

• Navigation is bloated, landing pages lack focus

• Functionality is heavy and unneeded

70

Page 71: Build Systems, Not Stuff

71

Diagnosis: Too many things, no priority. SUch a mess.

You have to work on documentation

71

Page 72: Build Systems, Not Stuff

72

idea to Combat:

Create a roadmap of features defined not

just against resources available but against user and business

goals

72

Page 73: Build Systems, Not Stuff

73

73

Page 75: Build Systems, Not Stuff

75

Diagnosis: NEver completing the feedback loop.

You need to work on measurement

75

Page 76: Build Systems, Not Stuff

76

Idea to Combat: Host a conversation with

designers, marketers and researchers to talk

about improving the flow of strategic guidance

and insight

76

Page 77: Build Systems, Not Stuff

How to get started in your organization

77

77

Page 78: Build Systems, Not Stuff

78

to Become a system advocate in your

organization

78

Page 79: Build Systems, Not Stuff

79

Lesson 1: You need pictures, because systems happen all at once.

79

Page 80: Build Systems, Not Stuff

80

Pictures are thought starters

80

Page 81: Build Systems, Not Stuff

81

Pictures allow you to see the connections

81

Page 82: Build Systems, Not Stuff

82

pictures allow quick illustration of problems and solutions

82

Page 83: Build Systems, Not Stuff

83

Pictures are great for understanding the systems, roles and rules

83

Page 84: Build Systems, Not Stuff

84

Pictures can illustrate a higher level view

84

Page 85: Build Systems, Not Stuff

Lesson 2: Evaluate the System as is

85

• Get the right people in the room to discuss the results of the current digital marketing environment

• Document it in simple pictures, perhaps stocks and flows

• Highlight hardships you feel today or know about externally

85

Page 86: Build Systems, Not Stuff

Lesson 3: Take Stock of what you need

86

• Identify the goals you have for your digital marketing

• Identify the obligations you have to meet for stakeholders

• Identify the things colleagues have complained about or asked for

86

Page 87: Build Systems, Not Stuff

Lesson 4: Prioritize issues to work on

87

• Identify the issue type. Is it a lack of resource, bad process, old technology?

• Determine how much (and who) it hurts?

• Assign a internal and external priority

87

Page 88: Build Systems, Not Stuff

Lesson 5: Try New flows

88

• Get the space, team and instance needed to experiment.

• Make sure people know they are guinea pigs

• Treat it as a research assignment (try A/B testing, and asking followup questions in a focus group etc...)

• Document what you are trying, why and how you feel it will change things

88

Page 89: Build Systems, Not Stuff

Lesson 6: Reduce, Reuse, Recycle

89

• Reduce the complexity across initiatives

• Reuse technological investment across campaigns, building an arsenal of owned solutions over time

• Recycle your “stuff”: Always think about the lifecycle of the “stuff” your systems are producing.

89

Page 90: Build Systems, Not Stuff

90

Lesson 7: Have the right attitude

• Be honest and transparent

• Be collaborative

• Be forward looking

• Be willing to fail and try again

90

Page 91: Build Systems, Not Stuff

So...

91

Next time someone asks for stuff

91

Page 92: Build Systems, Not Stuff

Think...

92

How can we take this up a level?

Are we thinking about the life cycle?

Can we measure our impact here?

Who else is impacted by this and how can they help solve this?

92

Page 93: Build Systems, Not Stuff

How can we...

93

Build a system, not just more stuff

93

Page 94: Build Systems, Not Stuff

94

Thanks!

@abby_the_ia

Abbytheia.com

[email protected]

94