Decision Rights Implementation Guide for Founders

A client proposal is ready to go, but it waits in someone’s drafts because only you can approve the scope. A capable manager spots a delivery issue, but pauses until you are free. You return from a holiday to find a queue of small decisions that nobody felt authorised to make. This decision rights implementation guide is for founders who are tired of being the default answer to every operational question.

The problem is rarely that your team lacks intelligence or care. More often, the company has never made the boundaries of authority explicit. People know what needs doing, but not who can decide, what standard to apply, or when a decision genuinely needs to come back to the founder.

That uncertainty turns you into a human routing system. It slows the business down, trains good people to wait, and makes every attempt to step back feel risky. Clear decision rights replace that dependence with a practical operating system.

Decision rights are not delegation

Delegation means assigning a task. Decision rights define who has the authority to choose a course of action, within what limits, and with what level of consultation.

You may have delegated client onboarding to an operations lead, for example. But if they still need your sign-off on timelines, exceptions, resourcing changes and client communications, you have delegated activity without delegating judgement. The work has moved, but the dependency has not.

This distinction matters because founders often mistake a busy team for an independent one. A team can complete plenty of work while the founder remains the approval point for all meaningful decisions. The result is the same familiar pattern: you are interrupted all day, decisions accumulate when you are unavailable, and your people become hesitant in areas they should own.

Michael Gerber’s central warning in The E-Myth Revisited still applies: a business cannot rely on the heroic availability of its owner. Decision rights are one of the mechanisms that turn that principle into day-to-day behaviour.

Start with the decisions that trap you

Do not begin by trying to map every decision in the business. That turns a necessary exercise into a documentation project nobody finishes. Start with the decisions that repeatedly pull you back into the operation.

For two weeks, keep a simple decision log. Each time someone asks for your input, record the decision, who raised it, how often it occurs, the consequence of getting it wrong, and whether it truly required your judgement. Include requests arriving through messages, meetings, calls and those casual desk-side questions that are easy to forget.

Patterns appear quickly. In an agency, the founder may be approving scope changes, solving client tension, prioritising delivery work and deciding who can speak to a prospective client. In an expertise-led firm, the bottleneck may be technical judgement, quality exceptions or the final wording of recommendations.

Then sort the decisions into three groups: recurring operational choices, occasional exceptions, and truly founder-level calls. The first group is where you should act first. These decisions are frequent enough to consume your attention, predictable enough to define, and low enough in consequence that they should not require you every time.

If you are unsure where to begin, look for the point where work waits. Waiting is evidence. It shows where authority is unclear or confidence is missing.

Assign one accountable decision owner

Every repeatable decision needs one named owner. Not a committee, not a vague department, and not a manager who must still check with three other people before acting.

That owner does not need absolute freedom. They need a clear mandate. For each decision, define the outcome they are responsible for, the boundaries they must work within, the people they must consult, and the circumstances that require escalation.

Take a common example: a project manager needs to respond when a client requests work outside the agreed scope. A weak instruction is, “Use your judgement.” A useful decision right is, “You may agree minor changes that do not alter the delivery date or require another team member. For anything beyond that, offer the client two defined options and involve the account lead before confirming.”

The difference is not bureaucracy. It is usable authority.

Be careful not to assign ownership to the most reliable person without checking their capacity. That simply moves founder dependence to a new bottleneck. The right owner is usually the person closest to the information, sufficiently experienced to make the call, and able to explain the reasoning afterwards.

Build a decision card people can actually use

Long policy documents do not help someone facing a real client issue at 4.30pm on a Thursday. For high-frequency decisions, create a one-page decision card in plain language.

A good card answers five questions:

• What decision is this person authorised to make?
• What result are they trying to protect?
• What rules, thresholds or non-negotiables apply?
• Who needs to be consulted before the decision is final?
• When must the issue be escalated, and to whom?

Add two or three examples from real situations your team has faced. Examples matter because people often understand rules in theory but hesitate when the facts are slightly different. Show the normal case, a permitted exception and an escalation case.

Keep the language specific. “Keep clients happy” is not a decision standard. “Respond within one working day, protect the agreed delivery plan, and do not promise work that the delivery lead has not confirmed” gives someone something they can act on.

Decision cards should not attempt to eliminate judgement. They should make good judgement easier and escalation more intentional.

Implement decision rights in a live area first

Do not announce a company-wide authority restructure and hope it sticks. Choose one operating area where founder involvement is frequent and visible, such as project delivery, client communication or recruitment. Pilot the approach there for 30 days.

Start by explaining the reason for the change. Your team needs to hear that this is not the founder disappearing or avoiding accountability. It is a deliberate move to make the business faster, clearer and less dependent on one person.

For the first few weeks, ask decision owners to record the calls they make and their reasoning. Review a small sample with them weekly. The purpose is coaching, not taking back control. If you overrule every imperfect decision, you will teach people that the new authority was never real.

Instead, distinguish between poor judgement and a poor decision framework. If several people hesitate at the same point, or make inconsistent choices, improve the decision card. If someone repeatedly ignores a clear boundary, address that directly through training, support or a change in responsibility.

You will also need to change your own behaviour. When someone brings you a decision they own, resist answering immediately. Ask: “What do you recommend?” Then ask which boundary or standard they used. This reinforces thinking rather than dependence.

Some decisions should still reach you. Founder-level calls often involve a major change in direction, a relationship that only you can credibly handle, or a choice with consequences outside an established operating boundary. The aim is not to remove the founder from every decision. It is to reserve your attention for decisions that genuinely need it.

Measure whether authority is actually moving

A tidy responsibility chart proves very little. Look at behaviour instead. Are approvals happening without you? Are decisions being made closer to the work? Is the team escalating with a recommendation rather than a blank question? Can you be unavailable for a day without a pile of delayed work waiting on your return?

Watch for two failure modes. The first is false delegation, where a manager has nominal authority but keeps seeking reassurance. The second is uncontrolled autonomy, where boundaries were never defined and decisions begin to vary wildly. Both are fixable, but they require different responses: coaching for the first, clearer standards for the second.

The Optional Founder’s 12 Chains Diagnostic treats decision dependency as a distinct constraint because it rarely stays contained. When approvals depend on the owner, client service slows, managers lose confidence and the founder’s calendar becomes the operating system.

Clear decision rights do not ask you to trust blindly. They give your people a defined arena in which to earn and exercise trust. Pick one decision that has no business waiting for you tomorrow, name its owner, set the boundaries, and let the company prove it can move without your constant sign-off.