Side Quest

Product Prioritization Simulator

Which bet gets the time, once customer, competitive, and commercial signals disagree?

The problem

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.

My contribution

I keep hitting this gap in the field.

One example

A scoring sheet for a handful of bets using feedback, revenue context, and effort. This version tests: Does making tradeoffs visible change which bet gets resourced?

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.
What it produces
A decision record. Not an automatic roadmap.
Request a walkthrough
Workflow and next steps
Inputs → review → output
A short list of bets → write impact, confidence, and effort → a decision record.
Planned next
A scoring sheet. Not an automatic roadmap.
Technologies in this repo or a linked project
None.

Metric to test

The test is whether writing impact, confidence, and effort changes which bet gets the time.

How it works

Project overview

Concept. Not a completed design and not software. It sits with GTM workflow design as a note, not a tool.

This page. I have not scored a bet in software.

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

Implementation notes

Proposed architecture. The technology section identifies what each project uses today.

Manual inputs first · Later: APIs from feedback and revenue systems

Bet · Score · Assumption · Decision

Workflow outline and requirements.

Goals

  • Score a small set of bets on impact, confidence, and effort.

Out of scope

  • An automated roadmap.
  • A substitute for product judgment.

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.

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.

Explore related work

Back to all projects