Managing Designers: 1:1s, Career Conversations, Performance (2026)

The 1:1: load-bearing artifact of design management

The 1:1 is the load-bearing artifact of design management. The canonical mechanics drawn from Julie Zhuo's chapter 6 ('Amazing Meetings'), Lara Hogan's Resilient Management chapter 2 ('Stable Ground'), Michael Lopp's Rands in Repose 1:1 patterns ('The Update, The Vent, and The Disaster'), and Bob Baxley's design-management essays:

• Cadence. 30 min weekly with every direct report. Some senior IC designers can sustain bi-weekly 30 min, but the default is weekly. Cancel only when both parties agree the cancellation is appropriate; never cancel because you're 'too busy.'
• Agenda. The report's, not yours. Open with: 'this is your time. What do you want to discuss?' If they say 'nothing,' don't fill the silence with status updates — ask a follow-up question (Hogan's BICEPS frame helps).
• Purpose. The 1:1 is for the report's growth, not your information-gathering. If you find yourself using 1:1s to status-check on projects, you're misusing the artifact. Status updates go in writing or in standups; 1:1 time is for the report's career, growth, blockers, and frustrations.
• Notes. Take notes during the 1:1 (in a private doc) on what was discussed and what action items emerged. Review your notes before the next 1:1. Continuity from week to week is the signal that the 1:1 is working; lack of continuity is the signal that you're treating it as overhead.
• Cancellations. Hogan's framing: cancel a 1:1 only when both parties agree. Never let a 1:1 slip without rescheduling. The team notices.
• Hogan's BICEPS framework. When a designer brings a complaint or frustration, the BICEPS frame helps you diagnose what's underneath. Belonging — does the designer feel they belong on the team? Improvement — are they growing? Choice — do they have agency? Equality — are they treated fairly relative to peers? Predictability — do they have stability and information? Significance — does their work matter? The answer to which of the six is being threatened usually clarifies what action would help.

The feedback equation: Hogan's most-cited single artifact

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. The mechanics:

1. Observation: what did you actually see, in specific terms? 'I noticed in last Thursday's critique that you reframed the feedback for the new designer in your own words.' Avoid: 'You're so collaborative.' Avoid: 'You're always supportive.' The observation has to be specific enough that the designer can match it to a memory.
2. Impact: what was the effect of what you saw? 'It made the feedback land for the new designer; she came up to me afterwards and said the critique was the most useful one she'd had.' Avoid: 'You were great.' The impact has to be specific enough that the designer can recognize the value of what they did.
3. Question or request: what do you want them to do or reflect on? 'Can we talk about how you might do that more often?' or 'I want to recognize this in your perf packet.' The question or request has to be specific enough that the designer knows what action you're inviting.

The equation works for positive feedback (recognition) and for critical feedback (corrective). The canonical mistake new design managers make: skipping the observation, or making the observation vague. 'You did great' and 'you need to communicate more' are both feedback failures because they lack the specificity that makes feedback actionable.

Use the equation for every piece of feedback — positive or negative — for the first 6 months as a new design manager. After 6 months it becomes muscle memory.

Career conversations: the quarterly or semi-annual artifact

Career conversations are different from performance conversations. The mechanics drawn from Julie Zhuo's chapter 5 ('Managing Yourself'), Mia Blume's Design Dept materials on career-conversation patterns, and Hogan's Resilient Management chapter 3 ('Career Conversations'):

1. Cadence. Quarterly or semi-annual, in addition to the weekly 1:1. The career conversation is a longer (60–90 min) deeper conversation about 18–36 month aspirations, growth areas, and the gap between current scope and target scope.
2. Structure. Hogan's three-part structure works well: (1) where do you want to be in 18–36 months — what scope, what role, what kind of work, what kind of team? (2) what gaps exist between your current capability/scope and that target? (3) what specific bets can we make this quarter or this year toward closing those gaps?
3. Document the conversation. Write up the career conversation in shared notes within 24 hours. Re-read the notes before the next career conversation. Track which bets were made, which played out, which didn't.
4. Sponsorship. The design manager's job at career conversations is sponsorship — actively advocating for the designer's growth in calibration meetings, in cross-functional partnership conversations, in hiring-loop assignments. The career conversation is where you commit explicitly to specific sponsorship actions.
5. Honest conversations about ceiling. Some designers want to be staff/principal IC, some want to be design managers, some want to leave for an external opportunity, some are at their natural scope-ceiling for their company. The career conversation is where these honest conversations happen — not at the perf-review meeting where the rating is the focus.

Difficult performance conversations: the canonical hardest situation

Difficult performance conversations are the canonical hardest design-management situation. The failure mode is delaying the conversation by a quarter and watching the team's strong ICs disengage. The mechanics drawn from Zhuo's chapter 4 ('The Art of Feedback'), Hogan's Resilient Management chapter 4 ('Mastering the Art of Disagreement'), Bob Baxley's design-management essays on performance management, and the engineering-management equivalent reading (Larson's 'Useful PiP' essay on lethain.com which applies cross-disciplinary):

1. Don't delay. The single most common failure mode for new design managers: delaying the difficult performance conversation by a quarter. The team notices. The team's strong ICs interview elsewhere. Six months later you have a recovery problem instead of a development opportunity.
2. Use the feedback equation. Observation: 'In the last quarter the design-system roadmap items you owned slipped two of three deadlines.' Impact: 'It means the team's product partners think the design system is unowned.' Request: 'I want to work with you to define what the design-system lead role looks like in writing, with explicit commitments, by next week.'
3. Document the conversation. Write up the conversation in writing within 24 hours. Send a follow-up email recapping what was discussed and what was committed. The written trail is essential if the situation escalates to a formal performance improvement plan or a separation.
4. Structured improvement period. If the situation requires structured improvement, set explicit behavioral targets, weekly 1:1 dedicated to the improvement plan, and a named time horizon (typically 3 months). Larson's 'Useful PiP' essay (cross-disciplinary applicable) is the canonical mechanic.
5. Performance Improvement Plan (PIP) when needed. A properly-scoped PIP either restores someone or lets them exit with dignity. The failure mode is the manager who delays — the team notices and quits around them. Consult HR on the formal PIP process; the HR partner walks you through your company's specific mechanics.
6. The exit conversation. Some performance situations end in separation. The Hogan-and-Zhuo posture: separation should be done with dignity, with explicit acknowledgment of the designer's contributions, and with a clear plan for the transition. The team notices how separations happen; a respectful separation strengthens the team's trust in the manager.