What the process map leaves out

Most organisations run two processes. The documented one, and the real one. Cost, delay and risk accumulate where those two diverge, and none of them appears in the reporting, because the reporting is built on the documented version.

Wrenwell redesigns processes, workflows and services around how work actually runs. That starts with watching it, because in a workshop people describe the process they are supposed to follow, then go back to their desks and do something more sensible that nobody has written down.

Wrenwell works alongside operational leaders to find where effort is wasted, where handoffs fail, and where controls exist on paper but not in practice. Then what is found gets changed, the change gets measured, and the routine that keeps it holding after the engagement gets built.

Operational redesign

  • Process & Workflow Redesign — End-to-end redesign grounded in direct observation of the real operation, workarounds included. The design is for the operation you have, and it removes the reasons the workarounds existed in the first place.
  • Service Redesign — Services rebuilt around what users actually need and what the operation can sustainably deliver. Service level and cost trade off against each other, and which way the trade is being made is stated before the work starts.
  • Control Effectiveness — Controls tested by walking the process with the people who run it. Where a control is not working, that gets said and the control gets redesigned, because retraining people into compliance theatre fixes the audit finding and nothing else.

Operational improvement

  • Performance Measurement — Metrics the front line recognises as real and managers can act on. Measures that drive the wrong behaviour get removed, and that often means removing more than gets added.
  • Waste & Friction Reduction — Targeted removal of rework, queues and handoff failure, prioritised by where the operation actually loses time. That is seldom where measurement is easiest.
  • Sustainment — Improvement designed to hold, with the management routine, ownership and reporting to sustain it. Improvement decays when nobody has been made responsible for noticing that it has decayed.

How an engagement runs

  • Observe — Watch the operation run, including the undocumented workarounds people rely on.
  • Diagnose — Quantify where effort, time and control effectiveness are actually being lost.
  • Redesign — Rebuild the process and the measures together, and pilot before scaling.
  • Sustain — Install the ownership and management routine that keeps the improvement in place.

What prompts the call

  • Cost or cycle time has drifted and the process map no longer describes reality.
  • An audit or incident has shown a control that exists on paper but not in practice.
  • A previous improvement programme delivered gains that have since decayed.

Where this has been done. An international retailer rebuilt its payment systems and the financial processes on top of them against a date it could not move. Read the case studies

Related practice areas

Standards and obligations

What process work runs against

BPMN and DMN, the sixth edition of ISO 9001, ISO 9241-210 for human-centred design, the DTA’s Digital Experience Policy, and the automated decision-making disclosure that falls due on 10 December 2026 are what process and service design work runs against. There is no ISO standard for process mining.

All five areas are set out in one place, with sources and dates, on the standards and obligations page. It was last checked in September 2026.