The Experience Architect Career Ladder

View raw

{
  "title": "The Experience Architect Career Ladder",
  "slug": "career-ladder",
  "objectNumber": 7,
  "version": "1.0",
  "status": "published",
  "source": "Series Three · Article 4 (capstone)",
  "sourceArticleUrl": "https://medium.com/enterprise-experience-architecture/you-can-describe-the-job-you-cannot-name-it-74d88bd07aae",
  "summary": "A four-tier career ladder for the Enterprise Experience Architect function — Designer, Architect, Principal, Chief — leveled on specification authority and blast radius rather than tenure. Includes the banding guidance for compensating each tier against the engineering ladder rather than the design ladder, and the structural reporting-line requirement that holds at every tier: a ratifier cannot report solely into the function whose delivery pressure the ratification exists to check.",
  "lastUpdated": "2026-08-16",
  "changelog": [
    {
      "date": "2026-08-16",
      "version": "1.0",
      "note": "Enterprise Experience Architect tier's description gained one added sentence — this tier's standing commitment to scheduling and commissioning Cognitive Endurance re-evaluation, reciprocal to a matching addition on /exa/clarity (the Human Clarity pillar page) the same session. Also added: a real link from this tier's card back to /exa/clarity (CareerLadder.astro, tier-gated, not a schema change — `description` is a plain-text field and can't render markup, so the reciprocal link needed a small addition to the render component itself). Additive only — the tier's existing description, `blastRadius`, and every other tier are unchanged; no version bump, matching this repo's established precedent for content additions to a published object (e.g. the Lexicon's own source-field and workedExample fixes)."
    },
    {
      "date": "2026-08-14",
      "version": "1.0",
      "note": "Published. Content (the four tiers, banding guidance, and reporting-line requirement) was already verified against the live article; this session's own editorial framing — summary and tagline — was surfaced verbatim and explicitly approved by the author before this flip. Status/version flip only, matching Object 6's own two-stage process; no content or framing changes in this entry. This closes Release 5 (v1.4) — both objects it required, the EEA Rubric and the Career Ladder, are now published."
    },
    {
      "date": "2026-08-14",
      "version": "0.1",
      "note": "Initial authoring, staged as draft per the Project Brief's standing recommendation. Content pulled verbatim from Series Three, Article 4's own \"The Ladder\" section, not the Content Strawman's Section 3 table — the Strawman's table was checked directly against the published article and found to carry a stale fifth tier (a separate \"Leadership / Director-VP\" row) that did not survive to publication; the article folds that mention into the Principal tier's own paragraph instead. Built to the article's real four-tier structure — see this file's header comment for the full finding. Not yet published: pending author review of this object's own editorial framing, matching Object 6's own draft-then-publish process."
    }
  ],
  "type": "reference",
  "tagline": "Not tenure. Not screens shipped. Four tiers of specification authority and blast radius.",
  "careerLadder": {
    "tiers": [
      {
        "title": "Enterprise Experience Designer",
        "blastRadius": "One surface",
        "description": "Authors constraints for a single surface or feature. Their work passes through the Logic-Review Gate; they propose amendments, they do not ratify them. This is where specification authority gets learned, on a surface small enough that being wrong is recoverable."
      },
      {
        "title": "Enterprise Experience Architect",
        "blastRadius": "Every surface in that product line",
        "description": "Authors the constitution for a product or domain. Runs the gate for the domain, approves amendments inside it, and holds the veto over deployments within its scope. This is the first tier where the org chart confers standing rather than influence, and it is the tier the energy company in the cold open needed and had no vocabulary to ask for. Its standing commitments include scheduling and commissioning Cognitive Endurance re-evaluation — a calendar-driven track, not a triggered one, since judgment degrading under sustained load produces no telemetry signal for anything else in this framework to catch."
      },
      {
        "title": "Principal Enterprise Experience Architect",
        "blastRadius": "Cross-domain",
        "description": "Sets constitutional patterns across multiple domains. Defines how gates operate rather than operating one, arbitrates when two domains ratify conflicting constraints against the same state, and owns the shared constraint library the domains inherit from. Larger organizations frequently carry a Director or VP of Experience Architecture alongside or above this tier, owning the operating model, the funding, and the staffing of the gates themselves."
      },
      {
        "title": "Chief Experience Architect",
        "blastRadius": "Enterprise-wide",
        "description": "Owns the discipline for the enterprise and answers for it at the executive table. Accountable to the CTO, CPO, and CFO for whether the specification layer is governed at all — and the peer counterpart to the Chief AI Officer three-quarters of large organizations already carry, and to the head of AI governance Forrester expects most of the largest US companies to appoint this year. Note that this tier sits above both practitioner tracks, not only this one, which is why the title drops the qualifier that distinguishes them and keeps the one that distinguishes the discipline."
      }
    ],
    "bandingGuidance": "Band those tiers against the engineering ladder, not the design one. An Architect belongs alongside a Staff or Principal Engineer; a Principal alongside a Principal or Distinguished Engineer; a Chief alongside a VP or SVP of Engineering. The logic is leverage, not prestige: one architect's ratified constraint set governs every squad executing against it, which is the leverage shape a Staff Engineer's technical decisions carry and not the leverage shape of a design lead reviewing individual screens. Band it against the design ladder and you underpay the role relative to what it actually moves, which attracts candidates who cannot exercise the authority once they hold it. The band is not a courtesy. It is the first signal a strong candidate reads about whether the seat is real.",
    "reportingLineRequirement": "One structural requirement holds at every tier of this ladder, and it is not optional: the ratifier cannot report solely into the function whose delivery pressure the ratification exists to check. An Architect who reports to the product line they gate will eventually be asked to ratify against a deadline instead of a constraint, and the org will not notice which one won until the incident. This is not a design-specific rule — it is the same separation that makes an internal auditor report to the audit committee and not to the CFO they audit. Below Chief, the function can sit inside a design or experience organization as long as that organization's leadership does not also own the delivery targets the ratifier is checking. At Chief, the requirement sharpens rather than relaxes: accountable to the executive table means the seat does not report solely into the CPO whose roadmap it can halt, or solely into the CTO whose platform it can gate. It answers to both, structurally, the way the Cultural Veto's executive air cover already requires in Article 3 — a veto backed by one interested executive is a veto that gets overruled the first time it costs that executive's own number."
  }
}