WEBVTT

1
00:00:00.000 --> 00:00:03.000
Happy Monday! I'm Cory Foy, and welcome to

2
00:00:03.000 --> 00:00:06.000
another Mapping Monday's video. In this week's video

3
00:00:06.000 --> 00:00:09.000
I want to go back to some basics of Wardley Mapping

4
00:00:09.000 --> 00:00:12.000
and help you create your first map.

5
00:00:12.000 --> 00:00:15.000
Wardley Mapping is, at it's core, a way of

6
00:00:15.000 --> 00:00:18.000
understanding the landscape of components necessary

7
00:00:18.000 --> 00:00:21.000
to deliver one or more user needs. 

8
00:00:21.000 --> 00:00:24.000
So we'll start by asking a simple question

9
00:00:24.000 --> 00:00:27.000
Who are your users? And can you identify

10
00:00:27.000 --> 00:00:30.000
one need a user has they come to you for?

11
00:00:30.000 --> 00:00:33.000
So take a piece of paper and write that need

12
00:00:33.000 --> 00:00:36.000
at the top, circling it. Here we'll use an example of

13
00:00:36.000 --> 00:00:39.000
eating a sandwich to make things easier.

14
00:00:39.000 --> 00:00:42.000
With a user need identified, we now need to understand

15
00:00:42.000 --> 00:00:45.000
the components necessary to service that need.

16
00:00:45.000 --> 00:00:48.000
So for each component, write it somewhere below

17
00:00:48.000 --> 00:00:51.000
the user need, circle it, and then connect it to 

18
00:00:51.000 --> 00:00:54.000
the user need. For our sandwich, we'll need

19
00:00:54.000 --> 00:00:57.000
bread, cheese, protein, vegetable and condiments.

20
00:00:57.000 --> 00:01:00.000
Each of these are high level components.

21
00:01:00.000 --> 00:01:03.000
Now, what components do we need to service these

22
00:01:03.000 --> 00:01:06.000
high level components? So for bread, we'll need something like flour

23
00:01:06.000 --> 00:01:09.000
for cheese we'll need milk, for protein we could use either

24
00:01:09.000 --> 00:01:12.000
meat, or something like peanut butter. For vegetables we

25
00:01:12.000 --> 00:01:15.000
could have tomato and lettuce, and for condiments we could have things like

26
00:01:15.000 --> 00:01:18.000
mayonnaise and mustard. And we may need to do this loop

27
00:01:18.000 --> 00:01:21.000
a couple of times to get our components. The goal

28
00:01:21.000 --> 00:01:24.000
here isn't necessarily to capture every permutation

29
00:01:24.000 --> 00:01:27.000
or level, but to drive out to interesting insights,

30
00:01:27.000 --> 00:01:30.000
which is where the art of this comes in.

31
00:01:30.000 --> 00:01:33.000
For example, we'll show that for flour, we make it

32
00:01:33.000 --> 00:01:36.000
ourselves, so we need both wheat and a flour mill.

33
00:01:36.000 --> 00:01:39.000
Once we have our components and the 

34
00:01:39.000 --> 00:01:42.000
interconnections, we've drawn what's known as a value chain.

35
00:01:42.000 --> 00:01:45.000
This allows us to have a picture of what's necessary

36
00:01:45.000 --> 00:01:48.000
to deliver that user value. It's not a map

37
00:01:48.000 --> 00:01:51.000
yet - but we're close! To make it a map

38
00:01:51.000 --> 00:01:54.000
we have to add one more piece - movement.

39
00:01:54.000 --> 00:01:57.000
Simon Wardley defines four stages of

40
00:01:57.000 --> 00:02:00.000
component evolution in his maps. In Genesis

41
00:02:00.000 --> 00:02:03.000
it's all brand new - from scratch. Custom Built

42
00:02:03.000 --> 00:02:06.000
has enough knowledge to be assembled, 

43
00:02:06.000 --> 00:02:09.000
but we have to do it every time. Product means it's

44
00:02:09.000 --> 00:02:12.000
something we can purchase, and utility means we can treat it like

45
00:02:12.000 --> 00:02:15.000
electricity. It's something we can just get without really thinking about it.

46
00:02:15.000 --> 00:02:18.000
So we need to take our components, and

47
00:02:18.000 --> 00:02:21.000
map them to the stages. When we map things

48
00:02:21.000 --> 00:02:24.000
out, we notice that a majority of our components

49
00:02:24.000 --> 00:02:27.000
are products, but bread is something we custom build

50
00:02:27.000 --> 00:02:30.000
using genesis components. 

51
00:02:30.000 --> 00:02:33.000
The underlying assumption is that components will evolve through

52
00:02:33.000 --> 00:02:36.000
these stages as they become more widely adopted. So 

53
00:02:36.000 --> 00:02:39.000
bread, will eventually mature to be a product we purchase

54
00:02:39.000 --> 00:02:42.000
based on this simple view. In that case

55
00:02:42.000 --> 00:02:45.000
the investments we have in things like the flour mill will become

56
00:02:45.000 --> 00:02:48.000
less valuable, so we can start to think about how we

57
00:02:48.000 --> 00:02:51.000
transition as an organization to hande a new reality

58
00:02:51.000 --> 00:02:54.000
of bread as a product.

59
00:02:54.000 --> 00:02:57.000
The other thing we can look at is other components

60
00:02:57.000 --> 00:03:00.000
that lead to new business opportunities. For example,

61
00:03:00.000 --> 00:03:03.000
someone has to order a sandwich (even in their own head).

62
00:03:03.000 --> 00:03:06.000
And the sandwich has to be assembled. If we do it ourselves

63
00:03:06.000 --> 00:03:09.000
we buy the components, but we still custom

64
00:03:09.000 --> 00:03:12.000
build the sandwich. That could also move

65
00:03:12.000 --> 00:03:15.000
towards productization, creating new market

66
00:03:15.000 --> 00:03:18.000
opportunities for suppliers for ingredients for the sandwich. 

67
00:03:18.000 --> 00:03:21.000
And possibly even moving towards Sandwich as a Service

68
00:03:21.000 --> 00:03:24.000
I either order a sandwich and it comes, or 

69
00:03:24.000 --> 00:03:27.000
I subscribe to sandwiches and every day a new

70
00:03:27.000 --> 00:03:30.000
one shows up. But now you have your first Wardley Map!

71
00:03:30.000 --> 00:03:33.000
From here you want to map more of your user needs

72
00:03:33.000 --> 00:03:36.000
and ask questions about the landscape that gets generated.

73
00:03:36.000 --> 00:03:39.000
And as you ask more questions, there's a wealth of resources

74
00:03:39.000 --> 00:03:42.000
available to help. Simon has a wonderful blog

75
00:03:42.000 --> 00:03:45.000
and a book in progress, there's a great forum, wiki and

76
00:03:45.000 --> 00:03:48.000
Slack channel, and Ben Mosior has 

77
00:03:48.000 --> 00:03:51.000
Learn Wardley Mapping dot com. And, of course, I'm always happy

78
00:03:51.000 --> 00:03:54.000
to jump on a call and help you create your maps or ask questions

79
00:03:54.000 --> 00:03:57.000
about your organization. Just reach out on Twitter at @Cory_foy 

80
00:03:57.000 --> 00:04:00.000
or via email at hello at Cory foy dot com.

81
00:04:00.000 --> 00:04:03.000
All of these links are also on the blog post for this video.

82
00:04:03.000 --> 00:04:06.000
Until next week, have fun with your new maps!