Architect X · Experience Architecture
ARCHITECT X
Experience Architecture

We Design for Experience

Organizations are highly intentional about strategy, technology, operations, finance, governance, and infrastructure. They are rarely intentional about the experiences those systems produce.

Our disciplines Get in touch
EXPERIENCE
Organizational
Human
Digital
Intelligent
Decision
Physical
Spatial
Brand
Why the name

Architects exist far beyond buildings.

ENTERPRISE
SOFTWARE
URBAN
SPATIAL
X

Whether intentional or accidental, experiences are constantly being generated. Every product, service, technology, process, policy, environment, space, interaction and decision influences how people perceive, feel, think, connect, behave, and make meaning of their world.

The word architect is most often associated with buildings. Its meaning extends much further. Architects exist across enterprise, business, software, solution and data architecture, across urban planning, interior design, and the built environment. What unites them is not what they design, but how they think: understanding complexity, integrating diverse disciplines, and intentionally designing coherent systems that enable meaningful outcomes.

Architect X takes this broader philosophy as its foundation. Experiences cannot be designed directly, but the conditions that influence them can.

The X represents possibility. Every ecosystem, every discipline, every challenge, every opportunity. It also represents the intersections, where perspectives converge to produce what no single discipline could reach alone.

The distinction

We do not design experiences. We design the conditions from which experiences emerge.

Experiences emerge within people, through their interactions with systems, environments, services, technologies, spaces, cultures, brands, policies and relationships. No organization controls that emergence. What can be controlled is everything surrounding it.

Systems
Services
Spaces
Policies
EXPERIENCE
EMERGES
Cultures
Brands
Technologies
Environments
Instead of asking
What should we build?
Architect X begins with
What should people experience?
And then
What conditions, across every relevant discipline, must be intentionally designed to make that experience more likely?

Every engagement begins here. Not with requirements, not with technology, not with budget. From this answer, Architect X studies the ecosystem, uncovers its existing experiential patterns, and designs the conditions that make the intended experience more likely to emerge.

The eight disciplines

No single discipline can design an experience.

Experiences emerge through the interaction of many conditions at once. Architect X therefore integrates eight Experience Architecture disciplines into one enterprise. Each contributes a distinct body of knowledge while working toward one objective.

Together they produce an Experience Architecture: a coherent and intentional design of the organizational, human, digital, intelligent, decision, physical, spatial and brand conditions that influence how people perceive, feel, think, behave, connect and create meaning within an ecosystem.

01

Organizational Experience

Designing organizational strategy, governance, operating models, enterprise architecture, innovation, and business transformation.

02

Human Experience

Designing customer, employee, user and service experiences through psychology, behavioral design, user research, customer experience, and service design.

03

Digital Experience

Designing software, digital platforms, solution architecture, technical architecture, cloud infrastructure, DevOps, cybersecurity, and digital ecosystems.

04

Intelligent Experience

Designing artificial intelligence, machine learning, large language models, computer vision, natural language processing, and intelligent automation.

05

Decision Experience

Designing data engineering, analytics, business intelligence, data science, and decision-support capabilities that enable better organizational decisions.

06

Physical Experience

Designing robotics, IoT, automation, embedded systems, mechatronics, and interactions with the physical world.

07

Spatial Experience

Designing architecture, interior design, urban environments, smart buildings, landscapes, and the built environment.

08

Brand Experience

Designing brand strategy, identity, communication, marketing, media, and the way organizations are perceived and remembered.

How the disciplines are delivered

Disciplines describe what Architect X designs. Services describe how that design is built.

Three delivery services carry the majority of build work across the eight disciplines. They are never engaged as standalone offerings, because a system built without the conditions around it produces an unintended experience with great efficiency.

Service
Primary discipline
Supporting discipline
Software Development
Digital Experience
Human Experience
Hardware & Physical Technologies
Physical Experience
Spatial Experience
AI Solutions
Intelligent Experience
Decision Experience
Wrapping all three
Organizational Experience
Brand Experience

Organizational Experience and Brand Experience govern all three: the operating model that sustains what is built, and the perception that surrounds it.

Software Development

Architect X builds software as a condition, not as a deliverable.

The question is not whether a system meets its specification, but what it is like for the person required to use it on a Tuesday afternoon under pressure.

What we build. Enterprise platforms and internal systems. Public-facing digital services. Solution and technical architecture. Integration between systems that were never designed to cooperate. Cloud infrastructure and DevOps. Cybersecurity. Modernization of systems that work but are no longer usable.

What this changes. Requirements defects are found in a document review rather than in a sprint retrospective. Senior stakeholders approve something they have seen and operated, not something they have read a description of.

Hardware & Physical Technologies

Digital systems end at the screen. Experience does not.

A queue, a door, a sensor, a vehicle, a temperature, a wait: these shape how people feel about an institution long before any software is opened.

What we build. Robotics and automation. IoT networks and sensing. Embedded systems and mechatronics. Device and product engineering. Instrumentation of physical environments. Integration between physical systems and the digital and intelligent layers above them.

What this changes. Organizations stop treating the physical and digital as separate programmes with separate owners, and stop producing the seam that people experience as institutional incoherence.

AI Solutions

Intelligence changes what a system can do.

It also changes what people are willing to trust it with. Both are design problems, and only one of them is technical.

What we build. Large language model systems and applied AI. Machine learning and predictive models. Computer vision and natural language processing. Intelligent automation. Data engineering, analytics, business intelligence, and decision-support systems.

What this changes. Intelligence arrives attached to a decision and a person who owns it, rather than as a dashboard that impresses in a demonstration and is ignored within a quarter.

Hardware & Physical · Layers
Intelligent layer
Digital layer
Physical and spatial layer
One programme, one owner, across all three layers.
AI Solutions · Overlap
Intelligent
Experience
Decision
Experience
Intelligent Experience designs what the system can reason about. Decision Experience designs what a person does with the result. The work sits in the overlap.
Software build sequence
1
Experience Vision gate
Intended experience defined per audience
2
Solution architecture
Every requirement names its outcome
3
Clickable prototype
Every screen, every state, including empty
4
Code
Committed only after the above
Ecosystems

We are architects of ecosystems.

Architect X works across the ecosystems of human life. Every ecosystem generates experiences continuously. The work is to make them intentional.

Government
Finance
Health
Education
Housing
Food
Transportation
Energy
Talent
Entertainment
Retail
Industry
How we work

Seven steps, in a loop.

Every engagement follows a structured method that moves an organization from understanding its ecosystem to continuously improving the experiences it creates. Step 7 feeds step 1: experience is never static.

STEP 7
FEEDS STEP 1
1
Ecosystem Discovery
2
Experience Diagnosis
3
Experience Strategy
4
Experience Architecture
5
Experience Transformation
6
Experience Governance
7
Experience Intelligence
  1. 01
    Ecosystem DiscoveryUnderstanding the ecosystem before proposing anything. Its people, relationships, culture, environments, technologies, operations, governance, constraints, aspirations and existing dynamics.
  2. 02
    Experience DiagnosisEvery ecosystem is already generating experiences. Identifying the existing patterns, where they create value, and where they produce friction, confusion, disengagement or missed opportunity.
  3. 03
    Experience StrategyDefining the intended experiential outcomes and the strategic direction required to reach them, aligning organizational objectives, stakeholder expectations and ecosystem realities around a shared experience vision.
  4. 04
    Experience ArchitectureDesigning the organizational, human, digital, intelligent, decision, physical, spatial and brand conditions that make the intended experiences more likely to emerge.
  5. 05
    Experience TransformationTranslating the architecture into action through coordinated implementation across the relevant disciplines: embedding capabilities, aligning stakeholders, enabling sustainable change.
  6. 06
    Experience GovernanceEstablishing the governance models, roles, decision frameworks, standards and performance mechanisms that keep experiences intentional and measurable over time.
  7. 07
    Experience IntelligenceContinuously measuring, observing and learning from the ecosystem, so the Experience Architecture evolves as people's needs, behaviors, technologies and environments change.
Standards, not claims

Most firms describe their rigor. Architect X publishes it.

Three internal standards govern what leaves the firm. Each is versioned, each is enforced by automated checks, and each fails a deliverable that does not meet it.

The Solution Architecture Standard

TOGAF 10-aligned, twelve fixed sections, every heading tagged to its ADM phase. The first technical section cannot be drafted until the Experience Vision gate is passed. Every requirement names the experiential outcome it serves.

The Experience Prototype Standard

WCAG 2.2 AA validated before a screen is built. Every metric on every screen declares who acts on it and what they do; a metric that cannot is a build error, not a review comment. Every declared screen state is built, including the empty one.

The Business Document Standard

The upstream brief, written before research and before any solution. It excludes technical detail and schedules by rule, and defines the project in one sentence that survives being quoted alone in an email.

A quality score is calculated on every deliverable as the average of its two weakest dimensions, never the mean.
A document is as good as its weakest gate, and averaging hides precisely the failure the score exists to catch.
Dimension A
86
Dimension B
62
Dimension C
91
Dimension D
58
Dimension E
79
Five dimensions, illustrative. The two weakest set the score.Score 60
Values

Six values, each with a working definition.

Humanity

We begin with people. Behind every product, service, technology, policy and process are individuals living through experiences.

Curiosity

We seek understanding before action. We question assumptions and learn from people, ecosystems and emerging knowledge.

Creativity

Meaningful innovation begins with imagination. Creativity connects ideas across disciplines and challenges conventional thinking.

Courage

We embrace uncertainty and pursue better solutions even when they require difficult conversations or unconventional approaches.

Simplicity

Complexity should be understood, not transferred. Our responsibility is to turn complexity into clarity.

Beauty

Beauty is not decoration. It is a fundamental quality of exceptional experiences, and it creates emotional connection, trust and memory.

Our aspiration

Architect X aspires to become the global reference for Designing for Experience.

We envision a future in which organizations move beyond designing products, services, technologies, spaces and infrastructure, toward intentionally designing the conditions that shape how people experience them.

By integrating diverse disciplines into a unified Experience Architecture practice, Architect X seeks to change how organizations think, innovate, build and lead across every ecosystem.

Because people do not ultimately live through products, services, technologies or buildings. They live through experiences. And every experience matters.

Our mission

To architect the conditions that enable experiences across the ecosystems of human life.