Service designers identify and order goals in service systems.  Service systems are a unit of analysis for an exchange of skills and capabilities which leads to the production of value in use (Vargo et al., 2008).  Service systems are developed though the creation of value, where reinvention can transform the relationships of use and practice. Service systems are characteristically intangible, heterogeneous, simultaneous in production and consumption, non-perishable, and grounded in times and places that maintain their meaning and value (Kimbell, in prep).

One of the ways that designers understand service systems is by using a variety of approaches and concepts that isolate or concentrate focus on the relevant aspects of a system so they can drive experimentation and change. An example of this is a touchpoint, which means the aspects of the service are visible and come in contact with the users of that service (but see this discussion of its origins). You may have suspected that in a relationship of co-creation, touchpoints multiply quickly when production and consumption are linked since users are creators and vice versa. Another example that designers use is the line of visibility. This is similar to the touchpoint, and it describes what users see and experience in their relationships with a service system. It helps in rendering a system so that its processes and organizational structure are visible.

A draft diagram of a business process showing the line of visibility between the user and the organization dedicated to providing a service.

Because touchpoints and lines of visibility exist not only as tools but in practice, service experiences are tightly bound to tied to the production of narrative. Suspense in particular is a common experience for users when parts of a process, system, or set of relationships are hidden from view.  Just imagine a time when you were the creator or recipient of a service.  Much of your uncertainty or satisfaction was probably driven by what you knew or could expect about the outcome as well as the communication process that was taking place while the service was being delivered.

Richard Allen discusses suspense in his book about [Alfred] “Hitchcock’s Romantic Irony”. Allen cites Meir Sternberg’s distinction that, “suspense derives from a lack of desired information concerning the outcome of a conflict that is to take place in the narrative future, a lack that involves a clash of hope and fear; whereas curiosity is produced by a lack of information that relates to the narrative past, a time when struggles have already been resolved, and as such it often involves and interest in information for its own sake.”

So when working in service design we should decide if we desire to create curiosity or suspense and design our process accordingly. Allen also incorporates Ian Cameron’s view that suspense is a “channeling of emotions”. Clearly emotions can be powerful, but how and why? In Allen’s analysis, suspense is something that happens in us as we are forced to take up the prospect of narrative outcomes that are contrary to the ones we desire. Suspense is constructed out of moral uncertainty, balancing our expectations with potential outcomes.

Allen discusses Hitchcock and develops descriptions of two types of suspense: pure and impure. Pure suspense is broad and objective, prolonged by tension, delay, and narration that is unrestricted, moving between vantage points and locations. It leads to an anxious uncertainty and an increased expectation of a bad outcome as the deadline looms. Arbitrary delays segment time and increase the tension because a bad outcome seems close at hand. Often, the audience sees a threat before the protagonist and surprise happens through the manipulation of time. The outcome almost always favor of the moral victory, especially in popular media.

Impure suspense on the other hand is local and subjective. It is developed from points of view that provide different sources of knowledge often through the eyes of the protagonists and antagonists, keeping the audience informed while the characters remain unwitting. Deadlines are set early on and acceleration commonly heightens the alert attentiveness of the spectators who are active participants in the construction of the suspense. Knowledge is not made by the director. It is made by the audience in cooperation with the information provided to the characters. All too often, the audiences senses the outcome before the characters do by filling in blanks sources of meaning that haven’t been provided. Impure suspense favors empathy for the character, as if we were living through them. The moral outcome is less certain and often unrealized.

In order to try to make the differences between pure suspense and impure suspense more tractable, I imagined what users in a service system might say if they were experience one or the other.  The result is in the chart below, and it adapts these distinctions and starts to resolve how one might go about implementing different narrative objectives for a service system.

References:
Vargo, S. L., Maglio, P. P., & Akaka, M. A. (2008). On value and value co-creation: A service systems and service logic perspective. European Management Journal, 26(3), 145-152. doi:10.1016/j.emj.2008.04.003