The Control Phase, deep-dive course
Lock in the gains: SPC, standard work, response plans, hand-off to the process owner, closure, and replication — worked through the same mid-sized IT Service Desk project.
What is the Control phase?
Improve proved the fix works in a pilot. Control makes sure it keeps working after the project team walks away: the new process is documented, monitored, owned, and protected against slipping back to the old way.
The “C” means two things
Control — hold the gains with SPC, standard work, and response plans. Continue — keep improving and spread what worked to other teams. A project is not “done” at go-live; it is handed to an owner who keeps the loop running.
Document
Capture the improved process as standard work so everyone does it the same way.
Monitor
Track the vital few measures on control charts with a response plan for signals.
Hand off & replicate
Transfer ownership, close the project, and look for other places to reuse the fix.
Where the Service Desk Project stands
- Define: tickets took far too long to resolve (baseline 3.6 days vs. a 1-day SLA).
- Measure: a validated measurement system (Gage R&R 4%) and a right-skewed baseline.
- Analyze: vital X's confirmed — queue wait time, ticket category, and the auto-routing × training interaction (86 → 42 hours in the DOE).
- Improve: bundle of auto-routing, triage training, staffing realignment, and a poka-yoke ticket form, piloted and validated.
- Control (now): the new process averages about 40 hours. Control keeps it there — and “Continue” pushes on toward the 24-hour SLA.
The importance of the Control phase
Without controls, processes drift. People revert to habits, new staff learn the old way, and the improvement quietly decays. Drag the slider to see what happens over a year.
| Without Control | With Control |
|---|---|
| Gains erode within months | Gains are locked in and measured |
| Knowledge lives in a few heads | Standard work and SOPs anyone can follow |
| Problems found by customers | Signals caught early by control charts |
| Project “ends” and no one owns results | Named process owner with a response plan |
| Wins stay in one team | Replicated to similar processes |
From Improved Process to Sustained Result
Document the improved process
Write standard work, SOPs, and update the process map for the new routing, triage, and form.
Build mistake-proofing & visual management
Lock in poka-yoke controls and put queue boards where the team sees them every day.
Establish SPC and the monitoring plan
Control charts on average resolution time, reopen rate, and CSAT, with a response plan for each signal.
Train people and run the communication plan
Everyone who touches the process is trained; stakeholders hear what changed and why.
Transition to the process owner
The service desk manager accepts ownership, documents, dashboards, and the response plan.
Verify results and close the project
Confirm benefits with Finance, hold the final gate review, and archive lessons learned.
Replicate and continue
Share the solution with other support teams and feed new ideas into kaizen.
Core Components and Activities
Tap each component to open it. Together they form the control system.
Statistical Process Control (SPC)
Control charts separate normal variation from real signals so the team reacts only when something truly changed.
IT example: a daily chart of average resolution time with control limits.
Standard Operating Procedures (SOPs)
Step-by-step written instructions for the improved process, with owners and versions.
IT example: “How to triage and route a new ticket” in the knowledge base.
Mistake-Proofing (Poka-Yoke)
Controls that make errors impossible or instantly visible so quality does not rely on memory.
IT example: locked category dropdown and required fields on the ticket form.
Response and Escalation Plans
What to do, who does it, and how fast when a control signal appears.
IT example: a point above the upper limit triggers a same-day review by the shift lead.
Personnel Training and Hand-Off
Everyone who runs the process is trained, and the process owner formally accepts the results.
IT example: triage refresher in onboarding plus a signed hand-off checklist.
Process Audits and Visual Management
Scheduled checks that the process is followed, plus boards and signals that make status visible at a glance.
IT example: monthly SOP audit and a wall dashboard of queue age.
SPC: Common vs. Special Causes
SPC assumes every process varies. The question is whether the variation is normal noise or a signal worth acting on.
Common (chance) causes
Always present, many small sources, predictable pattern. Points stay inside the limits. Fix: improve the system — don't tamper day to day.
Special (assignable) causes
Unusual events from specific sources. Points outside limits or non-random patterns. Fix: find and remove the specific cause.
Try it: sort the causes
Tap a cause, then tap the bucket it belongs in.
Common cause
Special cause
0 of 8 sorted correctly.
Interactive control chart
Daily average resolution time after the Improve rollout. Pick a scenario, then add your own data point with the slider.
| Signal rule | What it looks like | Likely meaning |
|---|---|---|
| Beyond a limit | One point above UCL or below LCL | Special cause event |
| Run / shift | 7 points in a row on one side of center | Process mean has moved |
| Trend | 6 points steadily rising or falling | Gradual drift (wear, backlog) |
| Chart type | Data | Service Desk use |
|---|---|---|
| X-bar & R | Continuous, subgroups | Average resolution time per day |
| Individuals (I-MR) | Continuous, one value at a time | Weekly CSAT score |
| p chart | Proportion defective | % of tickets reopened |
| c / u chart | Count of defects | Misrouted tickets per day |
Control Tools: SPC, TPM, Visual Factory, and Lean
The most common tools are SPC, Total Productive Maintenance, Visual Factory, and the Lean tools — 5S, Kanban, Kaizen, and Poka-yoke. Tap a tool.
Total Productive Maintenance (TPM)
TPM is the systematic execution of maintenance by all employees through small-group activities. It seeks to reshape the organization to make full use of its own potential.
TPM in an IT service desk
Agents own the health of their own tools: they report slow systems early, run weekly checks on the ticketing platform and routing rules, and fix small issues themselves — so the process doesn't break at the worst moment.
Documentation, Standard Work, Visual Management
Documentation
Process map, SOPs, training guides, and the control plan — kept current and easy to find.
Standard Work
The best-known way to do the work, with steps, sequence, and timing so results are repeatable.
Visual Management Checklist
20 questions that test whether abnormal conditions are obvious at a glance.
Standard work for “Triage and route a ticket”
| # | Step | Target | Key point |
|---|---|---|---|
| 1 | Review auto-assigned category | 1 min | Confirm; override only with reason |
| 2 | Check priority and asset tag | 1 min | Form blocks missing fields |
| 3 | Route to specialist queue | 2 min | Use rules-engine suggestion |
| 4 | Send acknowledgement | 1 min | Use approved template |
| 5 | Log exceptions | As needed | Feeds weekly kaizen review |
Mini visual-management audit
A quick six-question taste of the full 20-question checklist. Tick what is true for your team.
Monitoring Plan and Response Plan
A monitoring plan says what to watch, how often, and who watches. A response plan says what happens when a signal appears.
| Measure | Chart | Frequency | Owner |
|---|---|---|---|
| Avg resolution time (Y) | X-bar & R | Daily | Shift lead |
| Queue wait time (vital X) | Individuals | Daily | Queue manager |
| Reopened tickets | p chart | Weekly | Quality analyst |
| CSAT score | I-MR | Weekly | Desk manager |
Try it: what happens when a signal fires?
Quick wins and visual boards
Before hand-off, the team inventories its quick wins, visual boards, and other value-adding techniques, and considers what might work for another team.
Maintaining Control and Sustaining Improvements
Maintaining control
- Control charts reviewed on schedule
- Response plan followed for every signal
- Periodic process audits
- Poka-yoke controls checked for bypass
Sustaining improvements
- Training built into onboarding
- Standard work updated, not abandoned
- Targets and incentives aligned to the new process
- Regular kaizen events to improve further
| Risk to sustainment | Countermeasure |
|---|---|
| Staff turnover | Standard work + onboarding training |
| Workarounds creep in | Poka-yoke and quarterly audits |
| Metrics ignored | Visual board reviewed in daily huddle |
| Demand changes | Recalculate takt time and staffing quarterly |
Communication Plan and Transition to the Process Owner
| Audience | Message | Channel | When |
|---|---|---|---|
| Service desk agents | What changed, new standard work | Team meeting + training | Before go-live |
| IT director (sponsor) | Results vs. goals, benefits | Gate review | At closure |
| End users | Faster, clearer ticket form | Email + portal banner | At go-live |
| Finance | Validated savings | Benefit sign-off | 30–90 days post |
Hand-off checklist (service desk manager = process owner)
Project Exit and Closure Plans
Closure is a deliberate event, not a fade-out. The team proves the results, transfers the work, releases resources, and records what was learned.
| Closure item | Service Desk Project result |
|---|---|
| Primary metric | Avg resolution ≈ 40 h (baseline 86 h) |
| Investment | $37,000 one-time |
| Expected annual benefit | ≈ $126,000 |
| Open item (Continue) | Still above the 24-hour SLA — next kaizen cycle |
Identify Opportunities for Replication
The final act of the project: ask “where else does this work?” Tap a candidate to see what to reuse.
| Candidate | Similar process | Same root causes | Fit |
|---|---|---|---|
| Network Ops | High | High | Start here |
| HR helpdesk | Medium | Medium | Adapt |
| Facilities | Medium | Low | Partial |
| Field support | Low | Medium | Later |
Control Phase Outputs and Deliverables
Checks are saved in your browser as you go.
Control Phase Survival Challenge
Three hearts. Three wrong answers and it's game over. Build streaks for bonus points.
Final score:
20-Question Final Quiz
70% (14 of 20) or better is a pass.
Quiz complete
Score: / 20