Anila is a fractional exec at opsbridge.io, helping scaling orgs restore ops discipline & clarity to improve margins & accelerate growth.gettyOne of the most common requests I hear from leadership teams (and I mean almost every leadership team at some point) is, “We need to improve our processes.”By the time they say it, they’ve usually already tried months of workflow redesigns, new approval steps, different tools and restructured meetings. All of it aimed at getting work to move faster.Sometimes it works, but just as often, the same problems surface again three months later. And when that happens, it highlights that the process was never really the issue; it was pointing toward something else entirely.​Why Process Gets The BlameProcess is one of the few parts of an organization that feels concrete. You can map it, measure it, hold it up in a meeting and say, "This is where things are breaking down."So when work slows, process gets the attention. That makes sense in principle, except most of the time the process is doing exactly what the business designed it to do. It’s not broken; it’s reflecting something about the environment it operates in. The process is visible, but what created the conditions for it to struggle usually isn’t.That’s the distinction most improvement efforts miss. I’ve seen this play out across very different kinds of organizations: growth-stage companies, businesses in the middle of acquisitions, established players working through transformation and more. What changes is what triggered the strain. What rarely changes is where the problem actually lives.​Where Accountability Goes MissingMcKinsey’s research on organizational decision-making found that only about a quarter of respondents said their organizations consistently make delegated decisions that are both high quality and fast. This reflects a gap that shows up repeatedly in organizations: the documentation exists, but the accountability doesn’t. An approval workflow slows down not because it’s poorly designed, but because nobody’s actually clear on who owns the final call. Leadership meetings happen every week, yet teams still walk out uncertain because decisions aren’t being made. The process may look functional, but when you lift the lid, it becomes apparent that the problem is sitting just underneath.This is partly why process improvement initiatives underdeliver so often. The workflow changes, but the conditions that created the problem don’t. And when the conditions stay the same, the friction doesn’t disappear; it just finds somewhere else to surface.It rarely stays contained to one area either. When one process starts showing strain, other parts of the business feel the impact. Delivery gets less predictable, decisions that used to get made in one conversation now take three and teams start building quiet workarounds just to keep things moving. And at that point, the pressure falls on execution, even though execution is rarely where the story started.​Why Technology Makes This More UrgentThis isn’t a new challenge, but technology has changed the timeline. As organizations invest in AI and automation, information moves faster and decisions need to happen sooner. That creates real opportunity, but it also puts pressure on an operating environment that may not have been built to absorb it. Technology can improve what the business is capable of, but it can’t clarify who owns a decision or resolve the competing priorities that have been quietly building across functions. Those are still leadership problems.This is why so many technology investments don’t deliver what leaders expected. The tool performs exactly as designed, but the environment around it hasn’t changed. Decisions still cluster at the top, teams still operate to different assumptions and the accountability gaps that were always there become more expensive to ignore. The technology didn’t create those problems, but it made them harder to defer.​What To Ask Before Redesigning AnythingWhen a process starts to struggle, improving the visible workflow might still be the right call. The only mistake is assuming it should be the first one.Before you touch anything, ask what the process is actually telling you. The most useful question usually isn’t “How do we make this faster?” but “What is this workflow revealing about how decisions actually get made around here?” The answer tends to point somewhere other than the process itself. It may be unclear ownership, quietly misaligned priorities or work that’s been handed off across teams without anyone holding the thread.In my experience, the organizations making lasting operational progress aren’t the ones redesigning the most. They’re the ones that diagnose before they fix.The process isn’t always telling you what to change. It’s telling you where to look. Start there, and the question shifts from “How do we improve this workflow?” to “What is this workflow telling us about how our business actually operates?” That second question is usually what I've found to be the more useful one.​Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?