Design Manager vs Individual Contributor Promotion Criteria

The most damaging misconception design leaders bring into promotion decisions is that management is the next rung up from senior IC work. Design managers and individual contributors sit on parallel tracks with fundamentally different criteria. One is measured by the quality and scope of personal craft, the other by the growth and output of a team. Understanding both sets of criteria is what lets design leaders make the fork intentional rather than accidental.

Why the IC/manager fork in design is a structural split, not a seniority ladder

An individual contributor creates value through their own work. Designs shipped, research proven, problems solved directly. A manager creates value through other people: hiring, coaching, performance, team strategy. Neither is a promotion of the other, and at companies with mature career ladders senior ICs reach the same pay and influence as senior managers without ever owning headcount.

The Harmny designer career ladder maps this split visually. On the IC side, the path runs Designer I through Designer II, Senior Designer, Lead Designer, and then Staff or Principal Designer. On the management side, it runs Design Manager through Senior Design Manager, Director of Design, and VP Design. These are two distinct sequences, not one sequence with a management section bolted on top.

The fork happens at a specific moment: around the Lead Designer level. The path is shared until that point, which is why the misconception takes root so easily. A designer spends years climbing one ladder, then watches peers step onto what looks like a higher rung. But scope of influence and organizational visibility are not the same thing as seniority. Staff and Principal Designers shape product vision and are recognized experts inside and outside the company. That is a different kind of power, not a lesser one.

What the IC track actually measures at each level, from Designer I through Staff/Principal

IC promotion criteria follow a consistent logic. Each level expands the scope of craft ownership and the independence with which that scope is executed. It is not just about getting better at design. It is about the size of the problem you can own without supervision.

Designer II, at two to four years of experience, is where independence first becomes the measure. The designer works end-to-end through full feature flows without oversight. They contribute back to the design system so the next designer doesn't rebuild what they built. And they partner directly with engineers instead of working through a lead. Reliability and craft carry the IC1 to IC2 promotion.

Senior Designer, at four to seven years, shifts the measure to ownership. The designer now owns design quality for a full product area or major user journey. They run user research rather than waiting on a dedicated researcher. They mentor IC1 and IC2 designers, and they contribute to cross-platform consistency. The IC2 to IC3 leap is about independence and cross-functional ownership.

Lead Designer, at six to nine years, is where the scope becomes organizational. This level sets design standards, leads design reviews, and has significant influence on roadmap. The quality bar they raise now spans multiple teams. IC3 to IC4 requires demonstrated versatility across products and strategic contribution, and this is also the fork level, the point where the IC path and the management path formally separate.

Staff or Principal Designer, at nine plus years, operates at company-wide design strategy scope. They own the design system, shape product vision through design work itself, and are recognized experts internally and externally. IC4 to IC5 requires that company-wide scope and external recognition. The behavioral evidence must come before the title, not after. Promotion is recognition that someone is already operating at the next level consistently, not occasionally. What IC leadership looks like without headcount is worth naming directly. Mentoring others, aligning teams around a design standard, and resolving conflicts between competing approaches: all of it happens without owning a single performance review.

What the management track actually measures at each level, from Design Manager through VP of Design

Management promotion criteria shift the unit of measurement entirely. The question is no longer how good the individual's design work is. It is how well the team under their ownership grows, ships, and holds together.

At M1, a Design Manager leads a team of three to six designers, owns quality for that team, and still contributes IC work. The key differentiator is managing designers' performance and development. Where IC3 is measured by research ownership and product area quality, M1 is measured by how well the designers under them are growing and shipping. The manager's own design artifacts are not the point.

What separates M1 from M2 is not just headcount. It is the move from managing ICs to managing other managers, a qualitatively different skill set involving organizational design and culture ownership. The skills that compound on the management track are people judgment, organizational design, narrative writing, and staying calm under pressure, all largely distinct from the skills that compound on the IC track.

Director of Design, at M3, owns the entire design org and shapes company design philosophy. They partner with the CPO and product leadership, and their accountability is org-wide, not team-wide. VP of Design, at M4, owns the design and research org together, with company-level accountability for design quality and the design org itself.

The key structural difference in how management promotions are evaluated is that they depend heavily on team performance, organizational needs, and business results. These are fuzzier signals than IC deliverables, and they sit less within the individual's direct control. A manager can do everything right and still lose a promotion because the team missed a quarter.

The four competency pillars that both tracks share, and how they diverge in practice

Shared competency language creates a false impression of interchangeability. The same word, leadership, mentorship, quality, measures different behaviors on each track. Thea Betts's career framework names four pillars: People, Product, Leadership, and Process. Each one means something different depending on which path you are on.

People is about empathy and communication. On the IC track, those are used to collaborate with engineers, PMs, and users. On the management track, the same skills are used in 1:1s, performance conversations, and hiring decisions. The surface is identical. The behavior is not.

Product is the clearest split. On the IC track, it means design craft, methodology, visual quality, and deliverable precision. On the management track, it means product strategy input, design culture ownership, and quality owned through others' work. A manager's product pillar is evaluated through the work their team ships, not through files they personally opened.

Leadership on the IC track runs through technical authority: setting standards, running design reviews, mentoring without reporting lines. On the management track, it runs through people decisions, org structure, and cross-functional influence with headcount accountability. Process follows the same pattern. ICs operate within and contribute to established processes. Managers own operational processes such as hiring, onboarding, performance cycles, and design rituals.

The critical failure mode this creates is confusing performance with potential. A star IC can be a low-potential manager. Using IC performance as a proxy for management potential promotes the wrong people and misses the right ones. Thea Betts makes the point directly: leadership is available on both tracks. It is not a position but a choice to lead an initiative, a project, or people. One might argue that the real mistake is treating that choice as a promotion, when it is a direction.

Why calibration sessions systematically get promotion decisions wrong for both tracks

Knowing the criteria is not the same as applying them consistently. Calibration sessions most often default to advocacy and narrative rather than structured evidence. The criteria exist, but they don't govern the decision.

Standards drift across teams. The same rating, exceeds expectations, can reflect genuinely exceptional impact on one team and simply adequate work on another. That produces promotion gaps that have nothing to do with actual performance. Consider two managers, each leading six people who did comparable work. One rates five of them exceeds expectations. The other rates none that high. The promotion gap becomes visible only when both show evidence against the same rubric in the same room.

Why exactly does this happen? Most calibration sessions run on memory and narrative. When comp history, tenure, and equity data aren't visible in the room, the conversation rewards proximity and visibility rather than output. The most articulate advocate wins, not the most deserving candidate.

The performance-as-potential failure is especially destructive at the IC-to-management fork. Promoting the strongest Senior Designer into Design Manager because they are an excellent designer, not because they show evidence of the coaching, performance, or hiring behaviors the M1 role requires, damages both tracks. The team loses a senior craft practitioner and gains a manager who was never evaluated for the job.

How to build a promotion framework that holds up across both tracks

A promotion framework that works across both tracks must make the criteria for each track explicit, separate, and reviewable against structured evidence. Not a single rubric applied to everyone. The foundational principle is that the behavioral evidence must come before the title, not after. The framework's job is to make that evidence visible and comparable. A functioning IC promotion framework tracks technical complexity of work owned, scope of ownership relative to level expectations, cross-functional partnerships initiated, mentorship behaviors demonstrated rather than just claimed, and research or standards contributions that outlast the individual project.

A functioning management promotion framework tracks team health indicators: designer retention, growth velocity of reports, quality of hiring decisions made. It also tracks organizational contributions like culture ownership and cross-functional influence above the team level. IC promotion criteria are more standardized and observable than management criteria precisely because they are rooted in scope of work and demonstrated output. That is the same principle Lantern applies when it evaluates candidates against evidence of actual work rather than credentials or titles.

At the fork specifically, where a Lead Designer chooses between Staff or Principal and Design Manager, require separate evidence packages. Craft-track candidates demonstrate cross-team quality impact. Management-track candidates demonstrate coaching, performance management, and team-building behaviors accumulated before the promotion, not projected after it.

Calibration discipline is the hard part. Run every promotion conversation against the level-specific rubric for the track the person is on. Make comp history, tenure, and scope data visible in the room so the conversation is grounded in evidence rather than advocacy. Management promotion criteria are harder to standardize because they hinge on relationship, judgment, and org maturity, qualities that resist template rubrics and reward the kind of calibrated evaluation that happens when a leader has spent time explicitly defining what exceptional leadership looks like inside their specific company context. Lantern's hiring process reflects that same discipline: understanding what exceptional looks like at each track, pressure-testing that definition against the real talent market, and evaluating candidates against evidence rather than titles.

Just as Lantern learns what exceptional looks like at a company before evaluating candidates, a design org must calibrate its own definition of craft excellence and leadership at each level before promotion decisions make sense. A template career ladder is only useful if it reflects your specific beliefs about what IC mastery and management impact really mean. Design leaders who operate both tracks with explicit, separate criteria make the fork intentional rather than accidental, and that is the difference between a promotion system that compounds talent and one that quietly loses it.