lockstep
5 min readNaman Jain

Product decision-making frameworks: 6 that teams actually use

Six product decision-making frameworks compared: one-way and two-way doors, DACI, RAPID, RICE, decision matrices, and decision logs, with when to use each.

Most product teams don't lack frameworks. They lack a sense of which one fits the decision in front of them. A two-line copy change gets a DACI document and three meetings; a pricing change that's hard to reverse gets decided in a Slack thread on Friday afternoon.

The useful frameworks answer three different questions: how much process does this decision deserve, who decides, and how do we compare the options? A fourth practice keeps the answer once it exists. This guide covers six, from their original sources, checked on 16 November 2026.

The short answer

FrameworkAnswersUse when
One-way and two-way doorsHow much process does this need?Every decision, as a first filter
DACIWho decides?Cross-team decisions with real disagreement
RAPIDWho decides, and who can veto?Decisions that need formal sign-off, such as legal
RICEWhich option or project first?Prioritizing a list of ideas
Decision matrixWhich option best fits our criteria?Choosing between a few options on several criteria
Decision logWhat did we decide, and why?After every decision that constrains future work

1. One-way and two-way doors: how much process

In his 2015 letter to Amazon shareholders, Jeff Bezos split decisions into two types. Type 1 decisions are consequential and irreversible or nearly so, one-way doors, and should be made methodically and with consultation. Type 2 decisions are reversible, two-way doors, and should be made quickly by high-judgment individuals or small groups. His warning: as organizations grow, they tend to use the heavy Type 1 process for most decisions, which leads to slowness and too little experimentation.

Use it first, on every decision. It tells you whether the rest of this list applies at all. A reversible copy change needs an owner and a log entry, not a framework.

2. DACI: who decides

DACI assigns four roles to one decision: a Driver who gets it made, a single Approver who makes the call, Contributors who give input without a vote, and Informed people who need the outcome. Atlassian's DACI play stresses exactly one Approver.

Use it for one-way doors that cross teams, where opinions differ and nobody is sure who has the final say. See the DACI template and RACI vs DACI.

3. RAPID: who decides, and who can block

Bain's RAPID names five roles: Recommend, Agree, Input, Decide, and Perform. The Recommend role leads the process and proposes options; Input provides data and judgment without a veto. The distinctive role is Agree: someone whose sign-off is required, such as legal or security.

Use it when a decision needs formal approval from a function beyond the decision-maker. Otherwise DACI is lighter.

4. RICE: which project first

RICE, introduced by Sean McBride at Intercom, scores ideas so you can compare them consistently:

  • Reach: people or events affected in a time period, such as customers per quarter
  • Impact: 3 massive, 2 high, 1 medium, 0.5 low, 0.25 minimal
  • Confidence: 100% high, 80% medium, 50% low
  • Effort: person-months

Score = (Reach × Impact × Confidence) ÷ Effort.

Use it for roadmap prioritization across many ideas. It's weak for a single strategic choice, where the factors are hard to estimate.

5. Decision matrix: which option fits best

A decision matrix scores a few options against weighted criteria, such as cost, time to ship, and risk, and adds the weighted scores. Its real value is making disagreement specific: you argue about one weight or one score, not about the whole decision.

Use it to choose between two to five options on several criteria. Treat close totals as ties.

6. Decision log: what we decided

None of the frameworks above records the outcome. A decision log does: the decision, the reason, the options rejected, the owner, and the date. It's what stops a team from reopening the same question in three months, and what tells a new engineer, or an AI coding agent, why things are the way they are.

Use it after every decision that constrains future work, including two-way doors. See the decision log template.

Putting them together

A practical flow for a product team:

  1. Classify the decision: one-way or two-way door?
  2. Two-way door: the owner decides now and logs it in one line.
  3. One-way door: assign roles with DACI (or RAPID if sign-off is required), compare options with a decision matrix or RICE, then the Approver decides.
  4. Either way: log the decision and make sure it reaches the people building against it.

Where Lockstep fits

Lockstep handles step four. It captures decisions from PRDs, Slack threads, and pull requests, routes each to its owner for one-click approval, and briefs the engineers and AI coding agents who build against it, so a one-way door decided in a meeting doesn't get walked back by a session that never heard about it. When a decision changes, the new version replaces the old one.

See Lockstep for product teams.

Sources checked 16 November 2026

For how to use AI agents in product work, see how to use AI agents as a product manager. To compare decision log tools, see the best decision log tools for product and engineering teams. For pitching an idea in one page, see the product one-pager template. For laying out the result over time, see the product roadmap template. For setting quarterly goals, see the OKR template. For weighing uncertain outcomes, see the decision tree template.

Frequently asked questions

What is the best decision-making framework for product managers?
There isn't one. Pick by the job: one-way and two-way doors to decide how much process a decision needs, DACI or RAPID to decide who makes the call, RICE or a decision matrix to compare options, and a decision log to record the outcome. Most decisions need only one or two of these.
What are one-way and two-way door decisions?
Jeff Bezos's 2015 Amazon shareholder letter describes Type 1 decisions as irreversible or nearly irreversible one-way doors that deserve careful, slow deliberation, and Type 2 decisions as reversible two-way doors that should be made quickly by individuals or small groups. He warns large organizations against using the heavy process for every decision.
What is the RICE framework?
A prioritization score from Intercom: Reach times Impact times Confidence, divided by Effort. Reach is people affected in a period, Impact uses a scale from 0.25 to 3, Confidence is a percentage, and Effort is person-months.
What is the difference between DACI and RAPID?
Both assign roles for a decision. DACI uses Driver, Approver, Contributors, and Informed. Bain's RAPID uses Recommend, Agree, Input, Decide, and Perform, and adds an Agree role with a veto, useful when legal or compliance must sign off.
How do I make product decisions stick?
Record each decision with its owner, reason, rejected options, and date, and make sure it reaches the people and AI coding agents building against it. Decisions that live only in a meeting or a Slack thread get reopened or quietly ignored.

Keep reading