Effective backlog prioritisation for company happiness
summary
Argues prioritisation succeeds when product time is guarded and decisions tie to measurable outcomes: use email bankruptcy and schedule pruning to free white space, set one priority per day, collect feedback with analytics, interviews, NPS and EVO workshops, define quarter goals and OKRs, and run A/B test 2–3 variants to validate. Uses Kano, cost‑value and a pain‑slider to order backlog, keeps a quarter checklist (strategy → kickoff → OKRs → retrospectives), and advises short planning or PO-driven plans if planning stalls.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:32Product owner role
- 6:22Time management
- 8:14Feedback and strategy
- 10:44Team engagement
- 13:13Goal evaluation
- 15:43Backlog prioritization
- 17:52Q&A
related talks
28mIntegrate and Conquer: The Power of a Unified Backlog
33mPrioritizing Effectively and Forming a Product Vision
43mBacklogs – the good the bad and the ugly
32mLearning from industry: Product Management practices for the win
57mEveryone Can Agree With This Approach To Prioritization
50mFree your mind and the rest will follow - delete your backlog
44mOutcome-based Product Planning
33mAligning Goals & Processes between Engineering & Product