When you become head of design, the job changes in a way nobody explains well. You stop being judged on the work you make and start being judged on the system that makes it. Most of the frameworks available for that job are borrowed from general management, with “design” added to the front. They tell you to hire well, run good process and align with the business. All true, and none of it tells you what is specific about leading designers.
I think about the job in four parts: people, practice, product and profit, in that order. The order is deliberate, and I’ll come back to why.
People
People covers hiring, growth and the environment the team works in. Every leadership framework has this pillar, so it’s easy to treat as the obligatory one. For a design leader, it has a sharper meaning: scaling judgment.
A design team runs on taste and judgment, and those don’t scale by default. The natural path for a senior designer who becomes a leader is to become the best designer on the team and the final word on every decision. That works with four or five designers, when you can still see every piece of work yourself. Past eight or so, it makes you the bottleneck, and your team learns to wait for your opinion instead of forming their own.
The goal is a team that makes the call I would make, without me in the room. That means hiring people with real taste and judgment, giving them full context on the business and the customer, and explaining my reasoning every time I give feedback, so they learn how I think, not just what I decided.
How I’d know it’s working: we hire people with said taste and judgment, they are able ramp and get to making calls on their own quickly, and fewer decisions come to me each quarter.
Practice
Practice is how we make the work and how we judge it. It’s the craft, the quality bar, and the process and execution that make both reliable at speed.
The most important thing in this pillar is that a quality bar only counts if someone can say what it is. Every design team says it cares about quality. Very few can tell you what “good enough to ship” means for a given piece of work. Practice is where that gets defined concretely: in how crits run, when work gets reviewed, how feedback is labeled, and what has to be true before something moves forward.
Practice also includes the infrastructure the craft runs on. A design system and the tooling that connects design to production belong here. So does the habit of making ideas real with prototypes and working builds instead of describing them in slides. The closer designers work to the real medium, the less gets lost between the file and what customers use.
Execution lives here too. A design org earns trust by delivering what it committed to, when it said it would. Brilliant work that arrives late, or arrives in a different shape than the team planned for, costs more credibility than it earns.
How I’d know it’s working: there’s a written quality bar people actually reference, a predictable review cadence, a design system that teams adopt willingly, and commitments that land on time.
Product
Once the people and the practice are in place, the next question is whether the product holds together. Product means owning the experience end to end, at every altitude, from the full customer journey down to a single interaction.
The failure mode this pillar exists to prevent is what I’d call local optimization. Every team ships a good screen, every feature makes sense on its own, and the product still feels like five products stitched together. No single team caused it, and no single team can fix it. The most senior designer is often the only person whose job is to see the whole.
In practice, that means keeping an articulated picture of the end-to-end experience that the company can see and steer by: where customers start, where they get stuck, how the pieces connect and where they don’t. I should be able to explain that journey at the highest level and defend any individual screen inside it. If I can only do one of those, I’m either a strategist without craft or a craftsperson without a view of the whole.
How I’d know it’s working: leadership uses the experience map to make decisions, and the number of seams customers hit between product areas goes down.
Profit
Profit is where the chain pays off, and it has two halves.
The first half is the bet: building the right things at the right time for the right people. That’s strategy, and it belongs under Profit because “right” means right for the business, not just well designed. A beautiful solution to a problem customers don’t pay to solve is a cost.
The second half is the result: customers actually use what we ship. A product is useful, usable and desirable, but none of that counts until it’s used. Usage is the link between design and revenue. When adoption and engagement rise, retention and net dollar retention follow, and in B2B software those are the numbers that matter.
One caution. I don’t claim ARR or NDR as design’s number, because attribution is a fight design leaders lose. I claim what design can directly move: activation, feature adoption, time-to-value, task success and support volume. Then I show how those feed retention and expansion. It’s a more honest story, and a more credible one in an executive room.
How I’d know it’s working: the leading indicators design owns move in the right direction, and I can draw a clear line from them to the revenue metrics the business tracks.
Why the order matters
I think of the four like a relay race. Each leg hands something to the next. People build the practice. The practice is what makes the product good. A good product gets used, and when it gets used, the business feels it. Drop the baton anywhere and it doesn’t matter how fast everyone else runs.
That’s why I find it more useful as a diagnosis than a scorecard. When something feels off in my org, I don’t ask how we’re doing on each pillar. I ask where the baton got dropped.
If the work is inconsistent from one designer to the next, that’s almost always practice. We don’t share a definition of good, or I’m seeing the work too late to change it. If every piece is strong on its own but the product still feels like it was built by five different companies, that’s product. Nobody owns the seams. If the product hangs together and customers still aren’t using it, that’s profit. We either bet on the wrong problem or never checked whether the bet paid off. And if every fix runs through me, that’s people. I’ve built a team that waits for me instead of deciding.
The answer is rarely to work harder on all four at once. It’s to find the one link that broke and start there.
What this means for the role
The head of design is usually the only person in the company responsible for all four links at once. Product managers own pieces of Product and Profit. Engineering leaders own pieces of Practice. HR partners help with People. The design leader is the one who has to hold the whole chain and explain how it connects to the business.
That’s the job. You should be one of the best designers in the room, but the real work is showing, with evidence, how the team you built turns into revenue the company can count on.