Lean Process Mapping Drives Operational Excellence
- Jul 13
- 9 min read
Updated: Jul 15
How a structured lean process mapping engagement inside a financial regulatory body's customer complaints operation uncovered significant waiting-time waste and other non-value-added activity — leading to a recommended 25% reduction in end-to-end processing time.
The Scope: A Complaints Handling Function Under Pressure
The engagement focused on a specific part of a financial regulatory body's operations: the end-to-end function responsible for managing customer complaints, from initial receipt through investigation, casework, and resolution. Complaints handling in a regulatory context carries particular weight — beyond customer experience, it typically sits under statutory timeframes, external oversight, and reputational scrutiny that don't apply in the same way to a typical commercial service function. That combination makes it a strong candidate for lean process improvement, since even small amounts of non-value-added time compound into meaningful delays against externally-imposed deadlines.
The objective wasn't to redesign the function from scratch, but to systematically identify where time and effort were being consumed by activity that didn't add value for the complainant or the organisation — and to size the opportunity for improvement using an evidence-based, structured methodology rather than assumption.
Why Start With Stakeholder Engagement, Not Data
Before any process mapping or waste analysis began, the engagement started with a series of stakeholder sessions across the complaints function — from frontline case workers through to team leaders and management. This sequencing matters: process maps built purely from documented procedures often describe how a process is supposed to work, not how it actually operates day to day, including the workarounds, informal escalations, and manual checks that build up over time but never make it into a procedure document.
These sessions served several purposes at once: understanding the current process and activities as people genuinely experienced them, surfacing pain points and frustrations that staff hadn't had a structured forum to raise before, and identifying early signals of where opportunity and risk were concentrated. Just as importantly, engaging staff directly in this way builds early buy-in for whatever changes eventually follow — a lean initiative that arrives as a set of externally-imposed findings, without the people doing the work having been heard first, tends to face far more resistance during implementation.
Mapping the End-to-End Process
With stakeholder input as a foundation, the team then mapped the complaints process end-to-end — from the moment a complaint is first lodged, through triage, allocation to a case worker, investigation, any internal review or escalation steps, through to final resolution and communication back to the complainant. This end-to-end view is deliberately broader than any single team's day-to-day perspective; individual teams typically understand their own segment of the process well, but few people in a large function have full visibility of the complete journey, including the handoffs between teams where time and information are most often lost.
The process map captured not just the sequence of activities, but who performed each step, how long it typically took, what inputs and information were required, and where decisions, approvals, or quality checks sat within the flow. This level of detail is what allows the next stage — waste identification — to move from general impressions to a specific, evidence-based view of where the opportunity actually sits.
Identifying Non-Value-Added Activity Using TIMWOODS
With the process mapped, activities were assessed against the TIMWOODS framework — a widely used lean classification of the eight categories of waste, originally developed within the Toyota Production System by Taiichi Ohno as seven forms of waste (Transportation, Inventory, Motion, Waiting, Overproduction, Overprocessing, and Defects), with an eighth category — Skills, or non-utilised talent — added later as lean thinking spread beyond manufacturing into service and office environments. While TIMWOODS originated in a manufacturing context, each category translates directly into administrative and casework environments like complaints handling:
Transportation — in an office or casework context, this isn't physical movement of goods but the unnecessary handoff of a complaint case file or information between people, teams, or systems more times than genuinely necessary to reach a decision.
Inventory — cases sitting in a queue awaiting action, whether that's an unallocated complaint waiting for a case worker, or a completed investigation waiting for sign-off. Excess "inventory" in this context ties up capacity and often hides underlying process problems until a backlog becomes visible.
Motion — case workers switching between multiple systems, searching for information that isn't readily accessible, or navigating unnecessarily complex internal processes to complete a single task.
Waiting — arguably the most direct and customer-visible waste in a complaints context: the complainant waiting for a response, an update, or a decision, and the elapsed time within the process where no active work is actually occurring on their case.
Overproduction — producing more documentation, analysis, or communication than a case genuinely requires — for example, applying a highly detailed investigation process to a straightforward complaint that could reasonably be resolved through a lighter-touch pathway.
Overprocessing — additional steps, approvals, or checks built into the process over time (often in response to a single past incident) that add effort without meaningfully improving the outcome or reducing risk for the majority of cases.
Defects — errors, incomplete information, or rework required because a case wasn't handled correctly the first time, forcing additional cycles of correction before it can progress.
Skills — case workers' knowledge, judgement, and problem-solving capability being underused, for example when experienced staff spend disproportionate time on administrative tasks that add little value relative to their expertise, rather than on the more complex casework where that expertise adds the most value.
Mapping each step of the process against these eight categories allowed the team to move beyond generic observations ("this feels slow") to a structured, evidence-based classification of exactly which activities were adding customer or organisational value, and which were not.
The Central Finding: Complainant Waiting Time
Across the eight waste categories, waiting time emerged as the most significant and recurring theme. Multiple sub-processes within the end-to-end journey were consuming substantially more elapsed time than the actual active work involved — cases sitting in queues between steps, awaiting allocation, review, or approval, with no one actively progressing them during that interval. This is a common and often underestimated finding in service and casework environments generally: the total elapsed time a customer experiences is frequently dominated by queue and handoff time rather than genuine processing effort, since active work on a typical case might represent only a fraction of its total time in the system.
This finding is particularly significant for a regulatory complaints function, where elapsed time directly affects complainant experience, statutory timeframe compliance, and the organisation's reputational exposure — all outcomes that don't require any change to the substance of how a complaint is investigated, only to how efficiently it moves through the process.
Reconciling Stakeholder Input With Data Analytics
The qualitative insight from stakeholder sessions was then reconciled against quantitative data drawn from the team's own operational records and the recorded interactions between complainants and their case workers. This step matters because stakeholder sessions alone can surface strong opinions about where problems sit, which don't always align precisely with where the data shows the largest actual impact — and conversely, data alone, without the operational context that stakeholders provide, can misidentify the root cause behind a pattern in the numbers.
By triangulating the two — the lived experience of the people doing the work, and the objective record of how long each stage actually took across a representative volume of cases — the team was able to move from a broad set of hypotheses to a specific, prioritised set of focus areas: the particular sub-processes and handoff points where waiting time and rework were most concentrated, and where corrective action would deliver the greatest improvement in complainant experience and cycle time.
From Analysis to Recommendation: A 25% Reduction in Processing Time
The combined findings from process mapping, TIMWOODS-based waste classification, and data reconciliation supported a set of recommendations projected to reduce end-to-end complaint processing time by approximately 25%. Critically, this reduction was not framed as requiring more resourcing or a fundamental redesign of how complaints are investigated — it was achieved by targeting the specific non-value-added activities identified through the analysis: reducing unnecessary handoffs, addressing queue and approval bottlenecks, right-sizing the level of process applied to lower-complexity cases, and freeing case worker time from low-value administrative tasks to focus on genuine casework judgement.
The business is now taking these recommendations forward for implementation, with the expectation that the same lean methodology and TIMWOODS-based lens can be applied to other parts of the operation beyond the complaints function specifically.
Common Roadblocks in Lean Process Improvement Within Regulated Environments
Risk aversion inflating "overprocessing." Regulatory and compliance-driven functions frequently accumulate additional checks and approval steps over time, often introduced in response to a single past incident rather than a systemic pattern. Removing these steps requires careful risk assessment, not just a process efficiency lens, since the organisation needs confidence that reducing a check doesn't reintroduce genuine risk.
Staff concern around the "Skills" waste category. Highlighting that experienced staff time is being spent on lower-value administrative tasks can be misread as a precursor to headcount reduction rather than an opportunity to redeploy expertise to higher-value casework. Clear, early communication about intent is essential to avoid this undermining stakeholder engagement.
Statutory and compliance constraints limiting flexibility. Unlike a purely commercial process, a regulatory complaints function often can't simply remove a step because it's slow — some steps exist to meet legal or regulatory obligations regardless of their processing time impact, requiring the improvement approach to distinguish clearly between genuine waste and non-negotiable compliance requirements.
Data quality and availability gaps. Reconciling stakeholder input against operational data depends on that data being granular and reliable enough to support sub-process-level analysis; many organisations discover during this stage that their case management systems don't capture the level of timestamp detail needed to pinpoint exactly where time is lost, requiring a data improvement step alongside the process improvement work.
Sustaining the improvement after the engagement ends. As with any process improvement initiative, the risk is that gains achieved during an active improvement program erode over time without an embedded mechanism — such as a standing continuous improvement review — to keep monitoring cycle time and re-applying the same lean lens as new bottlenecks emerge.
A Realistic Program Timeline
Stakeholder engagement and current-state discovery — typically 3–4 weeks. Structured sessions across frontline, team leader, and management levels to understand the process as actually experienced.
End-to-end process mapping — typically 2–3 weeks, often overlapping discovery. Building a complete, validated map of the complaints journey, including handoffs, decision points, and cycle times.
TIMWOODS-based waste identification and data reconciliation — typically 3–5 weeks. Classifying non-value-added activity against the eight waste categories and validating findings against operational data.
Recommendation development and business case — typically 2–3 weeks. Prioritising focus areas, sizing the opportunity, and preparing recommendations for business sign-off and implementation planning.
Frequently Asked Questions
What is TIMWOODS in lean process improvement? TIMWOODS is an acronym representing the eight categories of waste in lean methodology: Transportation, Inventory, Motion, Waiting, Overproduction, Overprocessing, Defects, and Skills. The framework originated in the Toyota Production System as seven wastes identified by Taiichi Ohno, with Skills (non-utilised talent) added later as lean principles were adopted more broadly outside manufacturing.
Can lean process mapping be applied outside manufacturing, such as in financial services or regulatory bodies? Yes. While TIMWOODS originated in a manufacturing context, each waste category translates directly into administrative and casework environments — for example, "waiting" becomes queue time between process steps, and "transportation" becomes unnecessary handoffs of a case file between people or systems.
Why is waiting time often the biggest source of waste in service processes like complaints handling? In most casework and service processes, the total elapsed time a customer experiences is dominated by time in queues and handoffs between process steps, not the actual active work performed on their case — meaning a complaint can spend far more time waiting than being actively investigated.
How do you identify non-value-added activity in a business process? Non-value-added activity is typically identified by first mapping the end-to-end process in detail, including who performs each step and how long it takes, and then assessing each step against a waste framework such as TIMWOODS to classify which activities genuinely contribute to the customer outcome and which do not.
Why is stakeholder engagement important before process mapping? Stakeholder sessions surface how a process is actually performed day to day — including informal workarounds and manual checks that don't appear in official procedure documents — and build early buy-in among the people whose work will be affected by any resulting changes, which improves the likelihood that recommendations are successfully implemented.
What results can a lean process improvement program typically achieve? Results vary by organisation and process complexity, but programs that combine structured process mapping, TIMWOODS-based waste identification, and data-driven prioritisation commonly identify processing time reductions in the range of 20 to 30 percent without requiring additional resourcing, by removing non-value-added activity rather than changing the fundamental nature of the work.
The Takeaway
Reducing non-value-added activity in a regulated, casework-driven environment isn't primarily a technology or resourcing problem — it's a structured discovery exercise that starts with genuinely understanding how work happens today, maps that process end-to-end, and classifies activity against a proven waste framework before recommending change. In this engagement, that discipline surfaced waiting time as the dominant opportunity and supported a 25% reduction in processing time — without requiring the organisation to compromise on the regulatory rigour its complaints function exists to uphold.
This article reflects patterns observed across lean process improvement engagements in regulated and service-based operations. If you'd like a candid assessment of where non-value-added activity may be sitting in your organisation's operations, book a free diagnostic to identify your specific opportunities and next steps.
