How to tell when your leadership system has fallen behind your company

The approval that took three weeks

A customer asked for a small change. The account lead agreed it was sensible. Delivery said it could be done. Finance had no objection. Yet nobody was sure who could say yes.

The question travelled to the business head, then to the COO, and finally to the founder. Three weeks later, the customer got an answer.

Everyone involved was competent. The company had a strategy, an organisation chart and several weekly review meetings. It also had a leadership system built for a much smaller company.

At 50 people, a founder can settle an issue by walking across the office. At 300, the same habit produces a queue. More managers get added to the queue, and each one brings another interpretation of what the founder would have wanted.

When I use the term leadership system, I mean the way the senior team interprets priorities, makes decisions, resolves differences, allocates work and reviews progress. Some companies have designed this system. Others have a collection of habits that worked well until the company grew.

How do you know which kind you have?

1. Every important decision travels upwards

Look at the last ten decisions that required the founder or CEO. How many genuinely needed that level of attention?

Pricing outside an agreed range may need escalation. A large capital commitment certainly might. A routine customer exception, an ordinary senior hire or the sequencing of two internal projects should usually have another owner.

Leaders often explain the escalation by saying, “The CEO likes to be involved.” That sentence hides two different problems. The team may lack authority, or it may lack the principles needed to use that authority well.

Delegating a decision without sharing the reasoning merely moves the anxiety to somebody else. The new owner still returns to the founder for reassurance.

2. Leadership meetings are full of updates

A leadership meeting is expensive. Add up the hourly cost if you wish, although the opportunity cost is more interesting. What is the organisation waiting for while its most senior people report information they could have read before the meeting?

Updates have a useful social function. They allow people to demonstrate activity and avoid the discomfort of a real disagreement. The sales head presents the pipeline. Operations shares delivery numbers. HR reports hiring. Everyone gets a turn. The meeting ends with little change in what the company will do.

A leadership meeting should spend most of its time on choices that cross functions: which customer segments deserve scarce capacity, how much variation delivery can support, where to slow hiring, and which risk the company is willing to accept.

If those choices are being made elsewhere, find out where. If they are not being made, the meeting is giving you a false sense of governance.

3. The same priority means different things to different leaders

“We need to improve enterprise focus.”

Sales hears larger deals. Product hears new capabilities. Finance hears better margins. Delivery hears fewer exceptions. HR hears a demand for more senior talent.

All five interpretations can be reasonable. Together, they can produce five work plans that compete for the same money and people.

Communication is often blamed at this point. The CEO repeats the message at the town hall, and a new slide appears in the strategy deck. Repetition helps only after the leadership team has agreed on the operational meaning of the priority.

Ask every leader to complete this sentence separately: “Because enterprise focus is a priority, we will stop, start and continue...” Compare the answers. You may discover five strategies hiding beneath one phrase.

4. Roles are clear until two functions are involved

Most job descriptions look sensible when read alone. Problems appear at the seams.

Who owns a customer promise that affects both sales and delivery? Who decides whether a product request belongs on the roadmap? Can a business head overrule a functional standard? Who chooses between a quarter-end revenue opportunity and a delivery risk next quarter?

An organisation chart tells you where people sit. It says very little about how shared decisions will be made.

The usual response is to create a RACI chart. RACI can help with recurring work. It struggles when leaders have not agreed on the underlying choice. If sales and delivery hold different views on speed and quality, assigning an “A” will simply identify the person who has to absorb the conflict.

5. Employees rely on the unofficial version of the company

New employees receive the official process. Experienced employees teach them how things are really done.

They explain which approvals can be skipped, which leader needs to be consulted before the formal owner makes a decision, and which priorities will probably disappear after the next review. This knowledge is useful. It is also expensive, because access depends on tenure and relationships.

The gap between the formal and informal company is a good measure of system health. A certain amount of interpretation will always exist. Trouble begins when the informal version has more authority than the designed one.

6. Senior hires create another layer of friction

The company recruits an experienced leader to bring structure. Six months later, the founder is disappointed that the leader has become bureaucratic. The leader is frustrated that every meaningful decision is being revisited. The team below has learned to wait until the disagreement settles.

The hire may be wrong. It is worth examining the system before reaching that conclusion.

Was the new leader given outcomes or a long list of activities? Were decision boundaries discussed? Did the founder explain which parts of the company’s identity were non-negotiable? Did the existing team understand why authority was moving?

A senior title cannot compensate for an ambiguous mandate.

7. Every execution problem produces another restructuring

Restructuring is visible. It creates boxes, announcements and a feeling of movement. It can also leave the original issue untouched.

If two teams disagree about who should serve a customer, putting them under one leader may speed up the next escalation. It will not answer the strategic question. If leaders disagree about central control and local freedom, moving a reporting line will not settle the trade-off.

Look at the last restructuring. Which decisions became easier afterwards? Which behaviours changed? Which measures improved? If the answers are vague, the structure may have been asked to solve an alignment problem.

A 30-minute test for your leadership system

Choose three decisions from the past month. Pick one that was delayed, one that was escalated and one that had to be revisited.

For each decision, ask:

• Who believed they owned it?

• What information did they need?

• Which other priorities were in tension?

• What principle or precedent guided the choice?

• How was the decision communicated?

• What did teams do after they heard it?

The last two questions matter. A decision can be clear in the room and change shape as it travels through the company. At Align By Design, we describe this as the Think-Say-Do Gap™: the distance between leadership intent, what gets communicated and what people finally do.

One of our engagements began with a founder-led cloud infrastructure services company at around 100 people. The organisation was growing rapidly and wanted to prove that its model could scale. The work covered culture, strategic alignment, role clarity, decision ownership and operating reviews. As the company grew to nearly 350 people, execution became more predictable and less dependent on the founders. The company reached its five-fold revenue goal in two years. You can read the full case study here.

The headcount and revenue figure catch the eye. The timing carries the lesson. The founders worked on the leadership system while the company was growing, before accumulated workarounds became the accepted way of operating.

Take three decisions and run the test. If you need to explain each delay by naming a personality, a heroic intervention or a historical accident, your company may have grown faster than the system leading it.

The Execution Readiness Assessment can help you locate the gap.