Capability is a word that gets used a lot in design circles and is defined rarely.
It sits at the centre of everything Gale & Co. does, so it's worth being precise about what it actually means, and why the distinction matters more than most organisations realise.

What capability actually means

Capability isn't a design concept. It's a business one.

In its broadest sense, organisational capability is the ability of a business to deploy its resources: its people, its processes, its knowledge, in a way that consistently produces outcomes. Not occasionally. Not when conditions are perfect. Consistently.

The most capable organisations aren't the ones with the most talented individuals. They're the ones where talent is supported by the right structure, led with clarity, and pointed at the right problems. Where knowledge doesn't live in one person's head. Where the function performs even when key people leave, scale, or change.

Capability is what makes performance repeatable. And that's true whether you're talking about a sales function, an engineering team, or a design function.

Now apply that to design

A design team is a group of talented people doing design work. They ship things. They hit deadlines. On paper, they look like exactly what the business asked for.

A design capability is something more fundamental. It's the conditions that allow design to drive real outcomes: the right people, in the right structure, with the right leadership, working on the right problems. It's what determines whether design shapes decisions or simply executes them.

You can have a full design team and no real capability, and it happens more often than anyone admits.

How to tell which one you have

The signs are rarely dramatic. They're quiet, gradual, and easy to explain away.

Designers are consistently brought in too late, after the important decisions have already been made. Design is treated as a production function rather than a thinking one. Quality is judged on aesthetics rather than outcomes. The team grows in headcount but not in influence.

There's often a capable person at the top holding everything together through effort and relationships. When they leave, and eventually they do, the function struggles to maintain what they built. Because what they built lived in them, not in the structure.

Ask yourself honestly: If your Head of Design left tomorrow, what would remain?

If the answer is "not much", you have a team. Not a capability.

The real cost of getting this wrong

It isn't measured in bad hires or failed projects. It's measured in what doesn't get built.

Products that never quite land. Research that nobody acts on. Creative work that gets watered down before it reaches the customer. A function that's present in every meeting but absent from every important decision.

The organisations that get design capability right don't just produce better work. They move faster, make better decisions earlier, and build things their customers actually want. Design stops being a cost centre and starts behaving like what it actually is… a commercial multiplier.

What building capability actually requires

It starts before the first hire.

Capability requires clarity about what the function is actually there to do, not just what roles it needs to fill. Too many organisations approach this the wrong way around: they identify a gap, open a headcount, and hope the right person will bring the answer with them. Sometimes they do. More often, they inherit the same conditions that created the gap.

It requires leadership that knows how to position design inside the organisation, earning influence rather than waiting for it to be granted, and connecting the work to commercial outcomes that the rest of the business actually cares about.

And it requires the right structure around the people, not just the right people in the structure. A brilliant designer inside a broken operating model will either adapt to it or leave. Neither outcome serves the business.

Most organisations only start asking the hard questions after something isn't working. The ones that ask them first (what does good look like here in two years? What needs to be true about this team for it to have real influence?) build something that lasts.

The difference between a design team and a design capability isn't talent. It's intention.

And intention, it turns out, is something you have to build for, not hire for.

At Gale & Co., we work with organisations before, during, and after the hire , helping build the conditions that let design do what it's actually capable of.

If this resonates, get in touch.