By Design or by Default: Why Your Business Keeps Fighting the Same Problems

Prefer to listen? Click here to watch this week’s solo episode of Everyday Business Problems.

A distribution leader once described his business to me this way: “We go through hills and valleys. We go good for a little while, then we dip, then we go good for a little while, then we dip. That’s been consistent across the board since we opened this facility.”

Read that last part again. Since we opened this facility.

He wasn’t describing a bad week. He was describing the permanent rhythm of his company. The good stretches and the dips weren’t random weather. They were the output of something running underneath the surface, quietly, every single day, he just couldn’t see it.

A manufacturer I talked to put a different name on the same thing. “Death by a thousand cuts,” he said. “It doesn’t feel bad, because it happens slowly, over time. And then you kind of wake up one day and you’re like, oh shit.”

If you have ever felt either of those things, the slow bleed or the endless hills and valleys, I want to give you a better way to think about what is actually happening. Because it is almost never what you think it is.

You cannot out-discipline a system problem

Everybody who talks about firefighting in your business is basically telling you the same thing. Be more proactive, manage your time better. Use the Eisenhower Matrix, buy a tool that shifts you from reactive to proactive. Delegate more.

Every one of those pieces of advice treats the underlying problem as a discipline problem. As if the reason you keep fighting fires is that you, personally, are not organized enough or disciplined enough or proactive enough.

After nearly thirty years of this work, here is what I have found. It’s almost never a discipline problem. You cannot out-discipline a problem that lives at the system level. You can wake up earlier, color-code your calendar, and white-knuckle your way through a quarter, and the same fire will still be burning next month. Because the fire is not a willpower failure but rather a feature of the system you are currently running.

That is the real choice underneath all of this. The question of whether you are running the business by design vs by default.

Meet your default system

Every business is already running on a system. The only question is whether anybody actually designed it.

Most didn’t and what most companies have is what I call a default system. It is the system you grew into through a series of decisions. One workflow added here. One shortcut taken there. One bolt-on accessory layered over there. A workaround that solved a problem on a Tuesday and quietly became permanent. Nobody ever sat down and chose it, it accreted, and before you know it, you have inherited your default, whatever that default happens to be.

This is why “death by a thousand cuts” is such an accurate description. No single decision broke anything. Each one made sense at the time. But the sum of all of them is a system nobody designed, producing results nobody wants.

Here’s the part that really trips people up. The default system is not a broken system. That is exactly why it is so hard to fix. It is not flashing red. It is not down. It is the way you operate today. It is “that’s just how we do it around here.” It runs. It limps, it leaks, it costs you more than you realize, but it runs. So you never stop to question it because you’re in it every day.

Every system is perfectly designed to get the results it gets

There is a line from the quality world that nails this. “Every system is perfectly designed to get the results it gets.” It usually gets credited to W. Edwards Deming, though the actual origin traces back to a P&G executive named Arthur Jones and was popularized by Dr. Paul Batalden. The attribution is a fun footnote. The truth in it is the whole point.

Your recurring problems are not bad luck. They are not the result of one careless employee. They are the designed output of your default system, working exactly as it was unintentionally built to work.

The same quote opportunity that keeps getting lost. The same handoff that keeps dropping. The same month-end scramble. The same customer complaint, wearing a slightly different hat each time. If it keeps coming back, that is not an accident. That is the system telling you precisely what it was built to produce.

This is what I mean when I say fix the system, not the people. The people are not failing. The system is doing its job. So the question to stop asking is “who dropped the ball this time?” The question to start asking is “what makes this drop inevitable?”

Why you cannot see it from the inside

If your default system is so busy producing problems, why is it so hard to spot?

Because you cannot see the system from inside it. And the reason for that comes down to what I call your lens of experience.

You have a lens of experience. I have one. Everybody does, and every lens is valuable. But your lens is also the boundary of the solutions you can imagine. When a problem shows up, you reach for a fix that fits your lens. And that fix, by definition, comes from the same thinking that built the system in the first place. So you solve the problem through your existing lens, which means you keep growing into the system you already have.

Here is a simple test. If you had never learned about Theory of Constraints, or systems thinking, or synchronous flow, would you ever look at those ideas as the way to solve a growing backlog, or long lead times, or constrained capacity, or even a product quality issue? Probably not. Not because you are not smart. Because those tools are not in your lens, so they are not on your list of possible answers.

That is why a recurring problem can sit in plain sight for years. A services organization I talked to had more than 60% of it’s active projects sitting past their forty-five day service level agreement. That was thousands of projects, late. And when leadership asked the team about it, the answer was, “It’s always like that.” Nobody was alarmed. The backlog had become wallpaper. From inside the default system, a massive, profit-draining failure looked like normal Tuesday.

This is the real value of bringing in an outside lens. Not because the outsider is smarter, but because they are not standing inside your default system, mistaking it for the laws of physics.

The tool was never the problem

Watch what happens when a company finally decides to fix something. They almost always reach for a tool.

Pipedrive isn’t working for us as a CRM, so let’s get HubSpot. HubSpot is terrible, let’s move to Salesforce. Epicor is the worst ERP out there, what we really need is SAP, or Dynamics, or JD Edwards.

I have watched companies burn enormous time and money on this carousel, and here is the uncomfortable truth: By and large, those tools all function similarly. So what you think is solving the problem is actually just extending it. You are putting another Band-Aid on the system you already have, without ever uncovering the problem at the root cause level.

I saw this in its purest form inside a manufacturer’s CRM. It had been configured with dozens of pipelines and more than twenty thousand tickets, built that way to satisfy a previous management team’s obsession with tracking everything. The result? The person responsible for it self-admittedly avoided the entire thing. He ran his actual work out of his email inbox because, in his words, he had a panic attack every time he opened the CRM. Good intentions, a real tool, and a system so unusable that the human being routed around it entirely. The fix was not a different CRM. The fix was collapsing it down to one pipeline and a handful of stages that matched how the work actually moved.

That is the trap of the default system. We believe systems equal technology. While technology is certainly part of an effective system, we tend to skip right over the planning, the people, and the process parts, and jump straight to it. Then we wonder why the new tool did not actually save us.

The default system lands on your people

Here is the cost that does not show up as a line item. A default system survives by leaning on your people. The gaps in the system get filled by human beings, holding the whole thing together with memory, effort, and heroics.

Take sales, because it is easy to see there. A company wants to grow revenue, so it runs the traditional playbook. Account management, and some outbound business development. Marketing generating prospects and handing them over the fence to sales, who turn conversations into opportunities, who turn opportunities into closed business. On paper, that is a customer development system.

But underneath it, the conversation sounds like this. Why aren’t our revenue numbers up? Are you doing enough outbound? How many calls did you make? How many emails did you respond to?

All of the pressure lands on the people to produce the output. But the tactical pieces of how that output actually happens are missing. There is no well-defined process to follow. There are no coaching mechanisms. There are no feedback loops. So the team cannot reliably do the activities that produce the result, and the team cannot even tell you whether they made one effective call or a thousand random ones, because nothing underneath them is designed to make the difference visible.

So two things happen at once: The problem recurs, because the gap was never closed, and your people burn out, because you keep asking them why they are not delivering an output the system was never built to support. Eventually the good ones, the ones who can go anywhere, leave. Then the default system gets worse for whoever is left.

That is the quiet tax of running by default. Recurring problems, capacity that stalls out, and your best people walking out the door.

Designing on purpose: planning, people, process, technology

The only way out of your default system is to design one with intention.

For me, the design has an order: Planning, then people, then process, then technology. In that sequence, always. The default system reverses it. It jumps straight to technology and bolts a tool onto the chaos. Designing on purpose means naming what the system is actually supposed to do before you choose anything to do it with.

The thing I love about this work is what it doesn’t require. It does not require you to go buy something new. We can use whatever tools and technology you already own. We can use the people and the equipment you already have. From there we can improve product quality, shorten cycle times, and reduce backlog.

Look at what that unlocks. Happier customers, because they get their orders when they need them. More throughput, in the traditional manufacturing sense and in the customer experience sense. Customers who start to see you as a growth partner instead of a vendor, which opens the door to more opportunities. All of it flows back to your real levers. Profitability, cash flow, and your culture, because people stop drowning.

One manufacturer I worked with went from roughly four jobs a day to more than ten through this kind of work. Not by buying a faster machine or adding people. By designing the flow across the touchpoints of the operation so the work actually moved. That is what intentional design does. It increases flow, and flow is what gets you to the most effective path to growth.

This is not a one-and-done project, either. It is a cycle of improvement. You design, you watch the output, you find the next gap, you close it. Through the lens of experience, working across all the angles at once, instead of bolting on one more isolated fix.

Everyone is running by default right now

Here is the honest version of all this. Until you deliberately design otherwise, you are running by default. That is not an insult. It is just the starting condition of running a business.

“By design or by default” is the language I use, so let me be straight about what it implies. Almost everyone is currently running by default. The tells are not about your size or your industry or how long you have been at it. The tells are the symptoms you experiece. Problems that keep coming back. Your capacity hits a ceiling every time you try to grow. Your people are stretched and the good ones burn out. And growth comes slowly, in those same hills and valleys, if it comes at all.

If you recognize those symptoms, you are not broken and you are not behind. You are exactly where every business is by default. The difference between the companies that break out of it and the ones that stay stuck is not discipline, and it is not a better tool. It is the decision to stop running the system they inherited and start designing the one they actually need.

What to do Monday morning

You are not going to fix all of this at once. This is very much a crawl, walk, run situation.

Start by quantifying what is already happening. Most leaders know they have problems, but that feeling is hard to contextualize and even harder to put a number on, especially if you answer to somebody else. That is why I built the Cost of Chaos calculator. It is a quick pulse check across six categories where default systems leak money: firefighting, rework and scrap, expediting, customer escalations, employee turnover, and quoting inaccuracy. You plug in a few numbers, your loaded hourly rate, your operations headcount, a couple of drivers per category, and it gives you an estimated annual dollar cost of your chaos, plus your single biggest cost driver. For a lot of leaders, seeing that number is the first time the default system becomes visible at all.

Once you have the number, zoom in. Get an end-to-end view of what your default system actually looks like. How did you grow into where you are today? Walk the workflow. Find the spots where the work piles up, where it gets handed off, where people route around the official process.

Then get underneath the symptom to the root cause. If a problem keeps repeating, ask what is really driving it. Is it a flow issue, where improving flow would dissolve the problem? Is there a planning gap, a people gap, a process gap feeding it? Whatever output you are chasing, product quality, inventory accuracy, on-time delivery, those are downstream symptoms of a system. Resolve the system, and the symptom stops coming back.

Quantify it. See it. Get to the root. Then design for it, on purpose. That is the whole move from default to design.

You do not need a bigger team or a shinier tool to start. You need to stop accepting the system you inherited as the way things have to be.

See you next Saturday,

Dave