Portolan Operations decision desk
Open Portolan
All playbooks
Playbook · Service operations

Service operations and customer experience

Service failures are usually produced by handoffs, variability and mismatched recovery. This path maps the journey from the customer's side, measures waits honestly, and designs the promise, staffing and recovery together.

Start a decision

6 steps · 8 cited sources · free during beta

The question this path answers

Where does the customer experience break, and what should we change in the service system?

The path, step by step

  1. Blueprint the journey and its fail points

    Map one high-volume journey from the customer's actions through frontstage and backstage work to support processes. Mark every handoff and the places it commonly fails.

    Why it worksService blueprinting exposes the backstage and support work that a process map drawn from the inside misses. Most visible failures are produced by invisible handoffs.

    EvidenceBitner et al. (2008) · Frei (2006)

    CheckpointA journey map with fail points and one owner per handoff.

    Common failureRedesigning the frontstage script while the backstage handoff stays broken.

  2. Measure waits and how they feel

    Measure actual waiting at each stage and ask customers how long it felt. Compare the two, and look for unexplained waits, uncertain waits and waits where nobody communicates.

    Why it worksWaiting perception depends on whether the wait is explained, whether the customer can see progress and whether the queue feels fair. A shorter wait can feel worse when it is silent.

    EvidenceMaister (1985) · Little (1961)

    CheckpointActual and perceived wait by journey stage, with the worst gap identified.

    Common failureCutting average wait while leaving the unexplained wait untouched.

  3. Design the promise and the customer's role

    State what the service promises, what the customer must do for it to work, and what the operation will not promise. Test whether the offer, staffing and economics fit together.

    Why it worksService design has to align the offering, the funding, employee management and customer management. Customer participation can lower cost or raise variability depending on how it is designed.

    EvidenceFrei (2006) · Chase (1978)

    CheckpointA written service promise with the customer's role and the trade-offs made explicit.

    Common failurePromising a speed the staffing model cannot deliver at the peak.

  4. Staff and schedule for variability

    Plot arrivals and service time by hour. Match shifts, breaks and cross-trained staff to the peak, and give frontline staff a way to escalate when the queue exceeds a threshold.

    Why it worksQueueing evidence shows that matching capacity to the arrival pattern can improve access without adding hours, while staffing to the average hides the peak that creates most of the wait.

    EvidenceKc & Terwiesch (2009) · Green et al. (2006)

    CheckpointWait and abandonment by hour before and after the rota change.

    Common failureAdding headcount evenly across the day and leaving the peak untouched.

  5. Design recovery by failure type

    Classify recent failures by type and impact. Define a recovery for each class, including who can authorise it, how fast, and what the customer is told.

    Why it worksExperimental evidence finds that recovery resources should match the failure: the same apology or refund does not fit every failure. A generic script can increase the sense of unfairness.

    EvidenceSmith et al. (1999) · Bitner et al. (2008)

    CheckpointRecovery rules per failure class, with repeat-contact rate tracked.

    Common failureGiving every complainant the same voucher and calling it customer obsession.

  6. Test one service change and measure both sides

    Change one journey element in a controlled scope. Measure the customer outcome and the operational cost or load together, then keep, adjust or stop.

    Why it worksService improvements can move the burden rather than remove it. Measuring experience and operational load together prevents a frontstage win that creates a backstage failure.

    EvidenceFrei (2006) · Maister (1985)

    CheckpointExperience and load measured for the test and comparison group over the same period.

    Common failureRolling out a friendlier script that lengthens every contact and worsens the queue.

The evidence base

Each step above cites hand-selected research. These are the studies behind the path.

  • Bitner et al. (2008) — Service Blueprinting: A Practical Technique for Service Innovation
  • Frei (2006) — Breaking the Trade-Off Between Efficiency and Service
  • Maister (1985) — The Psychology of Waiting Lines
  • Little (1961) — A Proof for the Queuing Formula: L = λW
  • Chase (1978) — Where Does the Customer Fit in a Service Operation?
  • Kc & Terwiesch (2009) — Impact of Workload on Service Time and Patient Safety: An Econometric Analysis of Hospital Operations
  • Green et al. (2006) — Using queueing theory to increase the effectiveness of emergency department provider staffing
  • Smith et al. (1999) — A Model of Customer Satisfaction with Service Encounters Involving Failure and Recovery

More from the library

Further reading from Portolan's research library, matched by subject. These papers are not proof that any step works; check each checkpoint against your own operation.

  • Mamakou et al. (2023) — Measuring customer satisfaction in electronic commerce: the impact of e-service quality and user experience
  • Vaerenbergh et al. (2014) — A Meta-Analysis of Relationships Linking Service Failure Attributions to Customer Outcomes
  • Bustamante & Rubio (2017) — Measuring customer experience in physical retail environments
  • Ta et al. (2023) — Crowdsourced delivery and customer assessments of e‐Logistics Service Quality: An appraisal theory perspective
  • Harrison-Walker (2001) — The Measurement of Word-of-Mouth Communication and an Investigation of Service Quality and Customer Commitment As Potential Antecedents
  • Eisingerich & Bell (2008) — Perceived Service Quality and Customer Trust
  • Reimann et al. (2008) — Uncertainty Avoidance as a Moderator of the Relationship between Perceived Service Quality and Customer Satisfaction
  • Davis & Maggard (1990) — An analysis of customer satisfaction with waiting times in a two‐stage service process
  • Lee & Lin (2005) — Customer perceptions of e‐service quality in online shopping
  • Yang et al. (2004) — Measuring customer perceived online service quality

Other playbooks