Dates and deadlines...it's complicated
summary
Claims the common feature road map is a lie based on a failed migration where two chosen sites miss their launch and the customer renews their contract; proposes hypothesis road maps instead, tying hypotheses to company objectives and confidence levels. Uses a concrete example: onboarding hypothesis aims for a 6% lift toward a 10% activation goal, estimates 8 to 12 weeks, 20% confidence and promises an update in 3–5 days. Shows this method across companies and records improved alignment and fewer feature-factory behaviors.
AI-written summary · about
chapters (8)
- 0:00Intentional organization
- 1:06Failed launch deadline
- 2:29Unreliable feature road maps
- 3:53Process vs customer outcomes
- 4:37Hypothesis road maps
- 7:29Embracing uncertainty benefits
- 8:31Tips for clear deadines
- 10:41Never share dates without context
related talks
11mEstimates as probabilities
44mOutcome-based Product Planning
42mBuilding Powerful Roadmaps
44mHit the (ML) Road(map) Jack
47mBumpy 12 Months Road to Transform Team of Mercenaries Into Product Minded Team
34mFirst Principles in PMing: The Roadmap
09mThings You Wish You Shared With Your Team Before They Agreed on That Deadline
40mStars Aligned and Software Development Adrift - Why Can We Predict Planets but Not Deadlines?