A Smarter Question For Leadership Teams

Most leadership teams think they have a decision problem. Usually, they have a conversation problem.

The familiar question, “What should we do?” sounds productive, but it often creates a subtle trap. The room fills with proposals, people start defending their favorite answer, and the discussion turns into a contest between confidence levels. The loudest voice, the most senior title, or the cleanest sounding story can win, even when the underlying logic is shaky. A better question changes the whole meeting: What would have to be true for this option to be the best choice?

That shift matters whether a company is deciding on pricing, expansion, hiring, or even something operational like a Michigan business entity search before entering a new market or checking the status of another company. Instead of arguing over who is right, the team starts identifying the conditions that must exist for a decision to work. The conversation becomes less about personality and more about evidence.

Why This Question Calms the Room

Leadership teams are rarely short on opinions. What they are short on is a shared way to test those opinions without bruising egos. When someone says, “We should open a second location,” disagreement can feel personal. But when the group asks, “What would have to be true for a second location to be our best move?” the proposal becomes a model to examine, not a hill to die on.

That distinction is bigger than it sounds. It lowers defensiveness. It also invites quieter leaders into the process, because they no longer need a fully formed counterproposal to contribute. They can point out assumptions, risks, missing information, and dependencies. In strong teams, this is where the best thinking happens.

The U.S. Small Business Administration stresses that planning and market research help owners make sound decisions based on facts, not just instinct. Their guidance also emphasizes using projections and analysis to reduce surprises and test viability before moving forward. Those are exactly the habits this question encourages: surfacing assumptions and checking whether reality can support them through business planning and market research guidance from the SBA.

The Real Job of a Leadership Team

A lot of executives quietly assume their job is to have answers. In practice, their real job is to improve the quality of the company’s assumptions.

Every major initiative rests on a stack of beliefs. Customers will pay more. The new manager can scale the team. The product launch will happen on time. Competitors will stay slow. Regulations will remain stable. Supply costs will not spike. Most bad decisions are not caused by bad intent. They are caused by untested assumptions that sounded reasonable in the room.

When leaders ask what would have to be true, they expose the structure underneath a decision. Suddenly, a strategy is no longer a polished idea. It is a set of claims. That is useful, because claims can be examined. Some will prove solid. Others will look fragile the moment they are spoken out loud.

This approach is also helpful because it separates reversible assumptions from dangerous ones. If an assumption is easy to test cheaply, the team can run a pilot. If it is hard to test and very expensive if wrong, the team knows to slow down.

From Advocacy to Investigation

Most strategy meetings drift toward advocacy. Each executive presents a preferred direction and then spends the rest of the meeting supporting it. The smarter question pulls everyone toward investigation instead.

Say the team is considering a major software switch. Rather than debating abstract pros and cons, they can list what must be true for the switch to be the best option. Implementation must finish within six months. Staff adoption must exceed a certain threshold. Productivity cannot dip below a tolerable level. Integration with current systems must work cleanly. Vendor support must be reliable.

Now the discussion has shape. The team can rank those assumptions by importance and uncertainty. Which one matters most? Which one is least known? Which one can be validated quickly? That is far more useful than forty five minutes of vague opinions and one dramatic anecdote.

Even organizations in high stakes technical environments rely on clearly defined decision processes and documented analysis so recommendations can be evaluated on their merits, not just on authority. NASA’s guidance on technical management reflects that discipline by emphasizing defined decision roles and documented analysis in team recommendations through its technical management decision framework.

How Leaders Can Use It Tomorrow

This is not a theory that needs a retreat or a consultant to become useful. A leadership team can apply it in the next meeting.

Start with one live decision. Put the leading option on the table. Then ask everyone to complete the sentence: “For this to be the best choice, what would have to be true?” Capture every answer. After that, sort the list into three buckets.

First, things the team knows are already true. Second, things that are uncertain but testable. Third, things that are uncertain and hard to test.

That third bucket deserves the most attention. It usually contains the assumptions that can quietly wreck a plan. Once those are visible, the team can decide whether to gather more information, redesign the option, create safeguards, or reject it entirely.

This method also improves speed. It may seem slower at first, but it prevents teams from charging ahead on false confidence. In the long run, fewer bad bets mean fewer emergency meetings, fewer political arguments, and less expensive backtracking.

The Cultural Signal It Sends

There is another benefit leaders often miss. Questions shape culture.

When the top team keeps asking, “What should we do?” people learn to perform certainty. They show up with polished answers and protect them. When the top team asks, “What would have to be true?” people learn to think in conditions, evidence, and learning loops. They become more honest about what they know, what they assume, and what they still need to test.

That kind of culture is not passive. It is rigorous. It rewards judgment without pretending judgment is magic.

The smartest leadership teams are not the ones with the fastest opinions. They are the ones that know how to turn opinions into testable thinking. One question does that surprisingly well. Ask it often enough, and the team stops acting like a panel of advocates. It starts working like a group of investigators.