Embedding Discovery & Delivery in the Same Workflow
summary
Playbook formalizes five steps: problem understanding, solution exploration, product & tech delivery, then a required post-launch analysis and iteration until a “loveable product.” Developers join discovery (workshops, prototypes, Hotjar session replays) and squads own the whole flow. Prioritization uses RICE and tribe missions; product teams log one user conversation a week and feed Productboard. Roadmaps reserve 70% planned 30% flex, release plans replace fixed dates, and external timelines stay intentionally vague.
AI-written summary · about
chapters (7)
related talks
22mUsing Playbooks to Drive Innovation
52mShifting into continuous delivery
33mAligning Goals & Processes between Engineering & Product
20mIn the loop but out of the hierarchy
41mA tech leader's playbook: Galvanising product & tech organisations to deliver repeated success
19mGrow a Design team in a Non-Design-Driven Environment
48mLess Process, more Guidance with a Team Playbook
22mOptimizing Product Development: Balancing Speed, Quality, and Process