The Risk of Waiting to Change

There is a sentence I hear from leadership teams all the time: “We know this needs to change. We’re just not ready yet.”

On the surface, that sounds responsible. Maybe you’re waiting until Q1, until after the next hire, until you finish implementing a new system, or until things calm down and you have more capacity.

But here is the problem: things usually do not calm down. And waiting is not neutral. Waiting has a cost.

If you’re not sure where that cost is showing up in your organization, start with my free Operational Waste & Efficiency Assessment. It will help you identify where time, capacity, and resources may already be getting lost in the way work gets done.

In fact, one of the biggest mistakes I see companies make is treating the decision to change as if the options are to change now or change later. But those aren’t really the options. The actual options are to change now or continue paying for the current problem until you change it.

That is a very different decision. Sometimes the bigger operational risk isn’t changing too soon. It’s waiting too long.

One of the reasons leaders delay operational change is because the cost of the problem usually isn’t sitting neatly on a P&L. There isn’t a line item that says, “Poor handoffs: $147,000,” “CEO interruptions: $86,000,” or “Inconsistent onboarding: $220,000.”

Instead, the cost gets distributed across the organization. A customer waits an extra day here. Someone has to redo something there. An employee spends 30 minutes looking for information. A manager answers the same question for the sixth time. Sales promises something operations didn’t know about, operations builds a workaround, finance fixes an invoice, and leadership jumps into Slack.

Nobody calls any one of those things a crisis. And that is exactly why they’re dangerous.

Individually, they look small. Collectively, they become your operating model.

Research gives us an idea of just how much time can disappear into this kind of operational inefficiency. Asana’s Anatomy of Work Global Index found that knowledge workers spend 58% of their day on “work about work” rather than skilled or strategic work. Workers surveyed estimated that improved processes could save them 4.9 hours every week, or more than six working weeks over the course of a year.

That’s how companies end up with hundreds of tiny inefficiencies that everyone has quietly learned to tolerate. Eventually, you don’t even recognize them as problems anymore. You just call it work.

There is another assumption I hear frequently: “We’ll fix this once we grow a little more.”

But growth doesn’t usually solve operational problems. Growth exposes them.

If a process is inconsistent with 20 employees, it becomes chaotic with 60. If everything depends on one person at $5 million in revenue, that dependency becomes terrifying at $15 million. If customer onboarding is messy with 10 new customers a month, adding more customers doesn’t make it better. It just gives the mess more volume.

This is why I say: growth doesn’t create chaos. It exposes it.

Whatever variability exists inside your company today gets multiplied as volume increases. That’s why waiting until the business is bigger can actually make the eventual process improvement harder. There are now more employees to retrain, more customers affected, more technology intertwined, more exceptions, more habits, more politics, and more people saying, “Well, this is how we’ve always done it.”

You are no longer changing a process. You are unwinding an entire ecosystem of workarounds.

We talk a lot about technical debt in software. I think companies accumulate operational debt in exactly the same way.

You make a short-term decision because it solves today’s problem. Someone creates a spreadsheet. Someone adds another approval or Slack channel. Someone builds a workaround, adds another person, creates another SOP, or buys another software tool.

Every decision makes sense individually. But nobody stops and redesigns the underlying system.

Over time, the organization gets heavier. There are more approvals, more meetings, more tools, more handoffs, more coordination, and more people required to accomplish the exact same outcome.

That is operational debt. And just like financial debt, it accumulates interest.

Every new employee has to learn the messy system. Every manager has to navigate it. Every customer experiences some version of it. Every technology investment gets layered on top of it. Eventually, leadership asks, “Why does everything feel so hard?”

Because you’ve been paying interest on decisions that were never meant to become permanent.

This is where I have a lot of empathy for leaders, because changing something has visible risk. Doing nothing doesn’t.

If you change a process, people might push back. The rollout might be uncomfortable. You might temporarily slow down, discover bigger problems, make decisions people don’t like, or have to hold people accountable. Those risks are obvious.

The operational risk of waiting is much quieter. It looks like your best employee becoming exhausted. It looks like a customer finally leaving. It looks like a leader who has been compensating for a broken process resigning. It looks like margin slowly disappearing, growth plateauing, or the CEO spending another year solving problems they shouldn’t be solving anymore.

Nothing dramatically exploded. But the organization became a little less healthy every month.

Gallup has found that employees who very often or always experience burnout are 2.6 times as likely to leave their current employer. That matters operationally because the employees compensating for broken processes are often the very people organizations become most dependent on.

That’s why leaders often underestimate the risk of doing nothing. The consequences aren’t dramatic enough to demand attention until suddenly they are.

One of the biggest reasons companies delay process improvement is, “We don’t have the capacity right now.”

Sometimes that’s true. But you have to ask a second question: Why don’t you have the capacity?

Very often, the thing consuming your capacity is the exact problem you’re postponing fixing. The team is too busy because they are reworking things. The manager is too busy because employees constantly need clarification. Leadership is too busy because problems escalate upward. Operations is too busy because there is no standard process. Everyone is too busy because the organization requires an unreasonable amount of coordination just to function.

So when someone says, “We’ll improve the process when we have more time,” what I hear is, “We’ll fix the thing consuming our time once it stops consuming our time.”

That moment may never come.

Capacity often isn’t something you find. It is something you create. And good process improvement creates capacity.

There is also a financial reality here: problems compound.

Let’s use an incredibly simple example. Imagine your organization loses only 1% of productivity because of unnecessary friction. At $10 million in revenue, 1% is $100,000. At $50 million, it is $500,000. At $100 million, it is $1 million.

And operational friction is rarely isolated to one place. Think about all of the hidden places value disappears: rework, customer churn, delayed projects, missed sales follow-up, overstaffing, manager interruptions, poor onboarding, slow decision-making, billing errors, duplicated work, bad handoffs, and opportunity cost.

The question isn’t simply, “How much does improvement cost?”

The better question is: “What does the problem cost every month we leave it alone?”

That is the calculation most leadership teams never make.

Another reason companies wait too long is that smart employees are incredibly good at compensating for broken systems. Ironically, this can hide the problem from leadership.

You have someone who remembers everything. Someone who knows who to call. Someone with the secret spreadsheet. Someone who catches the errors. Someone who knows the customer history, which approval actually matters, or which step can secretly be skipped.

Those people become organizational shock absorbers. Because the work keeps moving, leadership assumes the system is working.

It isn’t. The people are working around the system.

This is one of the biggest operational risks inside growing organizations because your process isn’t actually the process. Your people are the process.

The minute one of those high-context employees leaves, goes on vacation, gets promoted, or simply burns out, everyone suddenly realizes how much invisible knowledge was holding the organization together.

That’s not scalability. That’s dependency.

I don’t believe you should change everything all the time. That creates another problem: change fatigue. The goal isn’t constant disruption. The goal is intentional improvement.

There are four questions I would ask.

If you keep having the same conversation, solving the same issue, or fixing the same mistake, you probably don’t have a people problem. You have a process problem.

That is a major warning sign because whatever is happening now is likely to become more expensive later.

If the answer is yes, you have operational risk. Scalable processes should not depend on one person remembering what to do, who to contact, or which workaround makes the system function.

That may be the most important question. What does it cost? What gets harder? Who burns out? What customer experience suffers? What opportunity gets delayed? What becomes harder to unwind?

That is your cost of waiting.

Here is the good news: changing doesn’t mean you have to transform the entire company tomorrow. You don’t need 200 SOPs, a 50-person transformation team, or another software implementation.

Start by making the work visible. Map what is actually happening today, not what the SOP says happens or what leadership thinks happens.

Where does the work begin and end? Who touches it? Where does information move? Where does it stop? Where does it get reworked? Where does someone have to ask a question? Where do customers wait? Where does leadership intervene?

Once you can see the work, you can improve the work. And once you improve the work, then you standardize it.

Consistency before differentiation. Same way, right way, every time.

Then you can automate. Then you can scale. Then you can introduce AI.

Because AI doesn’t fix broken processes. It amplifies them.

If there is one thing I want you to think about, it’s this: What problem inside your organization have you already decided needs to change, but you keep postponing?

You probably already know what it is. Maybe it is onboarding, sales handoff, customer communication, project delivery, billing, decision-making, or the fact that everything still comes back to you.

Now ask yourself: What will actually be different six months from now if we do nothing?

Waiting for the perfect time to improve your organization is usually a losing strategy. There will always be another customer, another quarter, another hire, another initiative, another fire.

The companies that become easier to run are not the companies that eliminate every problem. They are the companies that build the ability to solve problems systematically.

And that is ultimately what continuous improvement is. It isn’t fixing everything at once. It is building an organization that gets better at fixing itself.

So if you know something needs to change, don’t just ask, “Are we ready?”

Ask, “What is the risk of waiting?”

Because sometimes the most expensive decision you make is the decision you keep postponing.

Want to Work With Us?