APEX Business Growth · Insights

Your team cannot read your mind

Building the decision-making frameworks that let your people lead without you

You promoted your strongest strategist to head of delivery last spring. She is capable, trusted and well paid, and she still sends you a message before approving a scope change, a discount or a deadline extension. Your project managers do the same, and so, increasingly, do their teams. On paper the agency has three layers of leadership, yet in practice every road still leads to your inbox.

The org chart nobody follows

Many agency owners reach a point where they have done the hard part of hiring. There are managers, titles and reporting lines. The structure exists, and yet the owner is no less busy than before. If anything, the questions have multiplied, because there are now more people asking them.

This is a common source of frustration, and it is easy to read it as a people problem. The managers lack confidence. The team is too cautious. Nobody wants to take responsibility. Owners sometimes respond by hiring more senior people, only to find that the new hires begin escalating too within a few weeks.

The pattern is not about seniority. It is about information. An org chart describes who reports to whom. It says nothing about how decisions are made. When the logic behind decisions lives only in the owner’s head, every decision of consequence has to travel back to that head, regardless of what the chart says.

Every decision returns to the owner An org chart with the owner at the top, two managers below and four team members at the bottom. Decision lines from every manager and team member run back up to the owner node. Owner Manager Manager Team Team Team Team Every decision line ends at the same node Every decision returns to the owner An org chart with the owner at the top, two managers below and four team members at the bottom. Decision lines from every manager and team member run back up to the owner node. Owner Manager Manager Team Team Team Team Every decision line ends at the same node
The chart shows three levels. The decisions only ever show one.

People without logic

Every owner carries a set of rules they rarely say out loud. Which clients are worth bending for and which are not. When a scope change should be billed and when it should be absorbed. How much risk is acceptable on a deadline. What quality means for this particular agency. These rules were formed over years, through hundreds of judgement calls, and they feel obvious to the person who made them.

They are not obvious to anyone else. A manager who has not been given those rules faces a choice with every decision: guess, and risk being wrong in front of the owner, or ask, and be sure. Asking is the rational choice. Over time, it becomes the culture.

This is why installing people without installing the logic changes very little. The owner has added capacity but not authority. The Owner Ceiling remains exactly where it was, because the decisions still have a single point of passage.

What a decision framework contains

A decision framework is simply your judgement, written down in a form other people can apply. It does not need to cover everything. It needs to cover the decisions that most often travel back to you, and it needs to be specific enough that two people reading it would reach the same answer.

For each recurring decision, the framework sets out who owns it, the principles that guide it and the limits within which that person can act alone. A scope change under a certain size might sit fully with the account lead. A change that affects margin beyond an agreed threshold might require the head of delivery. Only changes that alter the client relationship itself come to the owner. The thresholds come from your financial reporting and your annual plan, which is why those foundations come earlier in the APEX build sequence.

The framework also needs a clear statement of what the agency values when principles conflict. If speed and quality pull in different directions, your people need to know which one wins, and when. Without that, they will ask you every time.

Installing it so it holds

A framework written once and filed away will not change behaviour. It needs to be introduced, practised and reinforced. When a question arrives that the framework already answers, the most useful response is to point back to the framework rather than give the answer. When a question arrives that it does not answer, that is a gap to close, so the same question never needs to reach you twice.

There is also a harder discipline for the owner: accepting decisions made correctly within the framework, even when you would have chosen differently. Overruling sound decisions teaches the team that the real rules are still unwritten. Respecting them teaches the team that the authority is real.

Over a few months, the volume of escalation falls. Managers begin to decide with confidence, because they know what a good decision looks like here. This is the point at which the owner can genuinely step back into leadership, and eventually hand day-to-day operations to a COO.

An org chart gives people positions. A decision framework gives them the judgement to act from those positions. Until the logic is written down and trusted, every line on the chart will lead back to you, however many people you hire. Install the logic alongside the people, and the structure you have built finally starts to carry the weight it was designed for.