What Should I Read Into When Everyone Accepts Inefficiency as Normal?

2026-10-15T19:46:07Z

Owen phillips22: Created page with "<html> When a team says, “That’s just how we do it,” they may be describing a harmless preference. Or they may be pointing at a business opportunity hiding in plain sight. In service businesses, inefficiency often becomes part of the furniture. A client request arrives by email, gets copied into a spreadsheet, is discussed in chat, and then has to be found again when someone prepares an invoice. Everyone knows the process is awkward. Everyone has a worka..."

<html> When a team says, “That’s just how we do it,” they may be describing a harmless preference. Or they may be pointing at a business opportunity hiding in plain sight. In service businesses, inefficiency often becomes part of the furniture. A client request arrives by email, gets copied into a spreadsheet, is discussed in chat, and then has to be found again when someone prepares an invoice. Everyone knows the process is awkward. Everyone has a workaround. And because the work still gets done, no one treats the friction as urgent. That reaction is worth paying attention to. Persistent frustration can be the seed of a durable business, a better internal system, or a more profitable way to deliver a service. But inefficiency alone does not prove there is an opportunity. The useful question is not simply, “Is this process clunky?” It is: “Who pays for the clunkiness, how often does it happen, and would they change their <a href="https://www.inc.com/benjamin-laker/why-the-best-business-ideas-come-from-the-messiest-workflows/91350475">inc.com</a> behavior to avoid it?” To answer that, look beyond the annoyance. Look at the workarounds, the handoffs, the hidden costs, and the expectations being reset by new tools. That is where workflow inefficiency becomes more than a complaint—and where status quo bias can make a real business opportunity harder to see. <h2> When “Normal” Is a Warning Sign</h2> Teams normalize friction because they adapt to it. They create a checklist, assign someone to chase approvals, or keep a private spreadsheet that makes a broken process survivable. Over time, the workaround becomes the process. New employees learn it as if it were an intentional design choice. This is one form of status quo bias: the tendency to prefer the current arrangement simply because it is familiar. In a busy agency, questioning a workflow can feel like extra work. People may think, “We know this is imperfect, but changing it could disrupt client delivery.” So they tolerate the known cost rather than risk an uncertain improvement. <img src="https://images.pexels.com/photos/12556887/pexels-photo-12556887.jpeg?auto=compress&cs=tinysrgb&h=650&w=940" style="max-width:500px;height:auto;" ></img> The cost, however, is rarely just the minutes spent on a task. A missing email can delay a project. A delayed approval can push work into an already full week. An invoice that depends on someone remembering which deliverables were completed can create billing delays or lost revenue. Repeated across accounts and months, small delays become a margin problem. That’s why “everyone accepts it” should prompt investigation—not an automatic verdict. It may indicate that the pain is too minor to solve. It may also indicate that the people experiencing it have little power to change it, have never seen a workable alternative, or assume the cost is simply part of the job. <h2> Frustration Is a Clue, Not a Business Plan</h2> Many durable businesses begin with frustration. Someone gets tired of repeating a task, coordinating too many people, or paying for a tool that does not solve the actual problem. The insight often sounds ordinary: “There has to be a better way to do this.” But frustration only becomes a business opportunity when it connects to a meaningful, repeated need. A useful starting point is to examine four things: <img src="https://images.pexels.com/photos/12244844/pexels-photo-12244844.jpeg?auto=compress&cs=tinysrgb&h=650&w=940" style="max-width:500px;height:auto;" ></img> <ul> <li> Frequency: Does the problem happen daily, weekly, or only once a year?</li> <li> Cost: Does it consume billable capacity, delay cash, cause rework, or risk client trust?</li> <li> Ownership: Who feels the pain, and who has authority and budget to fix it?</li> <li> Alternatives: What are people already doing to cope, and what does that workaround cost?</li> </ul> Workarounds are especially revealing. If a team has built a spreadsheet to reconcile project status with invoices, that spreadsheet is evidence of unmet need. It is also evidence that any replacement has to do more than look cleaner. The existing workaround may be ugly, but people understand it, control it, and rely on it. Before building a product or redesigning an operation, ask people to walk you through the last time the problem occurred. Ask what triggered it, which tools they opened, where they waited, who had to intervene, and what happened next. Specific stories are more useful than general opinions. “We waste a lot of time” is a starting point; “Every Thursday, our account manager checks three email threads to confirm which approved hours can go on the invoice” is a process you can investigate. <h2> Tool Sprawl: The Patchwork That Keeps Work Moving</h2> Tool sprawl is rarely caused by one bad decision. It usually accumulates as teams solve immediate problems. Email works for client communication. A project tool tracks tasks. A form collects onboarding details. A spreadsheet handles exceptions. Invoices live in accounting software. Each tool may be reasonable on its own, yet the connections between them depend on people. That is where workflow inefficiency hides: not necessarily inside a tool, but in the handoffs around it. Someone copies a client name from an email into a project board. Someone else checks whether a milestone is complete before drafting an invoice. A manager asks for a status update because the relevant information is split across systems. In a small team, these steps can seem manageable. But manual handoffs are fragile. They rely on memory, clear ownership, and timely communication. When volume rises or one experienced employee is away, the process can stall. Work may continue, but the team spends more time coordinating the work than delivering it. Signal What may be happening What to measure Client details are re-entered Intake and delivery systems are disconnected Time spent entering data; correction rate People search email for approvals Decisions lack a reliable, visible home Approval delays; time spent searching Invoices require manual reconciliation Delivery records do not reliably connect to billing Time to invoice; missed or delayed charges Status depends on asking a colleague Information is not accessible at the point of need Interruptions; response wait time The goal is not to eliminate every tool or automate every step. A new platform can add another layer of complexity if the underlying process is unclear. First map what happens from the initial request to completed delivery and payment. Then identify where information is duplicated, where decisions get stuck, and which steps depend on one person remembering to act. <h2> Why Agencies Feel the Pressure First</h2> Agencies and other service businesses operate under a particular kind of pressure: they sell expertise, but they deliver through repeatable activities. Every client may have different goals, stakeholders, and constraints, while the agency still needs dependable ways to scope work, assign capacity, track changes, and bill accurately. At a 25-person agency, a small process gap can become a meaningful operational cost. If project details arrive through email, scope changes appear in calls, and the team records time in a separate system, managers have to stitch together a picture of what is happening. That makes forecasting harder and increases the chance of delivering unbilled work. Productized services raise the stakes. A productized offer promises a clearer package, a more predictable experience, or a defined outcome. Clients expect consistency. The delivery team needs repeatable workflows that protect quality without turning every engagement into a custom operations project. This does not mean every agency should force its work into a rigid template. The right balance is a stable core with a deliberate path for exceptions. For example, standard onboarding can capture the same essential information every time, while a clear escalation route handles unusual access requirements or legal reviews. Without that distinction, “flexibility” can become a label for avoidable rework. Watch the relationship between the sales promise and the delivery process. If a service is sold as fast and straightforward, but the team must chase assets across email, rebuild project records by hand, and verify every invoice manually, the operating model may be undermining the offer. A better workflow can improve margin and client experience at the same time. <h2> AI Is Raising the Bar for What Feels Acceptable</h2> AI-driven expectations are changing how people judge routine work. Tasks that once seemed to require an afternoon may now appear automatable: summarizing email threads, drafting invoice descriptions, classifying requests, or turning a conversation into a task list. As these capabilities become more familiar, clients and employees may become less tolerant of slow, manual processes. That expectation inflation creates opportunity, but it also creates risk. “AI can do this” is not the same as “AI can do this reliably within our workflow.” A generated summary may miss a scope decision. An automated invoice draft may misinterpret a discount or billable milestone. If the process has poor data, unclear ownership, or no review point, AI can accelerate mistakes as easily as it can reduce busywork. Think of AI as a way to improve specific steps in a well-understood process—not as a substitute for defining the process. Before automating, establish what information is authoritative, what decisions require human judgment, and what should happen when the system is uncertain. <ul> <li> Use AI to summarize long email threads, but link the summary to the original conversation and verify consequential decisions.</li> <li> Use AI to draft invoice line items from approved delivery records, but require a person to check rates, scope, and exceptions.</li> <li> Use automation to route common intake requests, but keep a visible path for unusual or high-risk requests.</li> </ul> The competitive advantage may not come from using the most AI. It may come from having the cleanest workflow for applying it: good information, sensible controls, and fewer manual transfers between tools. <h2> How to Tell Whether the Inefficiency Is Worth Solving</h2> When you notice a normalized problem, resist the urge to begin with software. Start with a short operational investigation. Map the workflow as it actually happens—not as the process document says it happens—and include the exceptions. <ol> <li> Choose one recurring workflow. For example, trace a client request from the first email through delivery, approval, and invoicing.</li> <li> Record each handoff. Note who owns the next action, what information they need, and where they find it.</li> <li> Measure friction. Track waiting time, rework, duplicate entry, missed charges, and interruptions—not just active labor.</li> <li> Find the expensive failure. Determine whether the biggest cost is delay, error, lost revenue, poor visibility, or dependence on a particular person.</li> <li> Test the smallest change. Clarify ownership, standardize an intake form, connect two systems, or add a billing checkpoint before buying a large platform.</li> </ol> Look for a measurable before-and-after result. How long does it take to issue an accurate invoice? How often does a project wait for missing information? How many times does a client have to repeat a request? These measures help distinguish a genuine business opportunity from an irritation that simply feels prominent. Also ask what people might lose by changing the process. A workaround can preserve flexibility, personal judgment, or a sense of control. If a proposed fix removes those benefits, resistance may be rational rather than stubborn. Design around the real need instead of treating adoption as a communications problem. <h2> Read the Room, Then Read the Workflow</h2> When everyone accepts inefficiency as normal, read it as a signal to investigate—not as proof that the market is ready for a new product. The routine complaint may reveal status quo bias, but it may also expose a process with costs no one has measured. The difference matters. For agencies and productized services, the most promising opportunities often sit between tools: between email and project tracking, between completed work and invoices, between the promise made in sales and the experience delivered by operations. Those gaps are easy to overlook because people have built habits around them. Durable improvements begin with frustration, but they survive on evidence. Find the repeated pain. Understand who bears the cost. Measure the handoffs. Then fix the smallest important part of the workflow and see whether the result changes behavior. “That’s just how we do it” may be a reason to leave a process alone. It may also be the most valuable sentence in the room—especially when the people saying it are spending time, money, or trust to keep the workaround alive.</html>

Qqpipi.com - User contributions [en]

What Should I Read Into When Everyone Accepts Inefficiency as Normal?