Feature Prioritisation Frameworks

A defensible ranking of competing ideas: agreed criteria and decision rights, honest reach, impact, confidence and effort scores, a monthly re-score and trade-offs explained openly.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Feature Prioritisation Frameworks, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

201

Starter tasks

🧩 Product Management

Feature Prioritisation Frameworks

Ranking competing ideas with explicit criteria such as reach, impact, confidence and effort, and explaining trade-offs openly to stakeholders.

  1. Single list of every competing idea
  2. Decision rights for the final ranking call
  3. Agreed prioritisation criteria and weights
  4. Choosing a prioritisation framework that fits
  5. Impact scale tied to one business goal
  6. Reach estimates grounded in usage data
  7. Effort sizing scale agreed with engineering
  8. Confidence rubric with evidence levels
  9. Shared scoring sheet for the idea list
  10. First full scoring pass on the top 30 ideas
  11. Intake form for new ideas with minimum fields
  12. Monthly re-scoring of the top twenty
  13. Prioritisation decision log
  14. Quarterly capacity split across work types
  15. Weekly interrupt review against the ranked list
  16. Monthly ranking readout for stakeholders
  17. Predicted versus actual impact check after launch
  18. Quarterly pruning of parked ideas
  19. Effort re-check before work is committed
  20. RICE scoring practice on past decisions
  21. Kano survey to sort must-haves from delighters
  22. Cost of delay for time-sensitive work
  23. MoSCoW sort for a fixed-date release
  24. Importance versus satisfaction opportunity scoring
  25. Spotting bias in prioritisation discussions
  26. Running a value versus effort mapping session
  27. Buy a feature exercise with customers
  28. Two frameworks tested on the same 15 ideas
  29. Strategic fit weighting in the scoring model
  30. Ranking technical debt against features
  31. Written decline note for requests not prioritised
  32. Tie-break rules for equally scored ideas
  33. Scoring sales-requested features with deal evidence
  34. Dependency check before final sequencing
  35. Prioritisation tool or spreadsheet decision
  36. Fast lane for small requests under two days
  37. Quarterly prioritisation workshop with leads
  38. Annual planning ranking of candidate bets
  39. Reprioritisation after a plan-breaking event
  40. Explaining priorities to the board
  41. Audit of an inherited priority list
  42. Founder prioritising without a product team
  43. Prioritising before product-market fit
  44. Merging rankings across several product teams
  45. Prioritising with little or no usage data
  46. Reprioritising for a smaller team after cuts
  47. Platform team ranking of internal requests
  48. Ranges instead of point scores for big bets
  49. Pairwise comparison for the top ten candidates
  50. Prioritisation playbook for the whole product group

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Single list of every competing idea

Ideas for what to build usually live in five places at once: a sales spreadsheet, support tags, the founder's notes, old tickets and a whiteboard photo. Pulling them into one list with a single row per idea, a named source and a one-line problem statement is the precondition for ranking anything, because no framework can compare ideas it cannot see.

First tasks

  • List every place ideas currently live, including private notes and chat threads
  • Copy each idea into one sheet with source, requester and date
  • Merge duplicates and keep every requester's name on the surviving row
  • Rewrite each title as the customer problem it addresses

Decision rights for the final ranking call

Scoring arguments drag on when nobody knows who makes the final call, and the loudest voice ends up deciding by default. Writing down who proposes scores, who is consulted and who decides the ranking, before the first score is entered, turns later disagreements into input rather than vetoes.

First tasks

  • Write down who currently ends up making ranking calls in practice
  • Draft a note naming the proposer, the consulted parties and the final decider
  • Agree the escalation route for disputed rankings with your manager
  • Link the approved note at the top of the idea list

Agreed prioritisation criteria and weights

Without explicit criteria, every prioritisation meeting reopens the question of what matters. Agreeing three to five criteria, such as customer reach, revenue impact, strategic fit and effort, with a weight for each, gives the team a shared scale and turns a disputed ranking into a debate about inputs rather than taste.

First tasks

  • Pull this year's company and product goals onto one page
  • Propose three to five criteria that map to those goals
  • Run a 45-minute session to agree a weight for each criterion
  • Write a one-sentence definition for every criterion
  • Check the criteria and weights still match the company goals @recurring(yearly)

Make it yours.

Install Feature Prioritisation Frameworks, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.