Nobody warns you that becoming a design lead is like being handed the nuclear codes, except instead of world-ending weapons, you’re responsible for a group of highly sensitive creatives who can smell bullshit from three departments away and will passive-aggressively redesign the company logo in Comic Sans if you piss them off.

One day you’re debating border-radius values like your life depends on it. The next, you’re in a meeting trying to explain why Sarah momentarily dissociated during the product meeting — not a breakdown, per se, just her brain trying to process the cognitive dissonance of designing “joyful, intuitive experiences” for a platform built to manage stakeholder outrage, bureaucratic timelines, and the occasional public consultation meltdown.

Welcome to leadership. Population: you, a group of designers with strong opinions about Helvetica, and the growing suspicion that you’re all just highly educated kids playing dress-up in a digital sandbox.

The Lookaftering of Creative Humans

Designers are not normal employees. We’re more like those expensive houseplants that die if you look at them wrong, except we require very specific types of light (natural), water (oat milk lattes), and soil conditions (psychological safety mixed with creative challenge).

We’re also the only department that will spend six hours debating whether a button should be “Submit” or “Send” because we genuinely believe it matters for the user’s emotional journey. Spoiler: it does matter, which is why everyone else thinks we’re insane.

Managing designers means becoming fluent in a language where “I’m fine with either option” actually means “I have very strong feelings about this but don’t want to seem difficult,” and “quick question” is always followed by a 40-minute philosophical discussion about the nature of digital interaction.

The job requires equal parts therapist, ship captain, and hostage negotiator.

The Onboarding Minefield

New designer walks in. They’re bright-eyed, portfolio-fresh, ready to make beautiful things that improve people’s lives. They’ve probably got a favourite design podcast and strong opinions about whether dark mode is for accessibility purposes or just aesthetic preference.

Your mission: get them productive without crushing their soul or turning them into another burnt-out creative who refers to their passion project as “my real work”.

First week, they’re excited about the component library. Second week, they’re asking why there are fourteen different shades of blue. Third week, they’ve discovered the Archived folder where all the murdered features go to die, and they’re starting to ask uncomfortable questions about your discovery processes.

This is the moment. You can either help them understand that design is about working within constraints while still fighting for users, or you can let them discover on their own that half the company thinks designers are just people who make things prettier.

Choose wisely. Their sanity depends on it.

Design Reviews: A Masterclass in Professional Wrestling

Every design review follows the same script:

Act I: Designer presents work, explains thinking, tries to preempt obvious criticism.

Act II: Stakeholders provide “feedback” that ranges from genuinely helpful to “can you make it more like Apple but also completely different?”

Act III: Everyone nods politely while the designer internally calculates how many more years until they can afford to quit and become a ceramics teacher.

The real skill isn’t in presenting designs — it’s in translation. When the CEO says “it needs more personality,” they might mean anything from “add more visual hierarchy” to “I don’t understand why we can’t just copy Stripe’s design system.”

Your job is to decode the feedback, protect your team from the truly crushing comments, and somehow guide the conversation toward something that serves users instead of just stakeholder aesthetics.

The Impossible Balance

Here’s what they don’t tell you about design leadership: you’re simultaneously trying to push your team toward excellence while protecting them from the devastating reality that excellence often doesn’t matter if it doesn’t hit the right metrics.

You want them to care deeply about craft, but not so deeply that they have emotional breakdowns when their perfect user flow gets axed for a feature that increases conversion by 0.3%.

You need them to be user advocates, but also team players who understand that sometimes “user needs” and “business requirements” are about as compatible as oil and water in a NutriBullet set to maximum chaos.

It’s like being a coach for a team that’s playing a sport where the rules change mid-game and the scoreboard is broken, but somehow you still need to help everyone perform at their best while maintaining their love for the game.

Why does anyone do this job?

Most days, design leadership feels like being the person who has to explain why the Titanic shouldn’t aim directly for the iceberg, except the iceberg is Q4 targets and everyone’s already bought their tickets.

But then something magical happens. Your junior designer ships their first major feature and users actually love it. Your mid-level designer leads a cross-functional workshop without spiralling into Slack afterward, synthesises feedback like a boss, and somehow turns a vague product idea into a usable flow — and you realise you’ve accidentally built something that looks suspiciously like a functional team.

These moments don’t happen often. But when they do, you remember why you took this job in the first place: not for the title or the salary bump, but because someone needs to create space for people to do their best work in a world that’s designed to prevent exactly that.

You’re not just managing designers. You’re cultivating the conditions where design can actually matter, where human-centred thinking can survive contact with business reality, where creativity doesn’t get optimised out of existence by efficiency algorithms.

It’s ridiculous. It’s impossible. It’s probably the most fulfilling work I’ve ever done.