Summary
As designers we want to reach people’s experiences, make their lives better, and ultimately contribute to a better condition of humanity and our planet. But something is getting in our way. Instead of delivering breakthrough experiences we are relegated to feeding bits into downstream implementation and operations. The enterprises we work for make us chase arbitrary, short sighted goals, and chase after the next release. Meanwhile, the key business decisions that determine the outcomes of our efforts have already been made. 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."
Dig deeper—ask the Rosenbot:
















More Videos

"Flat Carol was a nearly life-size cardboard cutout of Carol."
Randolph Duke IIWar Stories LIVE! Randy Duke II
March 30, 2020

"Taking time to intentionally create a career strategy helps avoid reactive decisions based on fear."
Corey Nelson Amy SanteeLayoffs
November 15, 2022

"You shouldn’t send another survey unless you’ve implemented changes and allowed time for behavior to adapt."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022

"We observed a safety risk on a construction site and that helped open a door to honest stories that people wouldn’t have shared otherwise."
Amy BucherHarnessing behavioral science to uncover deeper truths
March 12, 2025

"Friction isn’t just annoying; it’s a force that reshapes behavior and can slow or stop user flow."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025

"Leading change is like shopping—take time to find the right store before you buy."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024

"Equity is equal outcomes, not just equal access to a bicycle everyone can’t necessarily ride."
Jennifer StricklandAdopting a "Design By" Method
December 9, 2021

"Design Ops might not just support design anymore—our work is requested by non-designers and solving broader business problems."
Rachel Posman John CalhounA Closer Look at Team Ops and Product Ops (Two Sides of the DesignOps Coin)
November 19, 2020

"Service designers connect the dots, which represent elements, teams, processes, policies, and customer needs that all must align."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024