KanDDDinsky 2022: How to relate your OKRs to your technical real-estate

Slide 1

Slide 1 text

@huizendveld #KanDDDinsky How to relate your OKRs to your technical real-estate

Slide 2

Slide 2 text

No content

Slide 3

Slide 3 text

@huizendveld #KanDDDinsky 🎯 => 🗺

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

@huizendveld #KanDDDinsky This talk is not for you if you want to learn about either OKRs or Wardley Maps.   This talk is about combining them.

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

No content

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

@huizendveld #KanDDDinsky 🎯 Objective A big goal the team is so thrilled about   it makes them jump out of bed each morning

Slide 11

Slide 11 text

@huizendveld #KanDDDinsky 📊 Key Results The metrics that inform us   that we have achieved the objective

Slide 12

Slide 12 text

@huizendveld #KanDDDinsky OKRHMs

Slide 13

Slide 13 text

@huizendveld #KanDDDinsky ❤🩹 Health Metrics The metrics that tell us that we are sacri fi cing important assets in the process of achieving the objective

Slide 14

Slide 14 text

@huizendveld #KanDDDinsky You can mess up trying to achieve your goals many times,   But you can mess up your health only once.

Slide 15

Slide 15 text

Finish the Phoenix Project

Slide 16

Slide 16 text

@huizendveld #KanDDDinsky Finish the Phoenix Project Ob j e c t ives ar e ab out o ut c o m e, no t o ut pu t

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

Catapult ourselves into the market for everyday items

Slide 19

Slide 19 text

@huizendveld #KanDDDinsky 📊 Key Results ✓💶 Revenue €100K within 30 days after launch ✓👉 15% of customers refer friends & family ✓⭐ 250 ≥ reviews of which 80% is 4 out of 5 stars

Slide 20

Slide 20 text

@huizendveld #KanDDDinsky ❤🩹 Health Metrics ✓😃 Team happiness stable at 3 out of 3 ✓👉 Cost of acquisition below average order pro fi t ✓⚖ Cash fl ow in ≥ Cash fl ow out

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

@huizendveld #KanDDDinsky Sim pl e v is u al si gna l s Be t ran s par en t , se nd t o an y on e in t er e s t e d

Slide 23

Slide 23 text

@huizendveld #KanDDDinsky I 😍 OKRs when done right

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

@huizendveld #KanDDDinsky 🤯 Ehm…

Slide 26

Slide 26 text

No content

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

@huizendveld #KanDDDinsky Looking at the same thing from multiple angles will yield valuable insights

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

@huizendveld #KanDDDinsky Stories are a bad format to gain situational awareness

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

@huizendveld #KanDDDinsky Tell me, you have to go somewhere:     What are the fi rst apps you open on your smartphone?

Slide 33

Slide 33 text

These apps provide situational awareness

Slide 34

Slide 34 text

No content

Slide 35

Slide 35 text

Visibility Close to user Far away from user Component Pipeline Anchor Lazy Person Consume Everyday Items Urgency Shoppy Floppy   Offering Catalog Everyday Items Line of the present Pricing Suppliers Needs

Slide 36

Slide 36 text

Doctrine Principle   Know Your Users

Slide 37

Slide 37 text

Doctrine Principle   Focus on User Need

Slide 38

Slide 38 text

Slide 39

Slide 39 text

Doctrine Principle   Everything Evolves

Slide 40

Slide 40 text

Slide 41

Slide 41 text

Slide 42

Slide 42 text

Slide 43

Slide 43 text

@huizendveld #KanDDDinsky How to make a map ✓Identify the user (the anchor of the map) ✓List the relevant needs of that user below ✓Ask “what component is needed?” in order to satisfy that user need ✓Put components on the axis of evolution ✓Everything evolves: genesis > custom build > product > commodity

Slide 44

Slide 44 text

@huizendveld #KanDDDinsky Wardley Mapping our ecosystem ✓By mapping we make assumptions explicit ✓Maps make it easier to challenge the strategy ✓Maps allow us to ask: “Why here over there?” ✓Di ff erent areas of the map need di ff erent skills and attitudes ✓Trace the value chain to understand risk and impact on the end user

Slide 45

Slide 45 text

@huizendveld #KanDDDinsky Great! Maps. But what about our OKRs?

Slide 46

Slide 46 text

Visibility Genesis Custom Build Product (+ rental) Commodity (+ utility) 2020 Lazy Person Consume Everyday Items Urgency Shoppy Floppy   Offering Catalog Everyday Items Pricing Suppliers Shoppy Floppy Catapult into market High Average   Order Value Perception of Value Price Communication Strikethrough pricing Component Pipeline Anchor Line of the present Needs Line of the future Future component

Slide 47

Slide 47 text

Slide 48

Slide 48 text

Visibility Genesis Custom Build Product (+ rental) Commodity (+ utility) 2020 Component Pipeline Anchor Lazy Person Consume Everyday Items Urgency Shoppy Floppy   Offering Catalog Everyday Items Line of the present Pricing Suppliers Needs Shoppy Floppy Catapult into market High Average   Order Value Perception of Value Price Communication Strikethrough pricing Line of the future Future component Novel Divergent Convergent Accepted

Slide 49

Slide 49 text

@huizendveld #KanDDDinsky OKRs and Wardley Maps ✓⚓ Departments/tribes/teams can be an anchor on the map ✓🎯 The objectives can be the needs of the anchor ✓⭕ They hypothesis can be a set of components (within a pipeline)

Slide 50

Slide 50 text

@huizendveld #KanDDDinsky OKRs and Wardley Maps ✓➡ As proof accumulates to support our hypothesis it will move to the   right of the map ✓🚧 We can visualize the inertia that we experience to achieve our goals ✓👀 The map is a vehicle to point out organizational bias

Slide 51

Slide 51 text

@huizendveld #KanDDDinsky “Don’t take what everyone says at the conference at face value”   – Dennis Doomen

Slide 52

Slide 52 text

No content

Slide 53

Slide 53 text

@huizendveld #KanDDDinsky 🤷 How does this relate to DDD?

Slide 54

Slide 54 text

Mapping will help us   Mapping will help us   build up a common language

Slide 55

Slide 55 text

Mapping will help us   Mapping will help us   think in abstractions

Slide 56

Slide 56 text

Mapping will help us   Mapping will help us   focus on user needs

Slide 57

Slide 57 text

Mapping will help us   Mapping will help us   di ff erentiate our approach

Slide 58

Slide 58 text

@huizendveld #KanDDDinsky Looking back and into the future

Slide 59

Slide 59 text

@huizendveld #KanDDDinsky OKRs work when ✓⚖ Frequently evaluated ✓🌙 Objective should inspire and aim for the moon ✓🧮 Key Results are measurable and indicate success ✓🛣 It is clear why we have chosen to pursue this objective over all   other possible things that could have been done

Slide 60

Slide 60 text

@huizendveld #KanDDDinsky Combine OKRs with Maps to ✓🗺 Articulate business- and technical strategy into a single picture ✓⛏ Uncover assumption below decisions ✓✋ Make it easier for people to challenge ✓🗣 Unify language between tech teams and stakeholders ✓📣 Share knowledge within the organization

Slide 61

Slide 61 text

No content

Slide 62

Slide 62 text

Feel free to reach out during or after the conference :-)   marijn@huizendveld.com @huizendveld Marijn Huizendveld B.V. Anthony Fokkerweg 3 - 1059 CM Amsterdam - The Netherlands Eager to learn more?