Prioritising development.
WHAT COMPETES FOR ATTENTION
Customer requests Defects Technical debt Sales requirements Your own ideas
WHAT TO ESTABLISH
A way of deciding that is not simply whoever asked most recently.
WHAT TO CONSIDER PER ITEM
How many customers it affects Whether it prevents work Whether it affects retention or acquisition What it costs to build and to maintain
WHY MAINTENANCE COST MATTERS
Every feature is supported and tested forever.
WHAT TO ASK ABOUT ANY REQUEST
What are you trying to achieve?
WHY
Customers request solutions; the underlying need is frequently better served another way.
WHAT TO WEIGH HEAVILY
Anything blocking customers from reaching value Anything causing cancellations Anything several customers raised independently
WHAT TO WEIGH LIGHTLY
Requests from prospects who have not bought Features competitors have Anything you want to build for its own sake
WHAT TO SAY NO TO
Requests serving one customer at everyone's expense.
HOW TO SAY IT
Plainly, with the reason.
WHY PLAINLY
Vague deferral produces repeated asking and eventual resentment.
WHAT TO KEEP
A record of what was declined and why.
