The assumptions never announce themselves.

A hiring plan can look obvious until you ask what problem the new role is actually meant to solve. A delayed project can look like a capacity issue until you ask whether the team is protecting work that no longer matters. The difficult part is that the assumptions inside these decisions rarely announce themselves. They arrive as common sense.

Challenging decision assumptions is not about becoming contrarian or slowing every choice to a crawl. It is a way to separate what you know, what you are inferring, and what you have simply become used to believing. For managers, founders and independent professionals, that distinction can prevent expensive rework and lead to more honest conversations.

Why assumptions harden before decisions do

Most consequential decisions begin with an incomplete story. You may have a few facts, a strong reaction, a deadline and a pattern from past experience. The mind does what it is designed to do: it fills gaps quickly enough to let you act.

That efficiency is useful. It also creates risk when the story becomes a premise without being tested. “The client is unhappy because the delivery was late” may conceal a different concern about communication. “My manager will see this as a lack of commitment” may be a prediction based on one tense meeting. “We need to ship by Friday” may be a deadline inherited from an earlier plan that nobody has revisited.

Assumptions become especially sticky when they are shared by people with similar incentives, backgrounds or pressures. Agreement can feel like evidence when it is only familiarity. The goal is not to distrust every instinct. It is to identify the assumptions that carry the most weight and deserve independent examination.

Start by naming the decision, not the debate

A useful challenge begins with precision. Broad questions such as “What should we do?” invite broad answers. Name the choice in a form that exposes its trade-off.

Instead of “Should we reorganize?” try: “Should we move customer success under sales this quarter, accepting a likely short-term disruption in order to improve renewal accountability?” Instead of “Should I take the offer?” try: “Should I accept a role with more scope but less predictable hours, given my current family commitments?” The questions that come before any offer exists — whether there is a career decision here at all — are their own page.

This framing matters because an assumption usually supports a specific leap. If the decision is vague, the leap remains hidden. Write down the decision in one sentence, then complete this sentence: “For this to be the right choice, we are assuming that…”

If the whole decision is what needs structure — criteria, options, a record, a review date — that is a larger job than this page: structured decision making for managers walks it end to end. What follows here is one move from it, done properly.

Do not stop at the first answer. In a project decision, you may be assuming the customer’s needs are stable, the team has the required skills, and a competitor will not change the market before launch. In a career decision, you may be assuming the new manager is trustworthy, the title will translate into future opportunities, and the financial upside offsets the personal cost.

Three questions that do the work

Once an assumption is visible, do not immediately argue against it. First, classify it. Some assumptions are facts that can be verified. Others are forecasts, interpretations or value judgments. Each calls for a different response.

What would count as evidence?

Ask what evidence would make the assumption more credible and what evidence would weaken it. This prevents teams from treating confidence as proof.

The assumption “customers want this feature” should lead to questions about recent behaviour, direct feedback, support patterns and willingness to change established workflows. It should not be settled solely by the enthusiasm of the product team. Conversely, a single complaint may not overturn a sound direction. The quality and relevance of evidence matter.

Be careful with evidence gathered after a decision has emotionally taken hold. Teams often look for confirmation because it is faster and more comfortable than reopening the question. Assign someone to make the strongest reasonable case that the assumption is wrong, then give that case a fair hearing.

What else could explain this?

This is a simple question with unusual power. It interrupts the tendency to confuse an explanation with the explanation.

If an employee has become quiet in meetings, the obvious story may be disengagement. Other explanations could include unclear expectations, conflict with a colleague, lack of psychological safety, a workload problem, or something personal that you do not need to know in detail. The appropriate next move is not amateur diagnosis. It may be a direct, respectful conversation about what would make participation easier.

The same applies to organisational problems. A missed target may reflect weak execution, but it may also reflect a target that was poorly designed, a dependency that was underestimated, or a reporting system that hid trouble until too late. Alternative explanations do not remove accountability. They make accountability more accurate.

If this assumption fails, what breaks?

This question shifts attention from likelihood to consequence. A low-probability assumption can still deserve scrutiny if its failure would create serious damage.

Suppose you are considering a partnership because you assume the other organisation can deliver technical support. If that assumption proves false, can your team recover without losing customers or breaching commitments? If not, the decision may require a staged commitment, clearer contractual terms, or a backup plan.

This is where small tests are valuable. You may not be able to remove uncertainty, but you can often reduce the cost of being wrong. Run a pilot with one customer segment. Ask for a working session before committing to a vendor. Schedule a candid conversation before interpreting silence as agreement. A reversible test is often better than a prolonged internal argument.

Choose a lens when you are too close to the story

Different thinking lenses expose different blind spots, and the right one depends on the decision in front of you. Reading what a lens returns as hypotheses rather than a verdict is its own discipline.

• An inversion lens asks “How could this fail?” — useful when a team is energised by a plan and has not spent much time on downside risk.
• A second-order thinking lens asks what happens after the immediate effect, which helps with incentives, policy changes, and decisions that solve one problem by creating another.
• A systems lens asks where feedback loops, delays and dependencies may be shaping the outcome.
• A stakeholder lens asks who carries the cost of a decision and whose information is absent from the room.

No single lens delivers the answer. A lens is a disciplined way of seeing. It can make a previously invisible assumption discussable without turning the meeting into a contest over who is smartest.

This is also why structured reflection helps when a decision feels tangled. LikeGenius applies a documented thinking method to the situation you describe and returns an independent interpretation, concrete next moves and a sharper question. It is a way to create distance from the first story your mind supplied — not a replacement for your own judgment.

Where this stops

A method can surface an assumption. It cannot carry the consequence of acting on it, and it does not know what you know: the history, the people, the contractual detail, the person who will live with the outcome.

That limit is sharpest in the example above about the colleague who has gone quiet. Reading a person’s silence is exactly where structured reflection should stop and a conversation should start. If the decision is an employment action — hiring, discipline, performance rating, compensation, reassignment, termination — or involves legal exposure, mental health, medical care, discrimination, harassment or anyone’s immediate safety, a thinking method can help you organise the questions, and it must not replace the manager, HR professional, lawyer or clinician who is accountable for the answer. LikeGenius is a tool for your own reasoning and preparation, never a system for deciding about other people.

The same discipline applies to what you share. Describe the situation in the terms needed to understand it — and leave out names you do not need to give, confidential records, and anything that belongs in a formal channel. Better analysis does not require careless disclosure.

Make challenge safe enough to be useful

People do not challenge assumptions honestly when they expect to be labelled negative, disloyal or indecisive. Leaders shape this quickly through the questions they reward.

Rather than asking “Does anyone disagree?” ask “What would make this plan fail in practice?” or “Which part of our reasoning is least supported?” The first can sound like an invitation to oppose a senior person. The second makes examination part of the work.

It also helps to distinguish a decision review from a performance review. If someone raises a weak premise, do not treat that as a challenge to the person who proposed it. Treat it as new information about the choice. You can preserve momentum while still changing course.

For high-stakes choices, record the major assumptions, the evidence behind them, the owner responsible for watching each one, and the date you will revisit them. This is not bureaucratic theatre. It creates a record that lets the team learn whether its reasoning was sound. Over time you will see recurring patterns: overconfidence in adoption, underestimation of coordination costs, or a tendency to mistake urgency for importance.

The aim is not to reach a state of certainty. Most meaningful professional decisions do not offer one. The aim is to make the next decision with clearer eyes: aware of what must be true, alert to what could change, and ready to adjust before an assumption quietly becomes a commitment.