lev-os The Making of a Manager
Overview
The Making of a Manager, written by Julie Zhuo from her experience going from Facebook's first intern to VP of Product Design, is a management framework built on three pillars: Purpose (what success looks like), People (building a great team), and Process (how the team works together). The critical insight: management is a specific skill set learnable through practice, not an innate talent or reward for being a good individual contributor. Zhuo's breakthrough is demystifying management for first-timers by articulating the mindset shift required - from "I create great work" to "I enable others to create great work" - and providing concrete practices for the Purpose/People/Process framework. Unlike technical management books, this emphasizes the human and design-thinking aspects of leadership.
When to Use
- Transitioning from individual contributor to first-time manager
- Evaluating if you're succeeding as a manager (Purpose/People/Process diagnostic)
- Building or rebuilding team culture and operating rhythm
- Struggling with impostor syndrome as new manager
- Designing team processes that enable rather than constrain
- Hiring and developing team members systematically
- Understanding what your manager should be doing for you
The Process
Step 1: Define Purpose - Understand Your Job
Clarify what success looks like for your team. Half your evaluation is team's results (shipping valuable, well-crafted work); half is team's strength and satisfaction. Your job is not doing the work yourself; it's multiplying the output and impact of others. Define clear goals: what outcomes does your team need to deliver? Why does it matter? Align team around shared purpose. Example: Design team's purpose is "Create products that are valuable (solve real problems), easy to use (intuitive), and well-crafted (delightful)" - measured by user metrics, usability scores, and team engagement.
Step 2: Build Trust Relationships (People Foundation)
Invest in 1-on-1s as sacred time to build trust, not just status updates. Listen more than talk. Understand each person's motivations, strengths, career aspirations, and challenges. Show vulnerability - admit your own struggles and uncertainties. Create psychological safety where people can share bad news or mistakes without fear. Trust is the foundation for everything else. Example: Weekly 30-min 1-on-1s where manager asks "What's on your mind? How can I support you better? What are you learning?" Not "Give me project status updates."
Step 3: Hire for People Who Will Be Great (Raise the Bar)
Define what "great" looks like for the role specifically. Create structured interview process testing for those attributes. During interviews, dig deep on past behavior, not hypotheticals. Assess for both skills (can they do the work?) and values fit (will they thrive here?). Set high bar - only hire people you believe will be in top half of team. Reject "good enough" hires who'll drag average down. Example: For designer role, test for craft skills (portfolio), collaboration (how they work with engineers/PMs), and growth mindset (examples of learning from failure).
Step 4: Develop People Through Feedback and Growth
Give frequent, specific feedback on both strengths and areas for growth. Frame feedback around helping person achieve THEIR goals, not just yours. Create opportunities for stretch assignments that develop new skills. Discuss career aspirations and create growth plans. Celebrate progress. Remove from team people who aren't succeeding after coaching - keeping low performers hurts team and the person. Example: "You want to get better at strategic thinking [their goal]. Here's a stretch project leading Q4 planning [opportunity]. I'll coach you through it [support]."
Step 5: Design Process That Enables Great Work
Establish team rituals and processes that create clarity and efficiency, not bureaucracy. Key processes: how decisions get made, how feedback is given, how work gets prioritized, how meetings are run, how information flows. Continuously improve processes based on team feedback. Avoid processes that optimize for your comfort at expense of team productivity. Example: Design critique process with clear purpose (feedback for improvement, not approval), role clarity (designer shares context, team gives feedback), and time limits (30 min).
Step 6: Run Effective Meetings (Process Execution)
Ensure every meeting has clear purpose and desired outcome. Decide if meeting is for information sharing (send email instead?), decision-making (who decides?), or brainstorming (how to ensure good ideas emerge?). Invite only necessary people. End with clear action items and owners. Regularly audit meetings - which should continue, which should stop? Example: Weekly team meeting = 15 min announcements, 30 min deep-dive on one topic, 15 min retrospective on how team is working together.
Step 7: Make Good Decisions (Balancing Purpose)
For important decisions, gather diverse perspectives (avoid echo chamber). Understand decision type: one-way doors (hard to reverse, go slow) vs. two-way doors (reversible, go fast). Separate decision-making from consensus-building - get input, but clarify who actually decides. Communicate decisions with reasoning. Track outcomes to improve decision-making over time. Example: Choosing design system = one-way door (years of impact), involves engineers/designers/PMs. Changing button color = two-way door, designer decides quickly.
Step 8: Measure What Matters (Purpose + People)
Define clear metrics for team success aligned to purpose. Track both outcomes (what we shipped, impact on users) and health (team satisfaction, retention, growth). Regularly review metrics with team. Use metrics to identify what's working and what needs to change. Avoid vanity metrics that look good but don't drive real impact. Example: Product team tracks: feature adoption (outcome), user satisfaction scores (outcome), team engagement survey (health), skill development progress (health).
Example
Julie Zhuo's Early Manager Story: At 25, promoted to manage 4 designers. First months were disaster - tried to do design work herself AND manage, failed at both. Realized job was different: not "make great designs" but "help team make great designs." Shifted to Purpose (define what great design means), People (hire talented designers, build trust through 1-on-1s, give feedback), Process (establish critique process, clear decision framework). One direct report struggling with stakeholder management - Zhuo shadowed their meetings, gave specific feedback, created opportunities to practice with safer stakeholders, celebrated progress. Over time, team grew from 4 to 100+ designers. Key learning: management is about multiplying others' impact, not maximizing your own output.
Anti-Patterns
Managing like you're still an IC: Doing the work yourself instead of enabling others to do it. Jumping in to fix things rather than coaching team to solve problems. Fix: Shift from maker to multiplier mindset. Success = team's output, not your individual output.
Purpose without clarity: Vague goals like "ship great products" that don't help team understand priorities or tradeoffs. Fix: Define specific, measurable outcomes. Great design = valuable + usable + well-crafted with clear metrics for each.
Process for process's sake: Implementing meetings, approvals, rituals that create bureaucracy without value. Processes that optimize for manager's control vs. team's productivity. Fix: Regularly audit processes. Keep only what clearly serves team effectiveness.
Avoiding difficult people decisions: Keeping low performers because firing is hard, dragging down team morale and performance. Fix: Coach first, but if coaching doesn't work, help person transition out. Protecting the team's standard of excellence is your job.
Treating all direct reports the same: One-size-fits-all management ignoring that people have different motivations, working styles, career goals, and needs. Fix: Customize your approach per person based on 1-on-1 conversations understanding their specific situation.
Related Frameworks
The Manager's Path (Camille Fournier): Career ladder framework for engineering management. Making of a Manager focuses on management fundamentals; Manager's Path maps progression across levels.
High Output Management (Andy Grove): Management mechanics (1-on-1s, meetings, performance). Grove provides systems and processes; Zhuo provides purpose and people focus.
Radical Candor (Kim Scott): Feedback framework. Complements Making of a Manager's "People" pillar with specific techniques for caring personally and challenging directly.
Measure What Matters (John Doerr): OKR framework for goal-setting. Operationalizes Making of a Manager's "Purpose" pillar with structured approach to defining and tracking objectives.
The Five Dysfunctions of a Team (Lencioni): Team health diagnostic. Complements Making of a Manager's focus on building trust, healthy conflict, and team satisfaction.