Stop Making Customers Chase the Answer
By Aldridge Dagos, operations software engineer
The customer wanted to finish a course. Your business also gave them a coordination job.
Imagine paying for a training course that includes a completion certificate. You attend the sessions and finish the required work. The instructor says your certificate will arrive by the end of the week. On Monday, you send a message because nothing has arrived. A helpful coordinator checks your attendance and arranges for the certificate to be issued.
It arrives with the wrong name. You reply with the correction, then receive a request to send the original registration confirmation so another team can check it. Everyone you meet behaves well. You have completed the training and acquired a second subject: the provider’s internal administration.
The provider can count each conversation as work handled. From your side, it is one course that keeps asking for attention. You have become the most invested person in getting the provider’s own job across the finish line.
In his January 2009 paper, John Seddon defines failure demand as “demand caused by a failure to do something or do something right for the customer.” Answering a preventable inquiry does not make that inquiry necessary.
That thought belongs beside the management argument in his 2003 book, Freedom from Command and Control. A business can become very good at processing work that its own design keeps producing.
Customer effort 01
One unfinished promise can make the work return
Original need Finish the course with a usable record
The work returns
- Course completed
The learner has done the required work.
- Certificate late
A promised part of the service is missing.
- Wrong name arrives
The record still needs correction.
- Learner chases
The same need creates another contact.
The customer reaches the finish
- Name confirmed
The learner checks it during enrollment.
- Course completed
Certificate delivery is part of the finish.
- Usable record sent
The learner can put the whole job down.
One customer, several pieces of work
The course example is invented, but the distinction it makes is practical. Asking about the next course could lead to a new enrollment. Asking for a correct record of a course already completed asks the provider to finish a responsibility it already accepted.
Those requests deserve different attention. The first may call for another instructor or a larger classroom. The second may disappear when the service fits together. Hiring someone to answer it faster could be useful today while leaving the reason for tomorrow’s call untouched.
Contact volume needs interpretation. New interest and unfinished service both make phones ring. The count alone cannot explain the demand.
The distinction stays hidden when every department counts its own successful action. The instructor taught the course, and the coordinator answered the message. Sending the certificate completes another task. The learner is still trying to obtain the record they were promised.
I want the completion rule to include the learner’s usable certificate. That keeps the discussion attached to something the business promised and the customer can recognize. It also gives the coordinator a reason to involve whoever controls the issuing process, rather than apologizing for a result they cannot change alone.
Seddon recommends studying demand in the customer’s terms. “Certificate inquiry” names a topic. “I completed the course and still cannot show the record I was promised” preserves the unfinished need.
There is a related habit in looking beneath a feature request. The first thing a person asks for may name the help they can imagine. Here, the request for an update may conceal a service that has quietly appointed the customer to keep it moving. That appointment comes without a salary.
The missing answer lives upstream
It would be easy to tell the coordinator to send more updates. That might help with the first delay. It would do little about the wrong name, because faster delivery of an unusable certificate still leaves the learner with work to do.
The word “complete” needs to include the promise made at enrollment. The teaching may have ended while the service still owes something. The instructor has finished their part. The business needs to deliver a certificate the learner can actually use.
A useful redesign could confirm the certificate name while the learner is still enrolling and bring certificate delivery into the course’s definition of completion. It could give the coordinator a clear way to correct an error without sending the learner between departments. The right choice depends on where the current name and approval come from.
An enrollment form could show the certificate name for confirmation before payment. If an employer buys the course, the payer’s billing details may differ from the learner’s name, which gives the provider two legitimate names for two different purposes. Keeping those uses separate would spare the coordinator from deciding which field the designer intended.
Ask while the learner is already supplying information, then make the confirmed version available to the person issuing the record. An extra form sent after the course simply creates another task for everyone. That small distinction is easy to miss when the enrollment screen is designed only around taking payment.
Compare that with writing a warmer apology for the next learner. Courtesy matters, and the person waiting deserves it. Yet the apology consumes time on both sides without changing what the next customer will encounter. A script can improve a conversation while the service remains exactly as troublesome.
The concierge booking site makes a small related distinction: receiving a lead includes confirmed delivery to the team. A friendly message on the visitor’s screen cannot, by itself, prove that someone inside the business has received the work. Completion has to cross the gap.
Some gaps come from commercial promises. The course page may promise a certificate before anyone has agreed who releases it. Others come from rules that once solved a problem and survived after it disappeared. A manager may need to change those conditions before the person answering the phone can improve anything.
Seddon’s paper links repeat contacts to fragmented work and activity targets. A quickly closed contact can leave the customer’s problem alive.
The owner gets something useful from this view. Instead of asking who should answer more messages, they can ask which promise keeps creating messages. That question reaches the choices they have authority to change.
Keep the door open
Keep help available while improving the service. Hiding the phone number merely leaves a customer with fewer ways to finish.
Silence proves very little. A person may have received the answer, given up, switched to another channel, or decided to leave. You need to inspect what happened to the original need before celebrating the quiet.
Useful contact should remain welcome. A learner asking about the advanced course has introduced new work. Someone seeking clarification about a lesson may want help they could reasonably expect from an instructor. A worried person may need a conversation even when written information exists.
Seddon distinguishes predictable failures from unusual events. Study recurring causes before redesigning the service around an isolated surprise. The affected learner still deserves help while you make that distinction.
Workers need protection from a careless reading of this distinction. The person who hears the complaint should not have to prove that it belongs to another department before helping. Give them enough room to settle the customer’s immediate need and a way to surface what made the help necessary.
An owned review path for unresolved work serves that immediate duty. It keeps a difficult case from vanishing. Learning from repeated customer effort serves a different duty: changing the ordinary service so fewer people arrive with the same difficulty.
Time spent fixing the original condition belongs in the workload. Asking a coordinator to handle every return call and redesign certificate issuing between calls is a neat way to keep the process unchanged. The manager must make space for the improvement and bring in whoever can alter the rule.
For the employee, the concrete gain is the chance to complete useful work without repeatedly defending a condition they did not choose. For the customer, it is the ability to ask a question because they want help, rather than because vigilance has become part of the purchase.
Let the customer put it down
Seddon treats the measure as a temporary aid to understanding the service.
The training provider could examine what happens after the next course ends. Did the promised certificates reach the learners, and were the records usable? A quieter inbox would be incomplete evidence. It might simply mean fewer people enrolled or that frustrated learners started calling instead of writing.
There is useful commercial information in that check. The provider may discover that participants need a particular detail on the certificate for an employer’s training record. It can clarify what the course supplies before the next enrollment. A promise becomes easier to keep when both sides mean the same thing by its finish.
The learner should also be able to flag a wrong result without reopening their entire course history. Asking for a correction should not mean proving attendance again when the provider already holds that proof. Give the coordinator access to what they need and a clear responsibility for carrying the correction through.
What happens to the time recovered matters too. The coordinator might answer new enrollment questions with more care or help an instructor prepare the next cohort. The provider might simply stop carrying yesterday’s preventable conversations into tomorrow. Choose a useful destination for that time without claiming every removed call creates a sale.
There is a quieter benefit for the customer. A completed service can leave their attention entirely. They can stop checking messages and rehearsing their history for the next person. The business no longer occupies a small, unwanted corner of the day.
Imagine finishing the course and receiving the correct certificate when promised. You save it beside your notes and return to work. The next time the course comes to mind, it can be because you found a use for something the instructor taught.
That is a good thing to be remembered for later.
Frequently asked questions
Can an automated update reduce failure demand?
It can when the update answers a real uncertainty with accurate information. It will not repair a missed promise on its own. Check whether the customer can act on the message and whether the underlying service reaches completion.
Should repeat contacts be counted per employee?
Study the service first. Keep related contacts together to identify which decisions produced the repeat work.
Does a customer changing their request count as failure demand?
A new preference can create legitimate new work. Look at why the contact happened. Asking to join another course differs from asking for the enrollment confirmation the provider promised to send.
What if the delay comes from an outside supplier?
Separate the supplier’s delay from the uncertainty your business can control. Give the customer a truthful expectation and a workable next step. Then consider whether sourcing or the original promise needs to change.