Compare product ideas
Roadmaps fill with objects. Argumont compares the underlying bets: who is in pain, what evidence exists, and what else you cannot ship.
decision
Put the roadmap item on trial
Product decisions fail when a preferred feature is treated as the destination. Argumont asks whether the underlying user problem is better solved by a different scope, sequence, or refusal to build.
What this decision type is
A product decision is a choice among scopes: build this, build a thinner version, buy a component, or do nothing and measure. 'Users will love it' is not an option. It is an unverified prediction.
Argumont is useful when two teams already disagree, and when they do not yet know they should disagree.
Common mistakes
Prioritization by volume of requests can overfit to the currently vocal cohort. Quiet, high-value users may need the opposite change.
Another mistake is scoring designs on completeness. A smaller release that learns faster can beat a complete design that ships late.
What evidence matters
Observed behavior, support transcripts, willingness to pay for the specific change, engineering cost ranges, and opportunity cost of delay. Mockups are not evidence of demand.
Customer interviews can be strong when they are recent and specific. They remain user-confirmed or unverified until behavior matches the quotes.
How Argumont evaluates it
The advocate defends the proposed item. The challenger attacks load-bearing assumptions. The alternative builder must offer a path that is not a cosmetic rename of the original spec.
The verdict should say what the original idea got right, even if it loses. That is a product rule, not a courtesy.
Example criteria
Problem severity
How costly the current pain is for a real buyer or user.
Evidence of demand
Behavior and commitments, not compliments.
Time to learning
How fast the option produces a signal you can trust.
Build cost
Engineering, design, and ongoing operations.
Opportunity cost
What else cannot ship if this wins.
Reversibility
Whether a bad call can be undone without scarring the product.
Common risks
Roadmap theater
The decision is used to end debate rather than to test it.
Scope creep as compromise
Two losing ideas are merged into a larger, weaker one.
Example decision
Should we build in-app reporting this quarter, ship a CSV export, or wait for usage data from the new workflow? The analysis should treat delay as a real option with its own risks.
Related pages
Should we launch?
Teams treat launch as a ceremony. The decision is whether this product, in this form, is the best use of scarce attention versus killing it, narrowing it, or wa...
Product managers
Product managers already live in tradeoffs. What they often lack is a durable record of why a bet won after the Slack thread is gone. Argumont stores options, c...
Claim analysis
Most strategy documents mix five kinds of statement. Argumont labels them so an assumption cannot survive as a fact because it was formatted in bold.
Decisions
These pages are not a directory of keywords. Each one describes a kind of choice, the evidence it needs, how Argumont scores it, and where to go next.
Challenge this product bet
Argumont challenges assumptions, researches evidence, compares competing approaches, and identifies the strongest decision.
Challenge this product bet