Prioritization Quadrant
The Prioritization Quadrant helps teams balance different types of work, such as new features, support tickets, and technical debt, ensuring a holistic approach to product development. It visually represents priorities based on impact and effort, guiding teams to make informed decisions about resource allocation.
Use this method when you need to ensure that your team is not solely focused on new features and is also addressing other important aspects of the product or service, such as maintenance and support.
Solves: Imbalanced focus on new features at the expense of maintenance and support; neglecting technical debt.
- 1
Step 1: Draw a quadrant with axes representing 'Impact' (high/low) and 'Effort' (high/low). (5 min)
- 2
Step 2: Brainstorm all types of work items (new features, support tickets, technical debt) and write each on a separate sticky note. (10 min)
- 3
Step 3: As a team, discuss and place each sticky note in the appropriate quadrant based on its estimated impact and effort. (20 min)
- 4
Step 4: Prioritize work items based on their quadrant placement (e.g., high impact/low effort items are top priority). (15 min)
- 5
Step 5: Document the prioritized list and communicate it to the team.
- Encourage honest discussion about the impact and effort of each task.
- Ensure all team members have a chance to contribute to the placement of sticky notes.
- Use different criteria for the axes, such as 'Value' and 'Risk'.
- Weight the quadrants based on strategic goals.