The 'Diagnose with Data, Treat with Design' Framework
by Julie Zhuo • Co-founder at Sundial at Sundial
Former VP of Product Design at Facebook (Meta), where she worked for over 14 years scaling the team from a handful to hundreds. Author of the best-selling book 'The Making of a Manager'. Currently building Sundial, an AI-powered product analytics platform.
🎙️ Episode Context
Julie Zhuo discusses the evolution of product management and design in the AI era, advocating for a shift from specialized roles to a 'Builder' mindset. She explores how to balance data intuition with creative design, manages the psychology of rapid change using the 'Willow Tree' metaphor, and shares timeless leadership advice on feedback and self-management.
Problem It Solves
Resolves the conflict between data-driven decision making and creative product intuition, preventing teams from blindly following metrics or ignoring reality.
Framework Overview
Data should be used to establish the 'observability' of a business—understanding what is actually happening (diagnosing). However, data cannot dictate the solution; that requires creative empathy and design thinking (treatment).
🧠 Framework Structure
Data reflects reality: Use metrics to...
Diagnosis vs. Treatment: Use quantita...
Avoid False Precision: Acknowledging ...
New Context, New Metrics: As technolo...
When to Use
When product teams are stuck in 'analysis paralysis' or when designers resist data because they feel it stifles creativity.
Common Mistakes
Expecting data to tell you exactly what feature to build next, or ignoring data when it contradicts your 'story' of the product's success.
Real World Example
Julie mentions how rapidly growing companies often run on 'vibes' until growth slows. At that point, they must implement data logging to diagnose the root cause (the 'why'), but the solution to re-ignite growth requires design intervention.
You want to diagnose with data and treat with design. Data is not a tool that's going to tell you what you should build.
— Julie Zhuo