240 - Count Your Sign-Off Decisions
How many decisions need founder sign-off each week? This episode shows why the number is a structural diagnosis, not a workload metric. Learn how unclear decision rights create dependency, how mapping authorization and escalation reduces founder-only decisions, and a practical exercise to build structural independence one decision at a time.
Count Your Sign-Off Decisions
Here is a question most founders have never actually answered: how many decisions require your personal sign-off each week? Not a rough estimate. Not “a lot.” The actual number. If you counted every approval, every escalation, every “let me check with the founder” moment from last week, what would that number be? Most founders don’t know, and not knowing is part of the problem.
Because that number is not just a workload metric. It is a structural diagnosis. It tells you precisely how much of your business’s operating capability lives inside your head and your calendar rather than inside the system. A business where 80 decisions a week require your sign-off is not an 80-decision problem. It is an architecture problem. Each of those decisions is a moment where your business could not move without you. Dependencies. Threads connecting everything back to one person.
I worked with a founder who ran a 25-person business and could not leave for more than three days without things starting to slip. He assumed it was a team capability issue. He had hired well. The people were good. The issue was not the people. It was that the business had no authorization structure. No clear decision rights. No framework for who could decide what without checking. The default for anything ambiguous was the founder. And in a growing business, ambiguity is everywhere.
When we mapped decision rights properly, who owns which category, what thresholds exist, what gets escalated and what does not, the decisions that genuinely required him dropped from roughly 60 a week to around 12. Same team. Same complexity. Different structure. That is the shift.
Structural independence is not about trusting your people more. It is about designing a system where trust does not have to be tested in every situation. Where your team has clear authority, clear scope, and clear escalation paths. Where the answer to “who decides this?” is already built into the organization, not waiting for you to show up.
Here is the exercise for this week. Count the decisions. Write them down as they come in for three days. Then sort them into two columns.
Column A: decisions only you can make. Strategic direction. Significant resource allocation. Relationships that are genuinely yours.
Column B: decisions you are making because there is no one else.
Column B is your architecture backlog. It is the structural work that will actually free you. Most founders find Column B is much longer than expected. That is not failure. That is clarity.
Start with one decision from Column B. Decide who should own it. Write down the authority they need. Transfer it. See what happens. That is how structural independence is built. Not in one transformation. One decision at a time.
Highlights:
00:00 Count Your Decisions
00:13 Workload vs Structure
00:27 Founder Bottleneck Story
00:43 Fixing Decision Rights
01:06 Track and Sort Decisions
01:21 Your Architectural Backlog
Links:
Website: https://www.marcogrueter.com/
LinkedIn: https://www.linkedin.com/in/marcogrueter/
Transcript:
How many decisions required your personal sign off last week? Not roughly the actual number. Most founders do not know, and that is part of the problem. That number is not a workload metric. It is a structural diagnosis. It tells you how much of your business operating capacity lives in your head versus in the system.
I worked with a founder 25 person business. He could not leave for a week without things starting to slip. He assumed it was a team problem, but it was not. It was an architectural problem. No clear decision rights, no framework for who could decide what without checking, default for anything ambiguous:
The founder. when we met decision rights properly, the decisions that generally needed him dropped from around 60 a week to 12. Same team, same complexity, different structure. This week, count your decisions for three days, sort them. One column is what only you can decide. The other one is what you are deciding because nobody else has authority.
The second column is your architectural backlog.