The EXA Field Guide.
Two 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 an incoming sequence on the organizational authority question the enterprise is now asking out loud.
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.
Loading articles from Medium
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. Article one is live; the rest publish across the series.
Loading articles from Medium
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.
The Specification Economy
The economic translation of EXA. Cost, P&L, the Retry Tax, AI inference costs — what happens to the balance sheet when the architecture is wrong and AI is building against it. Publishing now, one article at a time.
EXA vs. SDD
A frame-capture defense, not a terminology dispute. Spec-driven development's maturation is making experience specification feel already solved at the engineering layer — rendering the experience layer invisible by implication. This piece clears that ground before Series Three builds on it.
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.
The Reviewer's Interface
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? The organizational authority question Series Two leaves open — culminating in the Enterprise Experience Architect as a permanent governing function.
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.
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.