Durable Sessions AI UX vs Stop Wasting Time: Which Framework?
// TL;DR
These two frameworks solve completely different problems and should never be compared as alternatives. Use the Christensen Durable Sessions AI UX Framework if you are building or auditing an AI-powered product and need resilient streaming, multi-device continuity, or live agent control. Use the Amy Landino Stop Wasting Time Method if you are personally stuck in procrastination or over-commitment and need to reclaim focused time for meaningful work. They do not overlap. Pick the one that matches your actual problem.
// HOW DO THEY COMPARE?
| Dimension | Christensen Durable Sessions AI UX Framework | Amy Landino Stop Wasting Time Method |
|---|---|---|
| Best for | Engineering teams building AI chat/agent products that need resilient, multi-surface, controllable streaming | Individuals stuck in procrastination, over-preparation, or over-commitment who want to reclaim focused time |
| Domain | AI product engineering and real-time architecture | Personal productivity and attention management |
| Complexity | High — requires understanding of streaming protocols, pub/sub, WebSockets, and distributed systems | Low — requires honest self-reflection and willingness to change daily habits |
| Time to apply | Days to weeks for a full architectural redesign; hours for an initial audit | 30 minutes for the initial audit; ongoing daily practice |
| Prerequisites | An existing or planned AI product with streaming architecture (SSE, WebSockets, etc.) | No technical prerequisites — only a goal you are not making progress on |
| Output type | Architectural gap analysis, redesigned streaming infrastructure, validated Durable Sessions layer | Personal attention audit, obligation inventory, daily action plan |
| Creator background | Mike Christensen (Ably) — real-time infrastructure engineer, AI Engineer conference speaker | Amy Landino — YouTuber and author focused on productivity and time management |
| Team vs. individual | Team-oriented — engineering, product, and design collaboration required | Purely individual — self-directed audit and behavior change |
| Key mental model | Agent-Client Decoupling via a persistent session layer | Attention (not time) is the scarce resource; preparation is disguised procrastination |
| Failure if skipped | AI product breaks on network drops, multi-device use, or concurrent agents — users churn | You stay in a loop of consuming productivity content instead of doing the actual work |
What does the Christensen Durable Sessions AI UX Framework do?
The Christensen Durable Sessions AI UX Framework, introduced by Mike Christensen of Ably at the AI Engineer conference, diagnoses why AI chat and agent experiences break under real-world conditions. The core insight is that most AI products stream responses over a single HTTP connection (typically SSE), and when that connection drops — due to a network switch, a tab change, or a mobile context switch — the response is lost. Christensen calls this the Single-Connection Trap.
The framework defines three foundational capabilities every production AI product needs: Resilient Delivery (streams survive disconnections), Continuity Across Surfaces (sessions follow users across tabs and devices), and Live Control (users can steer or stop an agent mid-generation). The solution is a Durable Sessions layer — a persistent, shared pub/sub channel between the agent layer and the client layer. Agents write events to the session; clients subscribe to the session. Neither party holds a private pipe to the other. This eliminates the need for agent-side replay logic, resolves the SSE resume-cancel ambiguity, and naturally supports multi-agent architectures where sub-agents publish progress independently.
This is a technical architecture framework. It requires engineering resources, understanding of streaming protocols, and access to your product's infrastructure.
What does the Amy Landino Stop Wasting Time Method do?
Amy Landino's Stop Wasting Time Method helps individuals identify where their time and attention are leaking and apply a repeatable stop/start framework to reclaim meaningful progress. The central reframe is that attention, not time, is the scarce resource. Everyone has the same 24 hours; what separates productive people is obsessive management of where their focus goes.
The method walks you through a nine-step workflow: auditing your "permission-slip loop" (consuming productivity content instead of doing the work), naming the specific goal you are avoiding, surfacing the external and internal voices blocking you, inventorying where your attention actually goes, auditing obligations and practicing "no as a complete sentence," applying Parkinson's Law to every open project, reducing friction on needed learning, protecting small available time blocks, and distinguishing genuine rest from avoidance.
This is a personal productivity framework. It requires no tools, no team, and no technical background — just honesty about your current habits.
How do they compare?
These frameworks operate in entirely different domains. One is an engineering architecture pattern for AI products; the other is a personal attention-management system. There is no functional overlap:
- Problem type: Durable Sessions solves a technical infrastructure problem (fragile AI streaming). Stop Wasting Time solves a behavioral problem (procrastination and attention leakage).
- User: Durable Sessions is for engineering teams shipping AI products. Stop Wasting Time is for any individual who feels stuck.
- Complexity: Durable Sessions is high-complexity, requiring distributed systems knowledge. Stop Wasting Time is low-complexity, requiring self-reflection.
- Output: Durable Sessions produces an architectural redesign. Stop Wasting Time produces a personal action plan.
- Timeframe: Durable Sessions takes days to weeks to implement. Stop Wasting Time can begin producing results in a single afternoon.
If you are looking at both of these frameworks simultaneously, you are likely in the research phase of two completely separate problems. That is fine — just recognize they are not alternatives to each other.
Which should you choose?
Choose the Christensen Durable Sessions AI UX Framework if you are building, auditing, or scaling an AI-powered product and your streaming architecture cannot handle disconnections, multi-device access, user-initiated stop/steer controls, or multi-agent progress updates. This is a non-negotiable infrastructure layer for any AI product moving from demo to production. If your users lose responses when they switch networks or cannot see a live response on a second device, this framework directly solves that.
Choose the Amy Landino Stop Wasting Time Method if you are personally stuck — spending more time consuming productivity content than doing meaningful work, saying yes to every obligation, or deferring projects because they feel overwhelming. This framework is especially useful if you suspect the real blocker is not lack of time but misallocated attention and unexamined resistance.
You may need both if you are an AI product builder who is also personally procrastinating on shipping. Apply Landino's method to your own habits first, then apply Christensen's framework to your product's architecture. They are complementary, not competing.
// FREQUENTLY ASKED QUESTIONS
Can I use the Durable Sessions framework for non-AI products?
Yes. The Durable Sessions pattern — persistent pub/sub channels between producers and consumers — applies to any real-time product where streams must survive disconnections, span multiple devices, or support bidirectional control. It originated in AI UX but the architecture is general-purpose for real-time applications.
Is Amy Landino's method just another productivity system?
It is specifically designed to break the loop of consuming productivity content instead of doing the work. The first step is auditing whether your research into productivity is itself a form of procrastination. If you recognize that pattern, the method is pointed directly at you. It is less a system and more an intervention.
Do I need WebSockets to implement Durable Sessions?
Not necessarily, but you need a bidirectional transport if you require Live Control (stop buttons, steering messages). SSE is strictly one-way and creates an irresolvable ambiguity between resume and cancel. WebSockets or an equivalent bidirectional protocol is required for the full set of three foundational capabilities.
How long does it take to implement the Durable Sessions framework?
An initial audit against the three foundational capabilities takes a few hours. Designing and implementing the Durable Sessions layer — redirecting agent output to a persistent channel, switching clients to session subscriptions, and replacing SSE with WebSockets — typically takes days to weeks depending on your existing architecture and team size.
What if I feel like I am wasting time but I do not have a specific goal?
Landino's Step 2 addresses this directly. If you struggle to name what you want to be doing, that is a signal that outside voices (expectations) and inside voices (self-doubt) are suppressing your actual goal. Step 3 surfaces those voices explicitly so you can separate what you want from what others expect.
Can the Durable Sessions framework work with the Vercel AI SDK?
The Vercel AI SDK uses SSE by default, which places you inside the Single-Connection Trap. You can keep the SDK for agent orchestration but must add a Durable Sessions layer between the agent output and the client. The agent writes to the session channel instead of directly to the SSE response. This is a common migration path.
Are these two frameworks related in any way?
No. They solve completely different problems in completely different domains. Christensen's framework is a technical architecture pattern for AI product infrastructure. Landino's method is a personal productivity intervention. They share no concepts, workflows, or target audience. Choose based on whether your problem is a product architecture gap or a personal attention gap.