Not a Mentor, a Sponsor

From the field: “Who is this?”

In the meeting I said good things about this engineer. “Very solid, reliable, finishes what they start.” People nodded and moved to the next name. My promotion proposal was postponed with a note: “Let us see one more quarter.” The reason: “We have not seen their impact outside the team.”

They were right. They had not seen it. There was nowhere they could have seen it. That evening I opened my calendar for the last eleven months and made a list. Presentations to leadership. Incident walkthroughs. Meetings with the risk and compliance team. Project kick-offs. In other words, every moment where someone outside the team could ask “who did this?”.

There were fourteen. The same person was in nine of them: the most senior engineer on the team. In a team of seven, three people had zero. The engineer who sped up the reconciliation job was one of those three.

The most uncomfortable part was this. I had a monthly one-on-one with this engineer. We talked about their career. My advice was always the same: “Speak up a bit more in meetings, show yourself.” I thought I was a good mentor. But I was the one giving out the stage, and in eleven months I had not given them the stage even once.

Two roles, two different costs

Mentoring is not bad. It is just not enough. A mentor gives what they know and leaves the risk with the person. A sponsor puts their own reputation on the table. The clearest way to see the difference is where the conversation happens:

At the calibration table, my mentoring was worth nothing. None of the six managers knew what advice I had given. Even if they had, nothing would have changed. What mattered was how many rooms I had named this person in during the six months before. The answer was zero.

Why visible work always goes to the same person

I did not make any of those nine decisions to push one person forward. Each had a reasonable excuse:

• “It is the deputy general manager’s meeting, let us not take risks.” Important room, safe choice.
• “They gave this presentation before, they know the context.” Someone who presented once is faster the second time.
• “The incident was in their area.” Most of the time it was not; they had just offered to present it.
• “The others do not like being on stage.” I had never asked any of them.

One by one, each is defensible. The problem is the total. Visible work brings recognition, and recognition brings the next piece of visible work. The loop feeds itself. A year later, “the best presenter” really is the best presenter — because they had nine of the fourteen rehearsals.

Then there is the type of work. Quiet, good engineers often remove a problem before it happens. While the reconciliation job took 3 hours 40 minutes, the morning reports were late two or three times a month. Each delay was an incident, and each incident had someone to tell the story. When the job dropped to 52 minutes, the delays stopped. Nobody tells the story of a problem that is gone. The person who puts out the fire becomes visible. The person who replaced the wiring so the fire never started does not. Making them visible depends on you telling that story.

person  visible work  distribution
------  ------------  ------------------
A       9             #########
B       2             ##
C       2             ##
D       1             #
E       0
F       0             <- nightly reconciliation: 3 h 40 min -> 52 min
G       0
------  ------------
total   14

# visible work = a moment where someone outside the team
# could ask "who did this?": leadership presentation,
# incident walkthrough, risk/compliance meeting, kick-off

Making this table took twenty minutes. I had not done it once in eleven months. I had a dashboard for every part of the team’s work. I did not have a single number for whose voice reached outside the team.

Sponsorship is three things

1. Naming them with a concrete piece of work

“Very solid” is not a sponsor’s sentence. That is what I said at calibration, and it did nothing. Nobody at the table could connect it to anything. The sentence that works has this shape: person + work + result. “They cut the nightly reconciliation job from 3 hours 40 minutes to 52 minutes; the morning reports are now ready before 07:00.” People remember this sentence, because someone else can repeat it.

And this sentence has to be said months earlier, not at calibration. In the weekly leadership update. In a hallway conversation with the deputy general manager. In a planning session with another team’s manager. The calibration table should not be the first place anyone hears it.

2. Giving them visible work

Saying the name is not enough. People need to hear the person’s own voice. For that you give them a stage: a presentation, an incident walkthrough, a decision run with another team. There is an easy trap here. The two lists below look similar, but only one is sponsorship:

3. Taking the risk

Three weeks after calibration I gave this engineer their first stage: a twenty-minute walkthrough of the reconciliation change for the risk and compliance team. It did not go well. They got stuck on two questions. One was about report timing. The other was about how old and new results were compared. We should have covered both in preparation.

After the meeting, the risk team’s manager wrote to me: “Could you present next time?” That reply was the real test of sponsorship. I wrote: “I chose them, and I left the preparation incomplete. Let us do a second session next week. They will present again.” We prepared the second session together. We wrote down the questions in advance. After the second presentation, the same manager wrote directly to the engineer about the next change.

Sponsorship without risk puts the person into an exam alone. They pay the price: they will not ask for a stage again. In the post on psychological safety I wrote about why a team that can talk about mistakes starts with the manager admitting their own. The same is true here. “I chose them, the gap is mine” is the one sentence that makes a second attempt possible.

The other side: the person with nine jobs

Changing the distribution meant taking something away from the senior engineer. I was nervous about that conversation. It did not go as I expected. They said they had taken most of the nine jobs without really wanting them. In the last three months they had prepared presentations on two weekends. They gave four of them away happily.

Their role changed too. They were no longer the one presenting, but the one helping others prepare. That is also visible work. Someone who prepares others leaves a wider impact than someone who presents alone. The monopoly did not only hurt the invisible people. It was wearing them out as well.

The channels that carry a name

Sponsorship is not about big gestures. Most of it is adding one line to channels that already exist. After calibration I set a rule for myself: every week, at least one person from the team is named, with a concrete piece of work, in something that leaves the team.

The easiest place was the weekly update to leadership. The five-line update I described in the managing up post was already going out every Friday. The only change was the subject of each line. It stopped being “the team”:

# BEFORE
- Nightly reconciliation job was sped up.

# AFTER
- Nightly reconciliation job 3 h 40 min -> 52 min. The
  person who changed the query plan and compared old/new
  results in parallel for 3 weeks: [engineer's name].
  Morning reports are now ready before 07:00.

# rule: person + work + result. No "as a team".
# rule: the same name does not appear two weeks in a row.

The second rule mattered. Before I added it, the same loop leaked into the updates. The person with the most visible work also became the person named most often. If you want to spread visibility, you have to count each channel separately.

Other channels work the same way. In planning with another team, you say “this person knows the topic, write to them directly”. In an incident walkthrough, you name the person who fixed it in the first sentence. You invite them as the second interviewer in a hiring interview. None of this needs a separate meeting. It is about noticing whose name you say in rooms where you already talk.

What to track

The first count was 9 / 2 / 2 / 1 / 0 / 0 / 0. Over the next two quarters there were 12 pieces of visible work. Nobody got more than three, and nobody stayed at zero.

What did not work for me

• The “be more visible” advice. I gave it for eleven months. Nothing changed, because there was nowhere to be visible. I was holding the door and telling them to walk through it.
• A rotation list. To be fair, I put presentations on an alphabetical rotation. The first two went badly. Nobody helped with preparation and nobody took ownership of the bad ones. The list spread the work, not the risk. I dropped it in the third week.
• The idea that “quiet people do not want a stage”. I asked the three people at zero, one by one. Two wanted it. One said “written, not a presentation”. I made them the author of a design document, shared with their name on it. Visible work is not always a stage.
• Talking about it in one-on-ones. One-on-ones are the right place to pick up signals. But sponsorship does not happen in a one-on-one. There you only talk with the person. Sponsorship happens in the room they are not in.

Checklist

Conclusion

That engineer was promoted the following quarter. At calibration I barely spoke this time. Two managers at the table already knew them. One of them described the second presentation to the risk team. The same work, the same person. The only change was that their name was not arriving at that table for the first time.

For eleven months I thought I was a good manager. I gave advice, I listened, I did not cancel one-on-ones. The one thing I did not do was the most important: carrying their name into the rooms they were not in.

If someone on your team does good work and nobody but you knows their name, that is not their gap. It is your silence.