Stretch, sponsorship, exposure

Ask a manager how they grow their engineers and most will describe advice. They review designs, they answer the hard question in the 1:1. For my first year managing, that was my whole picture of development, and I told myself it counted. All of it is useful, and almost none of it is what advances a career. The development literature has a number for this, the 70-20-10 split: seventy percent of how people grow comes from challenging work, twenty percent from other people, and ten percent from formal training. The advice is the ten. The work is the seventy. We spend our energy on the ten because it is comfortable and safe.

Three instruments live in that seventy, and managers blur them constantly:

• Stretch is work beyond someone's current ability, the assignment they are not quite ready for.
• Sponsorship is your own credibility spent on their behalf in rooms they are not in.
• Exposure is visibility you engineer for them, putting their work and their name in front of the people who decide things.

Mentorship, the advice mode, helps someone do the job they have. These three reach for the job they don't. That is the line: the mentor improves your current role, the other three build your next one.

Naming the three is the easy part. Handing them out is where it goes wrong.

Co-author it, don't hand it down

The default picture is a manager handing out opportunity. You decide an engineer is ready for the hard project, so you give it to her. You decide to name someone in the promotion calibration, so you name him. The opportunity flows down from you, and that is where it goes wrong.

An assignment handed down is received as one of two things, neither good. If the person reads it as a gift, it looks like favoritism: why her and not me, what does she have that I don't. If they read it as more work dropped on a full plate, it creates resentment, because to them it is just the thing nobody else wanted. The same stretch, in the same words, can be either, and you do not get to decide which.

A good opportunity can go wrong like this. A senior engineer hands a junior the migration nobody wants to own, frames it in passing as a great chance to own something end to end, and carries on, sure he has done her a favor. The junior hears something else: I am now responsible for the job nobody wanted, alone, on top of everything I already had. Weeks later it is behind schedule, and the story that travels is that she couldn't handle the scope. The opportunity was real. The way it was handed over wasted it.

A better speech will not fix this. Stop handing the thing down and start building it with the person. The conversation comes first: where do you want to be stretched, and what kind of visibility matters to you. Then you shape the assignment around that answer. Co-authored, the same migration carries consent and ownership, because the engineer had a hand in choosing it. Where that conversation happens is its own instrument.

Consent is what separates developing someone from setting them up. Hold onto it, because every mistake that follows is a version of skipping it.

Ration it honestly, the capital is finite

You cannot do this for everyone equally, and pretending you can is a fiction your team sees through. You have a fixed amount of credibility to spend and a limited number of visible projects to hand out. Sponsorship especially is limited: the credibility you spend advocating for one person is credibility you are not spending on another. Sponsor all six reports in the same review and the word stops meaning anything.

So you ration, and the honest thing is to be open about the rationing rather than hide it behind a pretense that everyone gets the same. The people who did not get the visible project should know there was a project, that it went to someone, and why. Hide the rationing and you create the exact favoritism you were trying to avoid, because the people who missed out can see the outcome and were never told the rules.

This is the growth version of a harder question, where your best people go. That one asks who you put on the work that matters most to the business. This one asks who you put on the work that would grow them most. The two pull apart more than you would like: the person who would grow the most from the hard project is frequently not the safest pair of hands for it, and choosing growth means choosing some risk to the outcome, on purpose.

Stretch: match it to readiness, take something off the plate

A stretch is supposed to be uncomfortable, work slightly beyond reach, where you operate without full competence yet. But the same hard assignment can grow someone or grind them down, and support decides which.

Picture that same hard, visible project given to someone who is genuinely not ready, with no coaching attached, nothing taken off their existing load, and no path back if it goes wrong. They are carrying a high-stakes project in front of an audience, with none of the support that would let them grow into it. When it fails, and it often does, the failure reads as theirs, a personal flaw rather than a staffing decision. That is the glass cliff: a hard, visible job handed to someone who was not set up to succeed, and the failure later blamed on them rather than on the setup.

Three things keep a stretch on the developmental side of that line:

• Coaching, so they are reaching with a hand nearby.
• Removed load, because something has to come off the plate to make room.
• Reversibility, a way back that does not end a career if the thing goes wrong.

Get those right and the same difficult assignment grows someone instead of breaking them.

The hardest judgment inside a stretch is telling struggle from drowning. Struggle is the point; you are meant to let people work at the edge of their ability, because rescuing them too early is how you waste the stretch. Drowning is the failure of the stretch, and from the outside it looks almost identical. Reading that difference, and not pulling the plug on someone who is just in over their head for a while, is most of the skill.

Sponsorship: risk you carry, not praise you give

Praise is cheap: it is public and costs you nothing. Sponsorship is the opposite: it is often private, and it is a bet whose downside you personally carry.

The clearest version is the room the person is not in: a calibration meeting or a promotion committee, where their next opportunity is being decided and they have no voice in it. You put your name on them: you say, in effect, I vouch for this person, route the opportunity here. And the moment you do, their stumble becomes partly your miss. If they don't deliver, you were wrong, in front of the people whose opinion of your judgment matters.

That cost is not a flaw in the design: it is the design. The risk you carry is what makes sponsorship worth more than praise, because it is credible only when it is expensive to you. Which is also why you should only sponsor what you have co-authored. Advocate for someone's readiness without having built the work alongside them and you are vouching for a readiness you assumed rather than one you watched. The craft of making that case upward, or sideways to peers, belongs elsewhere. You are not complimenting them, but placing a bet whose downside you hold.

Exposure: engineer it for the ones who won't chase it

There is a popular framing of career advancement, sometimes called the PIE model, that weights performance at ten percent, image at thirty, and exposure at sixty. It claims that being seen by decision-makers matters more than the quality of the work. Taken as personal advice, it becomes a license to self-promote, and the people who follow it most eagerly are rarely the ones doing the best work.

Invert it. As a leader, those numbers are not advice for you to act on for yourself; they describe a gap you are well placed to close. The strong, quiet engineer who does excellent work and never mentions it goes unseen for exactly the reason PIE names. Your job is to engineer the exposure they will never chase on their own.

It shows up as a plateau that makes no sense on the merits. Someone whose work is consistently among the best on the team keeps getting passed over for the visible role and the named credit, because they do the work and then go quiet. Nobody with influence has seen it. You correct it by routing visibility on purpose: hand them the design review to present, put their name on the thing they built, and send them into the room instead of carrying their work in for them.

Exposure goes wrong in two ways. One is visibility with nothing behind it, which an audience sees through and which costs the person credibility. The other is exposure handed to someone not ready for the scrutiny, which is the glass cliff again in a different costume. Real exposure is good work made visible, given to someone ready to be seen.

What it comes down to

Stretch, sponsorship, exposure: three instruments, one discipline underneath. Each works when you co-author it with the person and ration it honestly across the team. Each does harm in its unilateral version, where the stretch becomes a dumping, the sponsorship becomes a bet you had no business making, and the exposure becomes a glass cliff. The growth that matters most happens outside the job description. Whether it grows the person or damages them comes down to whether they had a hand in choosing it.