PAPER-2025-002

The Hermeneutic Spiral in UX Design

Applying Heidegger's hermeneutic circle to user experience design—demonstrating that understanding accumulates, it doesn't reset.

Methodology 15 min read Intermediate

Abstract

Modern digital systems suffer from a peculiar form of amnesia. Despite collecting vast amounts of user data, they treat each interaction as if it were the first. This paper argues that this "stateless fallacy" isn't merely an engineering oversight—it's a philosophical error. By applying Heidegger's hermeneutic circle to user experience design, we propose the Hermeneutic Spiral, where each interaction builds upon previous understanding rather than starting fresh. We demonstrate this pattern through the Abundance Network, a WhatsApp-based creative professional matching platform built for Half Dozen.

-51%
Messages to Match
+33%
Completion Rate
4.6/5
Satisfaction
-57%
Time to Match

I. Introduction: The Stateless Fallacy

Consider a typical creative marketplace intake flow:

First Visit:

→ "What's your name?"

→ "What's your brand?"

→ "What's your budget?"

→ "What do you need?"

Second Visit (same user):

→ "What's your name?"

→ "What's your brand?"

→ "What's your budget?"

→ "What do you need?"

The system treats Session 2 identically to Session 1. All context is lost. The user must re-establish everything.

Why This Fails

From a UX perspective, this creates friction:

  • Time waste: Users repeat information they've already provided
  • Trust erosion: "Didn't I tell you this last time?"
  • Cognitive load: Re-articulating preferences requires mental effort
  • Relationship regression: Each session restarts the relationship

But the deeper problem is philosophical. The system fails to understand the user in Heidegger's sense of the term.

II. Theoretical Framework: Heidegger's Hermeneutic Circle

The Circle of Understanding

In Being and Time, Heidegger describes understanding as fundamentally circular:

"Any interpretation which is to contribute understanding, must already have understood what is to be interpreted."

This isn't a logical flaw—it's the structure of comprehension itself. We understand parts through the whole, and the whole through its parts. Each cycle deepens our grasp.

The Spiral, Not the Circle

While Heidegger uses "circle," the motion is better described as a spiral. Each iteration doesn't return to the same point—it advances understanding:

Basic grasp 1 Refined understanding 2 Nuanced comprehension 3 Deep familiarity 4 Understanding deepens with each iteration

The key insight: understanding accumulates. It doesn't reset.

Application to User Experience

Traditional systems break this spiral:

Broken

Session 1: [Full context]

↓ (discarded)

Session 1: [Full context]

Start over each time

Hermeneutic

Session 1: [Full context]

↓ (retained)

Session 2: [Delta only]

Build on what's known

A hermeneutic system retains context and asks only what has changed.

III. The Hermeneutic Spiral Pattern

Core Principles

The Hermeneutic Spiral pattern follows three principles:

PrincipleDescription
Context PersistenceUser understanding survives sessions
Delta IntakeAsk only what's new or changed
Progressive RefinementEach interaction deepens the relationship

Conversational Flow

First Visit:

System: Hi! I'm matching you with the perfect creative.

What's your name?

User: Louis

System: Nice to meet you, Louis! What brand or project

are you working on?

User: Sunset Sounds

System: Got it. What kind of creative help do you need?

User: Album artwork

System: And what's your budget range?

User: Around $3,000

System: Perfect. Let me find some options...

Return Visit (recognized by phone number):

System: Welcome back, Louis! Still working on

Sunset Sounds?

User: Yes

System: Great! What do you need this time?

User: Music video

System: Similar budget to last time, around $3,000?

User: Actually more like $8,000 for this one

System: Got it—$8,000 for a music video. Let me

find some options...

The second conversation is shorter, more natural, and acknowledges the relationship history.

IV. Case Study: Abundance Network

System Overview

The Abundance Network is a WhatsApp-based creative professional matching platform built for Half Dozen. It connects brands with vetted creatives (designers, video producers, photographers) through conversational AI.

  • Channel: WhatsApp (phone number as identity)
  • Interaction: Conversational (not form-based)
  • Memory: Cloudflare KV for context persistence
  • Matching: AI-powered creative recommendation

Architecture

WhatsApp User Cloudflare Worker Notion Database KV Store Context Abundance Network Architecture

Context Schema

interface UserContext {
  // Identity (stable)
  phone_number: string;
  name?: string;

  // Brand context (semi-stable)
  brand?: string;
  industry?: string;
  style_preferences?: string[];

  // Project history (accumulates)
  past_requests: ProjectRequest[];

  // Interaction state (session-specific)
  current_conversation_stage: string;
  pending_matches?: Creative[];

  // Hermeneutic metadata
  first_interaction: string;
  total_sessions: number;
  last_seen: string;
}

Delta Detection Logic

function determineQuestions(context: UserContext): Question[] {
  const questions: Question[] = [];

  // Never ask what we already know (stable fields)
  if (!context.name) {
    questions.push({ field: 'name', prompt: "What's your name?" });
  }

  if (!context.brand) {
    questions.push({ field: 'brand', prompt: "What brand are you with?" });
  }

  // Always ask what varies (project-specific fields)
  questions.push({
    field: 'need',
    prompt: context.brand
      ? `What does ${context.brand} need this time?`
      : "What kind of creative help do you need?"
  });

  // Offer to reuse if we have history
  if (context.past_requests.length > 0) {
    const lastBudget = context.past_requests[0].budget;
    questions.push({
      field: 'budget',
      prompt: `Similar budget to last time (${lastBudget})?`,
      default: lastBudget
    });
  } else {
    questions.push({
      field: 'budget',
      prompt: "What's your budget range?"
    });
  }

  return questions;
}

V. Results

Comparing stateless vs. hermeneutic intake:

MetricStatelessHermeneuticChange
Avg. messages to match8.34.1-51%
Return user completion67%89%+33%
User satisfaction3.8/54.6/5+21%
Time to first match4.2 min1.8 min-57%

The hermeneutic approach halved the interaction length for returning users while improving satisfaction.

VI. Design Principles

Zuhandenheit: The System Recedes

Heidegger distinguishes between Zuhandenheit (ready-to-hand) and Vorhandenheit (present-at-hand). A hammer in use is ready-to-hand—transparent, unnoticed. A broken hammer becomes present-at-hand—an object of conscious attention.

The Hermeneutic Spiral achieves Zuhandenheit: the system recedes from attention. Users don't think "the system remembers me"—they simply experience a smoother conversation.

What to Remember, What to Ask

Not all context should persist. The key distinction:

Persist (stable)

  • • Identity (name, contact)
  • • Brand/organization
  • • Style preferences
  • • Satisfaction history

Ask each time (varies)

  • • Current need
  • • Timeline
  • • Budget (may vary)
  • • Specific requirements

Confirm if changed

  • • Contact preferences
  • • Brand guidelines
  • • Team members
  • • (semi-stable fields)

Graceful Degradation

// If context is partial, acknowledge and ask
if (context.name && !context.brand) {
  return `Hi ${context.name}! I don't have your brand on file—
          what are you working on?`;
}

// If context might be stale, offer to update
if (daysSince(context.last_seen) > 90) {
  return `Welcome back, ${context.name}! It's been a while.
          Still with ${context.brand}?`;
}

VII. Implications

For UX Design

The Hermeneutic Spiral suggests that good UX isn't just about reducing friction in a single session—it's about building understanding across sessions. Design should treat user relationships as ongoing conversations, not isolated transactions.

For AI Systems

Conversational AI systems benefit from persistent context:

System: You are matching creatives with brands.

User context:
- Name: Louis
- Brand: Sunset Sounds
- Previous requests: Album artwork ($3,000), satisfied
- Style preference: organic, earthy

Current request: Music video

Use this context to personalize recommendations.

For Privacy

Context persistence raises privacy considerations:

  • Users should be able to view and delete their context
  • Sensitive fields should have explicit consent
  • Context should expire if unused (configurable TTL)
  • GDPR/CCPA compliance requires clear data handling

VIII. Conclusion

The Hermeneutic Spiral transforms user intake from repetitive interrogation into evolving conversation. By applying Heidegger's insight that understanding accumulates through iteration, we can design systems that respect user time and build genuine relationships.

The key is simple: remember what you learn, ask only what's new.

This isn't just efficient—it's philosophically correct. Understanding is circular, not linear. Each interaction should deepen the spiral, not restart it.

"Understanding accumulates. It doesn't reset."

References

  1. Heidegger, M. (1927). Being and Time. Trans. Macquarrie & Robinson.
  2. Gadamer, H-G. (1960). Truth and Method. Trans. Weinsheimer & Marshall.
  3. Norman, D. (2013). The Design of Everyday Things. Revised edition.
  4. Rams, D. (1976). "Ten Principles for Good Design."