Product Prioritization Simulator
Which bet gets the time, once customer, competitive, and commercial signals disagree?
- Who uses it
- A planning conversation before someone commits build time.
- Decision it enables
- What we will resource, and which assumption we are willing to be wrong about.
- Working today
- This page. I have not scored a bet in software.
Workflow and next steps
- Inputs → review → output
- A short list of bets → write impact, confidence, and effort → a decision record. Not built.
- Planned next
- A scoring sheet. Not an automatic roadmap.
- Technologies in this repo or a linked project
- None.
Where it stands
Concept. Not a completed design and not software. It sits with GTM workflow design as a note, not a tool.
My role
I keep hitting this gap in the field. I have not designed the simulator past this note.
Metric to test
No metric. I am not presenting this as a product.
Links
No public demo or repository beyond this page.
How it works
The problem I kept seeing
Teams struggle to prioritize what matters when customer, competitive, and commercial signals sit in different places.
Decide is the gap between discovering a theme and building the wrong thing.
Without a repeatable answer: Loudest request wins. Revenue, effort, and strategic fit stay implicit.
What I was working from
Release, feedback, and competitive systems only pay off if someone can decide. Field cycles already force implicit prioritization; the simulator makes it inspectable.
Workflow
Inputs from Discover → Scoring → Tradeoff view → Decision record
In plain language
Inputs → Scoring → Comparison → Decision record
Described stack — not what this repository runs
Names below are a sketch. They are not completed integrations unless the technology section says Built with.
Manual inputs first · Later: APIs from feedback and revenue systems
Bet · Score · Assumption · Decision
Next. Not started as software.
Goals
- Score a small set of bets on impact, confidence, and effort.
Out of scope
- An automated roadmap.
- A substitute for product judgment.
Smallest version
A scoring sheet for a handful of bets using feedback, revenue context, and effort.
Question that version tests: Does making tradeoffs visible change which bet gets resourced?
Metrics I would watch
These are not results unless the section above says they are on record.
- Faster decision records
- Use in planning
- Hypothesis: fewer builds disconnected from commercial evidence
If prioritization is explicit, the company should waste less build time on low-confidence bets. Next — not built.
Tradeoffs
- Simple scoring over a model that hides the judgment.
What I would build next
- Wire inputs from feedback and competitive systems once those MVPs exist.