← Back to blog

Running off the inbox, not a plan

Watch a mid-market operations team for a single day and you will usually see the same thing. Everyone is busy from the first message to the last. Calendars are a wall of fifteen-minute syncs. Work does not arrive as a plan; it arrives as interruptions, each one urgent to the person who sent it. At the end of the day the team is exhausted and, if you ask, cannot quite tell you what they decided.

That is not a busy team. That is a team running off the inbox instead of a plan. The real command center of most operating businesses is not a strategy or a system. It is whoever's inbox is loudest that morning.

We bring this up because it is the most expensive operating habit we see in the mid-market, and almost no one has it on a list of problems. It does not show up as a number. It shows up as a feeling: we are slammed, we are underwater, we need more people.

Why the inbox wins

Reactivity looks like responsiveness, and responsiveness is a virtue. A team that answers fast feels like a good team. So the habit gets praised instead of questioned, even as it quietly sets the company's priorities by whatever arrived most recently.

There is no system of record, so decisions get re-litigated. When the answer to "why are we doing it this way" lives in a three-week-old thread, it may as well not exist. The same questions get asked and answered again and again, and each lap costs senior time.

No one owns how the work arrives. Functions own their output. Nobody owns the intake. So the channel by which work enters the company, the email, the ping, the hallway ask, never gets designed. It just accretes.

What it actually costs

Take a professional services firm with $80M in revenue. The operations lead fields, by a rough but honest count, around forty ad-hoc requests a week that should have been a standing process: status questions, re-approvals, "can you just," lookups that exist somewhere but no one can find. Each one is a small interruption. Together they consume most of a senior salary in pure switching cost, and they push the actual planning work into the evenings, where it gets done worse.

None of that is a line item. It is absorbed as "that is what the ops lead does." It is also the clearest signal a company can have that it owns workflows it has never built.

Why a tool does not fix it

The reflex is to buy something. A chatbot, an assistant, an automation platform. But bolting AI onto a reactive operation does not make it less reactive. It makes the reactivity faster. You automate the symptom, the quick reply, and leave the cause, the unbuilt process, exactly where it was. Six months later you have a faster inbox and the same underwater team.

The cause is not a missing tool. It is that the work was never mapped. Reactive work is almost always a process that should exist and does not. Every recurring interruption is an unbuilt system wearing the costume of a one-off favor.

What works instead

You do not fix this by telling people to be less reactive. You fix it by looking at how the work actually moves, finding the interruptions that recur, and building the few that carry the most load into real processes, owned by the company rather than by one person's willingness to keep answering.

That is workflow first, and it is unglamorous on purpose. Map the intake. Find the asks that repeat. Turn the top handful into systems that answer themselves. The goal is not to eliminate the inbox. It is to stop running the company from it.

One question for the COO

If you want to know whether your company runs on a plan or on its inbox, ask the person who runs operations:

What share of our team's week goes to work that arrived as an interruption rather than as part of a plan, and which of those interruptions is the same thing over and over?

If they can answer crisply and the share is low, you are in good shape. If the honest answer is "most of it, and yes, it repeats," you are paying for it every single week.


What we do at Joust

The Joust Focused Read on the command-center problem maps how work actually arrives in your operation, finds the recurring interruptions that are really unbuilt processes, and sizes what they cost you. Where it is worth building, we turn the loudest of them into systems you own, so the company runs on a plan instead of on whoever's inbox is loudest.

If your team is busy all day and still behind, book a 30-minute conversation. No deck, no sales pitch. Just the conversation.

Or email Ron Davis directly at ron@joustagency.com.

Share this

Ron Davis

Founder

Three decades building enterprise platforms. Started Joust to close the gap between strategy decks and the work they're supposed to change.

LinkedIn

← Back to all posts

Get in touch