Prioritized work means that at any given moment, the team is working on the most valuable thing they could be working on. Simple concept, hard execution.
The core challenge: everything feels urgent and important. Stakeholders all believe their feature should be next. Without disciplined prioritization, teams either work on whateverâs loudest or try to do everything at once (which means nothing gets done well).
Prioritization techniques:
- MoSCoW â Must have, Should have, Could have, Wonât have. Simple and effective for categorizing requirements.
- WSJF (Weighted Shortest Job First) â prioritize by cost of delay divided by job size. Things that are valuable, time-sensitive, and small get done first.
- Value vs. Effort matrix â plot items on a 2x2 grid. High value, low effort = do first. Low value, high effort = do last (or never).
- Kano Model â categorize features as basic (expected), performance (more is better), or excitement (unexpected delighters). Helps balance different types of value.
- Stack ranking â force a strict order. No ties allowed. This is politically painful but creates absolute clarity.
Key principles:
- Say no often â the power of prioritization is in what you choose not to do. Every yes is an implicit no to something else.
- Revisit regularly â priorities change as you learn more. What was critical last month might be irrelevant today.
- Make it visible â everyone should be able to see the prioritized backlog. Transparency reduces politics.
- One priority at a time â multitasking is an illusion. Focus on finishing one thing before starting the next.