The Cognitive Board — How to Institutionalise Whole-Brain Decision-Making Without Founder Approval
Erwee Coetzee
Diamond Stack
Cape Town, South Africa
You’ve just assigned Mthembu as the guardian of the Stone Selection Framework. Your lead designer is now guardian of Design Direction. Your operations person owns Pricing.
You thought this would free you up.
It hasn’t. Not yet.
You’re still attending the daily stand-ups. You’re still in the weekly team meetings. You’re still the one who makes the final call when Mthembu brings an edge case. You’re still the bottleneck, just with guardians reporting to you instead of teams reporting directly.
The frameworks are consistent now. But you’re still making the decisions.
Post 9 solved the problem of framework consistency across teams. Post 10 solves a different problem: How do you make decisions at the team level without needing founder approval?
The Decision Bottleneck (Different From Framework Bottleneck)
There are two different bottlenecks, and it’s crucial you understand the difference.
Framework bottleneck (Post 9): “How do I keep frameworks consistent across teams?”
Solution: Guardians + quarterly reviews
Decision bottleneck (Post 10): “How do I make decisions at the team level without needing founder approval?”
Solution: Cognitive board
Example: Mthembu is the framework guardian, and the frameworks are solid. But a customer requests a custom stone in a colour that doesn’t fit the framework. It’s an edge case. Mthembu brings it to you. You decide yes or no. He executes your decision.
This is still founder-dependent decision-making, just with better frameworks underneath.
What if instead, the decision was made by a group? Mthembu (the sourcer, understanding the framework), your lead designer (understanding aesthetics and market), your operations person (understanding cost and feasibility), and your C-quadrant culture person (understanding customer relationship)? Four perspectives. One decision. No founder approval needed.
Why Groupthink Is Your Biggest Risk
Irving Janis (1972) spent his career studying why smart groups make terrible decisions. His answer: groupthink. When a group gets too comfortable with each other, they start validating each other’s assumptions instead of challenging them. They avoid conflict. They converge on consensus without actually testing ideas.
He studied the Bay of Pigs invasion, the Challenger disaster, corporate mergers that destroyed shareholder value—all cases where intelligent people in groups made catastrophic decisions because they weren’t allowing dissent.
Your cognitive board will face the same risk. If you assemble a team of four people who mostly think alike, they’ll converge quickly. But they’ll converge on ideas that feel safe, not ideas that are rigorous.
Schwenk (1990) tested a solution: devil’s advocate decision-making. Assign someone in the group to argue against the emerging consensus, not because they believe it, but because the group needs adversarial testing of ideas. This single structural change—formalising dissent—significantly improved decision quality in his research.
The Cognitive Board: Structure and Roles
A cognitive board is a team of leaders (not just your direct reports, but the people who represent the four thinking quadrants) who make decisions together on behalf of the whole organisation.
You attend to integrate. You don’t vote.
The ideal composition (4 people):
A-Quadrant Representative (Analytical): Your data-driven person. In your case, maybe your controller or operations analyst. Their job on the board: “What does the data actually show? Are we making assumptions that aren’t validated?”
B-Quadrant Representative (Operational): Your process person. Your head of production or operations. Their job: “How would we execute this? What’s the implementation risk?”
C-Quadrant Representative (Interpersonal): Your culture person. This might be your HR lead, or your most emotionally intelligent team leader. Their job: “How would this affect the team? What’s the relational dimension we’re missing?”
D-Quadrant Representative (Visionary): Your strategic person. This might be your lead designer, or your most creative team member. Their job: “What’s the bigger vision here? Are we thinking too small or too big?”
You’re the integrator. You listen to all four. Your job is to synthesise: “Here’s the decision that honours the data, the execution, the relationships, and the vision.”
How the Cognitive Board Prevents Groupthink
Here’s the genius: cognitive diversity prevents groupthink naturally.
When an A-quadrant person and a D-quadrant person are in the same room, they will disagree. Not on facts, but on what questions matter. The A person asks: “What’s the historical precedent?” The D person asks: “What if we had never done it this way before?”
This disagreement isn’t a bug. It’s a feature. It prevents the group from converging too quickly on an assumption that feels comfortable.
Katzenbach & Smith (1993) studied high-performing teams and found that the best teams weren’t harmonious—they were productively tense. They had different perspectives. They argued. But the argument was about ideas, not personalities. And they came to collective decisions that were better than any individual could have made alone.
That’s what a cognitive board is.
The Formalisation That Makes It Work
You don’t just assemble four people and hope they think differently. You formalise it.
Structure 1: The Decision Framework
Every decision that comes to the cognitive board gets framed the same way:
“What’s the problem we’re solving? What are the constraints (time, budget, customer expectations)? What options are we considering? What’s the decision date?”
This structure forces clarity. Vague problems don’t get solved by boards; they get masked. Clear problems get dissected by four different perspectives.
Structure 2: The Mandatory Dissent Rule
Before the board votes or reaches consensus, one person is assigned to argue the opposite position. Not because they believe it. But because the group needs intellectual adversity.
This role rotates. One week, your A-quadrant person argues against the data. The next week, your B-quadrant person argues that execution is impossible (even if they think it’s possible). This prevents groupthink from calcifying.
Structure 3: The Quarterly Retrospective
Every quarter, the board reviews the decisions it made. Which ones turned out well? Which ones missed the mark? Why?
This feedback loop keeps the group honest. If the board kept making decisions that favoured the A-quadrant perspective and ignored the C-quadrant perspective, the retrospective would surface it. The board would then adjust.
What This Frees You To Do
The cognitive board doesn’t make you irrelevant. It shifts your role.
You’re no longer the decision-maker. You’re the integrator. You listen to four perspectives and synthesise. When the A person says “the data shows X,” and the D person says “the data is misleading; here’s the bigger vision,” you hear both. Your job is to hold both truths simultaneously and decide which one matters more right now.
This frees you to spend time on two things:
1. Strategy (not decisions): Instead of deciding whether to accept that custom stone order, you’re thinking about: “What market are we trying to own? Are we premium-exclusive (strict frameworks) or premium-flexible (adaptive frameworks)?” That’s your job.
2. Culture (not meetings): Instead of being in every team meeting, you’re focused on: “Does the organisation feel trusted? Do people feel empowered to decide? Is there psychological safety?” The cognitive board’s health is a reflection of the organisation’s health.
Why This Is The Bridge Between Post 9 and Post 11
Post 9 solved consistency (frameworks stay coherent across teams).
Post 10 solves decisions (decisions get made at team level without founder approval).
Post 11 will solve evolution (frameworks stay fresh as markets change).
Right now, you have frameworks that are consistent but static. The cognitive board is how you make decisions that keep frameworks alive and relevant.
A custom stone request comes in. The cognitive board discusses it. A-quadrant asks: “Does this fit our historical pattern?” D-quadrant asks: “Is this signalling a market shift we should adapt to?” B-quadrant asks: “Can we execute this profitably?” C-quadrant asks: “Does this strengthen or strain our customer relationship?”
The board decides yes. You integrate: “This is a signal we need to update the framework for 2026. Let’s bring that to the quarterly framework review.”
Now frameworks are living things, not static rules.
Your Reflection for This Week
Look at your leadership team. Do you have all four quadrants represented?
Who would be your A, B, C, and D representatives? And who’s missing?
You don’t need to have all four quadrants on your payroll today. But if you’re missing one, that’s your gap. That’s the perspective that keeps getting overlooked in your decisions.
Start building for it.
Research & References
Janis, I. L. (1972). Victims of groupthink: A psychological study of foreign-policy decisions and fiascos. Houghton Mifflin.
The foundational work on groupthink and how intelligent groups make poor decisions when they lack dissent. Shows why cognitive diversity is essential for decision quality, not just nice-to-have.
Schwenk, C. R. (1990). Devil’s advocacy in managerial decision-making. Journal of Management Studies, 41(2), 66–80.
Empirical evidence that assigning someone to argue the opposite position significantly improves decision quality. Directly applicable to structuring cognitive boards.
Katzenbach, J. R., & Smith, D. K. (1993). The wisdom of teams: Creating the high-performance organisation. Harvard Business School Press.
On productive tension in teams. Shows that the best teams aren’t harmonious; they’re characterised by constructive conflict and diverse perspectives.
Nemeth, C. J., & Staw, B. M. (1989). The tradeoffs of social control and innovation in groups and organisations. Advances in Experimental Social Psychology, 22, 175–210.
On minority influence and how dissent can actually improve group decision-making. Theoretical foundation for why devil’s advocate structuring works.
