Managers solving problems before they reach the owner — in a business setup consultancy, that single sentence is most of what “scaling” actually means. If it is what you keep writing in annual plans, and what keeps not happening, this article offers a specific reading of why. The common explanations — they lack initiative, they fear mistakes, good people are hard to find — may each hold a grain of truth, but they all point at the managers. The structural explanation points at something missing between you and them: a recognition layer. Most escalations are not requests for your authority. They are requests for your pattern-matching — and pattern-matching, unlike judgment, can be written down and handed over.
The moment it happens
Annual planning—if this is you, you want managers solving problems before they ever reach your desk.
The plan says “empower the team.” The reality arrives at 8:14 the next morning: a client is upset about a visa delay the government caused; your manager forwards the thread with one line — “how should we respond?”
You know the answer in four seconds. Not because you are smarter — because you have seen this exact situation forty times and they have seen it four. By evening there have been five more of these, each small, each solvable, each yours. The annual plan and the daily inbox are describing two different companies.
Why this keeps happening
We hold no external data on this one, so take what follows as a working diagnosis to test inside your own firm — many owners we speak with recognize it immediately. When a manager escalates something you find obvious, the missing ingredient is usually not courage or intelligence. It is classification. You look at the angry-client thread and instantly know which of the forty prior situations it rhymes with, what the owner-level intent is (“protect the relationship, concede nothing on compliance”), and therefore what to do. The manager sees a novel crisis. They escalate to borrow your recognition — your ability to say which situation this is — and the decision rides along with it.
Notice that nothing in your company documents recognition. Job descriptions list responsibilities. SOPs list steps. Neither says: here are the twelve situations this role keeps meeting, here is how to know which one you are in, here is what I want protected in each. So every judgment call routes to the only place the pattern library lives — your memory.
The honest limit: whether this is your firm’s pattern is checkable only one way — read your last twenty escalations and ask of each, “was this a request for permission, or for recognition?”
The prescription
There is a precise parallel in advertising’s hardest problem, and it is where Eugene Schwartz was at his most surgical in Breakthrough Advertising. Facing readers who cannot yet recognize their own need, the ad must not argue, promise, or instruct — it must first identify: name the reader’s situation so exactly that they say “this is me,” because recognition is the gate through which all correct action passes. His identification headline sells nothing; it classifies the reader, and only then does the persuasion begin. Your managers stand before the same gate. Give them identification first, instruction second.
The working tool is a situation map for each role. A worked example for a client-services manager in a setup consultancy — three entries of the twelve: Situation: “Client angry about a government-side delay.” How to recognize it: anger aimed at us, cause outside us, deadline pressure real. Owner’s intent: keep the relationship, never blame the authority in writing, give a dated next step. Manager acts alone; escalate only if the client threatens formal complaint. Situation: “Client requests something non-compliant.” Recognition: the ask would breach licence terms, however casually phrased. Intent: refuse warmly, offer the compliant route, document. Always yours to see afterward, never to approve first. Situation: “Client mentions a competitor’s renewal offer.” Recognition marks, intent, boundary — likewise. Twelve situations cover, in most firms, the great majority of a role’s escalations. The map is your pattern library, finally outside your head.
What to do this week
- Collect the last 20 escalations from one manager. Label each: permission, information, or recognition. Confirm the diagnosis before building anything.
- Draft that role’s situation map — aim for ten to twelve situations — using the escalations as your source material.
- For each: recognition marks, your intent in one sentence, and the escalation boundary.
- Review it with the manager and let them rewrite the recognition marks in their own words. Their phrasing is the test that it transfers.
- New rule for one month: any escalation must arrive labeled with its situation number — or as a proposed new entry for the map. Watch the desk clear.
Where Kamai Ads fits (only if you want help)
We are a marketing firm, so our piece of this is the funnel: building the positioning and lead-handling frameworks that let your team run marketing conversations without you refereeing each one — with no lead promises attached, because honest people do not sell those. The 48-hour marketing audit (1,000 AED) shows where your current funnel routes judgment to the owner. WhatsApp us via kamaiads.com.
