You Are the Bottleneck: How to Stop Being the Human Spreadsheet

How do I know I am the bottleneck?

You are the bottleneck when the business waits for your read of the numbers. If you step out for three days, reporting stops.

Owners say: “If I am out for three days, reporting stops.” They also say: “Everything escalates to me, because being wrong is expensive and escalating is free.”

Check yourself against this list:

• You build or fix the weekly report yourself.
• Big decisions wait on your look at the numbers.
• Managers ask you instead of looking it up.
• You hold the real picture in your head, not in a system.
• You are the only one who can reconcile two reports.
• Vacation means checking in daily.

Three or more of these means you are the human spreadsheet. It is a wiring problem and not a people problem. Your team is not weak. The numbers have no home but you.

What is the one report to take off my desk first?

Take off the weekly cross-department report: the one that pulls sales, cash and ops into a single picture. It is the report only you can assemble.

Why this one: it uses the most of your time, and the most people wait on it. Every other report is smaller.

Name it. Write its title at the top of a page: “Weekly business picture.” Then list what is in it.

How do I hand it off?

Document the report in four steps, then hand it to one manager for four weeks of shadow runs.

1. List every number in it. Write the source tool next to each.
2. Write the definition of each number. One line per number.
3. Record yourself building it once. Screen record. Talk through each choice.
4. Name one owner. One manager, not a committee.

Then run it twice side by side. You build yours. The manager builds theirs. Compare. Where they differ, a definition is missing. Fix that line.

After four weeks, the manager runs it alone. You get the report. You do not build it.

How does a manager run the numbers?

A manager runs the numbers when the data is in one place and the definitions are written down. Without those, they must guess what you would do.

Give the manager:

• A source for each number, not a copy.
• The definition page.
• A rule for what counts as an exception: a number outside its usual range, or a customer or order that needs a call.
• Permission to act on exceptions below a set dollar limit.

Your job changes from “build the report” to “review exceptions.” You see what is wrong, not everything that is right. Set the limit yourself. Raise it as trust grows.

This is where one place for your data pays for itself. The manager reads from the same source you did, so numbers match.

What happens if my key ops person leaves?

Half your numbers and processes may leave with them. Owners say it plainly: “If our key ops person got hit by a bus, half our numbers and processes would disappear.”

Run this test today. Ask your ops lead to list every report and process only they run. Count them. Each one is a key-person risk.

Then take two steps:

1. Write each process in plain steps in one shared place.
2. Pick a backup name for each. Have the backup run it once.

The sheets guide shows how to map the files that sit on one person’s laptop. Start with the sheets only that person touches.

What does it look like when it works?

One manufacturer ($6.8M) got 32+ owner hours back every week. Examples describe particular client projects, not a prediction of your results.

The change was where the numbers lived. They moved from the owner’s desk into a place the team could read. Reports stopped waiting on one person.

Find your own number first. Track your hours for one week: how many went to reports, approvals and chasing? That is vital sign 12 in the 12 numbers every owner should know. If you want the built version of this handoff, the Business Brain is the name for it. The steps above work with a pen and a good manager.