Lanchester R&DTactical Exploration Lab
Coordination Systems
Conversation DesignUXMobileSocial

leaf

Branching conversation threads for complex deliberation.

leaf Diagnostic
IMG_REF // LEAF

Problem Defined

"Linear chat decomposes under multi-threaded topics, destroying context."

01

Strategic Context

Linear streams fail to manage simultaneous deliberations.

02

Competitive Imbalance

Chat derailment destroys decision momentum.

03

System Hypothesis

Anchoring threads to specific segments preserves context and signal.

04

Process Architecture

How the system was designed, tested, and refined.

01

DEFINE

Objective

Identify context destruction in linear conversation streams.

What We Did
  • Analyzed team deliberation logs
  • Mapped decision patterns
  • Identified derailment points
What Failed
  • Focused on threading UI rather than structural context persistence
What We Learned
  • Linearity is the enemy of multi-threaded deliberation
What We Adjusted
  • Reframed as a non-linear graph deliberation system
02

MAP

Objective

Visualize non-linear conversation anchors.

What We Did
  • Mapped segment-based anchoring logic
  • Identified context persistence nodes
What Failed
  • Initial maps were too complex for mobile-first behavior
What We Learned
  • Navigation must feel linear even if the data structure isn't
What We Adjusted
  • Created a "thread-folding" UI logic
03

VALIDATE

Objective

Test deliberation velocity in branching threads.

What We Did
  • Ran side-by-side deliberation tests
  • Measured time-to-decision
What Failed
  • Users lost track of "main" thread intent
What We Learned
  • Anchors must be explicitly visual and persistent
What We Adjusted
  • Integrated persistent segment headers for every branch
04

EXECUTE

Objective

Build the branching graph engine.

What We Built
  • Non-linear data store
  • Segment anchoring system
  • Graph navigation UI
What Failed
  • Over-built the summarization features early on
What We Learned
  • Context persistence is more important than automated summary
What We Adjusted
  • Prioritized structural anchoring over AI synthesis
05

MEASURE

Objective

Calculate noise reduction and decision velocity.

Metrics Tracked
  • Signal-to-noise ratio
  • Context retention time
  • Decisional speed
What Failed
  • Metrics focused on message count, not signal quality
What We Learned
  • Signal-to-noise is a qualitative shift that requires behavioral tracking
What We Adjusted
  • Introduced focus-persistence tracking for deliberators

Rule Application

How doctrine was operationalized.

Intellectual Rigor
01_INT
Applied By
  • Defining the mechanics of derailment before building
  • Mapping context anchors
Evidence

50% reduction in conversational noise recorded in dev cycles

Tactical Execution
02_TAC
Applied By
  • Shipping core segment anchoring first
  • Focusing on mobile-first navigation
Evidence

Working prototype achieved context persistence in 10 days

Human Calibration
03_HUM
Applied By
  • Reducing context-switching load
  • Designing around deliberation patterns
Evidence

Zero user rejection of branching logic after UI folding

Machine Leverage
04_AI
Applied By
  • Automated thread summarization for newcomers
  • Pattern detection in deliberation
Evidence

AI reduces the burden of catching up on complex branches

05

Product Architecture

Non-linear conversation graph with segment anchors.

leaf Architecture
System Schematic // V-01
06

AI Leverage

Automated thread summarization.

07

Outcomes & Learnings

Increased deep work efficacy by reducing context switching.