As an engineering leader, it is easy to fall into the trap of thinking your primary job is to tell people what to do. We call it "mentoring." We share our experiences, help engineers avoid our past mistakes, and try to draw a clear map for them.
But as your team scales and your engineers grow, relying only on mentorship becomes a bottleneck. The problem is not that engineers don't want to learn. The problem is treating a Senior engineer who needs an opportunity like a Junior engineer who needs a tutorial.
The Boundary of Mentorship
Mentorship is incredibly effective for Junior and Mid-level engineers. They need context, guardrails, and someone to help them navigate the codebase and the team dynamics.
A while ago, I was working with a junior engineer. They had high energy and a strong drive to grow, but they felt they didn't have enough space to make a real impact. We sat down and brainstormed. I decided to give them explicit Ownership of the bug list. That simple shift changed everything. Having a clear boundary allowed them to fix issues proactively, build their reputation, and feel truly effective.
But there is a hidden failure mode in mentorship. If you over-mentor, you build a dependency loop. The mentee stops taking risks, waiting for you to validate every step. On the flip side, the mentor feels pressured to always have the "right path" and gets frustrated when progress slows down.
The Paradigm Shift: Sponsorship
When an engineer proves their technical skills and takes responsibility, what they need changes. They don't need someone to answer "how" to do a task. They need Sponsorship.
Sponsorship is about giving away your stage. It is about advocating for your engineers when they are not in the room. It means giving them a high-stakes project, letting them make architecture decisions, and when they succeed, loudly praising their quality of work to the rest of the company.
Recently, I have focused heavily on this shift. Seeing a driven engineer step into a bigger role, make tough decisions, and get recognized for it is one of the most rewarding parts of leadership.
Optimize the System, Not the Task
Many managers never make this transition. They stay at the surface level, endlessly managing tasks and mentoring people who have already outgrown the advice.
True engineering leadership is not just about delivering features. It is about building structure, vision, and a system that does not depend on you as a hero. A good manager is one whose absence doesn't break the team. Capability and trust should travel.
A question for your next 1:1
Look at your direct reports. Who needs you to sit with them and map out the next steps (Mentorship), and who needs you to step aside, give them a high-visibility project, and advocate for them (Sponsorship)?
Top comments (0)