Product bets, with the tradeoffs in view.

Bring discovery, data and stakeholder views together before you commit a roadmap slot, a launch or a price, name what success looks like, and keep the reasoning for when the results come in.

How it fits

Problem framing

Frame the bet: the customer problem, who has it and why it matters now.

Evidence and options

Link the research and data to the options they support, including not doing it, and compare them on value, effort and risk.

Stakeholder challenge

Let engineering, sales, support and AI challenge the assumptions and the evidence behind each option.

Commitment and success measure

Record the call, who made it, how reversible it is and what result would show it worked.

Results review

Come back to the decision when results arrive and compare them with what was assumed at the time.

Questions

Where does the evidence go?

Attach research notes, reports and links to the options they support, so each piece of evidence sits next to the claim it backs.

Can stakeholders follow without editing?

Yes. Invite them as viewers to follow along, or as editors when you want their arguments in the record.

What happens after we commit?

Add actions for the follow-up, such as reviewing the results, and come back to the decision when they arrive.

Does it replace our roadmap tool?

No. prorso holds why a bet was made; your roadmap tool holds when it ships.

Explore example decisions · Read articles

prorso for other teams: Procurement · Software architecture · Finance & investment · People & HR · Operations & supply chain · Projects & PMO · IT, security & risk · Strategy & governance