This article is an invitation. It was written by a conference organiser to UX practitioners who may not yet have heard of the conference. Its argument is that a twelve-year conversation about enterprise-scale experience work exists at the Intersection Conference, and that UX designers who have hit the seam problem belong in it.

A user's journey through your product rarely ends where your design work does. A booking flow hands off to a call centre. A self-service portal hands off to a field technician. A sign-up form hands off to a legal-review queue and a welcome email somebody else owns. A mobile app hands off to a desktop application that reports into a different team on a different roadmap. The journey continues. The user doesn't notice the seam. The designer does, and usually alone.

UX designers who work in any enterprise large enough to have these seams already know the pattern. The craft they learned — user research, interaction design, usability testing, visual design, component systems — addresses the product in front of them brilliantly. It stops at the edge of what they control. What happens next tends to be handled by people in adjacent disciplines who rarely share their vocabulary: service designers, journey owners, enterprise architects, product leaders, organisation designers, operations managers. UX either reinvents the handoff itself, case by case, or accepts that the work gets compromised at every seam.

Where is there a conversation, a venue, a community, a set of case studies, where UX designers, the practitioners who handle what comes after, and the adjacent disciplines that shape the handoffs all meet as peers?

The Intersection Conference has hosted exactly this conversation since 2014. Talks by experience practitioners at airports, banks, research universities, and enterprise software companies have focused on the seam-management work UX designers feel daily but rarely see addressed from their side of the table. The 12th edition, Intersection 26, is in Montréal this October.

Two patterns run through what the Intersection archive contains on experience work:

• When UX work outgrows the product: the journey doesn't end where the software does.
• When UX work outgrows the designer: the practice becomes the product.

When UX work outgrows the product: the journey doesn't end where the software does

The first pattern is the one named in this article's title. A UX designer has mastered the product they own. The problem is that the user's journey extends beyond that product, across channels, teams, partners, time zones, and handoff moments, and the tools that worked for a single product do not scale to an experience whose scope is larger than the software. Four talks in the archive address this directly:

• Christoph Stühmer & Sercan Seyranlioğlu (Intersection 24, Rome): Unveiling an "EDGY" Customer Journey of an airport.
  The airport is the textbook case of an experience whose scope exceeds any one team's control. The passenger moves through dozens of touchpoints owned by different entities: airline apps, airport signage, security processes, duty-free retail, ground transport. And the journey only feels coherent if someone has designed for the seams. Stühmer and Seyranlioğlu walked through how they mapped this experience using Enterprise Design methods. The talk is essential viewing for any UX designer whose product sits inside a larger customer journey they do not own.
• Marion Boberg (Intersection 25, Brussels): Where Experience Meets Architecture: The Journey Ops Effect.
  Boberg names the emerging practice that sits exactly at the seam UX designers feel. Journey Ops is the disciplined, ongoing management of cross-channel, cross-team customer journeys, a practice that service design gestured at for years without fully naming. The talk is among the clearest public treatments of what journey work evolves into when a UX designer stops designing individual screens and starts designing the system that produces them coherently.
• Klaus Østergaard (Intersection 18, Prague): Better Customer-journeys and Architecture on Small Resources.
  Not every UX team has unlimited research budgets, mature design ops, and executive sponsors. Østergaard's talk is explicitly about doing serious journey work with limited resources, which describes most UX teams most of the time. The methods transfer: lightweight journey mapping, pragmatic architecture alignment, and the decisions about what to fake, what to skip, and what to invest in.
• Tomomi Sasaki & Mael Inizan (Intersection 19, Lisbon): Scaling CX: A Story About Building Bridges Together.
  The talk's language is almost identical to what UX designers say privately about their own work. Sasaki and Inizan describe scaling customer experience work across teams that were not designed to collaborate, using shared artefacts, shared language, and shared maps. The bridges metaphor is theirs; the problem is the reader's.

The common thread across these four talks: the designer's work does not end at the product boundary, and the discipline of designing for what comes after has been refined in public, by practitioners, since 2014. It is not a new conversation. It is just one that UX media has rarely surfaced.

When UX work outgrows the designer: the practice becomes the product

The second pattern is subtler. A UX designer at enough scale stops designing screens and starts designing the practice that produces them: the research protocols, the design system, the team structure, the handoff artefacts, the cross-team rituals. The output of the work is no longer a feature. It is a capacity the organisation uses to deliver many features. Four more talks in the archive address this:

• Laura Lorenzo (Intersection 19, Lisbon): Building Empathetic Workplaces.
  Lorenzo's talk is rare territory: workplace experience design, applied to the people inside the enterprise rather than outside it. UX designers often feel the tension between designing for external users and the internal experience of the colleagues they build with. Lorenzo names that tension explicitly and offers a practice for addressing both at once.
• Goh Hirose (Intersection 24, Rome): Digital Transformation in 2024 and why EDGY was key in accomplishing it.
  A transformation story told from inside BNP Paribas Cardif, where the experience work had to be reconciled with architecture, organisation, and multiple partner integrations. For UX designers working inside financial services or regulated industries, the talk is a practical answer to the question of what happens when UX methods meet enterprise complexity at scale.
• Maria Zenina & Mila Dymchenko (Intersection 24, Rome): Sustainable Enterprise Design.
  Sustainability is an emerging requirement UX designers are increasingly asked to design for, often without a clear practice for how. Zenina and Dymchenko address the question directly: how an enterprise designs for sustainability coherently, across products, operations, and customer-facing experiences. For UX designers being handed sustainability briefs, the talk offers a vocabulary for what is actually being asked.
• Nick Gall (Intersection 16, Copenhagen): Connecting EA, Business Architecture, and Design at IBM.
  Gall is an enterprise architect reaching across to design, which makes the talk the mirror image of what this article addresses. UX designers reading Gall will see what the architecture side of the seam looks like when someone from there is trying to meet them halfway. The talk is specific, practical, and told from inside IBM — a UX designer in any large enterprise will recognise the political geography.

The common thread across these four talks: the designer's practice, not the designer's output, becomes the unit of work at enterprise scale. That shift is rarely taught in UX education. It is widely experienced. And it has been the subject of serious, practitioner-led conversation at Intersection for years.

Your next step

The Intersection Conference is the twelfth-year-running venue where experience work meets adjacent disciplines (service design, enterprise architecture, organisation design, product, brand, and strategy) as peers rather than as handoff partners. The community is smaller than UX Collective or Nielsen Norman, and more technical than the mainstream UX circuit. That is part of the point. The conversation happens at a level of specificity that broader UX media rarely reach, because broader UX media doesn't treat the seam problem as a craft problem, and Intersection does.

Intersection 26 runs October 7–9, 2026, in Montréal. The theme is Beyond the Spark: Turning Ideas into Impactful Enterprises, which is directly the territory UX work evolves into when it outgrows the product or outgrows the designer. Whether you're designing products, journeys, or the practices behind them, you'll find people facing many of the same challenges from different perspectives.

Conference tickets are now available.

We look forward to welcoming you to Montréal!