The First Monday as CEO
Wednesday 7 October — Art of Trade · New CEOs
The table
The case
Subtitle: When the Title Arrives Before the System Is Ready
On Friday afternoon, everyone congratulated her.
There were flowers in the office, messages on LinkedIn, a short internal announcement, and the usual sentence repeated by almost everyone: “You deserve this.”
By Monday morning, the sentence had changed.
The first email arrived before 7:00. A key manager wanted approval for a pricing decision. Finance needed a position on a cost-cutting proposal. HR had a sensitive people issue that had been waiting for “the new CEO.” A board member asked for a strategic view before the next meeting. A supplier wanted a personal conversation. A senior colleague, who had also expected to be considered for the role, suddenly became colder than usual.
By 10:30, she understood something that no leadership program had fully prepared her for:
She had not simply received a promotion. She had inherited gravity.
Until now, she had been responsible for a function, a region, a team, a business line. She was measured by performance, professionalism, delivery and influence. Now everything moved toward her. Problems that had previously been “organizational” became personal. Silence from her became a signal. A sentence in a meeting became policy. A delay became uncertainty. A smile became reassurance. A wrong joke became culture.
The company was not in crisis. That was exactly what made the situation dangerous.
The numbers were acceptable. The brand was respected. The team was experienced. The board expected continuity. But under the surface, the system was tired. Decision-making was slow. Some senior people protected their territories. Younger managers wanted more autonomy but did not yet know how to carry it. Customers were becoming more demanding. Technology was changing the rhythm of the industry. The old model still worked, but it was becoming heavier every year.
Her first instinct was to prove herself.
She wanted to show that the board had made the right decision. She wanted to be present in every important conversation. She wanted to understand every problem before allowing action. She wanted to protect quality, protect trust, protect the team and protect the company from mistakes.
For the first few weeks, this worked.
People appreciated her energy. She answered quickly. She entered details. She solved problems. She calmed tensions. She made herself available.
Then the pattern appeared.
More decisions came to her, not fewer. People waited for her opinion before moving. The strongest managers became more cautious. The weaker ones became more dependent. Problems were no longer solved at the edge of the organization; they were carried upward, carefully packaged, waiting for the CEO.
She had become the bottleneck she wanted to remove.
The real dilemma was not whether she was capable enough. She was.
The real dilemma was whether she could stop proving herself long enough to build a system that did not depend on her constant intervention.
That required a different kind of leadership move.
Instead of answering every question, she began asking: “Who should own this decision?” Instead of correcting every detail, she defined decision principles. Instead of protecting people from pressure, she gave them clearer authority. Instead of being the smartest person in the room, she started testing whether the room could become smarter without her.
This created discomfort.
Some people missed the old clarity of escalation. Some interpreted empowerment as abandonment. Some senior managers enjoyed autonomy; others were exposed by it. The board wanted speed, but also reassurance. Employees wanted change, but not too much change. Customers wanted innovation, but not instability.
The CEO’s work changed from solving problems to designing the conditions under which problems could be solved without her.
She had to learn the difference between control and orchestration.
Control felt responsible. Orchestration looked risky.
Control gave immediate satisfaction. Orchestration built long-term capacity.
Control made her visible. Orchestration made others stronger.
After six months, the company had not transformed completely. That would be an illusion. But something important had shifted. More decisions were made closer to the customer. Meetings became shorter. Younger managers started bringing proposals instead of questions. A few people who had hidden behind complexity became visible. A few others who had been underestimated started to lead.
The CEO still carried pressure. But now the pressure was different.
At the beginning, her question had been:
“How do I prove I am ready to be CEO?”
Now the question had become:
“How do I build an organization that is ready for the future, not just dependent on me?”
That was the real beginning of her CEO role.
Not the announcement. Not the title. Not the first board meeting.
The real beginning came when she stopped trying to be the answer — and started building the system.
Discussion Questions
- What is the real leadership dilemma in this case: proving personal authority or building organizational capacity?
- Where is the most dangerous trap for a first-time CEO: over-controlling, over-communicating, avoiding conflict, or trying to please all stakeholders?
- What should the CEO do in the first 90 days to move from control to orchestration?
- What does this case teach us about Vanguard Leadership in the NEO era?
- Who is owed what when authority moves outward?
- What does a decision principle for money look like?
- What must she change in herself, not in the organisation?
- The NEO Turn, second half.
The manager exposed by autonomy, the one who became dependent, the one who was underestimated — three different debts.
The 7:00 pricing email and Finance's cost-cutting proposal both waited for her; what sentence would have let them not wait?
"Control felt responsible" — the feeling does not go away when the org chart changes.
The case says problems were "carried upward, carefully packaged". What happens when the packaging is done by an agent?
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.