Win on repeated judgment.
Best when the audience has frequent, language-heavy work and trusts the system with enough context to act.
A product hypothesis workbench
Compare what a domain could become with the same visible assumptions. Rank directions, expose friction, and choose what to test before you commit.
Use assumptions, not aura.
Apply one market view across all concepts.
Relative fit under your current assumptions, not a forecast.
Best when the audience has frequent, language-heavy work and trusts the system with enough context to act.
Best when a narrow team owns a costly process and will pay for reliability, records, and coordination.
Best when the pain is acute enough to justify regulatory work, security review, and careful distribution.
Use this lane to challenge the obvious categories with a more specific audience, transaction, or service model.
Evidence before confidence.
Generated from the selected direction and current risk profile. Check off completed work and record what changed your mind.
Change seats before deciding.
Turn the ranking into a conversation.