Innovation begins with a spark. An insight, a lingering annoyance, a new technology, a bold question. Intersection 26, the 12th global conference, running October 7–9 in Montréal, names this directly in its theme: Beyond the Spark: Turning ideas into impactful enterprises.

Most initiatives, however, do not survive scaling. The challenge is no longer generating ideas but designing the systems that let those ideas endure, grow, and deliver real-world impact. And the skills required to design for durability — not just creativity — live scattered across disciplines. Architecture, organisation design, strategy, product, brand. Most practitioners work inside one of these and reinvent the rest case by case.

What do enterprises that actually scale impact do differently, and how does a practitioner learn to see and design for those patterns?

Eleven years of Intersection Conference talks identify a recognisable pattern in enterprises that survive their own success. They are designed around durable Capabilities, coherent Organisations, and a Purpose that outlasts the founder's energy. These are not separate disciplines. They are three sides of the same enterprise. And they are what the EDGY 23 Language Foundations course teaches as a single language. The skills live together because the enterprise is one thing.

Three observations support this conclusion:

1. Durability lives in Capabilities, not features;
2. Coherence lives in Organisation, not org charts; and
3. Survival lives in Purpose, not marketing.

1. Durability lives in Capabilities, not features

Enterprises that scale impact invest in Capabilities. A feature ships, a capability endures. It outlasts the product, the reorg, and the person who championed it. Four talks from the Intersection archive make this distinction concrete:

• Scott Ambler (Intersection 25, Brussels): Fix the F*cking Data.
  Ambler argues that organisations treat data remediation as a project when it is, in fact, a permanent Capability. A project ends. Data drift does not. An enterprise that survives scaling builds the Capability to curate data continuously, not a backlog of one-time cleanups.
• Rijk van Vulpen (Intersection 16, Copenhagen): Transformation of an airline operations model at Transavia.
  An operating-model rebuild, shown not as a reorganisation but as the re-architecting of core operational Capabilities. Transavia's new operations model did not add features; it established Capabilities that could absorb future change.
• Patrick Hoverstadt (Intersection 16, Copenhagen): Designing self-organising enterprises and viable systems.
  Hoverstadt draws directly on the Viable System Model. An enterprise is viable when its Capabilities include the Capability to adapt. Without that second-order Capability, the first-order ones atrophy as the environment shifts around them.
• Oliver Cronk (Intersection 23, Vienna): Architecture for sustainability.
  Cronk argues that sustainability targets cannot be met through product-level features alone. They require Capabilities embedded at the architecture level — measurement, choice, and governance — that persist across the enterprise's product portfolio.

A common thread runs through these four talks: the speakers distinguish what the enterprise does today from what the enterprise is capable of doing, and they design for the latter. This is the skill Week 3 of the EDGY 23 course teaches: capability mapping, applied to operations and execution.

2. Coherence lives in Organisation, not org charts

Enterprises that scale impact are not those with the tidiest org chart. They are those whose organisational structure, culture, and operating rhythms cohere — where the way people work together expresses the strategy rather than contradicting it. Four more talks name this distinction precisely.

• Robert Briese (Intersection 18, Prague): Scaling Agility by Descaling Organizational Complexity.
  Briese inverts the usual scaling logic. Most enterprises try to scale agility by adding frameworks. Briese argues the opposite: scale agility by removing organisational complexity. The Organisation is the strategy, and when it is too complex to act, no framework recovers the coherence.
• Klaus Leopold (Intersection 24, Rome): FLIGHT LEVELS: Connect your Organization to Enable Enterprise Flow.
  Leopold's model distinguishes three levels of organisational coordination — strategy, coordination, operations — and argues that enterprises fail to deliver not because any single level is wrong, but because the three levels are disconnected. Coherence across levels is the product; any single level, in isolation, is not.
• Anne Landréat (Intersection 22, Stockholm): Scaling the power of togetherness: teams that team-up.
  Landréat examines what happens when teams that were designed to operate independently need to collaborate at enterprise scale. The answer is not "add a coordination layer." It is to redesign the Organisation so that collaboration is a structural property, not an after-the-fact overhead.
• Simone Cicero (Intersection 24, Rome): A Common Language for the Platform Organization.
  Cicero addresses the specific case of platform companies, where the organisational question is how to govern a platform without centralising it. The coherence shows up in the shared language of the Organisation, not in the reporting lines.

All four talks treat Organisation as a designed dimension of the enterprise, not as HR's administrative layer. This is the Identity-Architecture intersection in EDGY terms, and it is what Week 2 of the course teaches: Organisation, leadership, and culture as objects of deliberate design.

3. Survival lives in Purpose, not marketing

Enterprises that outlast their founders, their funding rounds, and their market cycles share one structural property: a Purpose clear enough that decisions can be made against it when the founder is not in the room. Five talks locate this clearly.

• Daniel Gona (Intersection 24, Rome): StratEDGY — activating the Zurich University of the Arts living strategy.
  A university is a long-lived enterprise by design. Gona shows how ZHdK used EDGY to make its Purpose operational — not as a mission statement in a PDF, but as a living strategy the faculty and staff could use to align decisions across decades.
• Jill Chang (Intersection 22, Stockholm): Connecting the value chain by having a clear purpose.
  Chang argues that value-chain coordination across suppliers, partners, and distribution is not a contracts problem but a Purpose problem. When partners share a Purpose, coordination reduces to conversation. When they do not, it requires legal infrastructure.
• Alexander Derno & Dennis Middeke (Intersection 17, Barcelona): Enterprise Design at Deutsche Telekom.
  One of the larger case studies in the archive. Telekom used Enterprise Design to align a multinational telecommunications business around a coherent Identity — the work that makes "digital transformation" survive its own leadership changes.
• Mark Adams & Anne Landréat (Intersection 15, Berlin): Culture Change by Design (Toyota EU).
  Toyota is the textbook example of an enterprise whose Purpose is older than most of its current employees. Adams and Landréat describe how culture change at Toyota EU was treated as a Purpose-led Identity design problem, not as a communications campaign.
• Aga Szóstek (Intersection 20, Virtual): The Umami Strategy.
  Szóstek's argument is that the strategies that endure are those with umami — a distinctive, hard-to-copy sense of purpose that differentiates the enterprise from its nearest rivals. Without it, marketing fills the gap, badly.

Across these five talks, Purpose is a structural dimension of the enterprise (the Identity facet in EDGY terms) and it is what Week 1 of the course introduces. Not because Purpose comes first in time, but because the language for discussing Purpose comes first in the learning path.

Why these three dimensions belong in one course

The pattern across the archive is not that enterprises scale on Capabilities, or on Organisation, or on Purpose. It is that enterprises that scale impact do all three. Capabilities without coherent Organisation become silos. Organisation without Purpose becomes bureaucracy. Purpose without Capabilities becomes rhetoric.

This is why the EDGY 23 Language Foundations course teaches the three together as a single language, not as three separate disciplines. Practitioners come to the course from one home base (architecture, service design, strategy, product, organisation design, brand) and leave with the language to see and design across all three facets of the enterprise at once.

Two course facts matter for any practitioner considering the investment:

The course is taught by experienced practitioners, not theorists. The instructors apply EDGY in the field; the course draws on real challenges, not only case studies. Three of the speakers cited in this article (Anne Landréat, Dennis Middeke, and Oliver Cronk) are active in the Intersection Group ecosystem as authors, coaches, or contributors. The language the course teaches is the language being developed in these talks.

The course is cohort-based and collaborative. Practitioners work with peers from adjacent disciplines. This is not incidental: Enterprise Design is itself a cross-disciplinary practice, and the course structure mirrors that practice. Learning alone would defeat the point.

Your next step

Intersection Group offers different entry points into the EDGY learning journey:

The EDGY 23 Language Foundations course is our flagship. A four-week remote cohort, leading to Certified EDGY Practitioner (Level 1). It is where practitioners learn the full EDGY language as a coherent whole.

The Getting Started with Enterprise Design workshop and the Enterprise Scan seminar are shorter entry points into EDGY. They help cross-disciplinary teams that need a shared language before a new initiative.

If you are ready to go deeper now, the upcoming Capability Modelling course is currently our most focused entry point into applied EDGY practice. Join us for the September cohort.

To stay informed about upcoming cohorts, new learning formats, and future EDGY training opportunities, join our newsletter!

Photo by Artem Shuba on unsplash