Hiring a Head of Design gets talked about like it's a milestone. The moment the organisation gets serious about design. The hire that will change things.

Sometimes it is.

Sometimes it's the most expensive mistake a business makes.

The difference rarely comes down to the quality of the candidates. It comes down to whether the organisation was clear about what it actually needed before it started looking.

Start with the question most organisations skip

Do you actually need a Head of Design right now?

It sounds like a strange question to ask, but it's the most important one. A Head of Design is a leadership hire. Leadership hires exist to do things that the team can't do without them: set direction, build structure, earn influence, develop people, make the case for design at a level the business will listen to. If those things don't need doing yet, or if the team isn't at a stage where they'd benefit from that kind of leadership, the hire may be premature.

Early-stage companies often need a strong senior practitioner more than they need a leader. Someone who can do the work, establish the standard, and figure out the function as it grows. Giving that person a Head of Design title creates expectations on both sides that the role can't yet deliver on.

At the other end, large organisations with established design functions sometimes hire a Head of Design when what they actually need is a more senior strategic voice: a Director or VP who can operate at a level the current structure doesn't reach. The Head of Design title undersells the scope and attracts the wrong candidates.

Stage and scope make all the difference. Get clear on both before you open the role.

Not all leadership roles are the same

Assuming you do need a Head of Design, the next mistake is treating the role as a generic one. Head of Design is a title, not a job description. What the role actually requires depends entirely on the context it's operating in.

A useful way to think about this is through archetypes. Most Heads of Design lean toward one of these, and the strongest candidates are usually honest about which one they are:

The Practitioner Leader

Still close to the work. Sets the standard through doing as much as directing. Valuable in smaller teams or earlier stage organisations where the quality of output is still being established. The risk: struggles to let go of the craft as the team grows, and can become a bottleneck rather than an enabler.

The Team Builder

Energised by developing people. Thinks about capability, career progression, and how to create the conditions for others to do their best work. Valuable when the team is growing quickly or when retention and development are the priority. The risk: can drift from the work itself, losing credibility with designers who need a leader who understands what they're dealing with.

The Organisational Operator

Skilled at navigating complexity. Earns trust across product, engineering, and business stakeholders. Makes design legible to people who don't speak its language. Valuable in large or politically complex organisations where design is still fighting for its seat at the table. The risk: can prioritise influence over output, producing a design function that is well-regarded but not particularly impactful.

The Visionary

Sets direction and inspires through a clear point of view on where design should go. Valuable when the function needs a change of direction or when the organisation is trying to elevate what design means internally. The risk: can be difficult to work with day-to-day, and often needs a strong operational partner to translate vision into execution.

The Coach

Leads through questions rather than answers. Develops designers by creating space for them to think and decide, rather than telling them what to do. Valuable in mature functions where the team has strong capability but needs support growing into more senior roles. The risk: can feel frustratingly indirect in fast-moving environments where people want clear direction.

Most strong candidates have elements of several of these. The point isn't to find someone who fits one archetype perfectly. It's to be honest about which of these the role most needs, and to weight the assessment accordingly rather than looking for someone who does all of them equally well.

The unicorn problem

Job descriptions for Head of Design roles are frequently a wishlist. Strategic and hands-on. Visionary and detail-oriented. A strong individual contributor who can also lead, develop, and inspire a team. Someone who can work autonomously but collaborate closely. A natural communicator who can influence at exec level and still run a crit.

Some of this is genuine ambition. Most of it is an unexamined list of everything the previous person wasn't, combined with everything the organisation hopes the next person will be.

The problem with hiring for everything is that you find nobody who meets the bar. Or you find someone who presents as all of these things in an interview process and discovers, three months in, that the role required a very specific set of them that nobody was clear about in advance.

A strong brief forces prioritisation. What does this role most need to do in the first twelve months? What's the single most important thing the incoming Head of Design has to get right? What can be developed over time, and what needs to be present from day one?

Answer those questions honestly and the job description becomes a tool for finding the right person, rather than a document that describes nobody.

What to actually assess

Once the brief is clear, the assessment needs to match it. The standard design leadership hiring process, portfolio review, competency interview, stakeholder presentation, rarely surfaces what matters most at this level.

At Head of Design level, the work is no longer the primary evidence. What matters is how they think about building a function, how they've navigated the organisational dynamics that determine whether design has influence or just presence, and whether they've developed people who went on to do significant things.

Ask about a design function they built or changed, not just the work that came out of it. Ask how they've handled a situation where design was being systematically undervalued. Ask about a person they developed and where that person is now. Ask about a decision they got wrong and what it taught them.

And ask, directly, which of the archetypes above they most identify with, and which they find hardest. The self-awareness in the answer will tell you as much as the answer itself.

One more thing

The Head of Design hire doesn't succeed or fail on the quality of the candidate alone. It succeeds or fails based on whether the organisation was ready for them.

That means being honest, before the hire, about what the incoming leader is walking into. What's broken? What are the constraints? What influence will they actually have and over what? What support will they get and from whom?

A strong candidate will ask all of this. The ones worth hiring always do. And an organisation that can answer honestly, that has done the thinking before the process begins, will attract a better calibre of leader and set them up to actually succeed.

The Head of Design hire changes things. But only if you're clear about what needs to change before you start looking.

At Gale & Co., placing design leaders is some of the most consequential work we do. If you're thinking about a Head of Design hire and want to think through the brief before you open the role, get in touch.