Upgrade to Pro — share decks privately, control downloads, hide ads and more …

KanDDDinsky 2022: How to relate your OKRs to yo...

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

A recipe for collaborative product ownership: Finding solutions to business problems that are feasible and sustainable.

How do you translate an OKR back to a hypothesis that can be challenged by the various roles within a team? How do you ensure that the communication around initiatives is not hindered by conflicting terminology or by misinterpretation? In what ways can you involve business stakeholders in finding solutions that will help them understand the technical constraints that a team has to take into account? And how do you prevent tech teams building the wrong thing the right way?

Imagine:

a way to visualize and clarify to the relationships between OKRs, hypothesis and the underlying technical constraints within the technical real-estate;
a clear path from "user need" to the responsible "components";
having a common language to talk about problems in context, removing ambiguity and confusion in the process;
and finally a way to collaboratively dive into the nitty gritty detail of the current landscape and the proposed solution;

In this session Marijn Huizendveld will take you through the process of leveraging your existing OKRs to clarify what needs to be done to all stakeholders and members of a team.

Marijn Huizendveld

November 06, 2022
Tweet

More Decks by Marijn Huizendveld

Other Decks in Technology

Transcript

  1. @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.
  2. @huizendveld #KanDDDinsky 🎯 Objective A big goal the team is

    so thrilled about 
 it makes them jump out of bed each morning
  3. @huizendveld #KanDDDinsky ❤🩹 Health Metrics The metrics that tell us

    that we are sacri fi cing important assets in the process of achieving the objective
  4. @huizendveld #KanDDDinsky You can mess up trying to achieve your

    goals many times, 
 But you can mess up your health only once.
  5. @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
  6. @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
  7. @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
  8. @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
  9. @huizendveld #KanDDDinsky Tell me, you have to go somewhere: 


    
 What are the fi rst apps you open on your smartphone?
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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 HIV test Coffee Eggs Covid tests
  15. @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
  16. @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
  17. 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
  18. 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
  19. 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
  20. @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)
  21. @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
  22. @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
  23. @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
  24. Feel free to reach out during or after the conference

    :-) 
 [email protected] @huizendveld Marijn Huizendveld B.V. Anthony Fokkerweg 3 - 1059 CM Amsterdam - The Netherlands Eager to learn more?