D³ Is Not a Framework—It’s a Way to See Enterprise Systems
A systems perspective on how Design, Decision, and Direction shape enterprise experiences.

Beyond Frameworks: A New Way of Seeing Enterprise UX
Enterprise organizations do not have a shortage of frameworks.
There are frameworks for strategy, service design, UX, architecture, governance, transformation, product management, innovation, AI, and organizational change.
Most of them are useful.
The challenge is not that organizations lack ways to structure complexity. The deeper problem is what happens between those structures.
A business leader sees an objective. An architect sees dependencies. A product team sees capabilities. A UX team sees an experience. A data team sees information. A risk team sees exposure.
A user experiences the system as a whole.
Each perspective can be valid, and yet the overall experience can still fail.
This is where my thinking around D³—Design, Decision, and Direction—began to evolve. I moved beyond asking which framework to use and began asking a different question:
What are we failing to notice because we are looking at the system from only one perspective?
A Framework Tells You What to Look At
A framework is useful because it gives structure.
It helps a team understand the stages, dimensions, capabilities, and measures that matter.
However, a framework can also create boundaries. As teams begin working within those boundaries, the customer journey may become one team’s responsibility, the workflow another’s, and data or governance someone else’s domain.
The framework has helped organize the work.
But in organizing the work, the relationships between the boxes can begin to disappear.
That distinction matters.
The problem is not the boxes themselves. The problem is when we stop seeing what connects them—and how a decision in one part of the system affects another.
This is why I distinguish between a framework and a way of seeing.
A framework tells us what to look at. A way of seeing changes what we notice about the relationships between what we are looking at.
The Map Is Not the System
Enterprise teams are very good at mapping.
We create journey maps, service blueprints, process maps, ecosystem maps, architecture diagrams, and data flows.
These are valuable. They help make complexity visible and give teams a shared representation of the system.
But a map is still a representation.
Two people can look at the same map and see very different things.
An architect may see a dependency, while a business leader may identify a risk. From a product perspective, the same situation may represent an opportunity. Meanwhile, a UX designer may notice friction, and a data scientist may recognize a missing signal.
The map has not changed; the perspective has.
And that distinction matters because the ability to see the same system through multiple perspectives—and understand what changes when the perspective changes—is itself a strategic capability.
The question is no longer simply: What does the map show?
It becomes: What are we able to see from here—and what might we be missing?
The Same System Can Be Correct from Multiple Perspectives—and Still Fail
Imagine an enterprise platform.
The business team says: “It delivers the required capability.”
The technology team says: “The architecture is scalable.”
The data team says: “The information is available.”
The UX team says: “The interface is usable.”
The compliance team says: “The required controls are present.”
And the employee says: “This is still difficult to use.”
Who is wrong?
Possibly nobody.
Each team may be evaluating a different part of the system.
The failure occurs because the organization has not created a shared view of how those parts interact.
That is the kind of problem D³ is intended to make visible.
A System Is More Than Its Parts
A system is not simply:
Component A + Component B + Component C
It is the pattern of relationships between them.
When one part changes, the effects can spread across the system. For example, a change in the business objective can reshape a decision, which may alter the workflow and, in turn, influence the interface. Similarly, changes in the data can affect a recommendation, potentially changing how people respond.
This is why systems thinking is so important to enterprise UX.
But seeing relationships is only the beginning.
We also need to understand what kind of relationship we are looking at—and what role each perspective plays within it.
D³ Begins with Three Perspectives
This is the simplest expression of D³:

Design
How does the system become an experience?
What do people see, understand, navigate, and do?
Design is where the system becomes tangible to people. It shapes interaction, comprehension, workflow, and the conditions through which an experience unfolds.
Decision
How does the system shape what people know, interpret, judge, and decide?
What information matters?
What intelligence is provided?
Where does judgment happen?
What should the person decide, and what should the system decide or recommend?
Decision brings attention to something that traditional UX can sometimes leave implicit: the quality of the experience is also connected to the quality of the decisions the system enables.
Direction
What organizational intent is shaping the system?
What priorities, incentives, policies, constraints, and strategic choices are influencing what gets built?
Direction makes visible the organizational forces behind the experience.
These are not three sequential stages.
They are three perspectives on the same system.
Design Does Not Sit on Top of Decision
A common mental model is:
Strategy → Decision → Design
As if the organization makes the important decisions first and UX simply translates them into an interface.
Real systems are rarely that simple.
Design influences what people can see.
What people can see influences what they understand.
What they understand influences what they decide.
Those decisions produce outcomes.
Those outcomes influence organizational priorities.
Those priorities influence what gets designed next.
It is a loop.
That is why D³ is not intended to be read as:
Design → Decision → Direction
as a linear process.
The three perspectives continuously influence one another.
Direction Is Often the Invisible Part
Design is visible.
Decisions are often visible.
Direction is frequently hidden.
But direction shapes the system continuously.
Why was this workflow prioritized?
Why was this metric selected?
Why is this process automated?
Why does this team own this capability?
Why is this information unavailable?
Why is this risk considered acceptable?
Why is speed prioritized over flexibility?
These are not merely design decisions. They also reflect organizational direction.
Sometimes, a decision that shapes the user experience is made long before a designer opens Figma.
Several organizational forces can shape the experience. For example, a policy may constrain the workflow, while a business priority determines which KPI receives attention. An architectural decision may limit the available interactions; similarly, governance requirements can introduce friction, and organizational incentives can shape what the product optimizes for.
This is why enterprise UX leaders need to understand not only the experience itself, but also the organizational forces shaping it.
A Real Enterprise Example
Consider a multi-module ERP environment. The same platform can be experienced very differently depending on a person’s role and responsibilities.
An administrator may need operational visibility.
A finance user may prioritize control and accuracy.
A manager may focus on approvals and exception handling.
An employee may simply need to complete a task without unnecessary effort.
The technology platform is shared. The decisions, responsibilities, and contexts are not.
The design challenge is therefore not simply: “How do we make the ERP easier to use?”
It is: “How do we design a coherent experience that supports different roles, decisions, and contexts without creating unnecessary fragmentation?”
That is a more strategic UX question because it considers the relationships between the platform, its users, and the work they need to accomplish.
D³ Is Not Another Layer
This is where I want to be very clear.
D³ is not intended to become another governance layer.
It is not: “First use your UX framework. Then add D³.”
It is not another checklist.
It is not another project methodology.
It is a way of looking at the same system differently.
D³ can be applied while working across:
- service design,
- product design,
- enterprise architecture,
- design systems,
- AI strategy,
- governance,
- transformation.
The purpose is not to replace those practices.
It is to help reveal the relationships they may not be designed to see.
A Different Way to Look at a Dashboard
Consider a workforce dashboard.
A conventional design review might ask:
- Is the layout clear?
- Are the charts readable?
- Is the navigation intuitive?
- Are the KPIs visible?
Those questions matter. But they do not fully explain whether the dashboard supports the decisions people need to make.
A broader review would also ask:
- What decision is the dashboard intended to support?
- What does the user need to understand?
- Which signals should influence their attention?
- What context is necessary to interpret those signals?
- What action should follow?
That was the thinking behind my workforce intelligence work at Omnicom, where the focus moved beyond complex data presentation toward KPI hierarchy, decision-first dashboard architecture, role clarity, and operational action.
The screen did not become less important. The reason for the screen became clearer.
That is what a different way of seeing can reveal.
The Interface Is Only One Expression of the System
This is perhaps the biggest shift.
When we look only at the interface, we see:
buttons, fields, tables, cards, charts.
When we look at the system, we see:
intent → information → process → decision → action → outcome
The interface sits somewhere inside that chain.
It is important, but it is not the entire experience.
This is why an excellent interface can still sit inside an immature system.
And why a simple interface can sometimes support an extremely sophisticated experience.
Enterprise UX therefore cannot be reduced to interface quality alone. The experience emerges from the broader system that surrounds the interface.
Seeing the Same System Differently
Consider an AI-assisted enterprise workflow.
A business leader may see an opportunity to improve efficiency.
A technology leader may see an opportunity to automate a task.
A data scientist may see a prediction problem.
A risk leader may see a control problem.
A UX leader may see questions of trust, usability, and human agency.
A user may see a recommendation they must decide whether to trust.
None of these perspectives is necessarily wrong. Each highlights a different concern, and each can lead to a different design decision.
D³ encourages us to consider these perspectives together and examine how they influence one another.
That becomes increasingly important as enterprise systems become more intelligent.
Why This Matters More in Intelligent Systems
Rule-based software often behaves according to explicitly defined logic. AI-enabled systems can introduce probabilistic outputs, recommendations, and interpretations that require users to exercise judgment.
A system can now:
- infer,
- recommend,
- prioritize,
- summarize,
- predict,
- generate,
- adapt.
That means the system’s behavior increasingly influences the user’s judgment.
This is one reason the future of enterprise UX cannot be separated completely from decision design and human-AI collaboration.
When an intelligent system recommends something, the experience is no longer only about how the recommendation is presented.
It is also about:
- why the recommendation exists,
- what evidence supports it,
- how much context the user receives,
- where human judgment remains necessary,
- what happens when the user disagrees,
- and who ultimately owns the decision.
The interface is only one part of that relationship.
From Frameworks to a Practice of Seeing
A framework helps teams structure work. A lens helps them notice relationships that might otherwise remain invisible.
For example, a team might evaluate a system through users, processes, and technology. A broader perspective asks how those elements influence one another—and how a change in one affects the others.

Similarly, a usability review might assess efficiency and satisfaction. A systems perspective also asks whether the experience helps people make informed decisions and act with appropriate confidence.
In an AI-enabled workflow, the question is not only what the technology can do. It is what role the system should play in a decision, where human judgment remains necessary, and how responsibility is shared.
This is the distinction I want D³ to make visible. It does not ask teams to abandon established frameworks. It encourages them to look beyond individual components and examine the relationships shaping the overall experience.
The value of this perspective becomes clearer when it changes the questions teams ask.
Instead of asking:
- How do we improve this screen?
- Can AI automate this task?
- Who owns this product?
- Is the workflow efficient?
Ask:
- What system conditions are shaping this experience?
- What role should intelligence play in this decision?
- Who is accountable for the outcome across the journey?
- Does the system help people make appropriate decisions?
The shift is from examining individual parts in isolation to understanding how the system works as a whole.
The Shift Is Not from UX to D³
This is another point I want to make clearly.
I don’t see D³ as the next step after UX.
I see it as a way of expanding the field of view of UX.
UX remains essential.
Research remains essential.
Interaction design remains essential.
Design systems remain essential.
Service design remains essential.
Architecture remains essential.
Governance remains essential.
The question is how these practices connect.
D³ is not UX → D³. It is UX with a wider field of view.
The goal is not to move away from design.
It is to understand the system in which design operates.
What Changes When We See the System Relationally?
When teams begin to see the system relationally, several things change.
Problems become less local.
A broken screen may be traced to a process decision upstream.
Research becomes more systemic.
We study not only users, but also dependencies, organizational conditions, and the forces shaping the experience.
Design discussions become more strategic.
Teams ask what experience the organization is trying to create—not just what interface it needs.
Governance becomes part of experience.
Policies, controls, and compliance requirements are considered as design conditions rather than purely external constraints.
AI discussions become more human.
The question shifts from “What can AI do?” to “What role should AI play in this human decision?”
Measurement becomes broader.
Teams consider outcomes and decisions, not only interaction metrics.
This is why I see D³ as a way of seeing systems, rather than simply another framework to implement.
The Value of a Shared Perspective
One of the biggest benefits of a common lens is not that everyone starts thinking the same way.
It is that people can understand why they are seeing different things.
The architect does not have to stop being an architect.
The business leader does not have to become a designer.
The UX designer does not have to become an AI engineer.
The data scientist does not have to become a strategist.
Instead, the team gains a shared language for discussing the relationships between their perspectives.
That can be surprisingly powerful.
This shared language matters because many enterprise conflicts are not necessarily disagreements about the goal. Instead, teams may disagree about which part of the system should be optimized.
Once those perspectives become visible, the conversation can move from: “Who is right?”
to: “What are we each seeing, and how do those views affect the whole system?”
That is a much more productive starting point for enterprise decision-making.
A Way of Seeing Becomes Valuable When It Changes Decisions
This is the test I would apply to D³.
Does it help teams notice something they would otherwise miss?
Does it change the questions they ask?
Does it expose dependencies earlier?
Does it help connect experience with decisions?
Does it make organizational intent visible?
Does it improve the quality of conversations between design, business, technology, data, and governance?
If the answer is yes, then the lens is doing useful work.
It does not need to replace every existing methodology.
Its value is in helping people see what those methodologies may not reveal on their own.
The Next Question: Can We Design the Decision?
Once we begin looking at enterprise systems this way, another issue becomes apparent: design influences decisions, decisions influence outcomes, and organizational direction shapes both.
Design influences decisions.
Decisions influence outcomes.
Direction influences both.
But what happens when the decision itself becomes increasingly influenced by intelligent systems?
That is where a new design question emerges.
It is no longer simply: “How should the AI look?”
It becomes: “How should the decision be designed?”
That question sits at the intersection of UX, systems thinking, AI, human judgment, and organizational intent.
And it points to a discipline that is still emerging:
Decision Architecture.
If D³ gives us a way to see the relationships between Design, Decision, and Direction, Decision Architecture asks what happens when we make the decision itself a deliberate design object.
That is the next question.
Key Takeaways
- A framework organizes complexity; a broader perspective reveals relationships that structure alone can miss.
- Different functions can interpret the same system correctly while experiencing different problems.
- D³ connects Design, Decision, and Direction as interacting perspectives, not sequential stages.
- Enterprise UX depends on the relationships between interfaces, workflows, decisions, and organizational priorities.
- In AI-enabled systems, trust, human judgment, and decision ownership are part of the experience.
- D³ complements established UX disciplines by expanding the questions teams ask about the systems they create.
Final Thought
We often ask whether a system is well designed.
Perhaps the more useful question is: Well designed from whose perspective?
Business sees one set of priorities. Technology sees dependencies and constraints. Data reveals patterns. Risk focuses on exposure. UX examines how people interact with the system.
But the person using it experiences the consequences of all these decisions together.
That is why enterprise design requires us to look beyond individual components and understand the relationships shaping the whole.
D³—Design, Decision, and Direction—is my way of making those relationships more explicit.
It is not a replacement for established design practices. It is a way to broaden the questions we ask about the systems we create.
Because the decision itself is part of the experience.
And once we recognize that, the next question is not only how we design the experience around a decision, but how we design the decision itself.
📬 Subscribe to Design with Depth for future articles.
Continue Exploring D³
• What Is D³? — A New Way to Think About UX Maturity
• Before vs After: How D³ Changes UX Thinking
• D³ Maturity Gap: Where UX Becomes Strategic
• D³ Framework: A Maturity Model for AI-Driven UX
• Systems Thinking Isn’t New. Why Are Organizations Still Struggling with It?
Share Insight:

You must be logged in to post a comment.