The slide deck clicked forward, the presenter’s voice steady. Charts glowed on the screen, but as I scanned the room, I realised no one was asking the obvious questions—the ones that would make or break our next quarter. My pulse quickened. Should I risk derailing the meeting?
I raised my hand.
After three pointed questions—“What’s actually driving these numbers?”, “Why haven’t we validated this assumption?”, “What’s the one lever we’re ignoring?”—the room fell silent. Then came the nods. The real conversation began.
Later, I realised: Every team needs 1-2 people willing to ask these “crux” questions. I called them the “Blue Team”, inspired by the idea of a “Red Team.”
In Making Better Decisions, I had written about “Red Teaming”: “It is a decision-making support process wherein a group actively challenges an organisation’s plans, policies, systems, and assumptions, mimicking potential adversaries to expose vulnerabilities. Originating from military exercises, Red Teaming’s primary goal in business and security contexts is to improve decision-making by providing a candid, critical perspective. It helps organisations anticipate potential threats and weaknesses by simulating an external attacker’s mindset, ultimately refining and fortifying decisions and defences.”
Red and Blue Teams work like a strategic yin and yang. While Red Teams ask, “What could go wrong?”, Blue Teams ask: “What must go right?”
| Red Team | Blue Team |
| Challenges assumptions | Uncovers core assumptions |
| Mimics external threats | Clarifies internal priorities |
| Prepares for failure | Ensures foundational clarity |
Red Teams are devil’s advocates. Blue Teams are architects of focus.
Management legend Peter Drucker believed the mark of an effective leader was asking, “What needs to be done?” rather than “What do I want to do?”
Blue Teams operationalise this. They cut through metrics-laden presentations and polite consensus to demand:
- “What’s the one thing we haven’t discussed that could change everything?”
- “If we had to bet the company on a single assumption, which would it be—and how do we know it’s true?”
This isn’t confrontation. It’s clarity engineering.
Most meetings fail here: We debate solutions before agreeing on the problem. Blue Teams fix this—but only if leaders:
- Reward courage, not compliance (“Thank you for asking that—let’s dig in”).
- Pause before problem-solving (“Let’s Blue Team this for 5 minutes first”).
- Separate ego from inquiry (Treat questions as contributions, not criticism).
o, in your next meeting, try this: Before diving into debate, ask: “What’s the Blue Team question here?” Watch how it shifts the conversation from reactive (“How do we fix this?”) to strategic (“Should we be fixing this?”). Because in a world drowning in data but starving for wisdom, the real power lies in asking fewer questions—just the ones that matter.
