How to Run Amazing Product Reviews - Alex Hood, Asana
•
1 like•203 views
Nearly all product organizations conduct product reviews with leaders. They can be amazing sources of coaching and innovation or they can be disheartening and confusing. How do you maximize the collaboration between PMs and leadership to produce better outcomes for customers? In this session, Alex Hood, Head of Product for Asana, will share the winning product review playbook for driving innovation, efficiency & engagement, including unpacking Asana's product toolkit for innovation throughout the product development journey.
Recommended
Recommended
More Related Content
More from Traction Conf
More from Traction Conf (20)
Recently uploaded
Recently uploaded (20)
How to Run Amazing Product Reviews - Alex Hood, Asana
- 1. Alex Hood Unpacking the Product Toolkit: How to Run Amazing Product Reviews
- 2. Goal: Velocity & Innovation
- 3. What have you seen go wrong at product reviews?
- 4. Product reviews can be fraught with lack of clarity
- 5. Clarity → Velocity & Innovation
- 6. Clarity on where the team is Clarity on expectations Clarity on fidelity Clarity on feedback and actions Clarity on leader’s role
- 7. Clarity on where the team is
- 9. D iscover→ D efine → Pains Solution Iteration D evelop → D eliver→ Discovery debrief Target customer and pain identified Solution kickoff Spec review Design review Launch review
- 18. Summary: _________ Vision Imagine moving from a world where… to a world where… Customer pain I am a _______ who is trying to _______, but _______ because _______, which makes me feel _______. Key elements of solution From: 1. _______ 2. _______ 3. _______ To: 1. _______ 2. _______ 3. _______ Our plan Key milestones and dates here, pasted timeline is OK. Metrics we’ll move Top metrics we think we’ll move. Baseline and target. Links to KRs are great.
- 19. Summary: Workload feature Vision Imagine moving from a world where… you are stressed because work is siloed, and you have no visibility into your team’s workload and worry about employee burnout and your important initiatives slipping through the cracks… to a world where… you have a window into your team's workload, where you can monitor and spot capacity issues, and rebalance work to prevent project delays. Customer pain I am a team lead who is trying to ensure work is distributed effectively across my team, but I don’t have visibility into overall workload because my tools are fragmented, which makes me feel worried about team burnout and stakeholder communication. Key elements of solution From: 1. Fragmented tools 2. Unclear team bandwidth 3. Inability to resolve capacity issues To: 1. A single source of truth for understanding workload 2. A clear picture of who is under or over allocated 3. A single place to easily rebalance work Our plan Launch: August 1 Metrics we’ll move Business tier adoption — Launch KR
- 20. D iscover→ D efine → Pains Solution Iteration D evelop → D eliver→ Discovery debrief Target customer and pain identified Solution kickoff Spec review Design review Launch review
- 21. Key questions → Discovery debrief Who are the various customer types and what are their pains? How do these customers solve pains today? What do competitors do well, what inspires us? What's the opportunity for differentiation / delight?
- 22. D iscover→ D efine → Pains Solution Iteration D evelop → D eliver→ Discovery debrief Target customer and pain identified Solution kickoff Spec review Design review Launch review
- 23. Key questions → Target customer & pain identified Who is the customer and what is their pain that we have chosen? What does this pain look like in practice? Which customers / pains did we decide not to pursue? What are your early thoughts on next steps?
- 24. D iscover→ D efine → Pains Solution Iteration D evelop → D eliver→ Discovery debrief Target customer and pain identified Solution kickoff Spec review Design review Launch review
- 25. Key questions → Solution kickoff What's your team's vision in one sentence? What's the ideal customer experience? (Assume you have a couple years and are not constrained by engineering resources) What's our best guess of what our v1 will include? What are the likely cross-functional high-level requirements? What's the likely positioning? (PMM)
- 26. D iscover→ D efine → Pains Solution Iteration D evelop → D eliver→ Discovery debrief Target customer and pain identified Solution kickoff Spec review Design review Launch review
- 27. Key questions → Spec review Are there any important or controversial principles worth discussing? What will we ship and in what order? What will it roughly look like? What are the most important risks and how do we mitigate them?
- 28. D iscover→ D efine → Pains Solution Iteration D evelop → D eliver→ Discovery debrief Target customer and pain identified Solution kickoff Spec review Design review Launch review
- 29. Key questions → Design review What have we learned that informs our design? What does the solution look like? What trade-offs or pitfalls exist in our solution? Did we invent a new pattern?
- 30. D iscover→ D efine → Pains Solution Iteration D evelop → D eliver→ Discovery debrief Target customer and pain identified Solution kickoff Spec review Design review Launch review
- 31. Key questions → Launch review What functionality are we launching today? Did we drop anything important from scope or quality? What’s our experimentation / evaluation approach? How well did we deliver on the benefits we are promising? Did we drop anything important from scope or quality? What’s the rollout plan? (PMM + PM)
- 32. D iscover→ D efine → Pains Solution Iteration D evelop → D eliver→ Discovery debrief Target customer and pain identified Solution kickoff Spec review Design review Launch review
- 35. Clarity on feedback and actions
- 36. Do Try Consider
- 38. Clarity on leader’s role
- 39. Process
- 42. Gardening
- 44. Inspiration
- 46. Clarity → Velocity & Innovation
- 47. D iscover→ D efine → Pains Solution Iteration D evelop → D eliver→ Discovery debrief Target customer and pain identified Solution kickoff Spec review Design review Launch review
- 51. Clarity on where the team is Clarity on expectations Clarity on fidelity Clarity on feedback and actions Clarity on leader’s role
- 52. Thank you!