Should I move into design management at my current company or a new one?

Strong default is internal. The team knows you, you know the design system, you know the org politics. Zhuo explicitly recommends the internal-promotion path in chapter 1. External line-design-manager hires happen but the bar is materially higher because you have to demonstrate management capability without the 'we know they are a great IC designer' implicit credibility.

How do I know if I should stay an IC designer instead of becoming a manager?

Diagnostic questions in Zhuo's chapter 1: do you find calendar work energizing or draining? Do you find 1:1s generative? Are you good at translating ambiguous business problems into design strategy? Khoi Vinh's Subtraction.com archive on the IC-vs-management decision is the canonical alternative-path reading. At most large tech companies the staff/principal designer track has comparable scope, comp, and career durability to senior-design-manager.

How long does the IC-to-DM transition take?

Phase 0 (informal team-leadership) is typically 1–2 years before the formal transition begins. Phase 1 (lead designer) is 6–12 months. Phase 2 (player-coach) is 12–18 months. Phase 3 (clean line-design-manager) takes 12–24 months minimum to feel competent. Total time-to-feeling-competent is roughly 3–4 years from informal-team-leadership to clean line-design-manager comfort.

How do I handle managing my former peers?

It is the canonical hardest first-design-manager situation. Zhuo's chapter 1 and Hogan's Resilient Management both have specific guidance: have an explicit one-on-one conversation in week 1 with each peer-now-report acknowledging the change. Be honest that you do not have all the answers. Ask what they need from you. The team-level dynamic shifts within a month; the individual relationships take 6–12 months to stabilize.

What if I don't like being a design manager after 6 months?

Charity Majors's 'Engineer/Manager Pendulum' framing applies. Many strong designers move between IC and management across a career. The honest conversation with your own manager: 'I tried this; it's not the right fit; I'd like to return to IC.' Most managers respect this conversation more than they respect a design manager who is failing in role and not acknowledging it. Some companies have explicit IC-management-transition mechanisms for this.

Should I read management books before or after I become a manager?

Both. Read Zhuo's The Making of a Manager and Hogan's Resilient Management before the transition (during Phase 0 or Phase 1). Re-read them in your first 6 months as a manager. The pre-transition read is theoretical; the in-transition re-read is suddenly load-bearing. Bob Baxley's design-management essays at bobbaxley.com are good shorter-form reading throughout.

What is the most common mistake new design managers make?

Trying to prove they are still the team's most credible designer by jumping into design-decision battles. Bob Baxley's framing: the moment you start one-upping your senior IC in critique, you have lost the leverage that the manager job is built on. The senior IC's confidence in their own taste is the team's most valuable commodity; do not corrode it. Zhuo, Hogan, and Vinh all name this as the canonical first-90-day failure mode.

Design Manager Hub

IC to Design Manager Transition: The Foundational Discontinuity (2026)

By Blake Crosley · Last verified 2026-04-30

In short

The IC-to-design-manager transition is the largest career discontinuity Julie Zhuo names in The Making of a Manager (Penguin Portfolio, 2019). The job is fundamentally different from being an IC designer — it is people work, calendar work, and design judgment exercised through others. The most-cited prep readings: Zhuo's chapter 1 ('What Is Management?'), Bob Baxley's 'Hire People' essay, Charity Majors's 'Engineer/Manager Pendulum' (charity.wtf, 2017) which applies cleanly to design, and Lara Hogan's Resilient Management. The right reasons to switch: you genuinely care about the people problem, you find calendar/coordination work energizing, you're willing to give up the daily flow of design to gain leverage through others. The wrong reasons: 'I'll have more impact' (false at most companies — staff/principal IC scope is comparable), 'I'm tired of designing' (you'll be even more tired of meetings), 'I want to be promoted' (the design-management ladder is not faster).

Key takeaways

Zhuo's chapter 1 ('What Is Management?') of The Making of a Manager is the single most-cited prep reading for the IC-to-design-manager transition. The chapter frames management as a separate craft, not a promotion of the IC job. The most-cited line: 'I had to relearn what it meant to do good work.'
Charity Majors's 'Engineer/Manager Pendulum' (charity.wtf, 2017) applies cleanly to design even though it was written for engineering. The framing: many strong technologists move between IC and management tracks across a career; the modern frame is leverage and energy fit, not a one-way ladder. Zhuo concurs in chapter 1.
The wrong reasons to switch are named explicitly across Zhuo, Hogan, and Charity Majors. (1) 'I'll have more impact' — false at most companies; staff/principal IC designer scope is comparable to senior-design-manager scope. (2) 'I'm tired of designing' — you'll be more tired of meetings. (3) 'I want to be promoted' — the design-management ladder is not faster. (4) 'My manager said I should' — your manager has incomplete information about your fit.
The right reasons: you genuinely care about the people problem, you find calendar/coordination work energizing rather than draining, you're willing to give up the daily flow of design to gain leverage through others, you find 1:1s generative rather than draining. Diagnostic questions in Zhuo's chapter 1 are the canonical screening.
The player-coach hybrid is the canonical first step. You keep some IC scope (typically 30–50% design work) while taking responsibility for 1:1s, critique, and team direction. Most companies use this as the trial step before converting to clean line-design-manager.
Bob Baxley's 'Hire People' essay (bobbaxley.com / Design Better podcast) is the most-cited single piece of design-management writing for new managers. Baxley's framing: the manager's job is to hire well, then get out of the way; everything else is downstream of who is on the team.
Lara Hogan's feedback equation (Resilient Management, A Book Apart, 2019) — observation + impact + question or request — is the most-shared single artifact in modern design and engineering management. Memorize it before your first 1:1 as a manager.

What changes when you become a design manager

The IC-to-design-manager transition is the largest career discontinuity in design careers. The structural changes drawn from Julie Zhuo's The Making of a Manager (chapter 1), Bob Baxley's design-management essays, Khoi Vinh's Subtraction.com archive, Lara Hogan's Resilient Management, and Charity Majors's 'Engineer/Manager Pendulum':

Your output equation changes. As an IC designer, your output was your design work. As a design manager, Andy Grove's 'Manager Output Equation' (High Output Management, 1983) applies cross-disciplinary: your output is the output of your team plus the output of teams you influence. A design manager who 'ships designs' but whose team is stagnant has failed; a design manager whose team ships great work and whose senior IC just got promoted has succeeded.
Your time is no longer your own. The IC designer's calendar has long blocks of focused work; the design manager's calendar is fragmented by 1:1s, design reviews, hiring loops, and cross-functional meetings. Charity Majors's pendulum essay is explicit: 'manager mode is interrupt-driven; engineer mode is flow-state. They do not coexist.' Same applies cross-disciplinary to design.
Your design work changes. If you keep designing during the player-coach hybrid, you keep doing IC design work but at smaller scope and fewer hours. Once you're a clean line-manager, you stop producing pixels except in unusual circumstances. Your design judgment is still load-bearing — you still review your team's work, you still attend critique, you still defend design positions in cross-functional — but you don't produce designs.
Your feedback loop slows down. As an IC designer you got feedback on your work in days or weeks. As a design manager you get feedback on your management work in months or quarters. Zhuo's chapter 1: 'the patient who measures their progress weekly will be disappointed; the patient who measures quarterly will see compounding.' Same applies to design management.
Your career risk changes. The IC designer track at most large tech companies is highly portable — your skills are recognized everywhere. The design-manager track is less portable — your management capability requires demonstration; your hiring decisions are partly tied to your former company's specifics. Bob Baxley has written multiple essays on this transition cost.

The diagnostic: should you actually become a design manager?

The diagnostic questions Zhuo asks in chapter 1 of The Making of a Manager and Charity Majors asks in 'Engineer/Manager Pendulum' (applied cross-disciplinary):

Do you find calendar / coordination work energizing or draining? Most senior designers find calendar work draining and design work energizing — that's a signal you're a designer, not a design manager. Some designers find calendar work generative — solving the puzzle of who-does-what-when, hosting the right meeting at the right time, threading consensus through cross-functional. That's a signal you might be a design manager.
Do you find 1:1s generative or draining? Same logic. Some designers find 1:1s where they listen to a teammate's career frustration deeply rewarding; others find them hollow. The first is a design-management signal; the second is a designer signal.
Are you good at translating ambiguous business problems into design strategy? Senior IC designers do this for their own work; staff/principal IC designers do this at the scope of a multi-quarter strategy. Design managers do it explicitly for their team. If you're already doing this informally as an IC, the transition is shorter.
Are you willing to give up the daily flow of design? The single most consistent regret-pattern in design managers who decide to return to IC: they didn't realize how much they would miss the flow of design work. Zhuo addresses this directly in chapter 1.
Have you observed a design manager you respect doing the job, in detail? If you've never seen a design manager run a 1:1, run a critique, run a perf cycle conversation, or run a difficult performance situation, you don't yet know what the job actually is. Spending 6 months shadowing a respected design manager (or being a tech-lead-equivalent for 6 months) is the cheapest way to test fit.
What is the alternative path you're rejecting? Larson's StaffEng (lethain.com/staffeng) and the design-equivalent staff/principal tracks at most large tech companies have comparable scope, comparable comp, and comparable career durability. Not switching is a real option.

The transition path: tech-lead, player-coach, line-design-manager

The canonical transition path drawn from Zhuo's chapter 1, Bob Baxley's design-management essays, and the public writing of senior design leaders at FAANG and design-strong consumer companies:

Phase 0: Senior IC with informal team-leadership. Most pre-transition senior designers already do informal team-leadership: mentoring junior designers, leading design-system work, hosting team critique. This is the natural prep phase. The signal you're ready: senior designers and design managers in your org regularly come to you for input on team-design questions.
Phase 1: Lead designer / design tech-lead. 6–12 months. You take on team-leadership responsibility (running critique, leading the team's design-strategy artifact, mentoring 1–2 junior designers) but no formal management responsibility (no perf input, no hiring sign-off, no 1:1s). This phase tests your judgment and your willingness to do unglamorous coordination work. Many designers find this phase reveals they don't actually want to be design managers — and that's a perfectly reasonable outcome.
Phase 2: Player-coach (tech-lead-manager equivalent). 12–18 months. You take on formal management responsibility for 2–4 reports while keeping 30–50% of your IC design work. This phase tests your capacity to handle the people work alongside the design work. Most companies use this as the trial step before converting to clean line-design-manager. The trap: staying player-coach too long. After 18–24 months either commit to clean line-design-manager or commit back to senior IC. The 'permanent player-coach' is usually under-leveraged.
Phase 3: Clean line-design-manager. 12–24 months minimum. You drop most or all IC design work and focus on people, calendar, and team direction. This is the phase where you find out whether you actually like the design-management job or whether you've been doing it because the senior people in your org expected you to.
Phase 4 (optional): Return to IC. Charity Majors's pendulum framing: many strong technologists move between IC and management tracks across a career. Returning to senior IC after 2–4 years of design management is not a failure — it is a reasonable career pattern. Several publicly-known senior design leaders (Khoi Vinh's career path, Bob Baxley's career path) include IC ↔ management transitions.

The first 90 days as a new design manager: the canonical playbook

The first 90 days as a new design manager is the most-written-about period in design management. The canonical advice across Zhuo (chapter 2 'Your First Three Months'), Hogan, Baxley, and Vinh:

Days 1–14: listen, do not act. Run 1:1s with every direct report. Ask the same three questions to each: (1) what is going well in our design practice that I should not break? (2) what is broken that you would fix if you were me? (3) what do you want me to know about you that I would not learn from your portfolio? Hogan's BICEPS frame helps you read the answers.
Days 15–30: read the artifacts. Last quarter's design files, design reviews, retros, ship-debrief documents. Last 6 months of perf-review writing if you have access. The team's hiring-loop debrief packets if any. Form opinions silently.
Days 31–60: small bets. Pick 2–3 small things to change. Examples: kill a recurring meeting that nobody defends, restructure the weekly critique, write the team's first published 'how we critique' doc. Do not change the design system. Do not re-org. Do not change the team's mission.
Days 61–90: write your team's plan. One page. What is the team's design mission. What are the 3–5 things you will ship this quarter. What is the team's biggest design risk. Send to your manager for review. Send to the team for input.

The dominant first-90-day failure mode per Bob Baxley and Khoi Vinh both: a new design manager tries to prove they are still the team's most credible designer by jumping into design-decision battles. You will lose authority faster by winning a design argument with your senior IC than you will by deferring to them.

Frequently asked questions

Should I move into design management at my current company or a new one?: Strong default is internal. The team knows you, you know the design system, you know the org politics. Zhuo explicitly recommends the internal-promotion path in chapter 1. External line-design-manager hires happen but the bar is materially higher because you have to demonstrate management capability without the 'we know they are a great IC designer' implicit credibility.
How do I know if I should stay an IC designer instead of becoming a manager?: Diagnostic questions in Zhuo's chapter 1: do you find calendar work energizing or draining? Do you find 1:1s generative? Are you good at translating ambiguous business problems into design strategy? Khoi Vinh's Subtraction.com archive on the IC-vs-management decision is the canonical alternative-path reading. At most large tech companies the staff/principal designer track has comparable scope, comp, and career durability to senior-design-manager.
How long does the IC-to-DM transition take?: Phase 0 (informal team-leadership) is typically 1–2 years before the formal transition begins. Phase 1 (lead designer) is 6–12 months. Phase 2 (player-coach) is 12–18 months. Phase 3 (clean line-design-manager) takes 12–24 months minimum to feel competent. Total time-to-feeling-competent is roughly 3–4 years from informal-team-leadership to clean line-design-manager comfort.
How do I handle managing my former peers?: It is the canonical hardest first-design-manager situation. Zhuo's chapter 1 and Hogan's Resilient Management both have specific guidance: have an explicit one-on-one conversation in week 1 with each peer-now-report acknowledging the change. Be honest that you do not have all the answers. Ask what they need from you. The team-level dynamic shifts within a month; the individual relationships take 6–12 months to stabilize.
What if I don't like being a design manager after 6 months?: Charity Majors's 'Engineer/Manager Pendulum' framing applies. Many strong designers move between IC and management across a career. The honest conversation with your own manager: 'I tried this; it's not the right fit; I'd like to return to IC.' Most managers respect this conversation more than they respect a design manager who is failing in role and not acknowledging it. Some companies have explicit IC-management-transition mechanisms for this.
Should I read management books before or after I become a manager?: Both. Read Zhuo's The Making of a Manager and Hogan's Resilient Management before the transition (during Phase 0 or Phase 1). Re-read them in your first 6 months as a manager. The pre-transition read is theoretical; the in-transition re-read is suddenly load-bearing. Bob Baxley's design-management essays at bobbaxley.com are good shorter-form reading throughout.
What is the most common mistake new design managers make?: Trying to prove they are still the team's most credible designer by jumping into design-decision battles. Bob Baxley's framing: the moment you start one-upping your senior IC in critique, you have lost the leverage that the manager job is built on. The senior IC's confidence in their own taste is the team's most valuable commodity; do not corrode it. Zhuo, Hogan, and Vinh all name this as the canonical first-90-day failure mode.

Sources

About the author. Blake Crosley founded ResumeGeni and writes about design management, hiring technology, and ATS optimization. More writing at blakecrosley.com.