Consider a hospital attempting to redesign its discharge process. The clinicians speak of care pathways and risk mitigation. The finance team frames the same problem through length-of-stay metrics and reimbursement codes. Operations sees bed turnover. IT sees system integration constraints. Patients, meanwhile, describe confusion, anxiety, and the strange loneliness of not knowing when they can go home.

Each group is discussing the same service. Each is correct. And each is operating within a semantic universe largely opaque to the others. The gap between them is not merely communicative—it is ontological. They perceive different realities because their disciplines have equipped them with different instruments of perception.

This is the terrain where service designers actually work. The romantic notion of the designer as creative visionary obscures a less glamorous but more consequential role: the designer as translator. Not translator in the shallow sense of rewording jargon, but in the deeper sense of moving meaning across incompatible worldviews without flattening what makes each perspective valuable. Systemic change depends on this translation work more than it depends on any particular design artifact or method.

Every organizational function develops its own dialect. Marketing speaks of segments, journeys, and conversion. Engineering speaks of dependencies, technical debt, and sprint velocity. Legal speaks of exposure, liability, and precedent. These are not merely different words for the same phenomena—they encode different theories of what matters.

The vocabulary a function uses reveals its success criteria. When operations talks about throughput, embedded in that word is a worldview where efficiency is virtue and variance is enemy. When clinicians talk about outcomes, they invoke a longer time horizon and a different moral register. Neither is wrong, but neither is complete.

Assumptions travel invisibly inside terminology. A finance director hearing the word experience may mentally translate it as satisfaction score—something measurable, defensible, budgetable. A designer using the same word may mean the felt texture of interaction across time. Both believe they are discussing the same thing until the project stalls at a review, and no one can name why.

Mapping these language differences is diagnostic work. Before intervention comes cartography: who uses which terms, what those terms actually reference in daily practice, and where the misalignments hide. This mapping resembles ethnography more than design research. It requires listening for the frames beneath the words.

The service designer's first contribution is often simply making the language landscape visible. Once functions recognize they have been talking past each other, the possibility of genuine dialogue opens. Not agreement, necessarily—but the more modest and more useful achievement of understanding what one is actually disagreeing about.

Takeaway

Vocabulary is not neutral—it encodes a worldview. Before you can redesign a service, you often have to redesign the conversation about the service.

Translation between languages is famously imperfect. Translation between organizational logics is worse. The service designer working across functions must decide, moment by moment, what to preserve and what to sacrifice as an idea moves between contexts. This is craft, not technique.

Consider the challenge of carrying a customer insight from a research session into a boardroom. The insight in its raw form—a mother in tears describing why she abandoned an application—has evidential and emotional weight. Rendered as a slide with a percentage, it acquires legitimacy but loses the texture that made it meaningful. Rendered as a persona quote, it may travel further but lose specificity. Every translation is a trade.

Skilled translators develop a sense for what a receiving audience can actually metabolize. A story that lands with the design team may bewilder the CFO not because the CFO is uncurious, but because the story lacks the structural features her decision-making requires. The designer's job is not to make the CFO more like a designer, but to find the form in which the insight can do work in her world.

This is why great service designers are often unglamorous communicators. They repeat themselves in different registers. They rebuild the same argument in the vocabulary of each audience. They resist the efficiency of a single deck that speaks to everyone, because such artifacts usually speak meaningfully to no one.

Preservation of essential meaning is the ethical dimension of translation craft. It is possible to make an idea acceptable by hollowing it out—stripping the discomfort that made it necessary. Good translators know when to protect the friction. The point of moving ideas across boundaries is not to make everyone comfortable, but to make coordinated action possible on problems that would otherwise remain invisible.

Takeaway

Every translation is a trade-off between fidelity and reach. The craft lies in knowing which distortions serve understanding and which erase it.

The sociologist Susan Leigh Star coined the term boundary object to describe artifacts that are meaningful across different communities while meaning different things to each. A patient journey map is a boundary object. So is a service blueprint, a prototype, a role-play script. These are not neutral documents—they are staging grounds for negotiation.

The value of a boundary object lies precisely in its productive ambiguity. A clinician looking at a journey map sees clinical touchpoints. An operations manager sees resource allocation. A patient advocate sees moments of vulnerability. The map does not force them to agree on what the service is. It gives them a shared surface on which to reveal what they each think it is.

This differs from consensus-driven artifacts, which try to produce a single agreed-upon representation. Consensus artifacts often achieve peace at the cost of insight. Everyone signs off, but no one has actually moved. Boundary objects, by contrast, hold difference in view. They make disagreement legible and therefore workable.

Designing effective boundary objects requires restraint. The temptation is to add detail, resolve ambiguity, close down interpretation. But the object's power depends on what it leaves open. A blueprint that specifies too much becomes a plan, and plans belong to whoever wrote them. A blueprint that specifies the right things and leaves the rest open becomes a shared instrument of inquiry.

In systemic work, boundary objects often outlast projects. Long after the workshop ends, the artifact continues to organize conversations. It becomes a fixture in how the organization thinks about the service. This is where service design does its most durable work—not in the recommendations, but in the persistent scaffolding it leaves behind for others to build upon.

Takeaway

Good boundary objects do not eliminate disagreement; they make it productive. False consensus is more dangerous than acknowledged difference.

The translator role is easily undervalued because it produces no signature aesthetic. There is no visible style to point to, no portfolio piece that captures what happened when a procurement director finally understood what a frontline worker had been saying for years. The work is diffuse, relational, and often invisible even to those who benefit from it.

Yet this is where service design earns its claim to systemic relevance. Complex organizations do not fail primarily because of bad ideas. They fail because good ideas cannot travel across the boundaries that separate the people who need to act on them. Translation is the connective tissue of coordinated change.

For designers working in this mode, the strategic implication is clear: invest in the boring craft of moving meaning. Learn the dialects. Build objects that hold complexity. Resist the seduction of clean consensus. The systems worth changing are the ones where translation was previously impossible.