Stop Making Your Team Pull Information: The Admin Overhead Quietly Eating Your Capacity

Picture an average Monday across your team. Before anybody makes a sale, builds a product, or delivers a single service, people are logging into various tools. They are running reports. They are trying to recall what happened last week, hunting for the note they scribbled, and piecing together which task comes next.That is not the work they were hired to do. That is the overhead of figuring out what the work even is.

Somewhere along the way, this became the default way of operating. Your team spends the first half hour to hour of every single day just trying to figure out what to do, not actually doing it.

I have started calling this admin overhead. It is the time people burn going to look for the work, recalling the tasks, and stitching one piece of information together with another piece before they can act on the thing they are actually responsible for. Across an organization, it adds up to an enormous amount of lost capacity that never shows up on any report.

Prefer listening? Check out this week’s Solo Session where I go even deeper on this topic.

The work isn’t the problem. Getting ready to do the work is.

What makes admin overhead so dangerous, is that it hides.

It does not show up as a line item. It is spread across every person and every role, a few minutes here and a half hour there, so nobody sees the total. The rep calls it getting organized. You call it Tuesday. Nobody calls it what it is, which is a second job you never hired anyone to do.

I worked with a few companies recently where we went after exactly this. In one case, somebody was pulling reports across a handful of different tools just to connect the data before they could take a single action. In another, the culprit was something as simple as following up on open quotes.

That second one is worth sitting with, because almost every business has some version of it. Following up on quotes is not complicated. Everyone knows the process. Everyone knows they are responsible for it. Yet these things either get pushed to the bottom of the list because they take too much time, or they fall off the list completely, because nobody has the time to go connect all the scattered pieces of data and information required to do it well.

This is past documenting a process. The process exists, and people know they own it. The breakdown is one layer down, in the sheer effort it takes to get ready to execute.

Push versus pull, and why the word “push” is going to bother some of you

Anybody who has spent time in lean or operations circles has heard push versus pull. The goal, as you may know, is to pull. You pull work at the demand of the customer. You do not build to a forecast and shove inventory down the line. Pull is the gospel.

So when I tell you the answer here is to push, I know that lands wrong for some of you but stay with me.

What we are pushing is not work. We are pushing information.

When you push the right information to the right person, you are not flooding the line with inventory nobody asked for. You are still working to the beat of the customer, because the thing you are enabling is something the customer ultimately wants. You are simply removing the non value added time, the hunting and the stitching, and handing the person what they need to go act.

Think of it as the full kit discipline from Theory of Constraints. On a production floor, you do not release a job until every part is staged and ready, because releasing a half kitted job just guarantees it will start, stop, and clog the line. Same idea here, you don’t hand someone a task until the context is staged with it. You take everything that is pertinent, every bit of contextual information, and you deliver it right to the person who can act on it.

The customer of that information is the person who has to do something with it. You meet their demand by doing the overhead for them. Technically it is a push. In practice, it is still pull, because it serves the moment of real demand. That distinction is the whole game.

What it looks like in practice

Take the quote follow up mention from earlier. The old way sounds something like this:

“Log into our system. Look at the last thirty days of quotes. Figure out which ones are still open and have not converted. Then check how many quotes we have per customer. Then take all of that and reach out to the right people.”

Every one of those steps is overhead. None of it is the conversation that actually moves a deal or relationship.

Now flip it. Same Monday morning, but this time the person opens their email or their task list and sees: reach out to Company XYZ. We have closed this many orders with them this quarter. They have quoted with us far more than that, so our win ratio with them is low. Don’t just ask if they are ready to order. Dig into why we keep losing these deals.

Same activity. Completely different result, because the system did the crunching and handed the person a decision instead of a research project. Their time goes to understanding, digging in, and having a real conversation that moves the relationship forward, instead of the task mentality of “I sent the follow up, never heard back.”

I built this for a small custom manufacturer with a two person business development team. Every day, the system pushes them a list: reach out to these accounts, here it is grouped by customer, here is the relevant history. Their setup was not fancy. They run a print specific management information system rather than a full ERP, with a CRM and a connector stitching things together. The connections had real limits. The system’s interface could not reach every field we wanted, and we could not hyperlink the way we hoped, so there were a few extra manual steps left in.

It did not matter. Just removing the mental overhead of running the report, filtering for the right things, and reconstructing the history before reaching out saved that small team somewhere in the range of fifteen to thirty minutes per person per day. That is one person freed up to do real outreach for a meaningful chunk of every week, on a process that used to quietly slip.

Quote follow up is just one place this lives. Accounts receivable is another favorite of mine. High value, high leverage, and almost always shoved down the list. Where are your receivables sitting, over thirty, sixty, ninety, a hundred and twenty days? Pull that together from wherever it lives, attach the context, and serve a touch point to the person who can collect the money. Same move. Different output.

Why now, and the trap inside the answer

Here is a fair question. Automation has existed for a long time. APIs and interconnectivity have existed for a long time. So why are we suddenly able to do this?

Because the new generation of AI driven tools makes the connections that used to be hard genuinely easy. The work of wiring scattered systems together and synthesizing the pieces, the part that used to take real engineering, is now within reach for far more businesses.

But there is a trap inside that answer, and it is the difference between automation and AI that most people gloss over.

Automation and code are deterministic. It is either this or it is that, every time. AI is different. It is exceptional at surfacing patterns and making connections, which is exactly the leverage we want. It also introduces inaccuracy. If you let AI aggregate the information and you push the result straight to your team without a layer of confidence or verification, you are now pushing people bad information to act on. That is worse than the overhead you started with.

So you use AI for what it is good at, finding and surfacing patterns, and you engineer accuracy and confidence around it so that what lands in front of your team is true and can be acted on. Leverage the pattern matching. Verify the output.

Where pushing goes wrong

This is not “automate everything and you are done.” Pushing goes sideways in two predictable ways.

The first is volume. If you push too much, you are just creating a new firehose, and people will start ignoring the list the same way they ignore everything else. The discipline here is to understand the intended output, the thing that actually enables the person and the process, and surface only enough to make that possible. Think minimum viable product. Less is more. There is a real sweet spot between giving people enough to act and burying them in so much that they are back to reading and thinking all day.

The second is accuracy, which we just covered. Push noise or push wrong, and you have taught your team not to trust the thing you built.

The way you avoid both is by bringing in the people closest to the work. They already know what the output needs to be, because they are the ones assembling it by hand today, right before they execute. They are the best source of truth for what belongs on the list and what is just noise.

This is a reorganization, not a new tool

I want to be clear about what this actually is, because it is easy to hear “AI” and “automation” and assume the answer is to go buy something.

It is not. This is building systems, and the way I define that is planning, then people, then process, then technology. In that order. Technology comes last, and its only job is to enable the people and the process to be effective. I would not encourage you to go shopping for another tool. I would figure out how to connect the tools you already have.

What we are really doing is reorganizing how you get from A to B. Your team is already doing all of this work today. That is the whole point. The admin overhead exists because a human being is currently going here, then there, copying that piece, pasting it over here, filtering it, sorting it, then hunting for one more piece based on what they just found. That is why people are burnt out. It takes enormous brainpower just to get to the starting line. It is honestly a little crazy what we have built into our systems over the years.

We are not adding work. We are taking the work people already hate, the connecting and the crunching, and moving it off their plate so their judgment goes where it belongs.

One caution worth naming. A lot of process improvement fails because it asks people to duplicate effort, to maintain the same information in one more place. If your fix requires someone to re enter what already lives somewhere else, you have not removed overhead, you have added it. Push from where the information already lives. Do not make people keep it in two places.

What to do Monday

You do not need to buy anything to start. You can begin this tomorrow.

Start by looking. Have some conversations with your team. Better yet, run a short time tracking sprint, even a manual one on a spreadsheet, and watch where the hours actually go. You are looking for the admin overhead, the recurring stretches where people are connecting data and getting ready to work instead of working. It is happening all across your team, your department, your org, wherever you sit.

Then quantify it, because that tells you where to start. If a follow up process eats five hours a week and most of that is data gathering rather than the actual outreach, you now know the size of the prize and whether it is worth automating.

Lastly, pick one. Start with the output in mind and build backward. Once you know exactly what the person needs in front of them to act, it becomes obvious where each piece comes from and how to bring them together. Then push it to the most appropriate person, creating that full kit moment that lets them be genuinely effective.

Final Thoughts

Most leaders try to create capacity the expensive way. They hire more people. They buy new equipment. They chase efficiency one task at a time. All of that has its place. But there is a quieter lever sitting right in front of you, and it costs nothing but attention.

Stop making your people pull. Stop forcing them to go find the work, reconstruct the context, and stitch the pieces together before they can do the thing you actually need. Push it to them instead, accurately and in the right amount, and let their time go to judgment and relationships and the work only they can do.

You already have the people. You already have the tools. You are already doing the work. The opportunity is not to do more. It is to stop making your team figure out what to do before they can do it.

That’s it for today.

See you all again next week!

Dave