A credible DXP starts from a small, durable spine, not a sprawling stack.
Here’s the spine that we believe will outlast this hype cycle:
Content domain model that travels
We believe organizations today must treat content as a product, not a project. Model business concepts (“policy,” “offer,” “destination,” “term”) rather than pages or widgets, and version them like code so they survive channel shifts. Example: a retailer reuses one product entity across web, mobile, store associate apps, and partner APIs - no forked schemas. Replace search or translation? The model stays, only edges change. Migrations pivot from “rebuild everything” to “swap a provider.” If your model can’t outlive a vendor, it’s not a model - it’s technical debt.
An event stream as the nervous system
If content is anatomy, events are nerves. Every material action - view, click, add-to-cart, consent update - emits a well typed, immutable event that any tool can easily subscribe to. That unlocks in-session optimization. For example, a traveler who views “family-friendly Maldives resorts” and searches “overwater villas” gets a targeted itinerary now, not next quarter. Because tools subscribe to the same stream, you can swap Experimentation A for B without re-coding business logic. No events, no optimization. No shared schema, no portability.
Policy, governance, and safety rails
A great digital experience is a governed digital experience. Policy spans consent, retention, approvals, access control, and prompt governance for AI (control inputs/outputs, tone, sources, audits). A healthcare portal can allow AI-assisted authoring only if PHI is redacted, citations are present, and region-specific disclaimers compile before you hit publish. A bank’s personalization must honor consent at the edge in milliseconds. Your workflows must treat policies as deployable artifacts so compliance accelerates delivery instead of blocking it.
A clear orchestration contract
Orchestration is how components discover and cooperate at build time (compose content into views) and run time (switch experiments/components/layouts). Document the contract: APIs, events, and SLAs for plugins—and the exit paths (structured export, event replay, cache invalidation, identity fallbacks). Example: component-based assembly governed by a layout service; components subscribe to events and fetch decisions from registered providers. Swap the decisioning engine? Providers change; the contract doesn’t.
4 non-negotiables for the next decade
Reversibility
Every important decision should be easy to undo. Dry-run migrations, make import/export first-class, and test outbound connectors as often as inbound. Use cases: switch search engines without touching templates; clone an editorial workflow to a new region without re-inventing permissions. If a change needs a multi-month program, it’s not reversible—it’s a bet.
Edge performance budgets
Performance quietly taxes every KPI. TTFB (time to first byte) = time from request to first response byte; CLS (cumulative layout shift) = how much the layout jumps while loading. Set budgets — for example, TTFB < 200ms for cached pages; CLS < 0.1 — and make them contractual for any integration on the edge path. If a promotion engine adds 150ms, it must prove ROI or run async. Enforce with canaries and deploy gates.
Default instrumentation
If you can’t observe it, you can’t optimize it. Ship analytics, experimentation, and decision logging by default. Make “content → experiment → decision” a loop measured in days, not quarters. Each content type gets built-in variant hooks and exposure rules; every decision engine writes to the same log for attribution. This is the backbone Forrester pushes under “experience optimization.”
Evergreen upgradeability
Upgrades should fade into the background via forward-compatible APIs and SDK-first extensions. If customizations sit behind SDKs your UI extensions keep working across minor (and most major) releases. Teams spend time on outcomes, not platform heroics.
Composable ≠ collecting logos
Composable should look like a governed supply chain, not a shopping spree. Demand SLAs for latency, data quality, and failure modes. Publish integration contracts. Insist on exit paths. Keep a living “bill of materials” for your experience stack. If a vendor can’t show how to remove them cleanly, they shouldn’t be near your spine.
AI, where it counts
AI creates leverage when it accelerates the loop. It must provide model-aware authoring that produces on-brand content. Event-driven targeting that adapts in session. Guardrails such as prompt governance, redaction, source tracking, so outputs are safe by design. IDC says buyers will pay more when AI proves outcomes. Impossible without a measurable spine.