Consider a patient discharged from hospital. On the ward, a dense system holds them: nurses, medication charts, scheduled checks, someone who notices if a meal goes untouched. Within hours, they are at home with a bag of prescriptions, a printed summary written in clinical shorthand, and a follow-up appointment that may or may not have been booked. Every part of the system worked as designed. The failure lives in the gap between the parts.

This pattern recurs across services. It shows up when a student graduates out of a support programme, when a customer migrates to a new billing platform, when a claimant moves from one entitlement to another, and when an employee shifts between roles inside the same company. Organisations tend to design states, such as being a patient, a customer, or an enrolled member, and treat movement between states as an administrative event. But users do not experience states in isolation. They experience the passage between them, and that passage is often where trust is quietly won or lost.

Herbert Simon described design as devising courses of action aimed at changing existing situations into preferred ones. Service transitions are exactly this kind of change, yet they rarely receive deliberate design attention. They fall between departments, budgets, and lines of accountability. This article examines three things: where transitions break down, which principles help users stay oriented through them, and how handoffs between channels, providers, and systems can be choreographed to preserve continuity.

Most service maps are drawn around touchpoints, the moments when user and organisation interact. Transitions are different. They are the stretches where a user has left one configuration of support and has not yet arrived in the next. The anthropologist Arnold van Gennep called this the liminal phase of rites of passage, a period when an established identity is suspended. In services, liminality is rarely ceremonial. It is administrative, and it is frequently invisible to the organisation.

Several categories of transition recur. Entry transitions move people from outside a service into it, through onboarding, enrolment, or admission. Lateral transitions shift users between parts of the same organisation, such as from sales to support or from one clinical specialty to another. Exit transitions move them out entirely through graduation, discharge, cancellation, or the death of an account holder. Systemic transitions happen when the organisation itself changes underneath the user through a platform migration, a policy reform, or a merger.

Each category carries characteristic failure modes. Entry transitions overload users with information before they have the context to absorb it. Lateral transitions demand that users repeat themselves, which reveals that the organisation's memory is siloed. Exit transitions often lack ownership entirely, because the departing user no longer generates revenue or appears in performance metrics. Systemic transitions impose costs on users for decisions they had no part in making.

Vulnerability is highest where three conditions overlap. The user's stakes are high, their knowledge of what comes next is low, and no single party is accountable for the passage. A useful mapping exercise plots transitions on these three dimensions. The points scoring high on all three rarely receive design investment, because by definition they sit in organisational gaps. Abandonment and confusion cluster there, but the evidence usually surfaces elsewhere. It appears as call volumes, repeat contacts, or downstream crises that get attributed to the next service rather than to the transition.

This is why transition mapping requires stepping outside the organisation's own boundaries. A journey map that stops at the organisation's edge will systematically miss exit and inter-organisational transitions. Following the user across the boundary reveals what the transition actually demands of them. That means tracing their path into the next provider, through the waiting period, and into the household absorbing the change.

Takeaway

Transitions are where organisational structure becomes user experience. Wherever accountability has a gap, users fall into it.

If transitions are where users lose their footing, the design task is to maintain orientation. Orientation is the user's sense of where they are, what has happened, and what comes next. Disorientation, more than inconvenience, is what drives abandonment. People tolerate long processes when they understand them, and they abandon short ones when they don't. This reframes the goal of transition design from speed to comprehension.

The first principle is legibility of state. Users should be able to tell at any moment which state they occupy. Parcel tracking became a reference model because the intermediate states became visible, not because delivery got faster. The underlying logistics barely changed, but their visibility did. Many services hide their in-between states entirely. An application is marked as submitted and then goes silent for weeks, and silence reads as failure.

The second principle is anticipatory preparation. Good transitions begin before the move itself. Hospitals that begin discharge planning at admission, rather than on the day of departure, are applying this logic. The user should encounter the next state as something already partly familiar, with the relevant materials, contacts, and expectations seeded in advance. Preparation spreads cognitive load across time rather than concentrating it at the moment of greatest stress.

The third principle is overlap rather than cutover. Engineers migrating software often run old and new systems in parallel before switching. Services can do the same by keeping previous support reachable while the new arrangement establishes itself. Benefits systems that withdraw one entitlement before the next activates create cliffs, and overlapping them creates a bridge. Overlap costs more in the short term, which is precisely why it gets cut. Its absence generates failure costs that land on other budgets and other services.

The fourth principle is a named point of return. In any transition, users need somewhere to go when things don't work as described. That might be a person, a reference number, or a single channel that holds their context. What matters is that users never have to reconstruct their situation from scratch. These principles share a logic drawn from Simon's work on bounded rationality. People navigate complexity with limited attention, so the design should carry the burden of continuity rather than placing it on the user.

Takeaway

People tolerate long processes they understand and abandon short ones they don't. Orientation, not speed, is the primary currency of a transition.

A transition describes the user's movement. A handoff describes the organisation's movement, the moment when responsibility passes from one channel, team, provider, or system to another. Most continuity failures can be traced to handoffs designed as transfers of tasks rather than transfers of context.

Relay racing offers a useful image. The baton must be exchanged within a defined zone, and the incoming runner starts moving before the outgoing one arrives. Both runners share the zone briefly, so the handoff is a coordinated overlap rather than a drop and a pickup. Service handoffs frequently resemble the opposite. One party finishes and closes the ticket, and the next party starts cold, often unaware of what the user has already been told.

Healthcare has developed some of the most explicit handoff practices, partly because the consequences of failure are so severe. Structured protocols such as SBAR, which stands for situation, background, assessment, and recommendation, standardise what passes between clinicians at shift change. The insight transfers well beyond medicine: handoffs need a defined payload. The receiving party needs to know what has been promised to the user and what remains unresolved. Without an agreed structure, each party passes on what seems important to them, which is rarely what matters most to the user.

The distinction between warm and cold handoffs is equally useful. A cold handoff gives the user a number to call. A warm handoff introduces them and carries context forward, and the first party lets go only after confirming the receiving party has engaged. Warm handoffs demand more coordination. They are especially difficult when the parties sit in different organisations with different data systems and incentives. At this point, handoff design becomes a governance question rather than an interface question. Someone must decide who funds the overlap, who owns the shared record, and who is accountable if the user is dropped.

Channel handoffs pose a quieter version of the same problem. A user who begins in an app, moves to chat, and ends on the phone expects the organisation to remember them across all three. Service blueprints, introduced by G. Lynn Shostack in the 1980s, are well suited to exposing these seams. They map the backstage processes that either carry context forward or let it drop. Choreography, in the end, means designing what each party does before, during, and after the moment of exchange.

Takeaway

A handoff is complete not when the sender lets go, but when the receiver holds the context and the user knows who now holds them.

Service transitions resist design attention for structural reasons. They sit between budgets, teams, and organisations, and their failures surface somewhere else, whether in the next service, in repeat contacts, or in crises that seem to come from nowhere. Treating transitions as design objects means accepting that the unit of analysis is the passage, not the state.

For design strategists, this suggests a practical reorientation. Map transitions explicitly, including those that cross the organisation's boundary, and assess them for stakes, uncertainty, and ownership. Apply the principles of legibility, preparation, overlap, and return. Design handoffs with defined payloads, and use warm transfers wherever the stakes justify the cost.

There are limits. Design cannot resolve misaligned incentives between providers, and choreography fails without governance arrangements that fund and enforce it. Still, naming the transition as something to be designed is itself a meaningful shift. It moves responsibility for continuity away from the user, who has been carrying it all along, and back to the system.