The most significant change when moving into design leadership isn't tactical; it's a shift in identity. As a senior practitioner, your value is tied to your craft, your ability to solve complex design problems, and the quality of your direct output, like a polished Figma file. Your success is your work.

When you become a leader, this equation flips. Your primary output is no longer your own design work. It's the performance, clarity, and growth of your team. You transition from being craft-centric to people-centric. The goal is no longer to be the best designer in the room, but to create an environment where every designer on your team can do their best work.

This means your measures of success change. Instead of pixel-perfect interfaces, you start measuring success by the team's autonomy, the clarity of their goals, and their ability to solve problems without your direct intervention. It's a move from creating artefacts to creating capabilities.

A common mistake for new leaders is adopting a single management style, often the one that felt most comfortable to them as an individual contributor. Effective leadership, however, is adaptive. It changes based on the person and the situation. This is the core idea behind the Situational Leadership II model.

This framework maps leadership behaviour against the development level of a team member for a specific task. It proposes four core leadership styles:

Your role is to correctly diagnose a team member's development level for a given task and apply the right style. Using a 'Directing' style with a senior designer who is fully capable (D4) leads to micromanagement and frustration. Conversely, using a 'Delegating' style with a junior designer who is still learning (D1) is setting them up for failure.

Delegation is one of the hardest skills for new design leaders to master, especially if their career was built on high-quality craft. It can feel like a loss of control. But effective delegation is not abdication; it is a tool for empowerment. To delegate well, you must build trust and provide clarity.

A simple framework for delegation involves answering five questions:

• What: What is the specific outcome you need?
• Who: Who is the right person for this task, considering their skills and development goals?
• Why: Why is this task important? Connect it to the larger project or business goals.
• How: What are the constraints, resources, and definition of 'done'? Provide context, not a step-by-step solution.
• When: What is the deadline, and what are the key check-in points?

This level of clarity empowers your team to own the solution while operating within safe boundaries.

This is also where coaching becomes critical. Coaching is different from mentoring. Mentoring is about sharing your experience and giving advice. Coaching, in contrast, is about helping others find their own answers. It involves asking powerful questions like, "What have you tried so far?" or "What would be the ideal outcome here?" to unlock their own problem-solving skills.

Finally, your role shifts to setting the North Star. Instead of providing solutions, you provide vision. A clear design vision statement acts as a compass for your team, helping them make autonomous decisions that are aligned with the overall strategy. It answers the question, "What future are we trying to build for our users?" It should be inspiring, concise, and something the team can use to evaluate their own work against.

Ready to test your understanding of these new leadership mindsets?

Mastering this mindset shift is the foundation of effective design leadership. It's a continuous process of learning to lead people, not just pixels.