Review Room

Decision Readiness

Product managers are paid for deciding under uncertainty. This room tells you whether a decision is actually ready.

Decision readiness
58%
Almost ready

One or two legs are thin. Resolve the lowest-scoring factor first.

Readiness is not confidence. It measures whether the team has done the preparation.
Evidence completeness
66 · weight 25%
1 quant · 2 qual · 0 recentpartial
Evidence is stale. Re-pull within the last two weeks.
Assumption validation
25 · weight 20%
5 stated · 5 untested · 0 contestedweak
5 assumptions still untested. Pick the most decisive and test it.
Risk visibility
70 · weight 15%
4 risks · 2 categoriesstrong
Risks cluster in one lens. Force at least one from another category.
Stakeholder alignment
46 · weight 20%
1 supportive · 2 need validation · 2 likely objectpartial
Walk into the room with a written answer for the likely objection.
Learning relevance
86 · weight 20%
3 principles · 0 lessons · 1 past decisionsstrong
We have seen this before — grounded in organizational memory.
Decision Lifecycle06Running
Continue →
Signal
Problem
Prep
Ready
Decided
Running
Reviewed
Learned
Blocker
Waiting for outcome by 1/15/1970.
Next step
Review the outcome in the Learning Loop when the window closes.
Under review

Make SSO setup optional during onboarding. Move it to a post-invite step gated only when an admin enables enterprise policies.

The SSO gate sits directly on the step where activation is bleeding, and three independent signals (funnel, churn interview, qualitative review) point to the same cause. Decoupling SSO from invites is the smallest change that addresses the dominant hypothesis.

Movement 01

Evidence

Do we have the right kind of evidence, and is it recent?
Quantitative
partial
1
Metrics, instrumentation, bug telemetry.
Qualitative
strong
2
Customer voice, interviews, escalations.
Recent (14d)
weak
0
Signals captured inside the read window.
Movement 02

Assumptions

Listed separately from facts. Each one tracked against the signal record.
Assumption
untested

The SSO requirement is the dominant cause (vs. seasonal traffic mix).

Evidence supporting
0
Evidence opposing
0
No linked signals speak to this. Run a check before deciding.
Assumption
untested

Most new workspaces don't have SSO ready on day one.

Evidence supporting
0
Evidence opposing
0
No linked signals speak to this. Run a check before deciding.
Assumption
untested

Letting admins defer SSO won't materially increase enterprise risk in week 1.

Evidence supporting
0
Evidence opposing
0
No linked signals speak to this. Run a check before deciding.
Assumption
untested

Deferring SSO does not materially raise security incidents in week 1.

Evidence supporting
0
Evidence opposing
0
No linked signals speak to this. Run a check before deciding.
Assumption
untested

The activation lift is causally tied to the gate, not seasonality.

Evidence supporting
0
Evidence opposing
0
No linked signals speak to this. Run a check before deciding.
Movement 03

Risks

Every decision must declare risks. The lens matters more than the count.
Security risk
  • Removing the gate could leak workspaces into production without governance.
  • Workspaces enter production without governance — mitigate with a 14-day SSO prompt.
Other risk
  • If the cause is traffic mix, the fix won't move the metric.
  • If seasonality is the real driver, the metric won't move and we've spent a sprint.
Movement 04

Stakeholder readiness

Simulated reactions and the line you should walk in with.
Product leadership
Likely object
Is this the highest-leverage move this cycle, or does it crowd out the activation bet we're already running?
Why:Concern touches a principle this stakeholder defends.
Suggested response: Frame the trade-off explicitly: name what we will stop or defer to make room, and tie the prediction to a portfolio-level metric.
Engineering leadership
Needs validation
What's the cost of being wrong, and can we land it behind a flag?
Why:Stakeholder needs a specific question answered before signing off.
Suggested response: Commit to a feature-flagged rollout with a defined kill switch and a single DRI; reread the prediction at week one before widening.
Security
Likely object
Loosening or deferring an auth control needs a compensating policy — what is it, and when does it expire?
Why:Concern touches a principle this stakeholder defends.
Suggested response: Pair the change with a written exception, a 14-day re-check, and an alert path so any abuse is observable, not theoretical.
Design
Needs validation
What does the user see and feel in the new flow, and how do we make the deferred step return without nagging?
Why:Stakeholder needs a specific question answered before signing off.
Suggested response: Prototype the new path end-to-end (including the deferred state) and run it past five users before the flag widens past 50%.
Sales
Likely supportive
Two deals are leaning on the original commitment — does this change what we can say in the next call?
Why:Concern is procedural — addressable with the suggested response.
Suggested response: Draft a one-paragraph customer-facing note before the decision lands so AEs have a single source of truth in the next conversation.
Movement 05

What would most increase confidence?

Not 'what should we do?' — the smallest move that lifts readiness the most.
material
Test the assumption: "The SSO requirement is the dominant cause (vs. seasonal traffic mix)."
Untested assumptions silently carry the recommendation.
+10 readiness
material
Test the assumption: "Most new workspaces don't have SSO ready on day one."
Untested assumptions silently carry the recommendation.
+10 readiness
material
Test the assumption: "Letting admins defer SSO won't materially increase enterprise risk in week 1."
Untested assumptions silently carry the recommendation.
+10 readiness
material
Test the assumption: "Deferring SSO does not materially raise security incidents in week 1."
Untested assumptions silently carry the recommendation.
+10 readiness
material
Test the assumption: "The activation lift is causally tied to the gate, not seasonality."
Untested assumptions silently carry the recommendation.
+10 readiness
material
Re-pull the underlying metric for the last 14 days.
Stale evidence won't survive a serious review.
+8 readiness
Movement 06

Recommendation

What we believe, why, what must be true, and the smallest experiment.
What we believe
Make SSO setup optional during onboarding. Move it to a post-invite step gated only when an admin enables enterprise policies.
Why
The SSO gate sits directly on the step where activation is bleeding, and three independent signals (funnel, churn interview, qualitative review) point to the same cause. Decoupling SSO from invites is the smallest change that addresses the dominant hypothesis.
What must be true
Deferring SSO does not materially raise security incidents in week 1. · The activation lift is causally tied to the gate, not seasonality.
What could invalidate this
Workspaces enter production without governance — mitigate with a 14-day SSO prompt. · If seasonality is the real driver, the metric won't move and we've spent a sprint.
Smallest experiment
Ship a feature-flagged soft-skip to 50% of new workspaces and read the 7-day cohort by Friday.
Expected outcome
Day-1 activation back to 45%+ on the treatment cohort within 14 days.
Movement 07

Readiness gates

A decision cannot move to Recorded until all five gates pass.
Gate to "Decision Recorded"
All gates passed
  • Evidence exists
  • Assumptions documented
  • Risks documented
  • Review date selected
  • Success metric defined
This decision can be recorded. Approving will open the Learning Loop.
Record decision