Business processes: how to stop firefighting and start managing

Why processes matter

Mid-sized Russian companies often run in a state of permanent crisis. People work in firefighting mode, reacting to problems as they arise. Deadlines slip, quality suffers, employees burn out. Leaders tend to blame the people: "We need better hires, we need tighter discipline." Yet the issue almost always lies not with the people but with the processes.

A good process lets even an average employee deliver results. A bad process undermines the efforts of even a strong specialist. This is a fundamental principle of quality management, and one that is too often ignored. When you invest in designing, documenting and optimizing processes, the payoff comes quickly: fewer errors, faster execution, and people freed up for higher-value work.

Business process management (BPM) is not about producing documents and systems. It is a management discipline that changes how a company works, step by step. Strong processes let companies scale without growing the team in proportion.

Process mapping: understanding what actually happens

The first step in process management is mapping. You need to understand how a process works from start to finish. That covers every step, decision, wait point, and the people involved.

When you ask different people to describe a process, they often give different answers. Why? Because much of the process is undocumented. Everyone works in their own way and patches the gaps with their own intuition. Which means the process does not scale.

The map has to be complete: it needs every step and every piece of data that is actually used. Steps are usually both formal and informal. The informal ones are what people actually do but that is written down nowhere — even though the work simply will not move without it.

Mapping should be visual. Use BPMN (Business Process Model and Notation) or simpler flow diagrams. Visualization helps you see the logic of the process, the branches, the loops, the wait points. A diagram immediately shows where the process is overloaded, where there are too many branches, where steps are redundant. Good mapping often reveals that a process has an entirely different structure than people assumed.

Diagnosis: finding bottlenecks and waste

Once the process is mapped, the analytical phase begins. Here you need to gather data on each step: how long it takes, how often errors occur, what it costs the company, how often rework happens.

One useful tool is value stream mapping. Borrowed from lean manufacturing, this method shows how much time genuinely adds value and how much is lost to waiting, checks, and rework.

For example, order processing might look like this:

• Customer places an order: 5 minutes (adds value)

• Order waits to be processed: 2 hours (adds no value)

• Order processing (verification, data entry): 15 minutes (adds value)

• Waiting for approval: 4 hours (adds no value)

• Approval: 10 minutes (adds no value — it is a control)

• Preparation for shipping: 30 minutes (adds value)

• Shipping: 5 minutes (adds value)

Total: 6 hours 55 minutes, of which only 55 minutes add value. That means 87% of the time is wasted. And this is exactly where the biggest improvement opportunity lies.

Once you see this picture, you understand where to focus. Rather than trying to speed up the order-processing step (a five-fold improvement buys you only 3 minutes), you can concentrate on cutting the waiting time.

Optimization: how to redesign a process so it works

Optimization means redesigning the process to be simpler, faster and more reliable. That can include removing unnecessary steps (often 20–30% of steps add no value), simplifying conditional branches, regrouping work so it is done consistently, and automating manual checks through standardized inputs.

For example, if an approval process takes 5 days because it requires sign-off from four different people, optimization might look like this: instead of sequential approvals (A signs off, then B, then C, then D), make them parallel (all four review at the same time). That can cut the time to 2 days. This is optimization, and it costs nothing, because it requires no new technology.

Automation makes sense after optimization. Automate a broken process and all you do is produce the wrong output faster. A good rule: first get the process simple enough, then automate.

Documentation: how to make a process standard and transferable

Once the process is optimized, you document the optimized version. Documentation serves several purposes: (1) it lets new hires quickly understand how to work; (2) it lets the company ensure the process is run consistently; (3) it helps surface further improvements.

Documentation should be accessible and readable. You do not need 50-page manuals. Usually it is enough to have: a process diagram, a description of each step (who performs it, what the inputs are, what the outputs are), the critical checks and controls (where errors are especially costly), a list of the tools and resources needed for each step, and examples of correct execution.

When the documentation is sound, a newcomer can be brought up to speed in days rather than weeks. That saves time and money. Documentation also lets the company speak a common language. When everyone uses the same terms and understands processes the same way, internal communication runs noticeably smoother.

The trap is that you can build a sprawling process with many conditional branches and variants. In practice the documentation then becomes useless, because it fails to capture reality. It is better to have a simple standard process that covers 80% of cases, with separate instructions for the exceptions. That avoids confusion and misinterpretation. When everyone shares one language, process improvement becomes more systematic and less dependent on individuals.

Implementation: the criticality of the process owner

An improved process will not implement itself. It takes teamwork and, above all, a process owner — a person accountable for the performance of the entire process end to end. This person does not necessarily perform all the steps, but they see the full picture and can coordinate improvements.

The process owner needs enough seniority in the organization to carry influence. A junior specialist will not be able to coordinate improvements that cut across other departments. Ideally the process owner is a middle manager or a department head to whom the people running different parts of the process report — or at least someone with strong relationships with those managers.

A good process owner is marked by several qualities: (1) deep knowledge of the process; (2) the ability to listen to improvement ideas from the people who run it; (3) the ability to take the data and make a decision on it; (4) the ability to influence different parts of the organization; (5) a commitment to continuous improvement rather than settling for "good enough."

Monitoring and continuous improvement

Once the process is implemented, you need to monitor its performance. To do that, pick 3–5 key performance indicators (KPIs): cycle time, error rate, cost per transaction, customer satisfaction. These KPIs are tracked on an ongoing basis, and when negative trends appear, you dig into why they are happening.

KPIs should be visible not only to management but to the teams that run the process. When people see how their work affects the metrics, they are more motivated to improve. It helps to show KPI trends monthly and discuss the reasons behind the changes.

Common mistakes in process redesign

In practice, most process-improvement initiatives meet resistance and often fail. Here are the most common mistakes.

Mistake one: redesigning without the people who run the process. Consultants or managers redesign the process in theory, and then the person who actually runs it finds 10 reasons why it will not work. Involving people in the redesign improves both the quality of the solution and the commitment to rolling it out.

Mistake two: ignoring external constraints. You might improve an approval process inside your own company, but if half the cases require input from outside partners or regulators, you cannot control the whole chain. You have to work with those constraints, not ignore them.

Mistake three: scaling too fast. It is better to pilot a process in one part of the organization, gather feedback, improve it, and then scale. Roll a poorly designed process out across the whole company and the resistance can be enormous.

Mistake four: no continuous improvement. The process is improved once, the people are released, and then nothing happens. In reality, continuous improvement is a culture. People should always be looking for ways to improve the process and offering ideas, and the organization needs a system for reviewing and adopting them.

Conclusion

Business process management is not dull administrative work. It is an investment in a company's productivity, quality and scalability. Companies that do it well are able to grow faster, retain their best people (because people prefer to work in well-run places), and hold quality steady for their customers. Start with mapping, then diagnosis, then optimization, documentation and implementation. And most important of all — make it part of the company's culture: continuous improvement, not a one-off project.

If this sounds like your situation — see how we help rebuild business processes as a service.