Why Smart People Still Produce Weak Decisions
Tuesday 6 October — Art of Intelligence · Intelligence
The table
The case
Subtitle: The Meeting Where Everyone Was Right and Nothing Moved — the writer's essay; the case that works the same pattern with a deadline is chapter 21 Source: The owner's own case (Dražen Kapusta, 2026-09-13, "CASE 4"), verbatim; discussion questions 1–3 his, 4–8 added by the professor at his request
The meeting began on time, which made it look disciplined.
The agenda was clear. The slides had been sent the evening before. Finance had prepared numbers. Sales had brought market signals. HR had employee concerns. Operations had capacity constraints. Marketing had customer data. The CEO had the pressure of the board in the back of his mind and the feeling that this meeting had to produce something more than another summary of the obvious.
The room was not full of fools.
That was the problem.
Everyone around the table was competent. Some were very experienced. Several had been with the company for years. A few had survived crises that younger managers only knew as stories. They knew the industry, the customers, the politics, the risks and the hidden costs behind every clean strategic sentence.
And yet, after two hours, nothing had moved.
There had been discussion. There had been disagreement. There had been polite interruption, defensive clarification, a few jokes, one long detour, and several moments where people nodded without agreeing. The meeting had produced language, but not a decision.
Everyone had protected something.
Finance protected margin. Sales protected growth. HR protected people. Operations protected feasibility. Marketing protected the brand. Legal protected exposure. The CEO protected optionality. Each person was right from the place where they were sitting.
The company, as a system, remained stuck.
Everyone was right.
Nothing moved.
The room had intelligence.
The organization did not.
This was not the first time.
The same pattern had appeared in strategy meetings, budget meetings, transformation meetings, hiring meetings and crisis meetings. A question would enter the room with urgency and leave the room with vocabulary. People would say “we need alignment,” “we need more data,” “we need to involve the team,” “we need to be careful,” or “we should come back to this next week.”
Sometimes those sentences were true. Often they were protection.
The CEO had begun to hate meetings, not because he hated people, but because meetings kept revealing something he did not want to admit. The company had enough individual intelligence to see problems, but not enough collective discipline to decide.
This is one of the most frustrating experiences in leadership.
You can sit with people who are educated, experienced, well-paid and apparently serious, and still watch the group produce an outcome worse than what one clear person could have done alone. It is not always because people are lazy. It is not always because they are political. It is not always because they lack courage.
Sometimes the meeting itself is badly designed.
The room rewards commentary more than commitment. It allows people to speak from functions, not from company interest. It lets disagreement stay abstract. It has no memory of previous assumptions. It does not force a clear owner. It does not separate facts from fears, risks from excuses, and uncertainty from avoidance.
So the meeting becomes a theatre of responsible people avoiding responsibility together.
Nobody says no. Nobody says yes. Nobody says “I own this.” Nobody says “this is the trade-off.” Nobody says “we are choosing this and therefore not choosing that.” Instead, the room produces a soft cloud of shared concern.
The next day, everyone is busy again. The unresolved decision becomes work. More emails. More calls. More side conversations. More preparation for the next meeting where the same decision returns wearing a different title.
The CEO sees it and feels anger first.
Then exhaustion.
Then distance.
He begins to speak less. He stops expecting much. He enters meetings already disappointed. He listens to people explain constraints and hears only fear. He watches slides appear and sees only delay. He looks at his team and thinks something dangerous: maybe it is easier to decide alone.
At first, that thought feels efficient.
If the room cannot decide, the CEO will decide. If people hide behind complexity, he will cut through it. If meetings create fog, he will act. For a while, this works. Decisions get made. The organization moves. People feel clarity.
But a new problem appears.
The team becomes even less capable of deciding without him.
People wait. They escalate. They prepare arguments for the CEO rather than decisions for the business. They learn the safest strategy: do not be wrong before the boss has spoken. The meeting problem has not been solved. It has been centralized.
The CEO has replaced bad collective intelligence with personal force.
That is not transformation. It is dependency.
The deeper leadership dilemma is not whether meetings should be shorter, stricter or more efficient. Those are surface questions. The real dilemma is whether leaders know how to design a decision system in which smart people can produce movement together.
A good meeting is not a gathering.
It is a machine for converting uncertainty into commitment.
That machine needs rules. It needs evidence. It needs roles. It needs memory. It needs conflict that is safe enough to be honest and disciplined enough to be useful. It needs a leader who does not confuse silence with agreement, and does not confuse discussion with progress.
Most companies do not have that machine. They have calendars.
This is where AI enters the story, but carefully.
AI will not save a weak decision culture. It may even make it worse. A team that already avoids clarity can now create better slides, longer summaries, faster research and more impressive scenario documents without ever deciding. AI can make the fog look professional.
But used properly, AI can also become a mirror.
Before the meeting, it can force the team to state the decision in one sentence. Not the topic. The decision. It can list the assumptions behind each option. It can show which facts are known, which are guesses, and which are emotional positions pretending to be facts. It can create three scenarios and ask what would have to be true for each to work.
During the meeting, it can capture the actual trade-offs. It can notice when the conversation circles back to a point already made. It can record who agreed to what. It can preserve dissent instead of letting it disappear under polite consensus.
After the meeting, it can become decision memory. What did we decide? Why did we decide it? What risks did we accept? What alternatives did we reject? What evidence would make us reverse the decision? Who owns the next step? When will we know whether the decision was right?
This sounds simple.
It is not.
Most organizations do not lack information. They lack the courage and structure to turn information into accountable choice. AI can help with structure. It cannot supply courage.
AI can prepare the room.
It cannot make the room honest.
AI can remember the decision.
It cannot own the consequence.
That remains human work.
This is why the COTRUGLI tribe matters.
Inside companies, people often cannot speak fully. They carry roles, histories, loyalties and fears. The CFO has to be the CFO. The HR director has to protect people. The sales director has to push for growth. The founder has to protect the company he built. The young manager has to calculate whether truth is safe.
But at a COlab table, something different can happen.
A leader can bring a dilemma without the internal politics attached to it. Alumni from other industries can hear the pattern more clearly because they are not trapped inside it. Someone from hospitality may see what a tech company misses. Someone from construction may understand execution risk better than a consultant. Someone from media may see the reputation angle. Someone from HR may hear the people signal behind the financial argument.
The tribe becomes a decision mirror.
Not because it has all the answers, but because it can ask better questions with less fear.
This is one of the hidden powers of CDayZ. The value is not only in panels, speeches or frameworks. The value is in putting leaders into rooms where they can test their thinking against people who understand pressure, but do not share the same blind spots.
The official session may open the problem. The table may sharpen it. The dinner may make the truth easier to say. The party may remove the titles long enough for people to speak as humans again. The next morning, the leader may finally see the decision that was hidden under two months of meetings.
That is not networking.
That is collective intelligence becoming usable.
The CEO in this case does not need another productivity hack. He does not need another meeting rule. He needs to rebuild the way his leadership team thinks together.
He begins with one change.
Every strategic meeting must start with a decision sentence.
Not “discuss market expansion.”
But “decide whether we enter the new market in Q2, delay until Q4, or reject the opportunity for this cycle.”
Then the team must name the real trade-off.
Not “we need more analysis.”
But “growth now increases execution risk, delay protects quality but may lose first-mover advantage.”
Then each function must speak twice.
First from its professional responsibility.
Then from the company’s total interest.
Finance may say: “From margin perspective, this is risky.”
Then: “From company perspective, the risk may be acceptable if we cap exposure and define exit criteria.”
Sales may say: “From growth perspective, we should move now.”
Then: “From company perspective, we should not sell what operations cannot deliver.”
This small discipline changes the room.
People are no longer rewarded only for defending their function. They are asked to carry the whole company in their thinking. Disagreement becomes more useful because it has to declare what it protects and what it costs.
AI supports the process by recording assumptions, open risks, dissent, decision owners and review dates. It does not lead the meeting. It keeps the room honest after the meeting ends.
After three months, meetings are not perfect. They never are. But something important changes.
Fewer topics return unchanged. Fewer people hide behind “alignment.” More decisions have owners. More disagreements become clear before the decision, not sabotage after it. The CEO speaks less, but the team thinks more. Some people become stronger. Others are exposed.
The company has not become magically intelligent.
It has stopped accepting collective stupidity as the price of involving smart people.
That is the leadership lesson.
In the NEO era, speed matters. But speed without decision quality is only faster confusion. AI matters. But AI without human judgment is only automated noise. Talent matters. But talent without decision architecture becomes expensive discussion.
The future will not belong to companies with the most meetings, the most slides, or even the most intelligent individuals.
It will belong to organizations that can see clearly, argue honestly, decide consciously, remember why they decided, learn from the result and move again.
That is cognitive superiority.
Not being smarter in theory.
Moving better in reality.
Discussion Questions
- Why do smart people in the same room often fail to produce a smart organizational decision?
- What most often blocks real decision-making in leadership teams: ego, functional protection, fear, unclear ownership, poor evidence or weak meeting design?
- Where can AI improve the decision process, and where would it be dangerous to let AI create false confidence?
- Which function do you speak from in your own leadership meetings — and what would you say if you had to speak a second time, from the company’s total interest?
- When did you last decide alone because the room could not? What did it cost your team’s ability to decide without you?
- What would change in your next strategic meeting if it had to open with a decision sentence and a named trade-off — and who in the room would resist it first?
- Where do you go to test a decision without the internal politics attached? Who at a COlab table would see your blind spot before you do?
- The NEO Turn. When the AI that prepares the decision also remembers it, tracks the owner and the review date — and can execute the next step — what would you require it to record, and what must remain yours: the sentence, the trade-off, the ownership, the consequence?
Your comment on this chapter
A question for the table, a disagreement, what you would have done. The case lead reads every comment; the ones the table takes up enter the chapter as questions from the room, with your name.