James Stanier, Winter Wi, Janet Balneaves a panel discussion at LeadDev London 2023
summary
Panel lays out concrete practices: a trifecta decision model (product, design, engineering share equal voice), a public proposal–prototype–build workflow with asynchronous reviews, and mandatory decision logs that escalate to VPs in two to three weeks. Specifics include using intranet project pages, recorded demos, and merchant research; one estimate example goes from two months to one day; metric misuse drives bad behavior around velocity. Alignment produces predictable daily work; misalignment produces rework and delays.
AI-written summary · about
chapters (16)
- 0:00Panel introduction
- 1:50Myth: 'Just add a button'
- 3:12Trifecta collaboration model
- 5:17Project phases and decisions
- 8:46Alignment failures in projects
- 11:31Tools for disagreements
- 14:20What each discipline cares about most
- 17:04Strong opinions vs impact
- 18:07Myth: Product ignores code quality
- 19:31Myth: UX only wants perfect designs
- 20:34Myth: Engineers ignore product
- 21:39Worst engineering collab
- 23:05Worst product collab
- 24:48Engineers influencing product/UX
- 27:38Pitching technical debt
- 29:23Closing remarks
related talks
45mSW Design, Architecture & Clarity at Scale
32mPanel discussion: The journey to building effective engineering teams
30mBuilding Better Products Faster
45mBuilding and conveying vision
48mBuilding a Product and Engineering Relationship that Works
42mDecision-making for developers
31mHarmonizing Across Product & Engineering (Cross Team Collab)
50mLean Design in Practice