SUMMARY
1.The Underlying Architecture of Services
From the customer’s perspective, services are experiences. From the organization’s perspective, services are the processes that are designed and managed to create the desired experience for customers. Processes are the underlying architecture of services.
2.Flowcharting and Blueprinting
Flowcharting is a technique for displaying the nature and sequence of the different steps in delivering a service to the customer. It is a simple way to visualize the total customer service experience. Blueprinting is a more complex form of flowcharting, specifying in detail how service processes are constructed, including what is visible to the customer and all that goes on in the back office. Blueprints facilitate the detailed design and redesign of customer service processes.
3.The Design Elements of a Blueprint
•The front-stage activities that map the overall customer experience, the desired inputs and outputs, and the sequence in which the delivery of that output should take place.
•The physical evidence the customer can see and use to assess service quality.
•The line of visibility clearly separates what customers experience and can see front-stage, and the back-stage processes customers cannot see.
•The back-stage activities that must be performed to support a particular front-stage step.
•The support processes and supplies where support processes are typically provided by the information system, and supplies are needed for both front- and back-stage steps.
•Fail points are where there is a risk of things going wrong and affecting service quality. Fail points should be designed out of a process (e.g., via the use of poka-yokes), and firms should have backup plans for failures that are not preventable.
•Common customer waits in the process and points of potential excessive waits. These should then either be designed out of the process, or if that is not possible, firms can implement strategies to make waits less unpleasant.
•Service standards and targets should be established for each activity, reflecting customer expectations. This includes specific times to be set for the completion of each task and the acceptable wait between each customer activity.
4.Developing Fail-Safe Methods
A good blueprint identifies fail points where things can go wrong. Fail-safe methods, also called poka-yokes, can then be designed to prevent and/or recover such failures for both employees and customers. A three-step approach can be used to develop poka-yokes:
•Collect information on the most common fail points.
•Identify the root causes of those failures.
•Create strategies to prevent the failures that have been identified.