Durable Sessions AI UX vs AI Landscape Explainer: Which Framework?
// TL;DR
These frameworks solve completely different problems. Use the Christensen Durable Sessions Framework if you are building or fixing an AI-powered product with streaming, real-time, or multi-device requirements — it is an engineering architecture framework. Use the Iseminger AI Landscape Explainer Framework if you need to explain, categorise, or position AI technologies for a non-technical or mixed audience — it is a communication and classification framework. There is almost no overlap; your choice depends entirely on whether you are building AI products or explaining AI concepts.
// HOW DO THEY COMPARE?
| Dimension | Christensen Durable Sessions AI UX Framework | Iseminger AI Landscape Explainer Framework |
|---|---|---|
| Best for | Engineers and product teams building or auditing real-time AI chat/agent experiences | Communicators, PMs, educators, and executives who need to explain or classify AI technologies |
| Primary output | Architecture redesign plan with a Durable Sessions layer for resilient, multi-surface AI UX | A clear, layered explanation or classification of any AI concept mapped onto the AI hierarchy |
| Complexity | High — requires understanding of streaming protocols (SSE, WebSockets), pub/sub, agent topologies | Low — designed for simplicity and accessible to non-technical audiences |
| Time to apply | Days to weeks (architecture audit + implementation) | Minutes to hours (prepare an explanation or classify a technology) |
| Prerequisites | Working knowledge of streaming architectures, client-server models, and AI agent infrastructure | Basic familiarity with AI as a concept; no engineering knowledge required |
| Domain | AI product engineering and real-time infrastructure | AI literacy, education, and technology communication |
| Creator background | Mike Christensen (Ably) — real-time infrastructure and AI UX delivery | David Iseminger — AI/technology education and explainer content |
| Handles multi-agent systems | Yes — directly addresses orchestrator relay problems and multi-agent session architectures | No — not designed for system architecture concerns |
| Audience | Technical: software engineers, architects, technical product managers | Broad: executives, journalists, students, PMs, anyone explaining AI |
| Actionable deliverable | Gap map, failure mode audit, architecture migration plan | Layered explanation, classification label, audience-calibrated narrative |
What does the Christensen Durable Sessions AI UX Framework do?
The Christensen Durable Sessions Framework is an engineering architecture framework for teams building AI-powered products with real-time streaming interfaces — think AI chat, coding assistants, or multi-agent research tools. It diagnoses why AI product experiences break under real-world conditions (network drops, multi-device usage, concurrent agent activity) and prescribes a specific architectural pattern: Durable Sessions.
A Durable Session is a persistent, shared resource that sits between the agent layer and the client layer. Instead of agents streaming directly to a single client connection (the "Single-Connection Trap"), agents write events to the session and clients subscribe to it independently. This unlocks three foundational capabilities: Resilient Delivery (streams survive disconnections), Continuity Across Surfaces (sessions follow users across tabs and devices), and Live Control (clients can steer or cancel agents mid-generation).
The framework includes a 10-step workflow that takes you from auditing your current streaming architecture through designing the Durable Sessions layer to validating all three capabilities. It also addresses advanced concerns like the SSE Resume-Cancel Conflict (where closing a connection is ambiguous between disconnect and cancel) and the Orchestrator Dual-Purpose Problem (where orchestrators are forced to relay sub-agent updates).
What does the Iseminger AI Landscape Explainer Framework do?
The Iseminger AI Landscape Explainer Framework is a communication and classification framework for anyone who needs to accurately explain or categorise AI technologies. It provides a Nested Venn Diagram mental model: AI contains Machine Learning, which contains Deep Learning, which contains Generative AI. Each inner layer inherits properties from the outer layers.
The framework's 8-step workflow walks you through classifying any technology — a fraud-detection system, ChatGPT, a deepfake tool — by testing it against each layer's defining characteristics. It also maps the technology's position on a historical timeline (Expert Systems → ML → Deep Learning → Foundation Models) and flags dual-use risks.
A core principle is that simplification is a feature. The framework is explicitly designed for mixed audiences and encourages upfront acknowledgment of generalizations so non-experts can build a working mental model before encountering edge cases.
How do the Christensen Durable Sessions and Iseminger AI Landscape Explainer frameworks compare?
These two frameworks occupy entirely different problem spaces. Comparing them is less about trade-offs and more about understanding which problem you actually have.
The Christensen framework is for builders. If you are an engineer or technical PM struggling with dropped streams, multi-device blind spots, or stop-button ambiguity in your AI product, this framework gives you a concrete architecture migration path. It requires deep technical prerequisites — you need to understand SSE, WebSockets, pub/sub, and agent topologies. The output is an architecture redesign plan.
The Iseminger framework is for explainers. If you are a product manager presenting to a board, a journalist writing about deepfakes, or a student trying to understand how ChatGPT differs from phone autocomplete, this framework gives you a structured, audience-calibrated explanation. It requires no engineering knowledge. The output is a clear narrative or classification.
The Christensen framework is significantly more complex and time-intensive to apply — it involves auditing infrastructure and implementing architectural changes over days or weeks. The Iseminger framework can be applied in minutes to produce a polished explanation.
One area of indirect overlap: if you are using the Iseminger framework to explain an AI product's architecture to stakeholders, the Christensen framework's concepts (Durable Sessions, the Single-Connection Trap, the three foundational capabilities) could serve as the subject matter being classified and explained. But the frameworks themselves are complementary, not competitive.
Which should you choose?
Choose the Christensen Durable Sessions Framework if you are building or maintaining an AI product with a streaming interface and you are experiencing (or want to prevent) failures around disconnections, multi-device continuity, or user control during generation. This is the right framework if your problem is architectural and your audience is your engineering team.
Choose the Iseminger AI Landscape Explainer Framework if you need to explain, teach, or classify AI technologies for an audience that ranges from non-technical to moderately technical. This is the right framework if your problem is communication and your audience is stakeholders, students, or the public.
If you are a technical PM at an AI product company, you likely need both: Iseminger to communicate AI concepts upward to leadership, and Christensen to diagnose and fix delivery infrastructure with your engineering team. But they are not substitutes for each other. Picking the wrong one for your problem is the only real mistake you can make here.
// FREQUENTLY ASKED QUESTIONS
What is the Christensen Durable Sessions AI UX Framework?
It is an engineering architecture framework by Mike Christensen (Ably) that diagnoses why AI chat and agent experiences break under real-world conditions — like network drops or multi-device usage — and prescribes a Durable Sessions architecture where agents write to a persistent shared session layer instead of streaming directly to clients.
What is the Iseminger AI Landscape Explainer Framework?
It is a communication and classification framework by David Iseminger that uses a Nested Venn Diagram — AI contains Machine Learning, which contains Deep Learning, which contains Generative AI — to help anyone accurately explain, categorise, or position AI technologies for any audience level.
Can I use both the Durable Sessions and AI Landscape Explainer frameworks together?
Yes, they are complementary. Use the Iseminger framework to explain AI concepts to non-technical stakeholders and the Christensen framework to diagnose and fix your AI product's streaming architecture with your engineering team. A technical PM at an AI company would benefit from both.
Do I need to be a developer to use the Durable Sessions framework?
Effectively yes. The Christensen framework requires understanding of streaming protocols (SSE, WebSockets), pub/sub patterns, and agent architectures. It is designed for software engineers, infrastructure architects, and deeply technical product managers building real-time AI products.
Is the AI Landscape Explainer framework only for beginners?
No. While it is excellent for non-technical audiences, it also helps experts communicate clearly by providing a structured hierarchy and deliberate simplification approach. It is audience-adaptive — you calibrate the depth of explanation based on whether your audience is beginner, intermediate, or expert.
What problem does the Durable Sessions framework solve that the AI Landscape Explainer doesn't?
The Durable Sessions framework solves engineering problems: dropped streams on disconnect, no multi-device session continuity, stop-button ambiguity with SSE, and orchestrator relay bottlenecks in multi-agent systems. The Iseminger framework does not address infrastructure or architecture at all — it solves explanation and classification problems.
Which framework should a product manager use?
It depends on the task. For presenting AI strategy to a board or explaining product positioning, use the Iseminger AI Landscape Explainer. For auditing why your AI product's chat experience drops streams or fails across devices, use the Christensen Durable Sessions framework — or bring it to your engineering team.
What is a Durable Session in AI product architecture?
A Durable Session is a persistent, stateful, shared resource between the agent layer and client layer. Agents publish events to it; clients subscribe independently. Messages outlive any individual connection, enabling resilient delivery, multi-device continuity, and live agent control without coupling agent code to client connection health.