By function: customer service
Kaizen for customer service and support teams
In short
Kaizen for customer service teams is a way of improving support work in small steps: the agents who handle the contacts remove one recurring waste at a time, such as a second reply, a transfer or a re-typed note, and look again afterwards to see whether the change held.
Service work has two kinds of improvement: handling a contact with less effort, and removing the reason the customer had to get in touch. What follows is a list of eight frictions from a typical ticket queue, sorted by the 8 wastes of Lean in office work, a way to tell the two kinds of improvement apart, and a 5 Whys on one friction, from the first message a customer sends to a changed contact form.
Eight recurring frictions in customer service, and the waste behind each
| Friction | Waste | First question to ask |
|---|---|---|
| The first reply to a customer asks for an order number the contact form never requested | Errors and rework | What does the agent need in the first message, and where could it be asked for? |
| A question for the warehouse sits in an internal ticket with no agreed reply time | Waiting | Who is the customer waiting on, and does that team know? |
| A ticket is moved through three queues before it reaches someone who can answer it | Handoffs | What would the first person have needed to answer it themselves? |
| Weekend contacts pile up, and on Monday the newest are answered first | Backlog | In what order is the pile worked, and who decided? |
| One answer needs the helpdesk, the order system, the carrier's tracking page and a chat thread | Searching and switching | Which of these facts could be shown where the agent already is? |
| Every ticket is tagged with a reason code that no report reads | Work nobody uses | Who last made a decision from this field? |
| Call notes are typed into the helpdesk and again into the customer record | Extra steps | Who reads the second copy, and when? |
| The most experienced agents spend the morning on password resets | Skills not used | Which contacts need their knowledge, and how do those reach them? |
Most contacts show two or three of these at once. Start from the waste the customer feels, then ask why it happens. The lesson on Waiting, Handoffs, Backlog and Searching follows one customer request through all four.
Fix the cause of the contact, not only the handling of it
A service team can improve in two directions. One is inward: fewer tools, fewer transfers, fewer second replies. The other is upstream: the unclear invoice, the missing tracking link, the confusing returns page that made the customer write in the first place. The agent is the only person in the company who sees both.
- For each friction, ask whether the contact should have happened at all. If something went wrong before the customer wrote, the countermeasure belongs with the team that owns that step, and service supplies the evidence.
- Count contacts by cause for one week, in the customer's words, before choosing what to fix. A tally on paper is enough; the 8 wastes checklist has one.
- Be careful with handling time as the only measure. A change that closes tickets faster and sends the customer back a day later has moved the work, not removed it. Check repeat contacts as well.
- The customer decides what is value. A step the customer would not miss, such as an internal note nobody reads, is a candidate for removal; a step they wait for is not.
A worked 5 Whys from a support queue
This chain starts at the top row of the table, the reply that has to ask for an order number, and is four whys long. For the method itself, and for what makes an answer solid enough to build on, read 5 Whys examples from office work.
Illustrative example, not a real company.
Problem. A customer who reports a damaged item should get a decision in the first reply. In a sample of forty recent damaged-item tickets, twenty-six needed a second exchange before the agent could act.
- Why was a second exchange needed? The customer's message had no order number and no photo, so the agent's first reply asked for both.
- Why were they missing? The contact form has one free-text box. It does not ask for an order number or offer a way to attach a photo.
- Why does the form not ask? When the help centre moved to a new tool, the form was rebuilt with the tool's default fields. The order number field of the old form was not carried over.
- Why has nobody put it back? Agents have a saved reply that asks for the missing details, so the gap costs a minute per ticket and is never reported. The form belongs to the web team, and service has no agreed way to ask for a change to it.
Root cause. The contact form has no owner on the service side, and a saved reply hides the gap: each ticket is patched, and the form stays as it is.
Should this step exist? The round of asking for details should not exist for damaged items: the customer has both the number and the photo when they first write. The saved reply stays for contacts that arrive by phone or email.
Countermeasure.
- When a customer chooses "damaged item", the form requires the order number and offers a photo upload.
- One named person in service owns the form's fields, with an agreed route to the web team for changes.
- The saved reply is kept, and its use on damaged-item tickets is counted.
Check. The team counts how often the saved reply was used on damaged-item tickets in the week before the change, then one week and one month after it. It writes its prediction first: fewer than five uses a week.
The workaround is the interesting part. A saved reply is a sensible answer to a missing field, and it is also why the field stayed missing: the cost was spread thinly over every ticket, and paid mostly by the customer, who waited a day longer. Shortcuts that agents have built for themselves are a good place to look for the next friction. The lesson on countermeasures explains the difference between containing a problem and removing its cause.
Where a customer service team should start
- Ask each agent for the one thing they do every day that feels pointless. Agents know; they are rarely asked.
- Take the one that most agents named, and pull ten recent tickets where it happened. Read them from the customer's first message to the last reply.
- Write down what the customer should have received and what they received, with the count from those ten tickets.
- Ask why until the answer is a form, a rule, a tool or a missing owner. Then ask whether the step should exist.
- Change one thing for one week, with one queue or one contact reason, and compare the same count. A PDCA cycle is no more than this, written down before and after.
Templates and lessons that fit service work
- 8 wastes checklist: follow ten tickets and tally what you see.
- 5 Whys template: write the chain where the whole team can read it and question an answer.
- PDCA template: the prediction before the change, the count after it.
- Lesson: gemba walk for office work, on watching how a contact is really handled instead of reading the procedure.
- Lesson: visual management board, for a team board that shows open frictions at a glance.
Questions
What is an example of Kaizen in customer service?
Changing the contact form so that it asks for the order number and a photo when a customer reports a damaged item. The agent can then decide in the first reply instead of writing back to ask. One form changes; the round of messages it removes was paid for by both the customer and the agent.
How is Kaizen different from a quality review of tickets?
A quality review looks at how an agent handled a contact. Kaizen looks at the process around the agent: the form, the tools, the handoffs and the rules that made the contact slow or necessary.
Do we need a Lean expert to start?
No. Start with one friction, a handful of real tickets and the question why, asked until the answer is something the team can change. The free lessons on this site cover the method in short steps.
Try it on your own work
Pick one task that wastes your team's time every week. Describe it in a sentence; KaizenProof names the waste, asks why until you reach the cause, and writes the fix. No account is needed to start.