Overview

Prioritize a list of initiatives, features, or tasks using the simple but effective Could Do / Should Do / Must Do framework. This template gives teams a fast, collaborative way to separate urgent necessities from important-but-optional work — without the overhead of scoring matrices or multi-day planning sessions.

Key Features

• Three-bucket layout: Could Do, Should Do, Must Do
• Item capture zone for listing all candidates before sorting
• Team voting mechanism for disputed prioritization decisions
• Capacity constraint field for anchoring decisions in reality
• Summary section for the agreed Must Do list with owners

How to Use

1. Start by adding all candidate items to the unsorted zone using sticky notes and the Quick Actions widget — don't evaluate yet, just capture
2. As a team, sort each item into Could Do, Should Do, or Must Do by dragging sticky notes into the appropriate bucket
3. For disputed items, use dot voting to let the team decide democratically — ties go to whoever owns delivery accountability
4. Review the Must Do bucket against capacity — if it exceeds what the team can realistically do, items move down to Should Do
5. Finalize the Must Do list in the summary section with owners and rough timelines

Benefits

Most prioritization debates are really capacity debates in disguise. Must Do / Should Do / Could Do forces the team to make the capacity constraint explicit — so decisions are grounded in reality, not optimism.