Step 1 · See the impasse
Two demands. One apparent dead end.
Product wants to launch now. Security wants to delay. If those are the only options, protecting one need appears to sacrifice the other.
Tools for stuck decisions
Choose decision analysis tools for the difficulty in front of you. Reopen a false choice, find a useful point of leverage, decide when more analysis is worthwhile, test an assumption with a reversible step, or examine a difficult tradeoff.
Diagnose the blockage. Match the tool. Test the result.
Start with your situation
Choose the closest description. See what to bring, what the tool can reveal, and a concrete example.
A starting point for your judgment. You can explore another route at any time.
Suggested tool · Ladder of goals
Instead of “Which CRM should we buy?”, ask “How could we stop losing qualified leads?”
See a reframing exampleSuggested tool · Evaporating Cloud / Split the contradiction
A launch-versus-delay argument can become a question about a safe, limited release.
Walk through the conflictSuggested tool · Constraint lens / Leverage point
More support staff may not fix a failed onboarding handoff.
Explore the leverage-point toolSuggested tool · Independent team input
Ask each person what could change their view before the most senior person states a preference.
See how independent input worksSuggested tool · Pre-mortem / The smallest step
Test with a limited cohort before committing the whole company. If the downside remains unacceptable, stop or choose another route.
Explore the pre-mortem lensEvaporating Cloud · interactive worked example
Follow a product and security disagreement. Watch what changes when the team examines the assumption connecting a need to a demand.
Illustrative scenario · possible options, not a customer result or a security recommendation.
“To learn in time, we must release the full product to everyone.”
Must we?Preserve both needs where feasible. Check the remaining risk before committing.
A Reality Move changes the frame to reveal an option the original choice concealed. This one is still a possibility—not an approved decision or a proven breakthrough. Ask the team to challenge it independently, then test what happens.
Step 1 · See the impasse
Product wants to launch now. Security wants to delay. If those are the only options, protecting one need appears to sacrifice the other.
Step 2 · Find the shared goal
Product needs timely customer learning. Security needs to protect customer trust. Both can support a successful, trusted launch. Agreement on the goal does not yet resolve the conflict.
Step 3 · Question the assumption
The hidden assumption is that timely learning requires a full release. Questioning that assumption opens a different option. It still needs evidence and both sides’ scrutiny.
Step 4 · Design a possible move
Consider a limited cohort, agreed safeguards, a rollback plan, and explicit stop conditions. Compare its learning value and remaining exposure with launching fully or waiting.
You may uncover a real trade-off that cannot be removed. Making it explicit is useful too.
Open your decision workspaceLadder of Goals · interactive worked example
One question changes the unit of comparison: from what to buy to what must improve.
Illustrative scenario · possible routes, not a customer result.
“Which expensive CRM should we buy?” The named options are vendors, but the reason for buying one is still implicit.
Example answer: “Sales must respond to qualified leads before interest disappears.” This moves attention from the object to its purpose.
Objective: stop losing qualified leads without increasing acquisition cost. A CRM is now one possible route, not the goal itself.
Compare routing rules, response alerts, qualification changes, a smaller configuration, and a new CRM. Test the lowest-cost route that can produce useful evidence.
Your objective: finish “We need to ___ so that ___.” Ask “What does that make possible?” twice. Then list at least three routes to the larger goal before comparing them.
Open your decision workspace →One visual language
Every symbol keeps its label. Lines say whether one element supports, depends on, or conflicts with another.
Not a seventh kind of record. This marker highlights an option or reframe worth testing: what changed, what became possible, and what still needs checking. The logo is a reminder to question the frame—not an endorsement of the answer.
Five focused tools
Reopen the options, locate a useful point of leverage, or design a small test. Choose the tool that addresses the current uncertainty, and check whether it changes your next step.
What does this specific requirement make possible?
Climb from a stated demand to the outcome it serves. Two incompatible requirements often become negotiable when their higher purposes are made explicit.
Which unknown, assumption, or unchecked claim can move the whole decision?
Line up the main unknown, weakest assumption, and unfinished checks. Work where one answer can change the map instead of researching everything.
What minimum evidence would make action responsible?
Set decision criteria before another research round. Add one justified check only when it can change the chosen path or its safeguards.
What minimum action will produce useful feedback from reality?
Define the signal, expansion condition, and stop condition before acting. Buy information without taking the full risk at once.
Can the opposing needs be met in different conditions, times, or system parts?
Look for separation before compromise. The tension may disappear when the two requirements do not have to operate in the same place or moment.
Inside the workspace
The technique and the record stay together. What you test can become evidence; what you expect can become a forecast; what happens can inform the next case.
Compare the support, independence, source quality, and conflicts behind an important claim.
Explore the platformIdentify which assumption the recommendation depends on and what would happen if it failed.
See refutationFind failure mechanisms, early warnings, preventive moves, and stop conditions before execution.
See pre-mortemConnect evidence, assumptions, options, forecasts, goals, and constraints in an inspectable map.
See visual mappingIndependent first. Together next. Give people the context, preserve their views before reveal, and compare the perspectives that matter.
See team decisionsSet a date to return when useful evidence should be available. Compare the forecast with events and note what you still do not know.
Explore Reality DatesA case-by-case fit
Describe what you are trying to accomplish, who is involved, and where the process gets stuck. We will assess whether we can help and quote additional support when there is a useful fit.
See additional supportQuestions, answered
Start from the blockage, not the tool name. Use a leverage point for too much detail, Enough to decide for analysis paralysis, and the smallest step when useful feedback can be bought reversibly.
The method, lenses, evidence analysis, assumption testing, stress testing, visual mapping, and outcome review are represented through structured workflows in the platform.
For your leadership team
See the platform in action, discuss an organization license, and identify an initial decision your team can work through.
Request a platform demo