Achieving Aligned Autonomy in Product Development with Inceptions
summary
Practical guide to running multi-day inceptions (typically 2–4 days) that produce a shared backlog and “aligned autonomy”: preparation requirements (customer journeys, user flows, validated technical/product artifacts), workshop activities (Jeff Patton style story mapping and slicing), facilitation rules (parking‑lot etiquette, right stakeholders in the room), and metrics of success — teams walk out with a prioritized set of stories and examples from 20 remote inceptions run in 2020.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:32Living Values
- 1:19Reflection
- 1:45Product Kickoff
- 2:19What is an Inception
- 2:43Aligned Autonomy
- 3:06Learning Objectives
- 3:21Three Questions
- 4:32Communication
- 5:12Inception
- 8:00Preparation
- 9:28Customer Journey
- 10:57User Flow
- 11:36Three Problems
- 12:01Story Mapping
- 12:38Slicing
- 13:00Story Map
- 13:53Building Fluency
- 15:47Questions
related talks
20mInception: Wasting Time or Investing It?
49mAll Aboard: Tools and Tactics for Building Team Consensus.
48mBuilding a Product and Engineering Relationship that Works
33mAligning Goals & Processes between Engineering & Product
29mDriving clarity in ambiguous projects
24mFrom Startup to Scale Up Designing for Growth from Day One
22mOptimizing Product Development: Balancing Speed, Quality, and Process
28mJourney from Design Afterthought to Design First