This article is an invitation. It was written by a conference organiser to product practitioners who may not yet have heard of the conference. Its argument is that a 12-year conversation about enterprise-scale product work exists at the Intersection Conference, and that product managers, product designers, and service owners belong in it.

Product management has matured enormously over the last fifteen years. The craft has methods, certifications, a career ladder, and large professional communities, particularly in digital and software product, around Mind the Product, Product Hunt, Reforge, and Lenny's Newsletter, with parallel communities in industrial, pharmaceutical, automotive, and consumer product domains. Across all of these, most product people now work in enterprises with dozens or hundreds of products, where the roadmap they ship into is shaped by capabilities they do not own, organisational structures they did not design, and brand decisions made years before they joined.

The next layer of the problem — how individual products fit into the enterprise-scale system that produces them — has no corresponding community or body of case studies visible in mainstream product media. Product people hit this layer and usually reinvent the answer alone, company by company. The product strategy that a reorg invalidates. The feature that ships into a capability vacuum. The product roadmap disconnected from the operating model that determines what is actually buildable.

Where is serious, practitioner-led thinking happening about enterprise-scale product work, and what does it look like?

A twelve-year conversation on exactly this question has been happening at the Intersection Conference, just not where mainstream product media have been looking. The conference has hosted product managers, product designers, and service owners from Intuit, Facebook, the UK Government Digital Service, SAP, VMware, and others presenting work that addresses the layer above the product: how products cohere with the enterprise that creates them. The 12th edition, Intersection 26: Beyond the Spark, is in Montréal this October.

Three concerns that shape enterprise-scale product work show up across the Intersection archive, each one the focus of talks from product practitioners at the scale the reader will recognise:

• When products outgrow their teams: scaling without losing coherence
• When product strategy collides with enterprise reality
• When products serve people across channels, not a channel

When products outgrow their teams: scaling without losing coherence

Product people hit an invisible ceiling as their organisation grows. The methods that worked for one team of eight, one backlog, and one product fail silently when the company hits four teams, three products, and a leadership structure that keeps changing. Three talks from the Intersection archive address this directly.

• Oli Shaw (Intersection 16, Copenhagen): Service design at scale: Designing for impact.
  Shaw, working at Designit, argues that service design breaks when scaled naively. The small-team methods — one journey map, one service blueprint, one team to own them — do not survive contact with enterprise complexity. What survives is a different practice: service design as a capability that the enterprise develops, not as a deliverable that a team produces. Product practitioners will recognise the same pattern in their own work.
• Louise Downe (Intersection 16, Copenhagen): Redesigning Government for the 21st Century.
  Downe led the UK Government Digital Service during its formative years. GDS took a national-scale set of citizen services and redesigned them as coherent products, not as a portfolio of government forms. The talk is essential viewing for any product person working inside a large, slow-moving institution. The lessons transfer directly to legacy enterprises, regulated industries, and any organisation where product has to coexist with compliance.
• Katharina Weber (Intersection 18, Prague): The Design Leadership Framework.
  Weber's talk is about design as an organisational function, but the argument applies cleanly to product. As a design (or product) team grows from 5 people to 50 to 500, the leadership question changes shape. Weber maps the changes explicitly, from craft leadership to practice leadership to function leadership, and names what each transition requires. Product leaders will find their own growth stages in the same map.

The common claim across these three: scaling product work is not a bigger version of the work; it is a different kind of work. The Intersection Conference is where this kind of work has a consistent audience.

When product strategy collides with enterprise reality

Every product manager who has tried to ship an ambitious roadmap inside a large organisation knows the moment: the strategy was approved, the team was assembled, the launch date was circled. And then a quietly-surfaced architecture decision, or an unmentioned enterprise-wide policy, or a reorg three levels above, reshaped what was actually possible. Three more talks document this collision and what to do about it.

• Filip Hendrickx (Intersection 16, Copenhagen): Bridging EA and BA with lean startup and innovation techniques.
  Hendrickx's premise: enterprise architects and product people are trying to solve adjacent problems with non-overlapping vocabularies. His talk is the practical bridge: how to bring lean-startup and innovation methods into enterprise architecture conversations in a way that both audiences recognise. For product managers negotiating with architecture teams, this is a rare public treatment of how the two sides can actually meet.
• Remco Lenstra (Intersection 17, Barcelona): Nice landing, wrong airport: lessons learnt the hard way in co-creation.
  Possibly the single most honest strategy-execution post-mortem in the archive. Lenstra describes a co-creation process that was textbook-correct in every step and ended with the wrong outcome anyway. The talk names exactly why: the product work was well-executed; the enterprise context had shifted underneath it. Reading the post-mortem is cheaper than living through one.
• Sasha Aganova (Intersection 17, Barcelona): Innovation and Engagement with Business Architecture.
  Aganova, from Process Renewal Group, addresses the specific case of innovation initiatives running inside organisations with strong enterprise architecture practices. The common failure mode — innovation bypasses architecture, fails on handoff — is not inevitable. Aganova names the practices that let innovation and architecture cooperate rather than competing.

The common claim: enterprise reality is a design constraint for product work, not an inconvenience outside it. Product managers who treat enterprise architecture, business architecture, and operating models as someone else's concern are not neutral in the outcome. They are losing information that would have made the product better.

When products serve people across channels, not a channel

Mainstream product thinking assumes the product is software, the channel is digital, and the user is a consumer. Enterprise-scale product work rarely matches all three. Products serve people across call centres, retail stores, partner networks, regulated intermediaries, and long-cycle B2B processes. The product is part of an ecosystem the customer navigates whether the product team has designed for that ecosystem or not. Three talks take this seriously.

• Mike Atherton (Intersection 16, Copenhagen): Bridging Experience through Brand.
  Atherton's talk, given while he was at Facebook, argues that experience and brand are the same problem at enterprise scale. The product does not exist separately from the brand story the user has already built in their head, and the user's experience of the product is partly inherited from the enterprise's brand. Product managers who treat brand as marketing's concern ship products that feel incoherent with the enterprise that made them.
• Clemence Debaig (Intersection 17, Barcelona): Creating a hub of digital services to better serve the public.
  Debaig addresses a public-sector case where no single product serves the citizen; a constellation of services does. The talk is about designing the hub — the integration layer that makes individual services feel like one coherent offering. Product managers inside platform companies, multi-sided marketplaces, or enterprise SaaS suites will recognise the pattern.
• Jeremy Wilken (Intersection 19, Lisbon): Building a Design System that Works at VMware.
  Wilken describes the design system work at VMware. Not the system itself, but what made it work inside a large, technically complex, globally distributed enterprise. The talk is a practical answer to a question most product people ask at some point: how do you build a shared component system that actually gets used across dozens of product teams who did not ask for it?

The common claim: product design at enterprise scale is ecosystem design, not product design. The talks cited above are each specific, practical, and given by practitioners doing the work. They are also a tiny slice of what the archive contains.

Your next step

If you recognised your own work in any of the examples above, chances are you've already encountered challenges that extend far beyond product management alone.

Intersection 26 brings together product practitioners with enterprise architects, service designers, organisation designers, strategists, and many other disciplines working on the same enterprise challenges from different perspectives.

Join us October 7–9 in Montréal for three days of talks, workshops, and conversations exploring this year's theme: Beyond the Spark: Turning Ideas Into Impactful Enterprises, which is exactly the territory enterprise-scale product work lives in.

Early Bird tickets are now available, giving you full access to all three conference days at a discounted rate.

We would love to welcome you to the conversation!

Photo by Zoe Richardson on unsplash