Practical Strategy: How to relate your OKRs to your technical real-estate
summary
Claims that OKRs map onto technical constraints using a Wardley Map and a cadence of status emails to avoid “set and forget” practices. Shows concrete KRs — revenue 1.2M in 30 days, 15% referrals, 250 reviews with 80% ≥4 stars — plus health metrics like team happiness 3/3, CAC ≤ average order profit, cashflow in > out. Visualizes hypotheses tied to specific microservices, moves hypotheses along evolution (Genesis → Commodity), and surfaces inertia and misplaced 17‑sheet strategy decks as actionable mismatches.
AI-written summary · about
chapters (24)
- 0:00OKRs and technical real-estate
- 3:13Strategy in software teams
- 6:03Defining strategy and environment
- 7:10Understanding OKRs
- 9:20Focus on outcomes not outputs
- 10:22Case study: grocery delivery OKRs
- 12:09OKR pitfalls and health metrics
- 13:56OKR cadence and ambition
- 16:25Team autonomy and goal alignment
- 17:54Status emails for OKR focus
- 20:24Traditional strategy challenges
- 21:26Why stories fail and maps succeed
- 22:52Maps for situational awareness
- 24:58Wardley Mapping principles
- 25:41User needs and value chains
- 27:30Product evolution stages
- 30:19Strategic questions with Wardley Maps
- 32:27Creating a Wardley Map step-by-step
- 34:36OKRs and Wardley Maps combined
- 36:02Visualizing progress and inertia
- 38:27Mapping OKRs to systems example
- 39:53Mapping improves design and communication
- 40:38OKRs with Wardley Maps in practice
- 42:02Conclusion and resources
related talks
48mHow to relate your OKRs to your technical real-estate
43mHow to Relate OKRs to Your Technical Real-Estate
42mHow to relate your OKRs to your technical real-estate
34mDesigning effective OKRs
19mLessons in addressing data challenges while using OKRs
46mOKRs beyond Business KPIs
40mMaking OKRs and Scrum work together: an Agile Management guide
31mBe Fearless: achieve your goals with OKRs