Services

Process & Operational Excellence

Every organisation runs two processes: the one in the manual and the one people actually follow. The distance between them is where the delays, the duplicated effort and a surprising share of the risk live.

The situation

What we usually find

For operations, finance and service leaders who can see that work takes longer than it should but cannot point to where it goes.

Nobody sets out to build a bad process. They accumulate. A check added after something went wrong, an approval added when someone left, a spreadsheet that began as a stopgap and became load-bearing. Every addition made sense on the day it was made. Nobody has looked at the whole since.

The cost rarely appears in the accounts as a line. It shows as things taking longer than anyone can explain, the same query answered twice by two departments, and a small number of people who are the only ones who know how something works — which is a continuity risk that only declares itself when they resign.

Process work is not a report. It is agreeing how the work should run with the people who do it, then changing the systems they use so that the new way is the easier way. A recommendation that depends on people remembering to behave differently has a half-life of about a quarter.

What changes

From where you are, to where this gets you

Most organisations arrive at this practice from a recognisable place. This is the distance it covers.

What this practice changes. Nobody can draw how the work actually flows becomes: The process mapped, agreed and measured. Approvals sitting in somebody’s inbox becomes: Steps that move without being chased. The same check done twice by two teams becomes: Duplicate work removed, the control kept. Performance discussed by opinion becomes: Performance tracked against agreed measures.

  1. Nobody can draw how the work actually flows

    The process mapped, agreed and measured

  2. Approvals sitting in somebody’s inbox

    Steps that move without being chased

  3. The same check done twice by two teams

    Duplicate work removed, the control kept

  4. Performance discussed by opinion

    Performance tracked against agreed measures

What this practice covers

The work itself

Engagements draw on whichever of these the situation needs. Very few use all of them, and we will say which we think apply before you commit to anything.

Seeing the work as it is

Following real transactions end to end rather than reading the documented version, because the two are never the same and the difference is the finding.

  • Process discovery
  • Process mapping
  • Process diagnostics
  • Operational audits

Redesigning it

Removing steps that no longer earn their place, while keeping every control that exists for a reason — and being able to say which is which.

  • Workflow redesign
  • Waste reduction
  • Duplicate activity reduction

Making it hold

Building the agreed process into the systems people use daily, so the correct path is also the path of least resistance.

  • Process automation
  • Internal control improvement

Knowing whether it worked

Measures agreed before the change, baselined before the change, and reviewed after it — so the improvement is demonstrable rather than asserted.

  • KPI development
  • Productivity improvement
  • Continuous improvement

How it runs

What happens if you call us

Every engagement has a decision point at the end of each stage. You can stop at any one of them, and what you have paid for up to that point is yours to take elsewhere.

  1. 01

    Follow the work

    We sit with the people doing it and follow real transactions from start to finish — including the workarounds, the side spreadsheets and the informal approvals that never appear in a procedure document.

  2. 02

    Show it back

    A map of the process as it actually runs, put in front of the people who run it. Disagreement at this stage is productive: where two departments describe the same step differently, that is usually the finding.

  3. 03

    Redesign it together

    What goes, what stays, what is automated — and for every remaining step, a stated reason why it exists. Controls are kept deliberately, not by default, and removed deliberately, never by accident.

  4. 04

    Build it in and measure

    Changes made in the systems people use, then measured against the baseline taken beforehand. A process that lives only in a document has already started reverting.

What you get

The things you keep

Advisory work is easy to buy and hard to hold on to. These are the artefacts that remain with you afterwards, and they belong to you whether or not the engagement continues.

  • A current-state map built from real transactions, not from the procedure manual
  • A quantified account of duplication, rework and delay, with the point each occurs
  • A redesigned process with the control purpose of every remaining step stated
  • The changes made in the systems people actually use, not only in a recommendation
  • Agreed measures with a baseline taken before the change, so the result is demonstrable
Three colleagues standing in discussion, one explaining a point from a tablet, sticky notes on a board behind them.

Where this is not the answer

We will not deliver a process improvement report and leave. If the recommendations cannot be built into the systems people use every day, the old process returns within a quarter — everyone involved knows it, and the report becomes evidence that consultants do not work.

Improve Your Business Processes

Tell us what you are trying to improve and we will tell you, plainly, whether we are the right people for it.

Book an Assessment

Also in services

Other practices

Back to top