What Does Hands-On Design Leadership Actually Mean?

I’m noticing a shift in how companies talk about design leadership.

Across startups, scaleups, and larger product organizations, more companies seem to be looking for hands-on design leaders: founding designers, heads of design, senior managers, and directors who can operate at a strategic level while still materially shaping the work.

Part of that is about scale. Product teams are moving faster, design work is spread across more squads, and systems are expected to carry more of the customer experience. Teams need principles, patterns, reusable components, shared interaction models, and clearer ways of making decisions. Those systems come from leaders who are close enough to the work to see what is repeating, what is breaking, and what needs to become more consistent.

As a designer who also leads teams, this shift feels familiar to me. This is how I have always operated: actively engaged in the work itself, contributing alongside the team to understand it, shape it, and make it better.

I stay close to the work because design leadership requires both a ground-level perspective and a broader product view. That proximity shows up in the quality of the product, the clarity of the design direction, the strength of the patterns, and the growth of the team.

That same closeness also shows up in how the product holds together. I help establish the principles and connective tissue that make an experience feel coherent across squads. I care deeply about making sure customers are heard, user needs are understood, and experience gaps are actively closed. That work requires moving between strategy, systems, product decisions, and the needs underneath the experience.

Some of the most valuable work I do as a design leader is helping the team see a few steps ahead: creating conceptual designs, future-state workflows, prototypes, storyboards, system models, or experience principles that give the work a clearer north star.

That kind of vision makes the work today sharper. When a team can see the direction, it becomes easier to decide what to prioritize, what to simplify, what patterns to create, and which tradeoffs are worth making. I love that part of the work because it connects imagination to execution. It gives the team something to react to, build on, and make better together.

Hands-on design leadership also means working across the organization.

Effective design leaders need to operate up and down the company. That means working with executive leadership to understand business priorities and translate company goals into product direction. It means staying close to product managers, engineering leads, design leads, and squad partners to understand what decisions are being made, where teams are stuck, and where the experience needs stronger direction.

It also means developing designers. Designers need leaders who can help them sharpen their craft, challenge assumptions, and understand how their daily decisions connect to larger product and business outcomes.

That development comes from creating the conditions for better thinking. Sometimes that means giving direct feedback and asking a designer to try a different path. Sometimes it means bringing in interaction pattern examples, facilitating a storyboard exercise, reframing the problem, or helping the team prioritize user needs before jumping into screen design.

My role is to push the work in a way that helps the team see something they could not see yet. Leadership becomes visible in what the team is able to do after we work through the problem together.

This is the translation layer of design leadership: business goals into design direction, customer needs into product decisions, and patterns into coherent experiences.

As products, teams, and systems become more complex, design leadership has to stay connected to the work itself. The measure of that leadership is whether the work gets better, the team gets stronger, and the product becomes more coherent because the leader was involved.