The Lobbi Delivery Team
Operational Systems Engineering
There is a moment in every growing business where the tools that got you here start working against you. Email and spreadsheets are almost always those tools.
I am not anti-email. I am not anti-spreadsheet. Both are brilliant general-purpose tools. But there is a difference between using them as tools and using them as your operating system. When your email inbox is your task queue, your spreadsheets are your dashboards, and your reply-all threads are your decision log, you have crossed a line that most businesses do not realize they have crossed until the consequences start compounding.
This article describes three diagnostic signs that your business has crossed that line. If you recognize all three, you are not just inefficient. You are building operational debt that gets more expensive every month.
The Quiet Crisis
The U.S. Census Bureau reports approximately 33.2 million small businesses in the United States [1].
The overwhelming majority of them run core operations through some combination of email, spreadsheets, and individual memory. For a while, it works. Email is free, flexible, and everyone already knows how to use it. Spreadsheets can model anything. Together, they are the Swiss Army knife of business operations.
The problem is that Swiss Army knives are not surgical instruments. They get the job done when the job is small and simple. When the job gets bigger and more complex, they become a liability.
The IMF's World Economic Outlook projects steady but modest productivity growth for advanced economies [2]. Companies that want to outperform that baseline need to find and eliminate the hidden drags on their operations. Email-and-spreadsheet-driven operations are one of the biggest drags I see, especially in regulated industries where accuracy, accountability, and audit trails are not optional.
Intuit QuickBooks research shows that small business owners spend 21 hours per week on administrative tasks [3]. When I dig into what those hours look like, a huge percentage involves searching for information in email, updating spreadsheets manually, and re-creating reports that should already exist. These are not productive hours. They are tax you pay for running a business on tools that were never designed to be an operating system.
Sign 1: Work Status Lives In Private Inboxes Instead Of Shared Queues
Here is the test. Walk into your office, or open your Slack, and ask: "What is the status of the Johnson account renewal?"
If the answer requires someone to search their email, you have a problem.
When work status lives in private inboxes, nobody except the person who owns that inbox knows what is happening. The client's question about their policy is sitting in Sarah's inbox. The underwriter's response is in Mike's. The compliance approval is in a thread that copied four people, but only one of them realized it required action.
This is not collaboration. This is a collection of private work streams that happen to be about the same thing.
The Deloitte Tech Trends report identifies information silos as a persistent barrier to operational efficiency, noting that organizations struggle to derive value from data and workflows trapped in disconnected systems [4]. Email is the ultimate disconnected system. Every inbox is a silo. Every person has a different view of reality.
What this costs you in practice:
Handoff failures. When someone is out sick or on vacation, their work is trapped in their inbox. Nobody can pick it up because nobody can see it. In an insurance agency, this means client requests sit unanswered. In a mortgage company, this means files stall because the processor's inbox is the only place where the status of a condition is tracked.
Duplicate work. When two people cannot see each other's work, they sometimes do the same thing. I once worked with a financial advisory firm where two assistants both called the custodian to request the same transfer paperwork because neither could see that the other had already handled it. The custodian noticed. The firm was embarrassed.
Client frustration. When a client calls and gets a different person, that person has to say "let me check on that" and then go hunting through someone else's email or wait for them to respond to an internal message. The client can tell that nobody knows what is going on. In regulated industries where trust is everything, that impression is corrosive.
Invisible backlogs. If work lives in individual inboxes, you have no way to see the overall queue. How many renewal requests are pending right now? How many are more than five days old? How many have been touched versus how many are sitting untouched? You cannot answer these questions if the work is scattered across 10 inboxes.
The National Federation of Independent Business surveys consistently show that small business owners cite management of day-to-day operations as a primary challenge [5]. Inbox-driven operations make this challenge dramatically worse because they rob leadership of visibility into what is actually happening.
What shared queues look like instead:
A shared queue is simply a place where work items are visible to everyone who needs to see them. It could be a shared inbox. A task board. A CRM pipeline. A simple shared spreadsheet, yes, even a spreadsheet, if it is shared and maintained as the single source of truth instead of a copy on each person's desktop.
The key property of a shared queue is that any authorized person can see the status of any work item without asking someone else. When the client calls, whoever answers can see that the renewal is in progress, that the underwriter responded yesterday, and that the account manager is scheduled to review it today. No hunting. No waiting. No "let me check on that."
Sign 2: Critical Metrics Are Manually Compiled And Always Stale
Ask your operations manager how the team performed last month. If the answer takes more than a day to produce, you have a problem.
In most email-and-spreadsheet-driven businesses, performance data is assembled manually. Someone exports data from one system, copies it into a spreadsheet, adds formulas, formats it into a report, and sends it out. By the time the report is ready, the data is a week or two old. By the time anyone acts on it, conditions have changed.
The U.S. Chamber of Commerce's data on small business operations highlights that access to timely business intelligence is a differentiator for growing firms [6]. But "timely" is doing a lot of work in that sentence. A monthly report that arrives three weeks after the month ended is not timely. It is a historical document.
What this costs you in practice:
Delayed response. When a process is breaking down, you do not find out for weeks. That policy renewal backlog that started building two weeks ago? You would have caught it on day two if you had real-time data. Instead, you found out when clients started calling to complain.
Decision-making by feel. When leaders do not have current data, they rely on gut feeling. "I think we are doing okay.
" "It seems like volume is up." "I feel like we are getting behind." Feelings are not data. They are influenced by whatever happened most recently, not by the actual trend.
McKinsey's research on AI and analytics adoption found that data-driven organizations are 23 times more likely to acquire customers and 6 times more likely to retain them [7]. You do not need to be a data science operation to be data-driven. You just need current, accurate data about your basic operational metrics.
Metric manipulation. I do not mean intentional fraud. I mean the subtle bias that enters when a human is compiling the report. The numbers that are easy to find get reported.
The numbers that are hard to find get estimated. The exceptions that make the team look bad get footnoted or excluded. Over time, the report drifts away from reality. Nobody is lying. But nobody is telling the complete truth, either.
Report fatigue. When reports take days to produce, people stop asking for them. When people stop asking for reports, nobody notices the trends. When nobody notices the trends, problems compound until they become crises.
The Census Bureau's Annual Business Survey data shows that businesses with data-driven practices grow faster than those without [8]. But the barrier to data-driven practices is rarely the analysis. It is the data collection. When your data lives in spreadsheets that are manually updated, the collection burden is so high that current data is never available.
What real-time operational data looks like instead:
Real-time does not mean a fancy dashboard with blinking lights. It means: at any point during the business day, you can see where things stand without asking someone to compile something.
How many open items are in each stage of the pipeline? What is the average time items are spending in each stage? Which items have been stuck for longer than the target? How does this week compare to last week?
These are basic operational questions. In a system with shared queues and structured data, they are answered instantly. In an email-and-spreadsheet operation, answering any one of them is a research project.
Sign 3: Nobody Can Answer Ownership Questions In Under 60 Seconds
Here is the test. Pick any active piece of work in your operation and ask: "Who owns this right now?"
Not who started it. Not who will eventually finish it. Who owns it right now, at this moment? Who is the one person responsible for moving it forward?
If the answer takes more than 60 seconds, your ownership model is broken.
SBA research emphasizes that clear accountability structures are a hallmark of high-performing small businesses [9]. When work moves through email, ownership is ambiguous by default. The email was sent to three people. Which of them is responsible for acting on it?
The thread has 15 replies. Who has the current action item? The spreadsheet has five people listed as team members. Who is the lead?
What this costs you in practice:
Diffusion of responsibility. When multiple people are copied on an email, each one assumes someone else is handling it. This is not laziness. It is a well-documented psychological phenomenon. When responsibility is shared ambiguously, everyone's sense of personal ownership decreases.
The NFIB's economic trends data shows that quality of labor remains a top concern for small businesses [5]. But I would argue that a significant portion of what looks like a labor quality problem is actually an ownership clarity problem. The same people who seem unreliable in an ambiguous email-driven workflow become highly effective when given clear ownership in a structured system.
Dropped balls. In an email-driven operation, work gets dropped for a simple reason: nobody thinks it is theirs. The email came to five people.
Each one assumed one of the others was handling it. Three days later, the client follows up and nobody has done anything. This is not a people problem. It is a system problem.
Accountability gaps. When something goes wrong, a deadline is missed, a filing is late, a client is unhappy, the postmortem is always the same: "I thought you were handling that." "I did not see that email." "It was not clear that I was supposed to act on that." These are not excuses. They are accurate descriptions of what happens when work is managed through email.
In regulated industries, accountability gaps have regulatory consequences. When a compliance deadline is missed, "it was in someone's email and they did not see it" is not an acceptable explanation to a regulator. The Census Bureau's data on business formation and survival suggests that operational failures. not market failures, are the primary driver of business closures [1]. Accountability gaps are operational failures.
The phantom workload. When ownership is unclear, work becomes invisible. Items sit in limbo. not on anyone's to-do list, not explicitly abandoned, just forgotten. Over time, this phantom workload accumulates.
The team feels busy but cannot point to what they are accomplishing. Leadership feels like headcount should be enough but the work is not getting done. The root cause is not insufficient capacity. It is work that has no owner.
What clear ownership looks like instead:
Every piece of work has exactly one owner at any given time. The owner is visible to everyone. When ownership transfers, from intake to processing, from processing to review, from review to completion, the transfer is explicit and recorded.
This does not require complex software. It requires a shared system where work items are visible and each one has a single name next to it. A shared board with columns for each stage and a person assigned to each card. A CRM with pipeline stages and owners. Even a well-structured shared spreadsheet with an "Owner" column that is actively maintained.
The key word is "actively maintained." A spreadsheet with an Owner column that nobody updates is worse than no spreadsheet at all, because it creates the illusion of clarity while actually obscuring reality.
The Compounding Danger
Each of these three signs is a problem on its own. Together, they create a compounding effect that gets worse over time.
When work status is in private inboxes (Sign 1), you cannot compile accurate metrics (Sign 2), and you cannot determine ownership (Sign 3). When you cannot determine ownership, work falls through the cracks, which makes the metrics look worse, which makes people try to hide things in their private inboxes to avoid scrutiny. The cycle feeds itself.
Deloitte's research on technology adoption notes that operational dysfunction tends to compound rather than stabilize [4]. Systems that are "good enough" at 10 employees become bottlenecks at 25 employees and break catastrophically at 50. The email-and-spreadsheet approach has a carrying capacity, and most businesses hit it well before they realize what is happening.
The McKinsey State of AI report found that organizations with structured operational data are in a dramatically better position to adopt AI and automation [7]. The inverse is also true: organizations whose operational data is trapped in email threads and manually maintained spreadsheets are effectively locked out of the AI productivity gains that their competitors are capturing.
This is the compounding danger. You are not just dealing with today's inefficiency. You are falling behind a curve. Every month that your operations run through email and spreadsheets, the gap between you and companies with structured operations widens. The structured companies can adopt new tools, onboard new employees, absorb new volume, and respond to market changes faster. You cannot, because you cannot see your own operation clearly enough to improve it.
The Uncomfortable Truth About Why This Persists
If email-and-spreadsheet operations are so costly, why do companies stick with them?
Three reasons.
Familiarity. Everyone knows email. Everyone knows spreadsheets. There is no training curve.
No implementation project. No change management. The tools are already there. The path of least resistance is to keep using them.
Flexibility. Email can carry any message. Spreadsheets can model any data.
There are no constraints, no required fields, no mandatory steps. For a business owner who values agility, this flexibility feels like freedom. It is. But freedom without structure is just chaos with good intentions.
Fear of disruption. Moving off email-and-spreadsheet operations means changing how people work. People resist change, especially when the current system, however dysfunctional, is at least familiar.
The U.S. Chamber of Commerce's surveys on small business technology adoption show that implementation complexity is a primary barrier to new tool adoption [6]. The irony is that the complexity of switching is almost always less than the ongoing complexity of staying.
What Moving Forward Looks Like
You do not need to replace email and spreadsheets overnight. You need to identify which of the three signs is causing you the most pain and address that one first.
If Sign 1 is your biggest problem (work status in private inboxes), the first move is establishing a shared queue for your highest-volume or highest-risk process. This might be a shared inbox with rules, a simple Kanban board, or a CRM pipeline. Start with one process. Prove the value. Expand.
If Sign 2 is your biggest problem (stale metrics), the first move is identifying the three to five numbers that matter most to your operation and finding a way to generate them automatically or semi-automatically. This might mean centralizing data entry into a single system, building automated reports from your existing tools, or simply establishing a daily standup where numbers are reported verbally.
If Sign 3 is your biggest problem (unclear ownership), the first move is establishing a rule: every piece of active work has one owner, and that owner is visible to the team. This can be as simple as a whiteboard with names and assignments. The medium does not matter. The discipline does.
The Intuit QuickBooks data suggests that even small improvements in administrative efficiency compound significantly over time [3]. You do not need to solve everything at once. You need to start.
A Note For Regulated Industries
If you operate in insurance, mortgage, financial advisory, healthcare, or any other regulated industry, the three signs carry an additional layer of risk.
Regulatory audits. When a regulator asks to see the history of a client interaction, "it is in someone's email" is not a compliant answer. Regulated industries require audit trails. Email threads are not audit trails. They are fragmentary, unsearchable, and dependent on individual retention practices.
Fiduciary obligations. When a financial advisor's recommendation to a client is documented only in an email exchange, the advisor is one accidental deletion away from losing their evidence of suitability. When an insurance agent's coverage discussion with a client exists only in a reply chain, the E&O exposure is significant.
Continuity requirements. Many regulated industries have business continuity requirements. If your operations depend on access to individual inboxes and personal spreadsheets, what happens when a key employee is unavailable? Some states and regulatory bodies have explicit requirements around operational continuity that inbox-dependent operations simply cannot meet.
The NFIB surveys show that regulatory burden is consistently among the top concerns for small business owners [5]. Ironically, running operations through email and spreadsheets increases your regulatory burden because it makes compliance harder, not easier. Structured operations with shared queues, automated metrics, and clear ownership are not just operationally superior. They are compliantly superior.
The Path Forward
If you read this article and recognized your business in all three signs, you are in good company. Most small businesses in regulated industries are in the same position. The tools that worked when you were small are straining under the weight of growth, complexity, and regulatory requirements.
The good news is that you do not need a massive technology overhaul. You need clarity about where your operations are breaking down and a structured plan to address the highest-impact areas first. Move one process from private inboxes to a shared queue. Make one critical metric available in real time. Clarify ownership for one workflow. Then build from there.
At The Lobbi, we see this pattern constantly. Companies that are growing, ambitious, and well-run on the surface, but struggling underneath because their operational infrastructure has not kept pace. We help these companies map their real operations, identify the three signs, and build structured systems that scale.
If your team is spending too much time searching for information, compiling reports, and figuring out who owns what, a discovery call is a good place to start. We will look at your actual operations. not the policy version, the real version, and show you where the biggest wins are.
Book a discovery call at thelobbi.io/discovery.
Topic clusters
Ready to see where the friction is?
The Lobbi's Operations Discovery maps your workflows, identifies your highest-impact bottlenecks, and gives you a clear picture of what's possible.