Durable Sessions AI UX vs High Standards High Support
// TL;DR
These two frameworks solve completely different problems and should never be treated as alternatives. Use the Christensen Durable Sessions AI UX Framework if you are building or fixing a real-time AI chat product that breaks on disconnects, multi-device usage, or mid-stream user control. Use the Liemandt High Standards High Support Builder if you are designing a team culture, education program, or onboarding system where people need to perform at their ceiling. Pick based on your problem domain — one is infrastructure engineering, the other is human performance design.
// HOW DO THEY COMPARE?
| Dimension | Christensen Durable Sessions AI UX Framework | Joe Liemandt High Standards High Support Builder |
|---|---|---|
| Best for | Engineering teams building AI chat or agent-driven product experiences with streaming delivery | Leaders designing team cultures, education programs, onboarding systems, or any environment requiring peak human performance |
| Problem domain | Real-time AI UX infrastructure — disconnections, multi-device sync, live agent control | Human potential development — disengagement, low standards, lack of scaffolded support |
| Complexity | High — requires replacing streaming architecture, adopting pub/sub, redesigning agent-client topology | Moderate — requires organizational discipline and culture change, but no technical infrastructure overhaul |
| Time to apply | Weeks to months — involves architectural migration from SSE to durable sessions with bidirectional transport | Days to weeks for initial commitments; months to fully embed culture and scaffolding ladders |
| Prerequisites | Existing AI streaming product, knowledge of SSE/WebSockets, understanding of pub/sub patterns | Authority or influence over culture, hiring, curriculum, or performance standards in your organization |
| Output type | Redesigned streaming architecture with resilient delivery, cross-surface continuity, and live control | Compressed strategy (Three Lines, Three Words), scaffolding ladders, feedback frameworks, and market-entry plans |
| Creator background | Mike Christensen (Ably) — real-time infrastructure expert, presented at AI Engineer conference | Joe Liemandt — billionaire founder of Trilogy/ESW Capital, founder of Alpha School, featured on My First Million |
| AI relevance | Directly solves AI product delivery problems — this is core AI infrastructure | Tangentially relevant to AI via Brain Lift concept and DOK stack; primarily a human performance framework |
| Who should NOT use this | Non-technical leaders, educators, or anyone not building a real-time AI streaming product | Engineers looking for a technical fix to broken AI chat UX — this will not solve streaming or connectivity issues |
| Key mental model | Decouple agents from clients via a persistent shared session layer (pub/sub) | Combine relentlessly high standards with genuine scaffolded support — never one without the other |
What does the Christensen Durable Sessions AI UX Framework do?
The Christensen Durable Sessions AI UX Framework diagnoses and fixes a specific architectural failure in AI chat products: the Single-Connection Trap. Most AI products stream responses from the model to the client over a single SSE (Server-Sent Events) connection. When that connection drops — because the user switches networks, changes tabs, or opens a second device — the stream is lost. The framework introduces a Durable Sessions layer between agents and clients, built on pub/sub infrastructure, that makes streams resilient to disconnections, visible across multiple devices, and controllable in real time.
The framework identifies three foundational capabilities every production AI UX needs: Resilient Delivery (streams survive disconnects), Continuity Across Surfaces (sessions follow users across tabs and devices), and Live Control (users can steer, interrupt, or cancel agent work mid-stream). It also solves the SSE Resume-Cancel Conflict — the fundamental ambiguity where closing an SSE connection could mean either "I disconnected, please buffer" or "I pressed stop, please cancel" — by replacing SSE with bidirectional transport.
For multi-agent architectures, it eliminates the Orchestrator Dual-Purpose Problem by letting every sub-agent write directly to the shared session, freeing the orchestrator from proxying progress updates.
What does the Liemandt High Standards High Support Builder do?
The Liemandt High Standards High Support Builder is a human performance framework for building environments — teams, schools, companies, bootcamps — where people consistently exceed their own perceived limits. Its core insight is that high standards without support causes disengagement, while high support without standards prevents the development of grit and self-confidence. Both must coexist simultaneously.
The framework provides concrete tools: the Three Lines, Three Words compression method forces you to distill your entire strategy into nine words that pass an "edgeful" test (someone reasonable must be able to disagree with each line). The 100-for-100 scaffolding technique starts people below their current level, lets them win, then escalates — rewriting their belief about what's possible. The Mentor Mindset framing, drawn from Dr. Yeager's research, transforms hard feedback from threatening to motivating with specific language: "I'm giving you this because I know you can crush it."
It also includes business strategy components: the Tesla Roadster Strategy for market entry (start premium, fund mass-market expansion) and the Nonprofit Is Non-Scalable principle, which argues that missions requiring global scale must be structured for capitalist funding.
How do they compare?
These frameworks operate in entirely different domains and should not be evaluated as substitutes. The Durable Sessions framework is a technical architecture pattern for AI product engineers. The High Standards High Support Builder is a human performance and organizational design methodology for leaders, educators, and founders.
The only overlap is that both are relevant to people building AI products — but they address opposite sides of the stack. Durable Sessions fixes the delivery layer between your AI model and your user's screen. High Standards High Support fixes the human layer — how your team performs, how your users or students grow, how your organization aligns around a strategy.
If you are an engineering lead whose AI chat product drops streams on mobile, the Liemandt framework will not help you. If you are a founder struggling with team disengagement and cultural drift, the Christensen framework is irrelevant to your problem.
One useful intersection exists: if you are building an AI-powered education product (like Alpha School's Time Back), you might use Durable Sessions for the technical delivery layer and High Standards High Support for the pedagogical and cultural layer. But even in this case, they solve orthogonal problems.
Which should you choose?
Choose the Christensen Durable Sessions AI UX Framework if: You are building or maintaining an AI chat or agent-driven product and your users experience broken streams on disconnect, cannot see live responses on a second device, or cannot stop/steer the agent mid-generation. This is your framework. It is clearly better for any streaming architecture diagnosis or redesign.
Choose the Liemandt High Standards High Support Builder if: You are designing a team culture, onboarding program, educational curriculum, or any environment where human performance is the bottleneck. It is clearly better for organizational design, culture compression, and scaffolded skill development.
If you are building an AI product company, you likely need both — Durable Sessions for your product architecture and High Standards High Support for your team and go-to-market strategy. But apply them to their respective domains. Do not conflate an infrastructure problem with a culture problem or vice versa.
Can these frameworks be used together?
Yes, but only in the sense that a company building an AI product needs both solid infrastructure and a high-performing team. An AI education startup, for example, might use Durable Sessions to ensure its AI tutor streams reliably across student devices, while simultaneously applying High Standards High Support to design a curriculum that pushes students beyond their perceived limits with proper scaffolding. The frameworks are complementary across domains, not competitive within one.
// FREQUENTLY ASKED QUESTIONS
Is the Durable Sessions framework or the High Standards framework better for building AI products?
They solve different layers of the same problem. Durable Sessions is better for the technical delivery architecture — making AI streaming resilient and multi-device. High Standards High Support is better for the human side — building the team that ships the product and designing experiences that push users to grow. Most AI product companies need both, applied to their respective domains.
Can I use the High Standards High Support framework to fix a broken AI chat experience?
No. If your AI chat drops streams on disconnect, cannot sync across devices, or lacks a working stop button, that is an infrastructure problem. The High Standards framework addresses human performance and organizational culture, not streaming architecture. You need the Christensen Durable Sessions framework for technical delivery issues.
What is the Durable Sessions framework and when should I use it?
The Durable Sessions framework is an architectural pattern that places a persistent, shared session layer between your AI agents and client applications. Use it when your AI product's streaming breaks on disconnects, cannot show live responses across multiple tabs or devices, or cannot support mid-stream user control like stop buttons or steering messages.
What is the High Standards High Support framework and when should I use it?
It is a human performance methodology from Joe Liemandt that combines relentlessly high standards with genuine scaffolded support. Use it when designing team cultures, education programs, onboarding systems, or any environment where people need to perform at their ceiling. It includes strategy compression (Three Lines, Three Words), scaffolding ladders, and the Mentor Mindset feedback approach.
Do I need technical skills to apply either of these frameworks?
The Durable Sessions framework requires significant technical expertise — understanding of SSE, WebSockets, pub/sub patterns, and streaming architecture. The High Standards High Support framework requires no technical skills but demands leadership authority, organizational discipline, and willingness to set and enforce genuinely hard standards while building visible support structures.
Which framework is faster to implement?
The High Standards High Support framework is faster to start — you can compress your strategy into Three Lines and redesign your feedback approach within days. Full culture change takes months. The Durable Sessions framework requires weeks to months of architectural migration, replacing SSE with pub/sub infrastructure and bidirectional transport, but delivers measurable UX improvements immediately upon deployment.
What is the Brain Lift concept and does it relate to Durable Sessions?
Brain Lift is a concept from the High Standards framework — a curated knowledge base of facts, summaries, and insights loaded as context when using AI tools to avoid consensus-level outputs. It does not relate to Durable Sessions. Brain Lift is about improving the quality of AI-assisted thinking; Durable Sessions is about improving the reliability of AI response delivery infrastructure.
Can the Durable Sessions framework help with multi-agent AI architectures?
Yes, this is one of its strongest applications. It solves the Orchestrator Dual-Purpose Problem where orchestrators are forced to both coordinate sub-agent tasks and proxy progress updates. With Durable Sessions, every sub-agent writes directly to the shared session channel, and clients subscribe once to see all concurrent agent activity without additional coordination code.