You have hired experienced people. You have told them they can decide. By the end of the week, the same kinds of questions are back in your calendar.
Decisions often return to the founder because the team lacks a usable boundary for ownership: what it can decide, the information it needs and when an exception should come back. Hiring and encouragement help, but they do not establish that boundary on their own.
Follow one decision through the business
Take a recent customer exception. Who first recognised the issue? What did that person know? Where did the decision wait, and what information was missing when it reached you?
The answer may reveal a genuine need for founder judgment. It may also reveal a price concession with no agreed threshold, a handoff between sales and delivery that nobody owns, or a team that has learned a decision will be reopened later.
Those are different problems. Treating them all as reluctance to take responsibility makes the response less precise.
A boundary is more useful than a broad instruction
Consider a delivery lead who needs approval for every small customer concession. Telling the lead to be more commercial leaves several questions unanswered. Which concessions are allowed? What cost can the business absorb? Which customer commitments change the risk?
A decision rights agreement would name the decision, its owner, the limit and who must be informed. It would also make escalation useful by stating what the founder needs to see when the issue does return.
This is an illustration of an operating pattern, not a JRDN case or a claimed result. In a real business the thresholds must come from its economics and obligations. A copied authority matrix can look complete while failing the decisions people actually face.
The founder's response is part of the system
If you routinely reverse decisions made within the agreed boundary, people will start seeking approval again. If every exception becomes a new rule, the team may wait because it cannot tell which rule applies.
That does not make you the problem. It means the operating agreement needs to include your role as well as theirs. You may need a review rhythm that lets you see patterns without stepping into each transaction.
Some decisions also carry an identity question. What remains yours when the team no longer needs your answer every day? That can be useful coaching work. It should be recognised as personal work rather than hidden inside a process redesign.
Run a small decision review
Choose one recurring decision for the next two weeks. Record each instance, its owner, the information available, where it waited and whether it returned to you. Agree a boundary with the people who actually make it.
At the review, look at the time taken, rework, avoidable escalation and the quality of the decision. Ask whether the new arrangement works when the case is awkward, rather than only when it is straightforward.
Do not begin by documenting every process in the business. A single recurring decision can expose whether the constraint is authority, information, capability or the way the founder intervenes. That evidence gives the next change a clearer purpose.
Operations and coaching have different jobs
In Founder Operations Advisory, I examine workflows, handoffs, decision rights, routines and measures. The fuller engagement develops process maps, operating procedures and an operating rhythm with the people who will own them.
If your main question is how you lead through the change, individual coaching creates a separate space to examine it. I agree the purpose and boundary of each engagement explicitly.
Bring one decision that keeps returning to you to a free 30 minute discovery conversation. It is a useful way to establish which kind of work would help first.
Written by Nirmalya Mukherjee, founder of JRDN Advisory and ICF Associate Certified Coach. This article is a practical application of the JRDN Founder Operations Advisory method. It contains no reported client outcome.