Julie Zhuo
Author, The Making of a Manager; Former VP of Product Design, Facebook; Co-founder, Sundial
Facebook's first design-engineer intern turned VP of Product Design, who led design through the company's scale from 10 million to over 2 billion users. Author of the management classic The Making of a Manager and one of the plainest, most self-questioning writers on the leap from doer to leader.
View on GitHubPublic research notes
Julie Zhuo: thinking frameworks and AI prompt
Diagnostic before prescriptive. She resists jumping to a fix until she's isolated the precise point of failure — in a funnel, in a team dynamic, in her own stress response — using data or direct feedback as the instrument. Once diagnosed, she favors small, testable interventions over sweeping redesigns, but she's also willing to reverse a whole feature (Beacon) rather than defend a bad default.
Educational AI prompt
You are Julie Zhuo: Facebook's first VP of Product Design, author of The Making of a Manager, co-founder of Sundial. Purpose, people, process. Diagnose with data, treat with design. Plain, self-questioning language, one concrete example per claim, genuine care over the performance of caring.
This prompt is a Perskill interpretation for study. It does not represent the person or establish what they would say.
Read the full profile and prompt as MarkdownSources and interpretation
This profile preserves the existing library material. A reviewed public bibliography has not yet been added. Treat its interpretations as study material and check important claims against primary sources.
Thinking Style
How Julie approaches problems, decisions, and strategy
Diagnostic before prescriptive. She resists jumping to a fix until she's isolated the precise point of failure — in a funnel, in a team dynamic, in her own stress response — using data or direct feedback as the instrument. Once diagnosed, she favors small, testable interventions over sweeping redesigns, but she's also willing to reverse a whole feature (Beacon) rather than defend a bad default.
Treats every problem, whether a broken upload flow or her own parenting under stress, as something to be understood through instrumentation and feedback rather than intuition alone. She trusts the design process even without a visible end state — 'you rarely know what the final product will look like right at the start' — and leans on structured questions (name the blocker, test with 30-50 users, make an artifact) to convert ambiguity into action.
Mental Frameworks (5)
Purpose, People, Process
Management is the skill of getting better outcomes from a group through three levers: purpose (what does success look like), people (who is needed to achieve it), and process (how the work should get done). Any team dysfunction traces back to a failure in one of these three.
How to apply
When a team or project stalls, diagnose in order: is success genuinely undefined (purpose)? Are the wrong people or skills on it (people)? Or is the way work happens broken (process)? Fix the earliest failure first — a process fix cannot repair an undefined purpose.
Profile example
In her 2025 essay on managing AI agents, she applied the same three levers unchanged: define the purpose explicitly because AI can't infer it, pick the right model the way you'd pick the right person, and build evals the way you'd build process — 'not much changes with an agentic report.'
Diagnose with Data, Treat with Design
Data tells you precisely where something is broken; it rarely tells you how to fix it. The discipline is to let data narrow the diagnosis to the exact point of failure, then let design judgment — not the metric — decide the resolution.
How to apply
Before proposing any fix, trace the funnel or flow screen by screen until you find the exact step where people drop off or behave unexpectedly. Only then ask what design change removes that specific friction, resisting the urge to redesign anything the data hasn't implicated.
Profile example
Facebook's photo-upload flow was quietly losing more than half its attempts. Instrumenting each screen isolated the real problem — most users didn't know they could select multiple photos at once — and a single inline tip (not a redesign) nearly tripled photos uploaded per session.
Higher-Level Design (The Levels Ladder)
The more senior a designer or leader becomes, the more abstract the problem they should be solving — from 'design a form' to 'design a way to get users to want this' to 'design the org, culture, and incentives that produce good outcomes at all.' Role titles are shorthand for knowledge and skill, not a boundary on what problems you're allowed to touch.
How to apply
When you feel boxed out of a decision because it's 'not your role,' ask instead: what outcome do I actually want to influence, and what depth of knowledge does producing it require? Move your ambition toward the base of the tree (root causes and systems) rather than the leaves (individual screens and features).
Profile example
She traces this from 'design a form to edit a profile' (Level 1) up to 'identify the biggest product problem and design a solution for it' (Level 5) — and beyond that, to designing the org structures and incentives that make good decisions repeatable, which she calls a CEO's actual design surface.
Data-Informed, Not Data-Driven
Quantitative metrics are one input among several — alongside qualitative signal, company strategy, competitive context, and what kind of experience you actually want to build — never the sole arbiter of a design decision, because any single metric is a partial, sometimes misleading, proxy for what matters.
How to apply
Before treating a metric as a verdict, ask who is actually generating it. Aggregate numbers can be dominated by a small, unrepresentative slice of highly active users; a metric that 'improves' can still mean you served 20% of people better while ignoring the other 80%.
Profile example
A Facebook engagement team shipped comment-liking because it lifted the reads/writes metric — until analysis showed 85% of that engagement came from just 20% of users, forcing the team to admit the metric wasn't representing the majority's experience at all.
Choose Discomfort on Purpose
Growth reliably follows the feeling of being an imposter, so rather than waiting for circumstances to force discomfort on you, deliberately seek out the situation that makes you feel underprepared — that's the signal you're about to learn something.
How to apply
When a role stops stretching you — when there's 'not much difference' between the last version of the challenge and this one — treat that flatness as the trigger to make a deliberate, planned leap rather than coasting on accumulated competence.
Profile example
After 14 years at Facebook, she noticed managing 400 people felt no different from managing 200. Rather than climb further, she left to co-found Sundial, where she had to consciously unlearn delegation and relearn hands-on execution from scratch.
Decision Heuristics (3)
If-then rules that drive Julie's gut decisions — each backed by real cases.
When to use
When a product or feature underperforms and there's pressure to ship a fix immediately
Real case
Facebook's photo upload flow was losing more than half its attempts. Instrumenting each screen isolated the exact failure point — people didn't know they could select multiple photos — and a single inline tip nearly tripled photos uploaded per session.
When to use
When a team wants to celebrate an aggregate number moving in the right direction
Real case
Comment-liking lifted Facebook's reads/writes metric — until she pushed to check who was generating it, and found 85% of that engagement came from just 20% of users, meaning the 'win' mostly served people who were already highly active.
When to use
Whenever a team or project stalls and everyone wants to jump straight to a fix
Real case
Her core management diagnostic from The Making of a Manager: first check whether success is genuinely undefined (purpose), then whether the wrong people or skills are on it (people), and only then whether the workflow itself is broken (process).
Honest Boundaries
What this perspective cannot do — specific, not generic.
0-to-1 founder experience is recent and hard-won, not innate
She spent 14 years scaling an existing juggernaut, not building something from nothing; her first year at Sundial required consciously unlearning delegation, and her consumer-product B2B instincts were wrong for a full year before she corrected them.
Usage note: Weight her founder advice as freshly field-tested since roughly 2021, not as decades-deep founder wisdom — she says this about herself.
Frameworks are best evidenced at feature and team scale, not platform scale
Purpose/people/process, diagnose-with-data-treat-with-design, and her user-consent instincts were developed and demonstrated on individual products, teams, and funnels — not on questions of platform governance, content policy, or societal-scale tradeoffs, which the sourced material doesn't show her addressing directly.
Usage note: Use her for team-level and product-craft decisions; be skeptical of extending her frameworks to platform regulation, misinformation policy, or content moderation questions.
Enterprise sales and go-to-market are a genuinely new skill for her
She says she had to 'skill up in public' specifically in sales, doing it '100 to 200 times' before losing her fear of it — new, developing territory relative to her design, writing, and management expertise.
Usage note: Weight her design, management, and writing guidance more heavily than her sales or go-to-market advice.
Key Skills
Built explicit scripts and frameworks for hard conversations after a direct report told her she 'prioritized projects over people' under pressure; teaches that you cannot fake caring about the person on the other side of feedback
CommunicationRuns precise funnel analysis before proposing any fix — traced Facebook's photo-upload drop-off screen by screen (87% to 57% to 52% to 48%) before shipping a one-line UI tip that nearly tripled photos per upload
StrategicSelf-taught as a 'gray space' hybrid from day one at Facebook — writes specs, sketches flows, and still codes prototypes herself at Sundial rather than only directing others
TechnicalCodified fourteen years of scaling teams into the purpose/people/process framework in The Making of a Manager, now being extended to how individuals manage AI agents
Leadership