Founder dependency is not one problem. The questions staff bring to the owner fall into two kinds: information dependency (asking because only the owner knows) and decision dependency (asking because the owner’s judgement or approval is genuinely required). The first can be routed away from the owner by giving the information a home; the second is not something to eliminate, only to narrow. Cut “reporting” without separating the two and the decisions the owner actually needs to see get buried along with everything else.
What this article covers
- The line between information dependency and decision dependency
- Six types of question that reach the owner
- Why information dependency builds up
- How to narrow decision dependency — one person holds the decision
- A four-step sequence for reducing founder dependency, and how to measure it
Founder dependency: why split it into two kinds first?
When a work design audit finds work piling up on the owner, the first step is to sort those requests into two kinds. Information dependency is when someone has to ask the owner to get information they need. Decision dependency is when the owner’s professional judgement or approval authority is actually required.
The two look identical on arrival. “Where are we on this?” and “Can we go ahead like this?” both land as one line in a chat app. The remedies are opposite. Information questions are ones the owner should not have to answer; decision questions are ones only the owner can answer. Left mixed, the owner spends the day answering and decisions still slow down, while staff learn that nothing moves unless they ask.
A widely used way to separate decision roles is Bain’s RAPID. Introduced in Rogers and Blenko’s 2006 Harvard Business Review article, it splits the people involved in a decision into Recommend, Agree, Perform, Input and Decide. As Bain explains, eventually one person decides, and giving the “D” to one individual ensures single-point accountability. Clearing out information dependency is how you leave that person with only the things that truly need deciding.
Six questions that reach the owner — a founder dependency map
Section 3.3 of our published work design report sample sorts requests reaching the owner into six types. The table below generalises it across industries (the original is written for a law firm, so it says “attorney’s judgement”). The first three are information dependency; the last three are decision dependency.
| Type | What it is | Target handling |
|---|---|---|
| Information | Checking client or case details | Look it up in the system |
| Status | Checking progress | Task view |
| Context | Checking earlier consultations or decisions | Work history |
| Approval | Signing off a deliverable or next step | Review and approval criteria |
| Professional Decision | Professional judgement and strategy | Owner’s judgement |
| Exception | Situations the normal rules cannot handle | Accountable person’s judgement |
Three kinds of information dependency: questions the owner need not answer
Information, Status and Context are questions whose answers already exist somewhere — a client’s contact details, which stage a job is at, what was agreed last time. They go to the owner because the answer lives only in the owner’s memory or the owner’s chat threads.
Three kinds of decision dependency: questions to keep with the owner
Approval, Professional Decision and Exception need human judgement, but not all of them need the owner. Approvals can be checked by a named person once the criteria are written down; exceptions go to whoever is made accountable for them. What finally stays with the owner is the decisions that require the owner’s expertise.
Why information dependency builds up — the information is not next to the work
Information dependency is usually a structural problem, not an attitude problem. When instructions and confirmations travel through chat, files sit in email and personal folders, and decisions are made on calls and in meetings, the only person who knows “where this job stands right now” is the owner, who was in every one of those conversations.
The time spent looking for information is a burden in its own right. In Microsoft’s Work Trend Index 2023 (31,000 people across 31 markets), 62% of respondents said they struggle with too much time spent searching for information in their workday. In a small organisation, the place people search is often the owner.
That is why the report sample does not add features. It connects clients, tasks, consultations, files, decisions and history around a single unit of work — for a law firm, the matter. Staff no longer need to remember everything going on in the company; they need to see the work in front of them and the context that work requires.
Decision dependency is narrowed, not reduced
Trying to “reduce” decision dependency tends to break up the owner’s authority, which lowers decision quality or means the same decision gets made twice. Section 5.4 of the report sample takes the opposite approach: leave the owner’s decision authority as it is, and remove only the trips to the owner made for simple information.
There are two ways to narrow it. First, attach review criteria to approvals. A written rule such as “if every one of these conditions is met, the person in charge checks it and proceeds; if any one is not, it goes to the owner” takes a large share of approval requests off the owner’s desk. Second, split what reaches the owner into three lanes.
- Action Required — work the owner has to act on personally
- Decision Required — work that needs professional judgement or approval
- Attention Required — changes the owner should know about, such as delays, risks or major client issues
Work that is progressing normally and needs no judgement from the owner does not go into any of the three lanes. The shorter the owner’s view, the faster decisions get made.
Reducing founder dependency in four steps
- For one week, write down every question that reaches the owner. Chat, phone or in person — just who asked what.
- Sort those questions into the six types above. The ratio of information dependency (Information, Status, Context) to decision dependency (Approval, Professional Decision, Exception) becomes visible straight away.
- For each information question, decide where its answer should live. Client details on the client record, progress on the task view, past decisions in the work history. Once the place exists, the next time that question goes there instead of to the owner.
- Write down approval criteria and who is accountable for exceptions. What remains with the owner should be professional decisions and cases that fall outside the criteria.
Measuring founder dependency without a savings percentage
Do not promise a figure such as “30% less time” up front. Once something unmeasured becomes the target, the work turns into hitting the number rather than improving. Count what can be counted instead. One of the 30-day review items in section 8.4 of the report sample is exactly this: “Are people still asking the owner for things they could check in the system?” Repeat step 1 after 30 days and the number of remaining information questions shows how far you have come.
Where this framework appears in a real report
The six-type map and the three lanes above are part of a work design report we actually delivered. Only details that could identify the client, such as the firm’s name, have been removed, and the full text is published as a sample. Read section 3.3 (people and decisions), 5.4 (reducing dependency on the owner) and 6.3 (how the owner works) together to see how this framework carries through from diagnosis to design to day-to-day operation. How to get the same audit is set out on the Operating System Audit page.
References
- Bain & Company — Decisions: Who does what? (RAPID)
- Harvard Business Review — Who Has the D? How Clear Decision Roles Enhance Organizational Performance (Rogers & Blenko, 2006)
- Microsoft WorkLab — Work Trend Index 2023: Will AI Fix Work?
Focus keyword: founder dependency
SEO keywords: founder dependency, information dependency, decision dependency, decision rights, work design, operating system audit, owner bottleneck
자주 묻는 질문
Where do we start if too many questions go to the owner?
Write down every question that reaches the owner for one week, then sort them into information, status and context (information dependency) versus approval, professional decision and exception (decision dependency). The first step is deciding where each information answer should live.
Should decision dependency be reduced too?
It should be narrowed, not removed. Written approval criteria and a named owner for exceptions leave the founder with only the decisions that need professional judgement.
How do we know it is working?
Do not promise a savings percentage up front. After 30 days, log the questions again the same way and count how many information questions remain.