What is a deviation in manufacturing?

Any gap between target and actual that affects the flow, quality, safety or on-time delivery: a machine stop, scrap, missing material, a missed KPI. A disruption is a deviation that interrupts the flow. A defect is a deviation on the product.

How do you capture deviations on the shop floor?

Where they happen, and right away: with location, category, duration and, if possible, a photo. In ValueStreamer, the team captures deviations at the board during the meeting or on a tablet at the station. Team, station and time are filled in, and similar deviations are recognized and linked.

Can ValueStreamer create deviations automatically?

Yes. When a KPI misses its target, ValueStreamer creates the deviation automatically, set per KPI. Alternatively, the team captures it manually on the KPI. KPIs, machine and process data come in via REST API from MES, ERP or BI.

What is a deviation list?

The list of all of a team's deviations with status, category, duration, owner and countermeasure. It shows which deviations are still open, which have no countermeasure yet, and what is overdue. In ValueStreamer, the deviation list sits next to the Pareto and the top deviations, for every team and the level above.

Which software shows target vs. actual deviations right on the shop floor?

Shop floor management software that shows KPIs against their targets on the team board and links deviations to them. ValueStreamer flags KPIs off target on the board, creates the deviation manually or automatically and follows it through to the countermeasure, for every team and through the cascade up to plant management.

How are deviations escalated?

Through the cascade: whatever a team cannot solve on its own goes into the meeting of the next level, such as department, area or plant, and comes back with a decision. In ValueStreamer, the deviation stays connected to its countermeasure and its history along the way.

What is the difference between deviation management and problem solving?

Deviation management makes sure every deviation is captured, prioritized and given a countermeasure. Structured problem solving starts when the cause is unclear or the problem keeps coming back: with PDCA or an A3 report with 5 Whys and Ishikawa. In ValueStreamer, both start right from the deviation.

Is the documentation audit- and ISO-compliant?

Yes. Deviations, countermeasures and A3 reports are stored completely and stay searchable across sites, compliant with audit, ISO and VDA requirements. ValueStreamer itself is certified to ISO/IEC 27001:2022.

Home › Functions › Deviation management

Function

Deviation management in manufacturing

Capture it where it happens. See what to tackle first. Stay on it until the KPI shows the fix.

Book a demo

How a deviation is handled

Capture

At the board, on a tablet, or automatically when a KPI misses its target

Overview

Deviation list, top deviations and Pareto per team and department

Evidence

Countermeasure right on the deviation, documented for audits, ISO and VDA

Digital shop floor board from ValueStreamer on a mobile large screen: raising a deviation at screwdriving station 3 with category, duration and a hint about a similar deviation

In short

What is deviation management?

Deviation management is the fixed routine a team uses to capture every deviation from target, assess it and follow it through to a countermeasure that works. On the shop floor, the deviation is recorded where it happens, with location, category and duration. It goes onto the team board, gets an owner and a countermeasure with a due date, and is closed only when the KPI shows it stays away.

In quality management, this is a process of its own. On the shop floor, it is daily business: every shift brings deviations, and the meeting at the board decides what comes first.

Fixing deviations: how a deviation is handled

Capture

At the board during the meeting, on a tablet right at the station, or automatically when a KPI misses its target.

In ValueStreamer: manually or by rule on the KPI, with data from MES and machines via REST API.

Assess and prioritize

Category by the 6Ms, duration and frequency. The Pareto shows which cause costs the most.

In ValueStreamer: deviation list, top deviations and Pareto per team and for the level above.

Set a countermeasure

If the cause is clear, a PDCA countermeasure follows. If it is unclear or the problem keeps coming back, it moves into structured problem solving.

In ValueStreamer: countermeasure with owner and due date right on the deviation, A3 at the push of a button. Go to structured problem solving

Follow up and escalate

Open countermeasures stay visible. Whatever the team cannot solve on its own goes one level up.

In ValueStreamer: deviation list with countermeasures, escalation through the cascade, closed only after the effectiveness check.

Deviation management is step 2 of the loop at the team board.

1 · KPITarget missed?KPIs land on the board automatically and show where things go wrong.
You are here2 · DeviationWhat happened?Capture it where it happens. The Pareto shows what to tackle first.
3 · Root causeWhy?PDCA for clear cases, A3 with Ishikawa for the tough ones.
4 · CountermeasureWho does what by when?Tasks and T-Cards with an owner and a due date.

Back to 1: the KPI shows whether the countermeasure worked

Raising a deviation in ValueStreamer on a tablet: team, station, reporter, category machine, duration 35 minutes, photo and a hint about a similar deviation from July 8

Raising a deviation at screwdriving station 3, with a hint about a similar deviation

Capture

Captured where it happens

The deviation is recorded at the station, not from memory at the end of the shift. Team, station, reporter and time are already filled in, and the team adds what happened.

Category by the 6Ms, duration and frequency
Photo straight from a tablet or smartphone
Linked to the KPI where it showed up
Recurrences recognized: similar deviations are linked instead of logged twice

Automatically from the KPI

Target missed, deviation created

When a KPI misses its target, ValueStreamer creates the deviation automatically, or the team logs it with one click on the KPI. KPIs, machine and process data come in via REST API from MES, ERP or BI.

Set per KPI: create automatically or capture manually
Linked deviations right on the KPI trend
From the plant KPI down to the unit that caused it

See what comes first

All of a team's deviations in one deviation list and as a Pareto by duration or frequency. For the meeting at the board, and for the level above, which sees where its department is struggling.

With and without countermeasure in one bar
Top deviations and deviations without a countermeasure at a glance
Plan a Go & See straight from the deviation

Try the Pareto yourself

Countermeasure

Fixed, not just noted

The countermeasure sits right on the deviation: a PDCA fix with owner, due date and implementation plan. The tasks land on the owner's task board, and the deviation stays open until the effect has been checked.

Countermeasure and tasks in one step
Escalation through the cascade when the team cannot solve it alone
Fully documented for audits, ISO and VDA

Cause unclear or problem keeps coming back?

Then it belongs in an A3 with 5 Whys and Ishikawa. Go to structured problem solving

Countermeasure right on the deviation in ValueStreamer on a tablet: PDCA countermeasure with team, owner, due date and implementation plan

PDCA countermeasure for the deviation at screwdriving station 3

From lean practice

Deviations that get closed

ValueStreamer grew out of lean consulting (formerly STAUFEN.AG). The routine from deviation to verified countermeasure comes from shop floor management practice in many plants.

Audit-ready
ISO compliant
VDA compliant
ISO/IEC 27001:2022 certified

Read the Ziehl-Abegg case study

117,000+

deviations closed

53,000+

countermeasures completed

4,900+

teams work with ValueStreamer

4 weeks

from kickoff to go-live

Totals as of October 2026.

#hs_cos_wrapper_dnd_area-module-14 .cp-faq__a { grid-template-rows: 1fr !important; } #hs_cos_wrapper_dnd_area-module-14 .cp-faq__a[hidden] { display: grid !important; } #hs_cos_wrapper_dnd_area-module-14 .cp-faq__a-inner { overflow: visible !important; }

FAQ

Frequently asked questions

The fixed routine for capturing deviations from target, assessing them and following them through to a countermeasure that works. In manufacturing, it covers capturing the deviation where it happens, prioritizing by frequency and duration, setting a countermeasure with an owner and a due date, and closing it only when the KPI shows the effect.

See your deviations on the board

A 30-minute demo built around your questions: from the captured deviation to the Pareto and the verified countermeasure.

Book a demo