Durable Sessions vs Architect Elevator: Which Framework?

What does the Christensen Durable Sessions AI UX Framework do?

The Christensen Durable Sessions Framework is a diagnostic and prescriptive methodology for AI product teams whose chat or agent experiences break under real-world conditions. It identifies a root cause that Mike Christensen calls the Single-Connection Trap: the default pattern where an AI agent streams responses over a direct HTTP connection (typically SSE) that is tightly coupled to one client's connection health. When that connection drops — a mobile user switches networks, a tab is closed, a second device opens — the stream is lost.

The framework prescribes rebuilding around a Durable Sessions layer: a persistent, shared, independently addressable resource that sits between agents and clients. Agents write events to the session; clients subscribe to it. This architectural inversion unlocks three foundational capabilities that separate a fragile demo from a production-grade AI experience:

1. Resilient Delivery — streams survive disconnections and clients resume exactly where they left off.

2. Continuity Across Surfaces — sessions follow users across tabs and devices.

3. Live Control — clients can steer, interrupt, or cancel agents mid-generation.

The framework also solves the SSE Resume-Cancel Conflict (closing a connection is ambiguous between disconnect and cancel) and the Orchestrator Dual-Purpose Problem (forcing orchestrators to relay sub-agent progress updates). It includes a concrete 10-step workflow from audit to validation.

What does the Hohpe Architect Elevator Methodology do?

The Hohpe Architect Elevator Methodology is a comprehensive operating system for the software architect role, derived from Gregor Hohpe's decades of experience at Google, AWS, and in enterprise consulting. Its core thesis: an architect's job is not to be the smartest person in the room but to make everyone else smarter.

The methodology provides a toolkit of principles and techniques for navigating the full vertical of an organisation — from the engine room (code-level detail) to the penthouse (CIO and board conversations). Key techniques include:

- The Phantom Sketch Artist — draw what you understood so others can correct you, unlocking their tacit knowledge.

- Common Framing — expand the solution space into a shared map (e.g., a 2×2 matrix) before allowing debate.

- Political Capital management — earn trust through delivery and transparency, then spend it deliberately on the one issue that matters most.

- Purpose-Driven Mapping — act as a scout with a specific objective, not a cartographer maintaining an exhaustive landscape.

The framework explicitly rejects binary "good vs. bad" architecture judgments, replacing them with suitable vs. not suitable evaluations grounded in actual business context. It also addresses how architects should use tools like LLMs: as amplifiers of their own reasoning, never as substitutes.

How do they compare?

These two frameworks operate at entirely different levels of abstraction and solve fundamentally different problems. Comparing them head-to-head on most technical dimensions produces a category error — they are complementary, not competing.

Durable Sessions is a domain-specific architecture pattern for a precise problem: AI streaming infrastructure that breaks under real-world conditions. It gives you a concrete diagnosis (the Single-Connection Trap), a concrete prescription (Durable Sessions via pub/sub), and a concrete validation checklist (three capabilities that must pass). You can apply it in a sprint and ship measurable infrastructure improvements.

The Architect Elevator is a role-level operating methodology that applies across every technology domain. It does not tell you what to build — it tells you how to think, communicate, and facilitate decisions about what to build. Its outputs are better decisions, clearer trade-off articulation, and organisational influence. It takes months and years to internalise, and its impact is measured in decision quality and team capability, not shipped code.

Where they do intersect is instructive: an architect using the Hohpe methodology might encounter a team struggling with AI streaming UX. They would apply Step 2 (Map the solution space) to frame the debate, Step 3 (Identify inherent complexity) to acknowledge that distributed real-time delivery has irreducible complexity, and Step 5 (Surface hidden assumptions) to expose the assumption that SSE is sufficient. The Durable Sessions framework would then provide the domain-specific solution within that broader architectural facilitation.

Which should you choose?

If you are an AI product engineer and your users are losing streamed responses, cannot continue sessions across devices, or have no way to stop or steer an agent mid-generation — use the Christensen Durable Sessions Framework. It directly diagnoses and fixes these problems with a step-by-step workflow.

If you are a senior engineer or architect navigating complex technical decisions, communicating with executives, or trying to grow your influence without becoming an ivory-tower bottleneck — use the Hohpe Architect Elevator Methodology. It is the more broadly applicable framework and will serve you across every domain and decision you encounter.

If you are both — a technical leader responsible for an AI product's architecture — use both. The Architect Elevator gives you the operating methodology for facilitating the decision and communicating it up and down the organisation. Durable Sessions gives you the specific architectural pattern to prescribe when the diagnosis points to streaming infrastructure as the root cause.

Neither framework substitutes for the other. Durable Sessions without architectural judgment risks over-engineering a simple product that does not need multi-device sync. The Architect Elevator without domain-specific patterns like Durable Sessions risks facilitating a debate without offering a concrete solution when one exists.