Digital Operations HBS SPRING'26
HMW design a life operating system that shows the right thing, in the right way, at the right time?
Jada Hawkins
State-Aware Operations
Problem
Providing one-size-fits-who? software is design malpractice.
one size
almost never fits all
Every inbox, calendar, and productivity tool presents the same load regardless if you're thriving or if you didn't sleep last night.
Five
States we identified
Three
Axes being assessed
Key Pain Point
The system shows you everything even if you can't handle it.
The Market Missed
Proximity once made life management a shared process. Analog workarounds extended it, and apps unbundled it. Now, individuals are left to manage this fragmented complexity alone.
Our Core Thesis
If we deliver the right information, in the right way, at the right time, we earn the right to ask for more as precision deepens client trust.
The Product
What Echo is and isn't.
Mandate
We study people at the point of cognitive and emotional collapse, with the intent to design better systems through failure.
The Client
High-performing. Exceptional until they aren't. Assumed to have ADHD, but not seeking a diagnosis.
The Problem
Existing tools assume users can initiate on their own. That assumption fails at the exact moment it's needed most.
Echo Is
✓
ambient
runs in the background of life
✓
a listener
reads what you do, not what you say
✓
calm infrastructure
same data, different interface based on your capacity
✓
built for who showed up today
not who you planned to be
✓
designed for dysregulation
it still works when nothing else does
✓
doesn't judge
you can't fall behind in your own life
✓
your receipts
patterns, triggers, logic, and language we observed
✓
the missing layer
that every other app assumed you had
Echo Isn't
×
a productivity tool
it doesn't assume you slept last night
×
an optimizer
efficiency is never our focus, you are
×
built for the best you
because that person doesn't need us
×
asking you to try harder
it meets you where you are, not where you want to be
×
built for linear lives
there's an entire industry already doing that
×
demanding discipline
because shame isn't a strategy
×
one more thing to keep up with
instead, it keeps up with you
×
trying to fix you
because you're not broken, you're unsupported
The Value Chain
Understand the client and the context to restore their capacity, stability, and agency
Detection
Triage
Prioritization
Scaffolding
Execution
Recovery
Accountability
Traditionally
Moms
Wives
Friends
Moms
Wives
Friends
Therapists
Moms
Wives
Friends
Family
Friends
Community
School
Work
Location
Admins
Therapists
Moms
Wives
Friends
Coaches
Apps
(None)
Note Taking Tools
Therapy Platforms
To-Do Apps
Task Managers
Second Brain Apps
Note Taking Tools
Comms Apps
Task Managers
Life OS Apps
Therapy Platforms
Mindfulness Apps
Crisis Apps
Habit Trackers
Coaching Apps
Body Doubling Apps
Analog
Body Scan
Journaling
Mood Tracking
Sticky Notes
Index Cards
Brain Dump
Eisenhower Matrix
Numbered Lists
Whiteboard Sorting
Bullet Journal
Printed Templates
Physical Binders
To-Do Lists
Physical Timer
Day Planner
Rest
Journaling
Nature Walks
Breathwork
Habit Tracker
Wall Calendar
Accountability Partner
Echo
Client Intake
Adaptive Understanding
Operates across the entire chain, translating signals into the right action at the right time.
Initial Workflows
Understanding users and adapting to them
Workflow One
Client Intake
Data onboarding for the day zero client
Built — initial concept
01
Integrate
System connects to client's inbox, calendar, and address book
02
Scan
System processes all user data from integrated accounts
03
Classify
System synthesizes and classifies findings into the data model
Day Zero scenario. The user has not opened their inbox or calendar in weeks. They are ready to re-enter but every starting point carries enough weight to prevent them from starting at all. The system removes all decisions.
Workflow Two
Adaptive Understanding
System prescribes the best next action based on client data and actions
In progress — state-aware operating model
Signals shape the response
Client Portrait (user data), Current Living Loop State (context), Real-Time Vitals (capacity)
Three axes define condition
Capacity, Stability, Agency
Five states of living
Day Zero → Not a Drill → Daily Management → Drift Detected → Stellar + Stable
Current state determines any interventions
Inputs → Axes → State → Response
Client Onboarding
Bring calm to chaos with a clear next move
Step One > Read Signals
Client Intake
Inbox 1,847 unread, last opened 11 weeks ago Flag
Calendar 14 meetings missed, 3 flagged invites unanswered Flag
Contacts 6 people you owe a reply to, some now at risk Flag
Latency Response avg 18 days, up from 2 Flag
Pattern Third re-entry. Recovery slower each time. Watch
Three Axes
Capacity
Low
Stability
Fragile
Agency
Minimal
Step Two > Adaptive Interventions
Day Zero
System Determined
Intake complete. Here’s what matters now.
Echo Asks
Can you take one action today?
What's Visible Right Now
VisibleThe 3 things that are genuinely on fire
Visible8 people you've made commitments to
VisibleThe one task that unblocks the most
HiddenYour full backlog
HiddenLong-range planning
HiddenAnything that isn't necessary right now
State-Aware Operating Model
How the system adapts
select a state to see what changes
Current State
Not a Drill
Capacity
Critical
Stability
At Risk
Agency
Absent
Signals Read
Inbox97% full, storage failure imminentFlag
CalendarRent missed, 3rd occurrenceFlag
ContactsLandlord + bank awaiting replyFlag
PatternFull collapse. No action in 30 days.Flag
The system has isolated what's actually on fire. Everything else is paused until we triage the crisis.
System Determined
Something here needs immediate attention.
Echo Asks
What’s actually at risk?
What's Visible Right Now
VisibleThe single highest-consequence item
VisibleThe exact action + who to contact
HiddenEverything else. Everything.
HiddenBacklog, relationships, planning
Current State
Day Zero
Capacity
Low
Stability
Fragile
Agency
Minimal
Signals Read
Inbox1,847 unread, last opened 11 weeks agoFlag
Calendar14 meetings missed, 3 flagged invitesFlag
Contacts6 people owed a reply, some at riskFlag
LatencyAvg 18 days, up from 2Flag
PatternThird re-entry. Recovery slowing.Watch
We found 28 open asks, 3 things that are actually on fire, and 1,612 items we're archiving on your behalf.
You don't need to see all of it. We'll show you what matters and hold the rest.
System Determined
Intake complete. Here’s what matters now.
Echo Asks
Can you take one action today?
What's Visible Right Now
VisibleThe 3 things that are genuinely on fire
Visible8 people you've made commitments to
VisibleThe one task that unblocks the most
HiddenYour full backlog
HiddenLong-range planning, low-consequence threads
Current State
Drift Detected
Capacity
Declining
Stability
Slipping
Agency
Weakening
Signals Read
InboxResponse rising: 2 days to 8 over 3 weeksWatch
CalendarTwo tasks rescheduled 4x, same onesWatch
PatternAvoidance sequence preceded last collapseFlag
History73% match to pre-collapse patternFlag
The same two tasks have been rescheduled four times. Response latency is climbing. These signals align with past drift cycles. Early intervention is required.
System Determined
Pattern identified. You’re starting to drift.
Echo Asks
What's the smallest correction we can make right now?
What's Visible Right Now
VisibleThe two avoided tasks + why they're stuck
VisiblePattern match to prior cycles
VisibleA small intervention that breaks the loop
HiddenFull backlog, new commitments
Current State
Daily Management
Capacity
Moderate
Stability
Stable
Agency
Present
Signals Read
InboxResponse 1–2 days, consistentClear
Calendar3 upcoming commitments, all on trackClear
Contacts22 loops: 8 on others, 14 actionableWatch
PatternStable engagement for 18 daysClear
Nothing is on fire. Everything is in motion. Take a moment to think. We’ve organized things so you can see the full picture.
System Determined
You're in control.
Echo Asks
Where do you want to start?
What's Visible Right Now
VisiblePrioritized queue with reasoning
VisibleWho's waiting on you, and for how long
VisibleDependencies and blockers
VisibleUpcoming deadlines with context
VisibleRelationship health signals
Current State
Stellar + Stable
Capacity
High
Stability
Strong
Agency
Full
Signals Read
InboxSame-day responses, 9 consecutive daysClear
CalendarAll commitments met this monthClear
ContactsRelationship health strong across all loopsClear
PatternLongest stable streak in 18 monthsClear
You have full capacity and strong stability. This is the window to close the gaps between who you are now and who you want to be.
System Determined
You're in a strong position. Leverage this time.
Echo Asks
What are you building towards?
What's Visible Right Now
VisibleComplete landscape: all matters, loops, tasks
VisibleStrategic opportunities, not just operations
VisibleFull relational context and health
VisibleVision and era alignment
VisibleEverything. You have the capacity for it.
Under the Hood
The Operating Logic
Client Intake
Mechanism
Behavioral signals pulled from integrated accounts. No manual input. The system reads actions and intentions.
ModuleSignals
InboxBacklog volume
LatencyTime before action
CalendarFollow-through rate
ContactsKey relationship Health
Pattern30-day behavioral trends
Implication
Observed behavior is more reliable than self-reported data, especially in a crisis when users cannot accurately assess their own state.
Loop Paths
Mechanism
Every signal is scored and averaged along the three axes that map to the observed collapse pathways in the Living Loop.
AxisAverage of
CapacityInbox + Latency + Pattern
StabilityCalendar + Contacts + Pattern
AgencyLatency + Contacts + Calendar
Implication
Capacity and Stability determine state, whereas Agency impacts the depth of the system's response.
User State
Mechanism
Rules engine that determines user state from a staged and prioritized signal analysis.
StateCapStabTag
Not a Drill≤ 1≤ 0Crisis
Day Zero≤ 2≤ 1Recovery
Drift Detected≤ 2or ≤ 1Warning
Daily Mgmt≥ 2≥ 2Stable
Steller≥ 3≥ 3Peak
Implication
States prevent users in crisis mode from being routed to things that they cannot currently handle.
Platform Response
Mechanism
State, past patterns, and inferred capacity with determine what's surfaced, held, or asked and how.
StateProtocol
Not a Drill1 item. Nothing asked. System acts.
Day Zero3 items max. One ask. Backlog held.
Drift DetectedPattern surfaced. Intervention offered.
Daily MgmtFull queue. Reasoning shown. You choose.
StellerComplete landscape. Strategic layer unlocked.
Implication
Response is different for each user depending on their state and the level of agency they have in their life.
State-Aware Operations
Adaptive Understanding
One-size-fits-who?
systems are
design malpractice.
Echo is a state-aware operating model that adapts what it shows you and how based on what it believes you can actually handle.
Digital Operations
Echo
Artifacts
Discovery, Documented
Harvard Business School
Spring 2026
Digital Operations 3 artifacts
Data Protocol
Architecture
Defines the inputs, logic, and data flow that drives the state-aware operating model.
Open →
State-Aware Operations
Deck
Explaining Echo's underlying operating model.
Open →
Adaptive Understanding
Prototype
Demonstrates how the system will transition based on the client, their context, and current capacity.
Open →
Entrepreneurial Strategy 3 artifacts
Design Against Collapse
Brief
How might we create living infrastructure that scaffolds your life when every other system has nothing left to give?
Open →
The Living Loop
Behavior
Maps the behavioral cycle that underpins the system's state machine that shifts based on users.
Open →
Client Intake
Concept
Onboarding the Day Zero user who is an avoidant, high-functioning ADHDer, who to restore control.
Open →
Navigating Your Worth 3 artifacts
Mapping My Product Process
Behavior
How I think about building products, from raw signal to structured output; tracing decisions and handoffs.
Open →
Hiring a Synthetic Team
Strategy
As a solofounder, I need an A1 innovation product team that can help me take Echo from zero to one on my own.
Open →
Product Refinement
Workflow
Upload your materials and let us handle the intake so your agents don't have to guess what they're working with.
Open →
Scaling Tech Ventures 1 artifact
After Intelligence
Whitepaper
Delight Didn't Die. It Adapted.
Open →
Roadmap
Four things to focus on.
01 Done
Client Intake
Understand clients and their particular patterns, triggers, and breaking points
Data integration, data processing, normalization, triage, classifying, scoring, and surfacing the right intervention for the Day Zero user
View Concept →
02 Done
Adaptive Understanding
Visualizing the state-aware operating model that powers our backend
Prescribes the right next step based on inferred client context, patterns, state, capacity, and capabilities
View Prototype →
03 Dev
Private Pilot
Launch the first version of Project Echo to test the product's value with prospective users and interest from potential clients
Dynamic waitlist that invites users who best suit our strategy and roadmap. Supports Google workspace users with 10 accounts or less
In progress
04 Next
AI Native
Establish the operating framework that allows me to safely and comfortably build and scale as a solopreneur
How might we build out the right synthetic team to help me design, build, manage, and monitor this application on my own?
Hiring Plan →