The decision made by whoever spoke first: critical thinking for teams that are busy

A vendor was proposing a system. The operations head, who had seen a demo, said it would solve the reconciliation problem, and said so with conviction. Around the table people nodded. Two people had doubts, one about whether the reconciliation problem was actually a system problem and one about the price, and neither raised them because the decision seemed to have been made. Eleven months later the system was live and the reconciliation problem was unchanged, because it had been a definition problem all along — two departments counting differently — and no system reconciles a disagreement about what to count.

Nobody in that room lacked intelligence. The room lacked a habit: the two-minute pause in which somebody asks whether the problem has been stated correctly before anyone proposes a solution to it. Critical thinking training for a working team is mostly the business of installing that pause.

Under time pressure, groups decide by momentum. The first confident proposal sets the frame; subsequent contributions are made inside it; doubts are weighed against the social cost of slowing things down and usually lose. The result looks like consensus and is closer to deference. The fix is not to make people less busy, which is not on offer. It is to make four questions so routine that asking them costs nothing socially, because everyone asks them and the meeting expects them.

1  WHAT IS THE PROBLEM, IN ONE SENTENCE, WITHOUT A
   SOLUTION IN IT?  'Reconciliation takes three days'
   - not 'we need a system'.
2  HOW DO WE KNOW?  What is the evidence that this is
   the problem, and who has looked at it?
3  WHAT ELSE COULD EXPLAIN IT?  Two alternatives, named,
   even if they seem unlikely.
4  WHAT WOULD CHANGE OUR MIND?  If we do this and it
   does not work, what will we have seen?

Ten minutes. The vendor decision would not have
survived question one.

Question one is the one that catches most bad decisions and the one teams most reliably skip, because a problem stated with the solution already inside it — 'we need a system' — feels like progress. Restating it without the solution is uncomfortable, slightly pedantic, and the single highest-value habit a working team can acquire.

Most problem-solving effort is spent on the problem as first described, which is usually a symptom described by the person who noticed it. The reconciliation took three days: that is a symptom. Why did it take three days? Because two sources disagreed. Why did they disagree? Because two departments defined the same thing differently. The problem was three questions below the one the meeting started with, and the vendor's system addressed the top one.

1. 1

   Ask why, three times, before proposing anything

   Not as a ritual — as a genuine attempt to find the level at which the problem is cheap to fix. Most problems are cheaper one level down.

2. 2

   Look for the definition problem

   A surprising share of operational problems are two parties using one word for two things. It is worth asking directly: are we counting the same thing?

3. 3

   Separate the problem from the person who described it

   The operations head was not wrong about the pain. He was wrong about the cause, and challenging the cause is not challenging him. Teams that cannot make that separation defer to seniority.

4. 4

   Name the cheapest test

   Before committing to the expensive fix, what is the small thing that would show whether the diagnosis is right? For the vendor decision: have the two departments count one month the same way and see if the three days go away.

Return to the two people who had doubts and did not raise them. One suspected the problem was not a system problem; the other thought the price was high. Between them they held both halves of the correct answer, and the room never heard either. That is the pattern in most bad group decisions: the information needed was in the room, distributed across people who each weighed the cost of interrupting a decision that seemed made. The four questions do not make people braver. They make the interruption unnecessary, because 'what else could explain this?' is on the agenda and the doubter is answering a question rather than raising an objection. That reframing — from objection to answer — is why the questions have to be asked by the chair, every time, and not left to whoever is brave that day.

Where a team's meetings have no chair, or the chair is the person proposing, the questions will not be asked. Appointing someone whose job in the meeting is to ask them — rotating, so it is not always the same sceptic — is a small structural fix that does more than any amount of training in reasoning. It is the kind of thing an HR process audit of how decisions get made would surface, because decision-making is a process and most businesses have never looked at theirs.

Critical thinking courses built on logic puzzles and famous case studies produce people who can spot a fallacy in a textbook and still nod at the vendor. The training that transfers uses the team's own last three significant decisions — the ones with an outcome that can now be seen — and walks each through the four questions with the benefit of hindsight. The gap between what was asked at the time and what would have been asked is specific, personal and uncomfortable, and it is the whole curriculum.

It also surfaces the pattern. A team whose last three decisions all skipped question one has a habit, not three accidents, and naming the habit in the room is worth more than any amount of technique. This is where critical thinking and problem-solving training either becomes a working practice or stays a day out, and the difference is whether the material was theirs.

The four questions are hardest to ask of the most senior person in the room, and that is precisely where they are most valuable. A managing director who wants the habit to take has one job: ask question three of their own proposals, out loud, first. 'What else could explain this?' from the top of the table, about the speaker's own idea, licenses everyone else to ask it. Without that, the habit is used on juniors' proposals and never on the ones that cost real money. It is a leadership behaviour before it is a team skill.

• Meetings take slightly longer and decisions take less time, because fewer are revisited.
• Vendors get asked what the problem is before they are asked what the system does.
• The quiet doubter speaks, because question three is an invitation with a slot in it.
• Some decisions are not made, because the cheapest test came back negative — which is the habit working, and feels like failure the first few times.

None of this requires cleverness. It requires four questions to become so ordinary that a team asks them of every proposal, including its own, and a senior person willing to go first. That is what critical thinking and problem-solving training should install, and the test of whether it did is the next vendor meeting: does someone ask what the problem is before anyone asks about the price.