Service design is a team sport
Customers experience one service even when the company is split across marketing, sales, product, support, and operations. Map the journey across handoffs, not departments.
Customers do not experience your org chart
A customer may discover the company through marketing, talk to sales, complete onboarding in the product, contact support, receive an invoice, and renew with an account manager. Internally those interactions belong to different teams. Externally they feel like one relationship.
Service design looks at the experience across those boundaries.
Map the journey around the customer’s goal
Start with what the customer is trying to accomplish, then map the stages they move through. Include visible interactions and the backstage work that makes them possible.
The useful unit is not “the support team’s process.” It is the customer journey through a problem that may cross several teams.
Pay special attention to handoffs
Handoffs are common sources of friction because context gets lost. The customer repeats information, receives a different promise, waits while ownership changes, or learns that one team cannot see what another team already knows.
For each handoff, ask what information should move, who owns the next step, and what expectation has already been set.
Include policy and systems in the map
Frontline employees often know what would help the customer but are constrained by systems, permissions, incentives, or policy. A journey map that only changes scripts may miss the cause of the problem.
Document the backstage dependencies: data, tools, approvals, staffing, and rules.
Use evidence from multiple teams
Support tickets reveal friction, sales notes reveal expectations, product analytics show behavior, finance sees billing problems, and customer success sees long-term context.
Bring those signals together before deciding that one department owns the problem.
Design the recovery path too
A service is judged not only by the normal flow but by what happens when something goes wrong. Map exceptions: failed payments, delayed delivery, incorrect data, technical problems, and unclear ownership.
A good recovery path makes the next step and responsible owner visible to both the team and the customer.
Make one cross-functional decision at a time
Service maps can become large and impressive. Keep them useful by choosing one friction point, identifying the evidence, and deciding what changes across the involved teams.
Service design is a team sport because the customer’s outcome is produced by a system. Improving that system requires the people who own its different pieces to see the same journey.