Revitalizing a cross-functional product org.
summary
Revitalization finishes in nine months by doing specific things: map roles with Venn diagrams of responsibilities, require a narrative template and milestone gates (discovery complete, design complete, code complete, shipped), add test and deployment plans, enforce a post‑ship iteration slot, and run joint comms like office hours and a ticktock doc for who says what when. Results show higher velocity, clearer accountability, fewer handoff fights, and more shipped work that actually gets iterated on.
AI-written summary · about
chapters (9)
- 0:00Start
- 12:57Create living product documents and processes
- 27:56Practice difficult conversations
- 28:51Create an environment to roleplay those conversations
- 29:39Find a great conflict mediator
- 30:53Mindful communication is magical
- 32:37Consider the room's power dynamics
- 33:40Meet transparency with responsibility
- 36:23Disjointed things happen in siloed teams
related talks
25mDelivering the Feeling of ‘Release First’: Approaches to Spark Change in Stagnating Teams
52mShifting into continuous delivery
21mWhy Do Well-Intentioned Efforts Fade? — How Retrospectives Became Decisions That Change Structures Over Six Months
22mOptimizing Product Development: Balancing Speed, Quality, and Process
22mEvolving DevOps Teams and Flexible Organizational Culture
52mToo many cooks! Supporting augmented teams without getting salty
33mCreating a culture of continuous improvement
31mTransitioning from Project to Product: An Experience Report