When Process Improvement Is Not Enough: A Re-engineering Test for African Service Operations

Continuous improvement is valuable, but it cannot repair an operating model whose structure creates delay. When work repeatedly crosses functions, customers re-enter the same information, controls are duplicated and exceptions require senior intervention, improving individual tasks may simply make a fragmented system operate faster. That is the point at which business process re-engineering should be considered.

Test whether the problem is local or structural

Begin with evidence. Map one customer journey or value stream from demand to outcome, including waiting, rework, hand-offs, systems and controls. A focused process-mining pilot can reveal actual variants and queues, while frontline observation explains why they occur.

Re-engineering is justified when several structural signals appear together: work moves backwards frequently; ownership changes without adding value; the same data is captured more than once; controls detect errors late; or performance depends on heroic escalation. If the issue is one unstable activity, use targeted improvement. If the architecture of work creates the problem, redesign the flow.

Design around outcomes and decision rights

Define the outcome before drawing a future-state process. What must the customer receive? What risk must the organisation control? Which decisions belong at the frontline, and which require specialist authority? Then remove unnecessary hand-offs, combine related work, place controls closer to the source and clarify accountability across the full journey.

This is broader than digitisation. As our guide to process optimisation before digital transformation explains, technology should scale a process that has already been simplified. Automating duplicated approvals or unclear ownership only embeds the old design.

Prove the future state before scaling

Pilot the redesigned flow with one customer segment, product or region. Establish baseline measures for end-to-end lead time, first-time-right performance, cost per outcome, control failures and customer effort. Assign benefit owners and track whether the change removes work or merely relocates it. A practical daily management system can expose early failure signals and keep corrective action visible.

Scale only after the pilot demonstrates better whole-system performance without weakening control or overloading another team. Effective re-engineering is not a dramatic workshop or a new diagram. It is a disciplined redesign of work, information, technology and decision rights that produces measurable commercial and customer value.

Agile Ops helps African organisations diagnose structural process problems, redesign end-to-end operating models and translate improvement opportunities into implementable change.