Core Principle

Experience design has always been pervasive.

It has always existed anywhere people interact with an organization.

Long before someone opens an application or visits a website, an experience has already begun.

Marketing establishes expectations.

Sales establishes trust.

Operations determines delivery.

Policies determine consistency.

Leadership shapes culture.

Technology enables execution.

The interface is where those decisions become visible.

It has never been where the experience begins.

Artificial intelligence did not expand the scope of experience design.

It exposed the consequences of treating experience too narrowly.

Definition

Pervasive Experience Design is the practice of intentionally designing the complete system that creates an experience, not merely the interface through which the experience is expressed.

The Problem

Many organizations unintentionally organize design around interfaces.

As a result:

• Business strategy is disconnected from customer experience.
• Operational friction is accepted as someone else's problem.
• Design teams are brought into conversations too late.
• AI initiatives optimize tasks instead of transforming systems.
• Business leaders question the value of design because design has been limited to production.

The issue is not the discipline.

The issue is how the discipline has been defined.

Why It Matters

Organizations compete through experiences, not interfaces.

Customers evaluate the entire journey:

• The promise.
• The purchase.
• The onboarding.
• The support.
• The delivery.
• The outcome.

Every interaction contributes to the experience.

Organizations that understand this design better businesses, not just better products.

The Framework

Experience design should intentionally influence:

• Business strategy
• Value creation
• Marketing
• Sales
• Customer success
• Operations
• Service delivery
• Workflow design
• Decision architecture
• Governance
• Technology
• AI systems
• Organizational capability

These are not independent disciplines.

They are different perspectives on the same experience.

Business Implications

When experience design is treated as a pervasive capability, organizations make better decisions earlier, reduce organizational friction, improve AI adoption, and create stronger alignment between strategy and execution.

The business benefits because design is contributing where value is actually created.

Expected Outcomes

Organizations adopting this perspective can expect:

• Better alignment across business functions.
• Earlier involvement of design in strategic decisions.
• More effective AI implementation.
• Stronger customer experiences.
• Reduced operational friction.
• Greater return on design and technology investments.

Related

Principles

• The Experience Gap
• The Interface Is an Artifact
• Business Before Interface
• The Outcome Is the Measure

Capabilities

• Experience Strategy
• Business Thinking
• Organizational Design
• Decision Architecture
• AI Systems Thinking

Services

• Executive Advisory
• Experience Architecture
• Organizational Transformation
• Design Organization Transformation

Questions for Leaders

• Where does your organization believe customer experience begins?
• Which business functions currently shape the experience but operate independently?
• Is design influencing strategy or primarily producing deliverables?

Core Principle

The interface is an artifact.

It is the visible result of countless decisions made across an organization.

Business strategy.

Customer research.

Marketing.

Sales.

Operations.

Policies.

Workflow.

Governance.

Technology.

Data.

Artificial intelligence.

Leadership.

Every one of these influences the experience before an interface ever appears.

An interface can only express the quality of the system behind it.

It cannot compensate for a system that was never designed well.

Definition

An artifact is the observable output of a system.

Interfaces, dashboards, mobile applications, websites, conversational agents, emails, notifications, and generated user interfaces are all artifacts.

They communicate the decisions that have already been made.

They do not replace those decisions.

The Problem

Many organizations evaluate design almost exclusively through its artifacts.

Screens become the measure of progress.

Wireframes become the definition of design.

Prototypes become the evidence of value.

This creates a dangerous illusion.

Teams spend significant effort refining interfaces while the business processes, governance, decision-making, and operational systems that determine customer outcomes remain unchanged.

The artifact improves.

The experience does not.

Why It Matters

As AI becomes embedded throughout organizations, interfaces become increasingly dynamic.

Some interfaces will be generated in real time.

Some will disappear entirely.

Some experiences will happen through voice, automation, APIs, background agents, or workflows with no traditional interface at all.

If organizations define experience design by the interface, they will continually chase changing technology.

If they define experience by the system that creates it, their thinking remains durable regardless of how technology evolves.

The Framework

Design should intentionally shape:

• Business decisions
• Organizational capability
• Customer journeys
• Operational workflows
• Decision architecture
• Governance
• Information flow
• AI behavior
• Human collaboration

Interfaces express these systems.

They do not replace them.

Business Implications

Organizations that optimize artifacts without improving systems eventually reach diminishing returns.

Organizations that improve systems create better interfaces naturally because the interface reflects a healthier organization.

Design becomes a driver of business capability instead of a production function.

Expected Outcomes

Organizations adopting this principle can expect:

• Better alignment between business strategy and design.
• More resilient customer experiences.
• Reduced organizational friction.
• More effective AI integration.
• Greater return from design investments.
• Interfaces that reflect stronger underlying systems.

Related

Principles

• The Experience Gap
• Experience Design Has Always Been Pervasive
• The Outcome Is the Measure
• Design the System

Capabilities

• Experience Strategy
• Decision Architecture
• Workflow Design
• Organizational Design
• AI Systems Thinking

Services

• Experience Architecture
• AI Systems Architecture
• Executive Advisory
• Organizational Transformation

Questions for Leaders

• What organizational decisions are your interfaces expressing?
• If every interface disappeared tomorrow, would the underlying system still create a great experience?
• Are you investing more in artifacts than in the systems that produce them?

Core Principle

The interface is an artifact.

The outcome is the measure.

Organizations often celebrate what they can see: interfaces, prototypes, feature releases, dashboards, and presentations.

Those artifacts have value.

But they are not the ultimate measure of success.

The real measure is what changed because of them.

Did customers succeed?

Did employees make better decisions?

Did adoption improve?

Did operational friction decrease?

Did the business create more value?

Experience design exists to improve outcomes.

Artifacts are only one means of achieving them.

Definition

An outcome is a measurable change in business performance, customer experience, organizational capability, or operational effectiveness resulting from intentional design.

Artifacts communicate work.

Outcomes demonstrate value.

The Problem

Organizations frequently measure design activity instead of design impact.

Teams report:

• Screens delivered.
• Features shipped.
• Prototypes completed.
• Design systems expanded.

These metrics describe production.

They do not describe value.

When organizations mistake output for outcome, they optimize for activity instead of impact.

Why It Matters

As AI accelerates software development, organizations will be able to produce interfaces faster than ever.

Production becomes easier.

Differentiation does not.

Competitive advantage increasingly depends on improving decisions, workflows, governance, customer value, and organizational capability.

Those are outcomes.

Organizations that measure outcomes build stronger businesses than organizations that measure production.

The Framework

Experience design should intentionally improve:

• Customer outcomes
• Business outcomes
• Operational outcomes
• Decision quality
• Organizational capability
• Employee effectiveness
• AI effectiveness
• Long-term business value

Artifacts should always support these outcomes.

They should never become the objective themselves.

Business Implications

Organizations that evaluate design through outcomes make better investment decisions.

They align design with executive priorities.

They increase confidence in AI initiatives.

They demonstrate measurable return on investment.

Design becomes a strategic capability rather than a production function.

Expected Outcomes

Organizations adopting this principle can expect:

• Better executive alignment.
• Better investment decisions.
• Stronger customer outcomes.
• More effective AI adoption.
• Higher organizational performance.
• Clearer measurement of design value.

Related

Principles

• The Experience Gap
• Experience Design Has Always Been Pervasive
• The Interface Is an Artifact
• Business Before Interface

Capabilities

• Experience Strategy
• Business Thinking
• Decision Architecture
• Organizational Design
• Measurement and Governance

Services

• Executive Advisory
• Organizational Transformation
• Experience Architecture
• AI Strategy

Questions for Leaders

• How does your organization currently measure the value of design?
• Which metrics reflect production rather than outcomes?
• What business results should experience design be accountable for?

Core Principle

Business before interface.

Every interface exists to serve a business objective.

Whether the objective is growth, retention, operational efficiency, customer satisfaction, revenue, trust, or compliance, the interface is only one mechanism for achieving it.

Experience designers should understand the business before they attempt to improve the experience.

Without that understanding, design becomes decoration rather than strategy.

Definition

Business Before Interface means understanding why the organization exists, how it creates value, who it serves, how it competes, and what outcomes it is trying to achieve before making design decisions.

Design begins with purpose.

Interfaces communicate that purpose.

The Problem

Many design teams are introduced to projects after key business decisions have already been made.

They receive requirements instead of participating in defining them.

Research often starts with stakeholder debriefs instead of independent investigation into the business, market, competitors, operations, and constraints.

As a result, designers solve the problem they were handed instead of validating whether it is the right problem.

The interface improves.

The business opportunity may not.

Why It Matters

Organizations invest in design because they expect business value.

They expect:

• Better decisions.
• Better customer experiences.
• Higher adoption.
• Greater operational efficiency.
• Stronger competitive positioning.
• Measurable return on investment.

Those outcomes require business understanding, not interface expertise alone.

The Framework

Experience design should begin by understanding:

• The business model.
• Value creation.
• Customer needs and behaviors.
• Marketing and positioning.
• Sales and revenue generation.
• Operations and service delivery.
• Decision-making.
• Governance and risk.
• Technical capabilities and constraints.
• Success metrics.

Only then should the interface be designed.

Business Implications

Organizations that involve design earlier create stronger alignment between strategy and execution.

Design becomes a contributor to business decisions instead of a downstream production function.

The result is greater organizational impact and a clearer return on investment.

Expected Outcomes

Organizations adopting this principle can expect:

• Better strategic alignment.
• Better product decisions.
• Better customer outcomes.
• More effective collaboration across business functions.
• Higher confidence in AI and technology investments.
• Greater business value from design.

Related

Principles

• The Experience Gap
• Experience Design Has Always Been Pervasive
• The Interface Is an Artifact
• The Outcome Is the Measure

Capabilities

• Business Thinking
• Experience Strategy
• Customer Understanding
• Decision Architecture
• Organizational Design

Services

• Executive Advisory
• Experience Strategy
• Organizational Transformation
• Design Leadership Advisory

Questions for Leaders

• Does your design team understand how your business creates value?
• Are designers participating in business decisions or reacting to them?
• What would change if design were involved before requirements were written?

Core Principle

Organizations create experiences.

Customers do not experience departments.

They experience promises made by marketing.

Expectations established by sales.

Products delivered by engineering.

Services provided by operations.

Support delivered by customer success.

Policies defined by leadership.

Technology enables these interactions, but organizations orchestrate them.

Every decision contributes to the experience.

Every team influences the outcome.

Experience design exists to understand, align, and intentionally shape those interactions.

Definition

An organization is the system responsible for producing experiences.

Every function contributes to the customer's perception of value.

Experience is an organizational capability before it becomes an interface.

The Problem

Many organizations assign ownership of experience to a single team.

Design owns the interface.

Marketing owns awareness.

Sales owns acquisition.

Operations owns delivery.

Support owns customer issues.

Each team optimizes locally.

Few optimize the complete experience.

The result is fragmented ownership, inconsistent decisions, duplicated effort, and customer journeys that break at organizational handoffs.

Why It Matters

Artificial intelligence increases the speed at which organizations operate.

It does not eliminate organizational complexity.

If workflows, governance, decision-making, and accountability remain fragmented, AI simply scales those problems faster.

Organizations that intentionally align their people, processes, technology, and decisions create experiences that competitors struggle to replicate.

The Framework

Organizations create experiences through the interaction of:

• Leadership
• Business strategy
• Marketing
• Sales
• Product
• Design
• Engineering
• Operations
• Customer Success
• Governance
• Data
• Technology
• AI systems

Experience design provides the connective tissue between these functions.

Its responsibility is not to own every function.

Its responsibility is to understand how they work together.

Business Implications

Organizations that treat experience as a shared capability improve collaboration, reduce organizational friction, align investments with strategy, and increase the value created by technology.

Experience becomes an organizational advantage rather than the responsibility of a single department.

Expected Outcomes

Organizations adopting this principle can expect:

• Better cross-functional collaboration.
• Better organizational alignment.
• More consistent customer experiences.
• Faster decision-making.
• Improved AI readiness.
• Greater long-term business value.

Related

Principles

• The Experience Gap
• Experience Design Has Always Been Pervasive
• Business Before Interface
• The Outcome Is the Measure

Capabilities

• Organizational Design
• Experience Strategy
• Business Thinking
• Decision Architecture
• Governance

Services

• Executive Advisory
• Organizational Transformation
• Experience Architecture
• Design Organization Transformation

Questions for Leaders

• Who owns the customer experience in your organization?
• Where do organizational handoffs create friction?
• Are business functions optimizing independently or as one system?