How to relate your OKRs to your technical real-estate
summary
Argues that linking OKRs to a Wardley-style map surfaces the exact constraint blocking an objective, using concrete examples: a 3-month objective with 3–5 key results (e.g. €100k revenue in 30 days), a hypothesis tied to the pricing component, and a proposed UI change like strikethrough pricing. Introduces a weekly status email to report confidence and blockers. Maps show hypotheses moving right as proof accumulates, expose inertia, and in one client case prevent wasted work by predicting a doomed initiative.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:46Three levels of organizational effectiveness
- 5:19What strategy is and why it matters
- 6:24OKRs: objectives and key results
- 8:14Health metrics and OKR failures
- 11:32Status emails for transparency
- 16:51Strategy documents to worldly maps
- 18:58Why maps beat stories for strategy
- 19:39Wardley mapping principles
- 21:24Building a worldly map step by step
- 23:09Climatic patterns and market evolution
- 25:43Shopping floppy case study
- 27:29Mapping your ecosystem
- 29:15OKRs versus worldly maps
- 33:09Visualizing friction and inertia
- 34:35Mapping insights and lessons
- 36:00Mapping improves software design
- 37:05Key takeaways: OKRs and maps
- 38:08Q&A
related talks
48mHow to relate your OKRs to your technical real-estate
43mHow to Relate OKRs to Your Technical Real-Estate
43mPractical Strategy: How to relate your OKRs to your technical real-estate
34mDesigning effective OKRs
46mOKRs beyond Business KPIs
19mLessons in addressing data challenges while using OKRs
10mA motivating process for deriving Objectives and Key Results (OKRs)
39mReawakening Agile with OKRs