01 · Create ownership around the process
Create ownership around the process
A process control team is the operating group responsible for maintaining an agreed process, responding to deviations and managing changes. The label is a practical organisational arrangement rather than a requirement to form a new committee for every improvement. Where existing daily management already covers the process, use that structure and clarify its responsibilities. The essential feature is reliable ownership that continues after the project team disperses.
Start with the end-to-end outcome. Dispatch quality may depend on order data, packaging, release checks and carrier collection. A team confined to the loading area cannot resolve every relevant issue. Identify a process owner with authority over the operating standard and clear escalation routes to other functions. Include the people who perform the work, because they can explain conditions that summary data miss. Add technical specialists when a decision actually needs their expertise.
Keep accountability distinct from participation. One role owns the process result; another may maintain data or equipment. Many people can contribute to improvement without all becoming joint approvers. Ambiguous shared ownership often produces a gap in which everyone assumes someone else has acted.
02 · Prepare a compact control agreement
Prepare a compact control agreement
Agree the process boundary, customer requirements, current standard, key measures and known risks. For each measure, specify the definition, data source, review frequency and response. Clarify what operators may do immediately, what supervisors may authorise and what requires a wider decision. Include backup roles for absence and out-of-hours work. A control plan that depends on one knowledgeable individual is not resilient.
Define escalation by condition and consequence. A confirmed wrong-service parcel still on site may require hold and correction. Several parcels released after a configuration fault may require wider containment and customer coordination. A stable but persistent performance gap requires improvement capacity rather than repeated emergency escalation. These conditions deserve different responses and different levels of authority.
Agree how the team will change the process. Distinguish routine restoration, a temporary deviation and a permanent redesign. Document the evidence required to adopt a new method and who checks its effect on safety, quality and downstream work. The team’s role is to keep the operating system coherent, not to require a meeting before every reasonable operational action.
03 · Worked example: Northbank takes over control
Worked example: Northbank takes over control
The fictional Northbank improvement project installs an automated carrier-service check. During the project, the analyst watches the chart and the engineer fixes system problems. After handover, the dispatch manager becomes process owner, shift leads own immediate containment, a trained coordinator checks data completeness, and the systems lead owns configuration restoration. An operator representative joins the weekly review to describe exceptions that the dashboard cannot explain.
On a late shift, a release check begins failing for one carrier. The shift lead holds the affected parcels, confirms that the scanner and order identity are correct, and calls the systems duty role. Unaffected authorised routes continue operating. The duty specialist restores the correct service table under the approved change procedure. The shift lead checks a controlled sample before normal release resumes.
At the next review, the team examines why the service table was changed without the dispatch owner’s approval. It adds a tested deployment check and a named signoff for changes affecting carrier validation. The team does not merely congratulate itself for restoring output. It closes the immediate incident and separately verifies that the new change control prevents the failure recurring.
04 · Run reviews without creating burden
Run reviews without creating burden
Use the shortest effective routine. Daily review may cover immediate abnormalities and unfinished actions; a weekly review may cover recurring losses and experiments; a periodic owner review may examine benefits, risk and capacity. Avoid reviewing the same numbers at several levels unless each level makes a distinct decision. Escalate a specific need, such as approval for a configuration change or support from transport planning.
Northbank’s daily huddle lasts only as long as needed to decide support and protection for the shift. It does not host a detailed root-cause discussion while parcels wait. The weekly control review follows the action record, checks trend evidence and chooses which recurring problem receives improvement time. Technical specialists attend that portion when needed rather than every daily meeting.
Protect work capacity explicitly. Reporting and review consume time, so measure whether they help prevent loss or resolve decisions. Stop collecting fields nobody uses. If every abnormality requires several duplicate updates, simplify the system. The control team should reduce uncertainty and recovery effort; it should not become an additional source of overload for the people whose process it manages.
05 · Interpret what the team should do next
Interpret what the team should do next
When a metric deteriorates, first verify that the observation is meaningful. Check definition, denominator, timing and missing records. Then distinguish a specific departure from the reference process from a persistent system problem. For a verified special cause, contain and investigate the event. For a stable process that misses requirements, plan a deliberate improvement. For uncertain evidence, collect the information needed to choose rather than debating opinions indefinitely.
Suppose Northbank sees more holds but fewer wrong-service dispatches. The increased holds may represent successful early detection, a new source of upstream errors or an overly sensitive release rule. The control team examines hold reasons, release outcomes and operator workload together. Declaring the hold count a failure without context could pressure staff to bypass the protective check.
Decide when an action is complete. Implementation evidence shows that a change occurred; effectiveness evidence shows its intended effect. Assign a review period suited to the frequency of the risk. A rare configuration failure cannot be proven eliminated by three quiet days. The team may need a failure-mode test, deployment evidence and longer monitoring.
06 · Develop capability and continuity
Develop capability and continuity
Common failures include creating a committee without authority, assigning measures without response owners, inviting everyone to every meeting and treating all deviations as operator errors. Another failure is keeping the improvement analyst as the permanent guardian. If the operating team cannot maintain definitions, read the chart or handle exceptions, handover is incomplete. Build those skills before declaring control established.
Use observed practice: a shift lead demonstrates containment, the coordinator reconciles source records, and the process owner explains the evidence needed for a standard change. Record unresolved capability gaps and supply support. Rotate appropriate review responsibilities so knowledge is distributed, while keeping final accountability clear.
Advanced arrangements may involve several sites or external partners. Maintain a common outcome definition but recognise local operating differences. A central review can coordinate shared carrier or software risks, while local teams retain authority to protect their own work. Review the control arrangement itself after staffing changes, expansion or repeated delays in response. Ownership should be reliable enough to survive normal organisational change.
07 · Test absence and competing priorities
Test absence and competing priorities
A useful readiness check is to simulate the absence of the usual owner during a busy period. Ask the backup to identify the current standard, locate the underlying records and make an authorised response to a representative exception. Northbank discovers through this check that its weekend supervisor can hold parcels but lacks access to the configuration incident channel. The team repairs access and confirms the duty route before the next weekend. This test is about the operating arrangement, not memorising names. Also clarify which priority prevails when throughput and release accuracy conflict, so the backup is not left to negotiate a fundamental requirement during an incident.
Connections
Related methods and phase use
Placed under Control because of the outcome it supports. Use the method in other phases when its purpose and assumptions fit the work; the phase list is a guide to selection, not a compulsory sequence.
Sources
Professional foundations and further reading
The explanation and fictional teaching examples are written for LeanTrainingLab. Linked primary sources provide professional foundations; example values and local conventions are stated in the guide. The accepted toolset draws on Six Sigma+Lean Toolset, second edition (Lunau, editor; Springer, 2013). No book text or examples are reproduced here.