How to Relate OKRs to Your Technical Real-Estate
summary
Claims that linking Objectives & Key Results to a visual Wardley map surfaces the technical constraints blocking goals and shifts work from output to outcome. Uses Wardley Maps and OKRs, shows a 17‑slide strategy deck turned into a map, links a €100,000‑in‑30‑days key result and a 15% referral KR to specific systems (a custom pricing service proves too risky), and introduces a weekly status email to avoid “set and forget.” Produces actionable changes: move hypotheses right as proof accumulates, expose inertia, and decide whether to build or buy.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:38Implementing change in orgs
- 6:07Strategy and OKRs
- 10:01Crafting effective OKRs
- 14:16Common pitfalls with OKRs and solutions
- 19:59Status emails and resources
- 21:45Stories vs maps
- 24:13Wardley Maps intro
- 26:25Tech evolution and maps
- 29:56Wardley Map step-by-step
- 33:07OKRs with Wardley Maps
- 37:24Mapping assumptions and biases
- 39:12Mapping for design and comms
- 40:18Key takeaways
- 41:22Closing remarks
- 41:43Q&A
related talks
42mHow to relate your OKRs to your technical real-estate
48mHow to relate your OKRs to your technical real-estate
43mPractical Strategy: How to relate your OKRs to your technical real-estate
10mA motivating process for deriving Objectives and Key Results (OKRs)
46mOKRs beyond Business KPIs
34mDesigning effective OKRs
19mLessons in addressing data challenges while using OKRs
46mOKRs: Implementation Experience