PRODUCT DECISIONS
Make product choices compete for the roadmap.
Product teams rarely suffer from a shortage of ideas. The harder problem is determining which idea deserves resources.
Compare competing product directions.
Argumont can examine features, product concepts, pricing changes, platform investments, launch strategies, and roadmap priorities against explicit criteria.
Expose assumptions before development.
The analysis challenges assumptions about customer demand, implementation effort, differentiation, adoption, revenue impact, operational complexity, and strategic fit.
Find the stronger alternative.
When the original choice is unnecessarily narrow, the Strategist can introduce an executable path and require it to compete on the same record.
How the method applies
The Decision names the user problem before the spec. The Champion defends the proposed item. The Challenger attacks demand and opportunity cost. Inspector keeps interview compliments from looking like purchase. The Judge explains what the original idea got right even if it loses.
Completeness is not a strategy
Completeness is not a strategy. A mockup is not evidence of demand.
Champion and Challenger test the case, Inspector checks the evidence, and Judge records the Verdict for the Decision Owner.
Example product Decision
Ship the platform rewrite, ship the wedge feature that a named buyer asked for, or wait a quarter. The Champion defends the rewrite. The Challenger attacks opportunity cost. Interview compliments stay opinions until someone who can pay repeats them.
Bring Argumont a Decision worth challenging.
Structure the question, test the evidence and the assumptions, and preserve what your organization ultimately decides.
Start a Product Decision