For teams
PMs need a record, not a louder meeting
A product manager rarely lacks ideas. What runs short is the honest comparison: what a feature is worth, what waiting for it costs, and what else stops while the team builds it. Those three numbers settle a roadmap far more often than the loudest request does.
Requests are a signal, not demand
Twelve customers asking for a feature tells you about twelve conversations, not about how many would pay, switch, or stay because of it. Ask the person bringing the request what changes if the feature never ships; the answer is usually smaller than the request.
Sales pressure deserves a place on the page as evidence, labeled by its source. A renewal at risk, backed by a letter, and a passing mention on a quarterly call should never carry the same weight.
Price the wait
Cost of delay is the value an item loses for each month it is not live. Divide it by the months it takes to build and you have a fair way to order the work: the most value per month of effort goes first. Teams that skip this step tend to build the largest item first, because size feels like importance.
The method needs only two estimates per item, and both are guesses at the start. Writing them down is what lets someone attack them.
The quieter rivals on a roadmap
Every roadmap item competes with a smaller first release, a manual workaround, buying a tool, or waiting until usage data arrives. The thin version often teaches the team, in a few weeks, what the full one would have taken a quarter to learn.
Retiring a feature is also a product decision. Sunsetting something used by a small, vocal group belongs in the same comparison as building something new.
A roadmap bet in a Decision Room
The full build, the thin release, and waiting each get their own Champion. The Challenger presses on the demand estimate, the number every ordering depends on. Craftsman tests whether the team can really ship the thin version in the time claimed. Diplomat maps who has to agree, from the sales lead to the support team that will answer the tickets.
The Verdict explains what the losing option got right, which is the part a stakeholder needs to hear when their item moves down.
Two features, one quarter
Feature A is worth an estimated $30,000 a month once live and takes three months to build. Feature B is worth $15,000 a month and takes one month. Build A first and the value lost while waiting comes to $150,000: three months without A, then four months without B. Build B first and the loss is $135,000: one month without B, then four without A. Value per month of effort (10 for A, 15 for B) points to B first and saves $15,000. Then the Challenger asks where A's $30,000 came from. If it rests on twelve sales requests and only four accounts would truly pay, A is worth nearer $10,000 a month and falls further down. The Verdict favors B now, with A's demand named as the claim to verify before the next quarter.
Questions
- Can I run a whole backlog through one Decision?
- Bring the few items competing for the same team and the same months, usually two to four. A backlog of forty needs triage first; the room is for the contested choice at the top of the list.
- What happens when an executive adds a must-have after the Verdict?
- Use Challenge the Verdict. An independent second pass takes the new item seriously and can overturn the first result, and both passes stay on the record.
- Who owns the roadmap call?
- The product manager or the team that owns the product. Their Human Decision is recorded separately from the Verdict, so a later reader can see where people chose differently and why.
Further reading
Bring Argumont a Decision worth challenging.
Start with a paid 60 day pilot on your own real Decisions.