Lean Six Sigma in materials testing can help teams understand recurring delays, errors and capacity problems across the full service: enquiry, sample receipt, preparation, testing, review and reporting. The aim is a more dependable operation, with the required technical method and quality controls maintained.
Start by following the work between departments. A technician’s daily output tells you something useful, but it does not explain whether samples arrived correctly, equipment was ready, results needed clarification or completed reports were waiting to be issued.
Look at the service from the customer’s point of view
A customer may need a result to release work, make a design decision or satisfy a contract requirement. Establish what they need, the agreed reporting date and the information required to start. Do not promise a turnaround time before checking the applicable method, sample condition and available resources.
UKAS’s construction laboratory guidance identifies technical competence, methods, equipment, environment and handling of test items among the factors relevant to accreditation. Operational improvement needs to work within these technical arrangements, rather than treat them as obstacles.
Make work ready before releasing it
A job can look scheduled while still lacking the information needed to carry it out. Agree a small readiness check for each main route. Depending on the service, it may cover the test request, sample identity, site details, access arrangements, required quantities, reporting instructions and the relevant commercial authorisation.
Name the person responsible for resolving missing information. A shared list of exceptions is more useful than several people chasing the same query in different inboxes. Keep the definition of ready visible so planning does not quietly become a promise that an unresolved job will somehow be completed.
See how business process improvement can clarify decisions and handovers when work crosses teams.
Understand where capacity is actually constrained
| Resource | Question to investigate | Useful evidence |
|---|---|---|
| People | Is the right competence available when the work becomes ready? | Work mix, authorisations, planned cover and time spent resolving avoidable queries. |
| Equipment | Is the constraint operating time, availability, setup or release of work? | A dated equipment queue, actual availability and setup patterns. |
| Space and storage | Can samples be located and moved without repeated handling? | Locations, travel, waiting areas and identification checks. |
| Technical decisions | Are complete cases waiting for a reviewer, or are incomplete cases entering the queue? | Readiness, query age, reviewer capacity and reasons for return. |
Use this evidence before deciding that the answer is more staff, more equipment or a new system. There may be a real investment need. The purpose of the investigation is to make that decision clearer.
An illustrative example: a busy team and an ageing queue
Imagine a fictional testing operation where the daily meeting focuses on completed tests. Output looks reasonable, yet customers continue to chase late reports. A review of outstanding jobs shows that the oldest cases have passed through several different queues.
Some samples arrived before their requests were complete. Some waited for a shared preparation resource. Others were tested but needed a reporting instruction confirmed. The local output measure encouraged each team to complete available work, while the age of the whole job remained difficult to see.
The operation trials one shared job-age view, clearer readiness checks and a daily review of the oldest unresolved cases. It records why each case is waiting and who will act next. Required conditioning, curing, preparation, test and review steps remain in place.
The team compares similar work before and after the trial, checks the effect on errors and workload, and investigates cases that still run late. This is an illustration of an improvement approach, not a reported client result or a guaranteed outcome.
Choose measures that explain the whole journey
Define turnaround from an agreed start point to an agreed finish point. If you also measure from physical receipt, record when missing information prevents work from starting. Both views can be useful when their meaning is clear.
- Delivery against the agreed date: keep the original commitment visible when dates change.
- Age of work in progress: review the distribution and the oldest cases, not just the average.
- Readiness at handover: count preventable returns for missing or inconsistent information.
- Rework and corrections: separate operational errors from repeats required for technical reasons.
- Workload by route: distinguish different test families, preparation needs and resource demands.
Read these alongside technical quality evidence. A reduction in lead time has little value if it creates misidentified samples, unreliable results or additional corrective work.
Improve information flow before automating it
When enquiry, planning, laboratory and finance systems use different references or statuses, people often bridge the gaps manually. Before building an integration, agree which system owns each field, what each status means and how an exception will be resolved.
Then follow a small set of representative jobs across the proposed connection. Include a changed request, a cancelled job and an incomplete case, rather than testing only the straightforward route. Our comparison of process mapping, modelling and mining helps choose the right way to understand this work.
Start with one route and a clear problem
Choose a recurring issue such as incomplete sample bookings, an ageing preparation queue or reports returned for missing information. Give it an owner, a defined work family and a baseline that the team trusts. Read Lean Six Sigma in ISO 17025 laboratories for the distinction between improving flow and changing technical controls.
VA Innovation offers Lean Six Sigma consultancy for structured problem solving and operational improvement. The Practical Improvement Library provides editable working resources for your team’s own application.

