Lesson 15: Good Leaders Know When to Step Back

Leadership is often associated with action. Leaders make decisions, provide direction, solve problems, and take responsibility for outcomes. In law firms, those instincts are often reinforced by years of practice. Partners are expected to know the answer, anticipate problems, manage risk, and exercise sound judgment.

But leadership is not always about stepping in. Sometimes, effective leadership requires knowing when to step back.

Developing associates requires more than teaching them what to do. It requires giving them opportunities to think independently, exercise judgment, make decisions, and take ownership of their work. Those opportunities become increasingly important as associates progress because associates cannot develop judgment entirely through observation or instruction. At some point, they have to exercise it.

Stepping back does not mean withdrawing support or lowering expectations. It means recognizing when continued intervention is helping an associate develop—and when it may be preventing them from doing so.

The goal of leadership should not be to create associates who always know when to ask the partner for the answer. It should be to develop associates who increasingly know how to find the answer themselves.

Sometimes the most important thing a leader can do is step back and let someone else step forward.

When Trust Takes Over Instruction

Early in an associate’s career, close guidance is necessary. Partners provide direction, answer questions, review work, and help associates understand not only what to do, but why. But as associates gain experience, the role of the leader should evolve with them. At some point, instruction has to give way to trust in the associate’s developing skills and judgment.

Trust means allowing associates to recommend strategy rather than simply execute it, make decisions within appropriate boundaries, take greater ownership of assignments, and occasionally approach a problem differently than the partner would have.

That last part can be difficult. Experience often gives partners good reason to trust their own judgment. But developing someone else’s judgment requires resisting the instinct to intervene simply because their approach is different.

Different is not always wrong, and leadership does not require your way to become everyone else's way.

There is a meaningful difference between preventing a mistake and preventing an associate from thinking independently. Strong leaders learn to recognize that difference.

You cannot develop independent thinkers by making every decision for them.

Stepping Back Is Not Disengagement

Giving associates greater autonomy does not mean leaving them without support. Strong leaders create the conditions for independence before expecting it.

That means setting clear expectations, defining appropriate boundaries, providing necessary context, and remaining available when guidance is needed. It also means following up. Associates should be expected to raise questions and seek guidance when necessary, but the responsibility for communication should not rest entirely with them. Partners should check in, ask about progress, and create opportunities to identify issues before they become problems.

Stepping back does not remove a leader from the process; it changes the leader’s role within it.

For many partners, that transition can be difficult. When you know how to solve the problem, it is often faster to provide the answer. When you have handled the issue before, it can feel more efficient to dictate the approach. And when you remain responsible for the outcome, stepping in can feel safer than allowing someone else to work through the uncertainty.

But efficiency in the moment can come at the expense of development over time.

Associates need opportunities to wrestle with difficult questions, propose solutions, and see the results of their judgment within appropriate guardrails. A partner can remain engaged without being the first person to solve every problem.

Sometimes the better response to an associate asking, "What should I do?" is not an answer, but another question: "What do you think we should do?"

Stepping back is not an absence of leadership; sometimes, it is leadership expressed through trust.

Ownership Changes the Relationship to the Work

There is a difference between completing an assignment and owning an outcome.

When associates are given meaningful responsibility, their relationship to the work begins to change. They are no longer simply asking what the partner wants done. They begin thinking about what the client needs, what the case requires, what problems may arise, and what should happen next.

Ownership encourages associates to think beyond the immediate assignment. They begin anticipating issues rather than waiting for direction, developing recommendations rather than simply identifying problems, and taking responsibility for moving the work forward.

That transition matters because independence is not developed by removing responsibility from associates. It is developed by gradually giving them more of it.

For partners, creating ownership also requires accepting that an associate may not approach every problem exactly as they would. The measure of development is not whether an associate learns to replicate the partner's judgment. It is whether the associate develops sound judgment of their own.

The goal of developing associates should not be to make them dependent on your judgment. It should be to help them develop their own.

The Bottom Line

Good leadership is not measured by how often your associates need your judgment. It is measured, in part, by how well you help them develop their own.

Knowing when to step in matters. Knowing when to step back matters too.

The goal is not simply to lead the work. It is to develop people who can increasingly lead it themselves.

Weekly Reflection: Where could stepping back create an opportunity for someone else to step forward?