prioritization framework

A prioritization framework is an agreed way of deciding what to work on first. It makes the criteria explicit, so a decision can be explained, repeated and challenged instead of resting on whoever argues loudest.

Common frameworks and when they help:

• Critical path: find the few steps in a customer journey that must work for anyone to adopt the product. Good for a new product or an MVP.
• Kano model: sort features into basic expectations, performance attributes and delighters. Good for choosing enhancements by perceived value.
• Desirability, feasibility, viability: score each idea 1–3 on customer want, buildability and business value. Good for a short list.
• Value vs effort (ROI scorecard) and RICE: turn value, effort and confidence into one number per item. Good for long lists.
• Cost of delay / WSJF: add urgency when timing changes value, e.g. before a seasonal peak.
• MoSCoW: not a ranking method, but a clear way to communicate release scope once priorities are set.

Whatever the method, the value side should come from your strategy: customer needs and business objectives, not generic "importance". The effort side should include everyone's work (engineering, design, marketing, support), not just code.

Frameworks support decisions; they don't make them. Scores ignore dependencies, promised deadlines and intangibles such as learning or brand. Use the ranking to start the conversation, adjust the sequence for real-world constraints, and write down why.