A Shared Language for Co-Creating Ambitious Endeavours
Summary
Enterprises are made of individuals forming great teams, applying a diverse set of skills, knowledge and experiences to ambitious projects. In order to bring this enormous potential to fruition, we need one thing: a shared understanding, appreciating each other’s viewpoints and backgrounds, tracing and translating decisions for greater impact on the whole.
Milan will introduce you to EDGY – a language designed to achieve just that, relying on your core skills as experience designers and information architects: understanding enterprises as systems embedded in a wider ecosystem and navigating their multifaceted nature. You’ll take away an approach for co-creating their future working with elements, dynamics and dependencies, and radically increase your impact on the outcomes they produce for people.
Key Insights
-
•
Poor enterprise design often causes frustrating user experiences that UX design alone cannot fix, as operational and systemic issues lie outside the UX scope.
-
•
Stafford Beer's principle that the purpose of a system is what it actually does helps measure enterprises by their real outcomes, not just stated intentions.
-
•
Edgy provides a shared language across disciplines to align enterprise purpose (identity), operational architecture, and user experience as inseparable views.
-
•
Tasks reflect what users want accomplished and are central to connecting experience design with enterprise capabilities and products.
-
•
Enterprise awkwardness manifests in disengaged employees, operational failures, and negative customer experiences, largely due to poor systemic design.
-
•
Designing better enterprises requires creating conditions for collaboration and coherence across organizational silos rather than blaming individual roles or departments.
-
•
Using a Rosetta Stone approach, Edgy translates the same enterprise concept into languages used by designers, strategists, and architects to foster shared understanding.
-
•
The framework anchors complex enterprise elements into simple base types—people, outcomes, activities, and objects—to make modeling accessible.
-
•
Early adopters have adapted Edgy into innovative mixed models combining journeys, maps, and system views, confirming the power of a shared language for enterprise design.
-
•
UX designers can begin applying Edgy with familiar tools like journey mapping and service blueprints, then iteratively seek expert feedback to refine enterprise-wide models.
Notable Quotes
"The purpose of a system is what it does—so you can measure an enterprise by its outcomes, not just by its slogans or strategy documents."
"Blaming the system for failures is like blaming the garden for not growing—the system is made by the people within it."
"Whenever you make a process model or service blueprint, make a wrong model first, then let the experts correct it to build shared understanding."
"Edgy is like a Rosetta Stone for enterprises, expressing the same thing in languages designers, strategists, and architects use."
"Experience is one of three inseparable facets of an enterprise: identity (purpose), architecture (operations), and experience (value to people)."
"Enterprises are basically people pursuing outcomes, doing activities, and using objects—this simple theory underpins the language of Edgy."
"The problem with the bike rental app wasn’t UX design; it was the enterprise’s inability to distribute bikes to meet user demand."
"When enterprises are awkward, employees disengage, operations break down, and the customer experience suffers."
"Shared language lets different roles venture out of their comfort zones and collaborate on changing the enterprise system."
"Designing better enterprises means creating conditions for all parts to work together coherently, like gardening rather than blaming individual plants."
Or choose a question:
More Videos
"Employees are now suing employers for inaccessible tools, with million-dollar verdicts even in conservative courts."
Sheri Byrne-HaberThe Importance of Accessible Design Systems
January 8, 2024
"I got a no. The message I was hearing was, scale the best you can with what you have and make it work."
Abbey Smalley Sylas SouzaScaling UX Past the Size of Your Team
January 8, 2024
"The point is not the product or output of note-taking, but to think more effectively — creating a mental place for your thinking."
Jorge ArangoExploding the Notebook: How to Unlock the Power of Linked Notes (2nd of 3 seminars)
April 19, 2024
"Using language that’s already common within the company helps principles feel natural and easy to adopt."
Sarah WilliamsA Framework for CX Transformation
June 11, 2021
"People who are struggling are constantly battling an unstable financial situation, which comes with a high cognitive and emotional energy cost."
Yasmine KhanChecking Bias and Listening to Financially Vulnerable Americans
March 30, 2020
"Where are our blind spots that cause us to forget or ignore important parts of our journey?"
Dave MaloufTheme 3: Introduction and Provocation
January 8, 2024
"For OKRs to work, incentives have to focus on learning, customer centricity, and evidence-based decision making, not just delivery."
Jeff GothelfWho does what by how much?
November 20, 2025
"The key to combating survey fatigue is short surveys triggered at the right context, making respondents feel listened to and valued."
Aleksandra Korczynska Caroline Jarrett Justyna ParmeeSurvey Tools
March 12, 2026
"When you put in that effort, you’re going to get the advocacy not only from your team but within the organization."
Frank DuranPartnership Playbook: Lessons Learned in Effective Partnership
January 8, 2024
