Redesigning processes without value insight wastes money

There is something that is repeated with an almost uncomfortable precision in organizations.

Months are invested in redesigning processes, workshops are convened, walls are filled with post-its, tools are purchased, everything is documented with an admirable level of detail... And in the end, when someone asks the right question, if at all, no one has a clear answer: Did this generate more value? No more order, no more control, no more visibility. Value. Because it is one thing to have better structured processes and quite another to have processes that impact the business. I've seen companies reduce times by 40% in processes that didn't move the needle, flawless automations that only managed to accelerate errors, dashboards full of indicators that look good in a meeting but say absolutely nothing about revenue, margin or experience. And the most interesting thing is that this does not happen for lack of effort, or interest, it happens because from the beginning the problem is being looked at from the wrong angle.

>> Map your business processes and boost business efficiency <<

Redesigning processes without a clear definition of value is simply reorganizing inefficiency

When a company decides to redesign processes, the typical conversation usually starts with the operational. We talk about activities, about those in charge, about tools, about times. Everything revolves around how the process works today and how it could work better (that is, faster) tomorrow. But there is a question that rarely appears at the beginning, and when it does, it is too late: what do we mean by value in this process? Customer value, business value, value in terms of revenue, margin, retention or real efficiency. Not value in the abstract, not value as an aspirational concept, but concrete, measurable value. Without that definition, redesign becomes an exercise in order. Tasks are reorganized, steps are eliminated, decisions are automated. The process looks cleaner, more logical, more efficient. But the real impact remains uncertain. The underlying problem is that most of the processes in companies were not designed to generate value. They were designed to function, to comply, to adapt to a system or an organizational structure. And that explains why many processes can be flawless internally and, at the same time, completely irrelevant from a business perspective.

  

Confusing efficiency with value is one of the most expensive mistakes a company can make

Reducing times sounds good, automating tasks too, standardizing processes seems a very logical sign of operational maturity. But none of these things, on their own, guarantee value generation. And yet, most redesigns are justified with exactly that. It is celebrated that the process is now faster, it is proudly shown that there is less manual intervention, it is documented that the flow is more orderly. Everything seems to indicate that there is progress, and in a way there is. But if you stop for a moment and ask what impact that had on margin, on conversion, or on retention, the conversation becomes fuzzy. This is where an uncomfortable truth appears: efficiency, when not aligned with value, can be dangerous. It can make an irrelevant process run better, it can amplify errors, it can escalate problems. It's like improving the speed of a vehicle without checking if it's going in the right direction. Everything works better, but the end result does not lead to an improvement.

>> What is a BPM and what is it for? <<

Operational metrics become comfortable when we don't want to question the business

There's something particularly seductive about operational metrics: they're easy to measure, easy to understand, and easy to report. Cycle time, number of cases, SLA compliance, volume processed. All of this gives the feeling of control. The problem arises when those metrics become the center of the conversation, when the process is optimized to meet internal indicators, not to generate business results. A team can meet all its SLAs and still be generating a mediocre experience, it can reduce times and increase rework, it can process more volume and decrease quality. But since the indicator is green, no one questions what is happening. The uncomfortable thing is that the metrics that really matter are not always so visible, they are not always in the system, they are not always easy to calculate, and many times they require connecting information between areas, systems and different moments of the journey. And that implies effort, it implies questioning, it implies getting out of comfort.

Value is not measured where tasks occur but where consequences occur

One of the biggest confusions in process redesign is assuming that value is generated within the process, when in fact value is usually manifested later. A business process can run perfectly, but if the delivery fails, the value disappears. A care process can be resolved quickly, but if the problem occurs again, the cost multiplies. An onboarding can be efficient internally, but if the customer doesn't perceive value, retention falls. The problem is that metrics tend to stay in the process, you measure what happens inside, not what happens next. And it's not that it's bad (keep measuring it anyway), but we don't take into account what happens next generates a dangerous illusion: we believe that the process works because internally it is under control, while the business tells a completely different story.

The metrics that really matter are usually the ones that no one wants to look at

When you start talking seriously about value, metrics appear that make you uncomfortable. Margin per customer, cost-to-serve, loss of revenue, rework, impact on conversion, impact on retention. These metrics force you to connect the process with the result, they force you to leave the operational world and enter the business world. And that is not always well received. We all want to look good in the photo. In many cases, these metrics reveal that seemingly efficient processes are generating losses, that well-executed operations are affecting the experience, that automated decisions are deteriorating the margin. It's not that the company doesn't have data, it's that it's not looking at the right data, or worse, it prefers not to look at it.

  

Value escapes into spaces where no one is looking

If there's one thing that changes the way we understand processes, it's recognizing that value is rarely lost within a specific activity, it is lost between activities. In the handoffs between areas, in the changes of system, in the decisions that are delayed, in the information that does not flow, in the moments where no one is clear about what is next. This is where the famous "value leakage" occurs. That moment when the customer has to repeat information, that point where an order stops because a piece of information is missing, that moment where the process depends on a person who is not available, that delay that does not appear in any diagram but occurs often. Interestingly, these points are almost never documented, because process maps often reflect how the flow should work, not necessarily how it actually works.

Organizational fragmentation is the greatest silent enemy of value

Companies are designed by areas, but processes are not. Processes cross marketing, sales, operations, service, and each area has its own objectives, its own indicators, its own priorities. The result is predictable. Each area optimizes its part of the process, improves its efficiency, meets its goals, but rarely is anyone optimizing the entire flow. Then the breaks appear. The lead that cools down between marketing and sales, the order that is delayed between sales and operations, the customer who repeats information when they go to support (we all hate to be asked the same data all the time). And the most curious thing is that, from the perspective of each area, everything is working well. "I did my part, the problem is with others, not mine", is the prevailing mentality.

The illusion of control increases while the value decreases

One of the most deceptive effects of process redesign is the sense of control it generates. There are more dashboards, more reports, more visibility. Everything seems to be under monitoring. But that doesn't necessarily mean that value is improving. Many times the opposite happens. The execution is more controlled, but the impact is less questioned, it is measured if the process is fulfilled, but not if the process generates results. And that creates an interesting paradox: the more control the organization has over its processes, the less it questions whether those processes are well designed, sounds ironic, right?

Most redesigns fail because they enhance the visible and ignore the structural

It's natural to focus on what you see. Interfaces, forms, screens, flows in systems. That's tangible, it can be redesigned quickly, and it creates a sense of advancement. But value is rarely defined there. It is defined in how information flows, in how decisions are made, in how systems are connected, in how incentives are aligned. And that is not always visible. That's why many redesigns stay on the surface. They improve the experience at one point, but they don't correct the structural problem, they speed up the process but don't eliminate friction. And the result is the same as always: more effort, more investment, little real impact.

And it is right here that everything becomes evident. It doesn't matter how much you optimize a business process if that process isn't aligned with the value the company needs to generate. You can make it faster, cheaper, more orderly. But if it doesn't impact the business, it's useless. And this is something that many organizations avoid questioning, because it implies accepting that not all processes are equally important, that some generate value, others support it and others simply exist. Redesigning them all with the same approach is not only inefficient, it's costly.

True redesign starts when we stop asking how the process works and start asking what value it generates because the problem was never the process, but what we expected it to solve

At some point, the conversation has to change. It has to stop revolving around tasks, times and those responsible, and start focusing on value. What value does the process generate, how is it measured, where is it lost. Because at that point, the redesign ceases to be an operational exercise and becomes a strategic decision. And not all answers are comfortable, but they are necessary.

In the end, many processes do not fail because they are poorly executed. They "fail" because they are required to solve things they were never designed to do. They are expected to generate value when they were designed to control, they are expected to improve the experience when they were designed to fulfill tasks, they are expected to drive revenue when they were designed to record information. And that's where the disconnect appears. The process fulfills its function, but it does not fulfill the purpose. And that, although it seems subtle, completely changes the way in which its redesign should be approached. The question isn't whether your processes work. The question is whether they are generating value. And that, curiously, is the one that is done the least.

When reading the article Surely you are asking yourself: What is meant by value?

Value is not that the process works. It's not that it's faster, more orderly, or more automated, either. Value is the real impact that process generates on the business and on the customer experience, measured in results that matter: revenue that is captured, costs that are reduced without deteriorating the experience, customers that stay, decisions that are made on time, and friction that disappears.

In simple terms, value is everything that, if it disappears, the business feels immediately. Everything else can be efficiency. It can be control. It can even be operational convenience. But it is not necessarily value.