DECISIONS AND ORGANISATION

The company grows. The decisions stay with the founder.

When approvals pile up with one person, we clarify who decides, within what limits and when to escalate.

BUSINESS SCENARIO · AN EXAMPLE OF THE HUMX APPROACH

THE CONTEXT

A founder-led company that has grown from a small team to a few dozen people, with production or services across several sites. The founder built the company decision by decision and remained the point everything passes through. The scenario is illustrative: it describes a type of situation, not a client.

WHAT YOU SEE

The symptoms need no interpretation: prices and discounts are approved one by one, exceptions to payment terms go up to the founder, and a hire already in the budget waits for a signal from them. Meetings are postponed until they reply.

The effect is twofold: the founder works in operations, and the people who should be deciding lose the habit of doing so.

POSSIBLE CAUSES

This is not a diagnosis, these are hypotheses to check. The roles were described through responsibilities, not through decisions. The limits were never put in figures, so everyone asks to be safe. There is a history of reversed decisions, and people have learned that asking is cheaper. Or the information a decision rests on does not reach the person who should be deciding.

Hiring a director does not solve this by itself. A new title without written limits reproduces the same approval route.

WHAT WE CLARIFY

You pick three recurring decisions — the ones that required the most approvals over the past two months, not the ones that matter most in principle. For each, four things get written down: who decides, within what limit they decide alone, from what threshold they escalate, and to whom.

The rest stays explicitly with the founder: investments above a set ceiling, hires outside the approved budget, partnerships and changes of strategy. What stays at the top matters as much as what moves down.

AN EXAMPLE

Commercial discount: the sales lead decides alone within the approved discount limit and on standard payment terms. Above the limit or outside those terms, they escalate — with the client history and the reason for the request, not just the figure. The rule fits in one paragraph and is told to the team once, clearly.

THE STEP FOR NEXT WEEK

For one week, write down every approval you were asked for: who asked, what they asked, what you decided and how long it took. That list is the raw material for the three decisions to delegate — and usually fewer things repeat than it seems.

WHAT YOU TRACK

The time from request to approval, how many decisions come back to the founder after being delegated, and how many exceptions appear against the written limits. These are process indicators: they show whether the rule is being applied, not that the business is doing better.

QUESTIONS

How do I set the limit if I have no written history?

Start from what you have already approved. Take the last ten requests of the same kind, see up to what value you said yes without much thought, and put the limit there. It is a starting limit, reviewed after two months, not a final rule.

What do I do if the decisions come back to me anyway?

Ask each time why it came up: the information was missing, the limit was missing, or the confidence that the decision would not be reversed was missing. The three answers call for different fixes, and answering the request instead of the person who should have decided confirms the old route.

Does this sound familiar?

Tell us which decisions come up to you most often and we will tell you where we would start.

Working with managers on delegation and feedback is described in Training & Leadership Development.

Discuss your situation →
SERVICES
01 Recruitment For the roles that matter. →
02 Outsourcing & Payroll HR expertise without an in-house function. →
03 HR digitalisation Processes simplified, then automated. →
04 Training & Leadership Managers who lead, not just coordinate. →
05 HR Audit What is not working, and where the risk sits. →
EXPLORE
Job openings →
For candidates →
Situations in organisations →
Resources →
About HUMX →
CONTACT Let's talk →
RO EN HU DE