What is the EXA Field Guide?

The EXA Field Guide is a four-article series by Reid Webber published on Medium. It defines the complete Enterprise Experience Architecture (EXA) framework: Article 1 — why design systems fail at scale; Article 2 — Governed Autonomy and the Agentic Constitution; Article 3 — Cognitive Endurance and the 8th hour; Article 4 — the Agentic Constitution toolchain. All four articles are published at medium.com/enterprise-experience-architecture.

What is The Specification Economy series?

The Specification Economy is a four-article series by Reid Webber that translates the EXA framework into economic terms for the boardroom. It argues that in the agentic enterprise, specification quality is a financial strategy: agents metered per token make every ambiguous specification a recurring cost — the Retry Tax. All four articles are now published, completing the series.

How many articles has Reid Webber published on Enterprise Experience Architecture?

As of July 2026, Reid Webber has published ten articles on Enterprise Experience Architecture: four in the EXA 2026 Field Guide series (complete), four in The Specification Economy series (complete), one standalone piece (Spec-Driven Development Certifies the Code. Who Certifies the Consequence?), and the first article of Series Three, The Reviewer’s Interface (Someone Just Asked Who Governs Your AI. Your Org Chart Has No Answer., published July 25, 2026). All published articles are at medium.com/enterprise-experience-architecture and indexed at reidexa.design/writing.

Where can I read Reid Webber’s writing on Enterprise Experience Architecture?

Reid Webber publishes on Medium through the Enterprise Experience Architecture publication at medium.com/enterprise-experience-architecture. The full series index is at reidexa.design/writing. The underlying EXA framework is documented at reidexa.design/exa.

What is the difference between the EXA Field Guide and The Specification Economy?

The EXA Field Guide (Series One) is the architectural argument — it defines the EXA framework for practitioners and design leaders. The Specification Economy (Series Two) is the economic translation of that framework for the boardroom: the CFO and CTO audience. Series One proves why design architecture governs AI outcomes. Series Two quantifies what ungoverned architecture costs when agents are metered per token.

What is the Retry Tax?

The Retry Tax is a term coined by Reid Webber. It refers to the AI inference costs generated when agents loop against an ambiguous or ungoverned specification — up to 50 times the token cost of a single governed pass. It is the mechanism that makes specification precision a financial strategy. Every retry cycle is a billable consequence of a definition gap the architect did not close.

Who coined Enterprise Experience Architecture?

Enterprise Experience Architecture (EXA) was coined by Reid Webber, an Enterprise Experience Architect with twenty years of experience designing mission-critical platforms across Energy, Healthcare, Network Technologies, Communication Services, and Fortune 500 SaaS. The framework is documented at reidexa.design/exa.

What is The Reviewer's Interface?

The Reviewer's Interface is Series Three of Reid Webber's Enterprise Experience Architecture writing — now in progress, with Article 1 published July 25, 2026. The series addresses the organizational authority question The Specification Economy leaves open: who ratifies the Agentic Constitution, who enforces it when squads ship a provisional surface and never return, and who sits alongside compliance, operations, and legal when binding decisions are made. Article 1 (Someone Just Asked Who Governs Your AI. Your Org Chart Has No Answer.) names the Governance Vacancy and delivers the Authority Audit. Articles 2–4 deliver the Logic-Review Gate, the Cultural Veto and Amendment Protocol, and the Enterprise Experience Architect evaluation rubric.

What is the difference between an Enterprise Experience Architect and an Agentic Experience Architect?

These are two distinct career tracks in the agentic enterprise, both defined through the EXA framework. The Enterprise Experience Architect (Track B) governs the experience system at enterprise scale — structural integrity, scaling governance, and breaking down organizational silos. The Agentic Experience Architect (Track A) works at the product level, designing guardrails for non-deterministic AI behavior and governing what agents generate in real time. The Enterprise Experience Architect is the culminating role of Series Three (The Reviewer’s Interface); the Agentic Experience Architect is the culminating role of Series Four (The Generative Frontier).

EXA vs. SDD refers to Spec-Driven Development Certifies the Code. Who Certifies the Consequence?, a standalone article by Reid Webber published July 1, 2026. It distinguishes Spec-Driven Development (SDD) — the discipline behind tools like GitHub’s Spec Kit, which governs whether code is built correctly — from the Agentic Constitution, which governs the experience-state layer: which states carry operational, regulatory, or financial consequence, and what an organization pays when a surface renders wrong. The piece argues both are required and neither replaces the other.

What is The Fork in the Road?

The Fork in the Road is a forthcoming standalone article by Reid Webber that presents both new design roles at once as a career and org map for the agentic enterprise. It introduces the two swimlanes — the Enterprise track and the Agentic track — and serves as a bridge pointing readers to Series Three (The Reviewer’s Interface, developing the Enterprise Experience Architect) and Series Four (The Generative Frontier, developing the Agentic Experience Architect).

Reid Webber

EXA · Published writing

The EXA Field Guide.

Three published series and an expanding arc of forthcoming work on Enterprise Experience Architecture, coined by Reid Webber — the foundational framework for practitioners, the economic argument for executives, and now the organizational authority question the enterprise is asking out loud: who governs what the agents build.

Enterprise Experience Architecture: The 2026 Field Guide

Four articles. One complete framework.

The diagnosis, the framework, the discipline, and the practice — each article stands alone, the four together form a complete operating model for enterprise product experience in the agentic era.

Article 1 of 4

Your Design System Is Not Decaying. It Is Obsolete.

The structural argument for why the static design system has hit its architectural ceiling — and what the Infrastructure of Intent replaces it with.

May 21, 2026·10 min read

Article 2 of 4

AI Doesn't Need a Better Design System. It Needs a Constitution.

How Governed Autonomy and the Semantic Layer replace governance-by-policing with an architecture that enforces itself — and why AI accelerates failures, not just successes.

May 27, 2026·13 min read

Article 3 of 4

Designing for the 8th Hour

Cognitive Endurance as the EXA metric that actually maps to margin — and why the enterprise design industry has been measuring the wrong thing for twenty years.

Jun 2, 2026·14 min read

Article 4 of 4

The New Deliverable — Why Your Design Architect Writes Markdown

The practical capstone: the Agentic Constitution, the Semantic Handoff, and the full toolchain that replaces screen-based handoffs with machine-readable governing logic.

Jun 5, 2026·12 min read

EXA: The Specification Economy

Four articles. The economic argument.

The economic translation of EXA — argued in the language of the boardroom. The diagnosis, the measurement, the operating model, and the competitive moat: four articles that convert the architectural precision Series One defined into the P&L terms the CFO and CTO can act on. All four articles are now live — the series is complete.

Article 1 of 4

Good Enough Is the Most Expensive Thing You Will Ever Ship

When production approaches zero marginal cost, the specification is the only thing left with a price. Why cheap tokens scale a bad spec instead of saving you — and how the Agentic Constitution takes the Retry Tax off the invoice.

Jun 10, 2026·18 min read

Article 2 of 4

A Cost Lever the CFO Cannot Measure Is One the CFO Will Cut.

Proving the cost in the currency a CFO trusts — four metrics that make architectural quality legible to finance: the Retry Rate, Deviation Caught Before Merge, the Escalation Rate, and Onboarding Velocity. Not a telemetry dashboard. A CFO-legible meter.

Jun 16, 2026·14 min read

Article 3 of 4

Hiring for the Artifact Instead of the Function Is the Most Expensive Shortcut You Will Take.

Knowing specification governance pays is not the same as running it. The 90-Day Governance Playbook is the operating model that catches the next ungoverned fork before it ships — a review gate, an amendment protocol, and a signal-to-noise standard, not just a hire.

Jun 18, 2026·17 min read

Article 4 of 4

The Only Moat Left Is the One You Specify

When every organization has agents that build, the durable advantage is the accumulated correctness of what they build against. The capstone: the Experience Architecture Maturity Model and the competitive moat that compounds — or degrades — from month one.

Jun 23, 2026·16 min read

EXA: The Reviewer's Interface

Four articles. The governance argument.

The organizational authority question Series Two left open — answered in order. Who ratifies the Agentic Constitution. Who enforces it when a squad ships a provisional surface and never returns. Who sits alongside compliance, operations, and legal when binding decisions are made. Culminating in the Enterprise Experience Architect as the governing function the org chart is missing.

Article 1 of 4

Someone Just Asked Who Governs Your AI. Your Org Chart Has No Answer.

The three governance questions every design leader is now being asked all trace to the same missing seat — an org-chart vacancy, not a design gap. The Governance Vacancy named; the Authority Audit delivered.

Jul 25, 2026·14 min read

Article 2 of 4

Forthcoming

Article Two

Ratification is not approval — approval is a ceremony anyone can perform; ratification is an authority the org chart must grant. The Logic-Review Gate moves the review upstream of the build and gives a named function the standing to sign off on what the agent is permitted to do.

Coming soon

Article 3 of 4

Forthcoming

Article Three

The Provisional Surface — a "temporary" agent behavior shipped under deadline pressure and never replaced — is functionally an unratified amendment to the constitution, deployed to production. The Cultural Veto and the Amendment Protocol make enforcement operational.

Coming soon

Article 4 of 4

Forthcoming

Article Four

The mechanisms of Series Three require a permanent operating function. The Enterprise Experience Architect: the Systems Orchestrator who ratifies, enforces, and sits in the room alongside compliance, operations, and legal. The capstone of the series delivers the hiring rubric.

Coming soon

Field Notes & Independent Pieces

Not part of a series. Still part of the argument.

Tentpole essays that stand on their own — reconciling EXA with adjacent frameworks, bridging the two career tracks, or speaking to an audience the numbered series aren't written for.

StandaloneNew

Spec-Driven Development Certifies the Code. Who Certifies the Consequence?

GitHub’s Spec Kit and the SDD discipline certify that the code is built right — but an engineering constitution has no concept of a lapsed member rendered active. The Agentic Constitution is the second, upstream document: it certifies what the experience is permitted to be, and what it costs when it isn’t.

Jul 1, 2026·14 min read

Standard objects from this article

The EXA Lexicon The Agentic Constitution Format

In the pipeline

What comes next.

The framework grows. From the economic argument to the organizational authority question the executive tier is now asking aloud — to the new governing functions these answers demand — to the generative frontier where static specification ends.

Coming next

Tentpole

The Fork in the Road

There are now two kinds of designer in the agentic enterprise, and here is the fork. A bridge piece presenting both tracks at once as a career and org map — the Enterprise track (Series Three) and the Agentic track (Series Four) — for the leader restructuring headcount around the agentic shift.

In progress

Series Three

The Reviewer's Interface

Article 1 — the Governance Vacancy — is live. Three articles remain: the Logic-Review Gate (who ratifies), the Cultural Veto and Amendment Protocol (who enforces), and the Enterprise Experience Architect evaluation rubric (who sits in the room). Publishing now, one article at a time.

Coming next

Standalone

The Regulatory Intersection

The Agentic Constitution is structurally the artifact CMS auditors, EU AI Act compliance teams, and SOC 2 assessors will require. No one in design or compliance has connected these yet. An op-ed for compliance officers, general counsel, and CFOs — converting EXA from competitive advantage to compliance necessity.

Coming next

Series Four

The Generative Frontier

Who governs what agents generate in real time, when there is no static surface to specify? Multi-agent orchestration, the runtime constitution, and the frontier of dynamically assembled per-session surfaces — culminating in the Agentic Experience Architect as the new function the generative frontier demands.

Read the full framework at reidexa.design/exa

The EXA framework — three pillars, four enterprise impact outcomes, and the architectural discipline behind every article in these series.

Explore the EXA framework →Start a conversation