Maps that cross departments need shared upkeep

What it is

The journey is drawn from the in-store question through after-sales, yet only the experience team may edit it. The store changes its greeting script, fulfillment changes the cut-off, and the handoffs on the map stay old. A map that crosses departments, without shared upkeep, detaches from the present in organizational space—not because time aged it, but because the people with jurisdiction never treated it as their file. Shared upkeep means each stretch’s owner can change that stretch and must see the seam with the next, rather than outsourcing the whole sheet to a “UX” role.

Why it happens

Departments optimize local metrics. Change notices travel internal channels and do not automatically reach the master map. The experience team knows the observation from the study, and does not know the rule the neighboring team shipped last week. Unilateral edits misdraw other people’s steps, so those people refuse the map and retreat to local flowcharts. After the refusal, cross-department breaks become oral lore again. Unless ownership is sliced by touchpoint and written into duties, the map’s status in the organization is a display piece: anyone may cite it, no one is answerable for its being wrong.

Studying it

List the department that actually runs each step, and check whether that department’s latest process change was written onto the map. Ask whether each group treats the sheet as an editable working file or as “the experience team’s poster.” Compare a single owner with stretch-level co-owners plus a seam review, on how many steps diverge from field rules. Outcomes: unsynced changes, steps a department will not acknowledge, and whether seam steps have a named owner.

Where it stops holding

A map that sits entirely inside one team’s control need not drag in unrelated departments for ceremony. Shared upkeep is also not an invitation to draw internal back-office procedures onto a user journey—unseen work belongs on another kind of diagram. What must be co-owned here are the stretches a person actually walks. If a vendor-run touchpoint is on the map, ownership must name the contract counterpart; otherwise “shared” happens only inside the client, and the map still detaches from the field.

Applying it

• Put an ownership table next to the legend: each step names the executing team and who may edit; ownerless steps do not enter a decision meeting.
• Where adjacent stretches belong to different departments, name a seam owner; a change on either side must notify the other and edit the map.
• Do not let the experience team ghost-write other departments’ steps. Those stretches are filled from that department’s live rules; research only supplies observational collisions.
• Audit: take a recent cross-department rule change and see whether the matching step moved. If not, treat the map as detached and pause using it for scope.

Related

• Same group: Q4.04.1 A journey map spans touchpoints and shows the whole course · Q4.04.2 Emotion and pain on the map need a source · Q4.04.3 An unverified map is a team hypothesis · Q4.04.4 As-is maps what happens; to-be maps what is wanted — keep them apart · Q4.04.5 Too fine a grain drowns turning points; too coarse hides breaks · Q4.04.7 An unrefreshed map drifts from a changed process
• Adjacent: Q4.05 Service blueprints · Q4.17 Communicating findings and acting on them
• Search terms: cross-department journey ownership · shared journey maintenance · organizational drift of maps