Beyond the Founder's Calendar: Turning Growth Targets into an Operating System
Photo: Francisclarke, CC BY-SA 4.0, via Wikimedia Commons
Founder dependency rarely announces itself. It appears as a diary full of check-ins, a commercial channel where every significant decision waits for one person, and a growth target that is understood at board level but not by the team expected to deliver it. The test is simple: if the founder stepped away for a month, would the 2027 target still be owned, monitored and acted on? If the answer depends on daily proximity, the target is not yet a system.
For UK SMEs, this is not an argument for removing the founder. It is an argument for designing the target so that founder judgement is applied at the right points rather than at every point. The aim is a team-operated system: clear decision rights, a weekly scorecard, escalation triggers and a target brief concise enough to survive absence.
Dependency is a design flaw
Founder dependency is often treated as a cultural issue. The team is said to lack ownership, or the founder is said to be unable to let go. In practice it is usually an information and authority design problem. The team cannot act because it does not know which decisions it owns, which numbers matter this week, or when a variance is serious enough to escalate.
That is good news. Culture is slow to change. Decision rights, scorecards and triggers can be written down and tested. They also make the founder's role more deliberate: instead of being the default approver for everything, the founder becomes the person who sets the standard, reviews the exceptions and intervenes when the system asks for it.
Decision rights: who can say yes, no and not yet
Start with the five to seven decisions that most affect the target. In a UK SME these are often pricing exceptions, discount approval, hiring, campaign spend, customer escalations, supplier commitments and product exceptions. For each, name a decision owner, a consulted party and an escalation route.
Decision rights should be documented in the target brief, not inferred from seniority. A sales lead may own discounts up to 10%, with anything above that going to the commercial director. A delivery lead may own overtime up to a set monthly cost, with anything beyond that escalated to the founder. The point is not to remove judgement. It is to place judgement where it can be exercised quickly.
| Decision | Owner | Consulted | Escalate when |
|---|---|---|---|
| Discount up to 10% | Sales lead | Finance | Margin falls below agreed floor |
| Campaign spend up to £5,000 | Marketing lead | Commercial director | Pipeline coverage below target |
| Customer escalation | Account lead | Delivery lead | Renewal value above £50,000 |
| Overtime up to £2,000 per month | Operations lead | Finance | Backlog exceeds eight weeks |
The weekly scorecard: five lines, one owner
A scorecard is not a dashboard. It is a short, owned view of the few measures that tell the team whether the target is on track this week. Keep it to five or seven lines. Each line should show the metric, the target, the actual, the variance, the action and the owner.
For a revenue target, the scorecard might include qualified pipeline created, proposal conversion, average order value, gross retention and delivery capacity. Some are leading indicators and some are lagging. That is deliberate. The leading indicators give the team time to act; the lagging indicators confirm whether the actions are working.
The weekly meeting should be 30 minutes. The scorecard owner speaks first. The founder asks questions last. If a line has no action, it is not a scorecard, it is a report. The discipline of naming an action and an owner is what turns measurement into management.
Escalation triggers: the cord the team can pull
Escalation is often treated as an admission of failure. In a well-designed target system it is a normal control. Triggers should be numeric and time-bound. Examples include pipeline coverage below three times the quarterly target, retention below an agreed threshold, a key account at risk, delivery backlog beyond a set number of days, or spend above a defined limit without matching pipeline.
The trigger should name the escalation owner and the response window. If the trigger is hit on Monday, who is informed by Tuesday, and what decision is expected by Friday? Without that specificity, escalation becomes a conversation rather than a control.
The founder's role is to receive escalations, not to create them by asking for everything. A team that knows when to pull the cord is more likely to act early. A team that fears escalation will wait until the variance is too large to fix.
The target brief: one page that outlives the founder's diary
The target brief is the operating document for the year. It should fit on one page and answer a small number of questions: what is the outcome, why does it matter, who owns it, what can they decide, which indicators matter, what thresholds trigger escalation, and when is it reviewed?
A concise brief might include the target itself, the three leading indicators, the two kill criteria, the weekly scorecard owner, the escalation route and the main dependencies. It should be written for the team that has to act on it, not for the board that approves it. The founder may sign it, but the team should be able to run it.
The empty chair test
Run a practical test once a quarter. The founder is absent from one weekly scorecard meeting and one decision meeting. Who chairs? Who decides? What gets delayed? Record the gaps and fix them in the brief. Repeat the test until the answer is boring.
The goal is not to make the founder irrelevant. It is to make their intervention deliberate. A growth target that depends on the founder being in every room is a target with a single point of failure. A target that survives an empty chair is a target that the team can own, measure and adjust. That is the difference between a calendar full of check-ins and an operating system for growth.
