How to give a stretch assignment that actually develops someone

What a stretch assignment actually is

A stretch assignment is work handed to somebody before they have proved they can do it. Not far before — the point is not to watch them fail — but far enough past their current evidence that they have to work part of it out themselves.

Radhika Sharma made the case for these in HR Katha, talking to HR leaders about assignments that revealed strengths nobody had predicted. Vinod Rai, group head of HR at Shahi Exports, gave a new joiner a 5,000-person hiring exercise with a sixty-day deadline and fortnightly board updates. Pankaj Lochan describes a whole career built out of moves into territory where the previous role's strengths ran out.

The pattern underneath the examples is the same one every time. The employee learns something about their own limits that no training course could have told them, because the learning and the consequences arrive together.

Responding to The work challenge that helps employees discover their strengths — Radhika Sharma, HR Katha

Air cover is the part most managers get wrong

Sharad Verma, CHRO at Iris Software, gives that piece its most useful phrase. Employees need air cover: knowing somebody is available when the situation becomes genuinely difficult, without that somebody immediately taking the problem back.

There are two ways to get this wrong and both of them feel like good management from the inside. Intervene too much and you remove the developmental challenge — the manager steps in on day three, the work gets delivered, and nobody learned anything. Intervene too little and the assignment stops being development and becomes abandonment. That one tends to turn chaotic, and the person carries the memory of it for years.

In practice air cover means reachable, not hovering. Somebody comes to you on day four and says they tried this, then that, it was working, and now they have hit a snag. The first question back is what have you already tried. That question alone unsticks a surprising number of people — they had the answer and were looking for permission to use it.

When they are genuinely stuck, get them over the hump and hand the work straight back. The handing back is not a formality. It is the difference between support and takeover.

Five things a stretch assignment needs

The assignments that develop somebody have five things in common. The ones that quietly go nowhere are usually missing one of them.

1. Real responsibility. It cannot be the work you did not want to do. People catch on to that almost immediately, and once something reads as grunt work it carries none of the development you were hoping for. The assignment needs real stakes — something that matters if it goes wrong.
2. Enough uncertainty to create a learning curve. Not so far beyond them that it is unfair, but far enough that they have to reach for skills they do not use every week. The discomfort is the mechanism, not a side effect. If they can do it on autopilot, nothing stretches.
3. Room to make decisions. Hand over a step-by-step blueprint from A to Z and they are following instructions, not developing judgement. Judgement is the thing being built here. Give them the outcome and the constraints, and let the method be theirs.
4. A manager who stays available. If they cannot find you on day four, the whole thing falls over. Being reachable costs very little and it is the single support that decides whether a hard week becomes a lesson or a bad memory.
5. A debrief afterwards. Without it they completed a task. With it they learned something. This is the step that gets skipped most often and it is the one that turns the work into development.

The debrief is where the development happens

Sit down once the work is done and look at the result together. Three questions cover it: what went well, what did not, and what would you do differently if you did this again.

The third question is the whole exercise. The answer is usually small and very specific. I would have pulled finance in during week one instead of week three, because chasing them at the end cost me a day I should have spent on the report. That is it. That is the developmental shift.

It does not have to be a big insight, and it is better when it is not. One small correction somebody arrived at themselves outperforms an hour of feedback they were given, because they will actually apply it. Ask the question, then be quiet long enough for them to answer it properly.

It does not need to be a special project

Managers hear the phrase stretch assignment and immediately start designing something. What do I need to create, where does it fit, who signs it off. That instinct is usually the reason it never happens.

Development fits inside ordinary everyday work. It only has to be challenging enough to make somebody slightly uncomfortable. The clearest example is somebody who rarely speaks up in meetings.

Start small. Ask them to cover one section of the next team meeting — the outreach and recruitment update, say. Give them the slot, give them some time, give them guidance on what it needs to land. Then leave the preparation to them and debrief afterwards.

The bigger version is handing over the meeting itself. Run the next one. Pick the topic, bring it to me first and we will talk it through. Now they are deciding what the room spends an hour on, which is a genuine leadership decision with genuine consequences.

What comes out of that is worth having either way. Some people discover a facilitation strength nobody had seen, including them. Others find that presenting frightens them — which is useful to know, and which gets better by doing it more often, not less.

• Own one recurring report. They gather it, they interpret it, and they present the version that goes upward. You review, you do not rewrite.
• Run the debrief after an event. Someone else has to collect honest views from colleagues and turn them into a recommendation. Harder than it sounds, and highly transferable.
• Be the point of contact for one partner. One relationship, theirs to manage, with you copied in rather than leading.
• Draft the budget line they know best. They know the programme better than the spreadsheet does. Let them make the first pass at the numbers.

How to tell whether it worked

Do not judge it on whether the output matched what you would have produced. It usually will not, and that gap is the price of the exercise rather than evidence against it.

Judge it on three things instead. Did they make decisions without checking every one with you. Can they name something they would do differently next time. Would you hand them a slightly bigger version of this next quarter.

Three yeses and the assignment did its job, whatever the result looked like on paper.

Stretch assignments take intentionality from the supervisor. Somebody has to choose the work, resist fixing it halfway through, and then sit down afterwards and talk about it properly. That is more effort than simply doing it yourself, and it is exactly why it gets skipped.

It is also the cheapest development available to any team. No budget, no course, no external facilitator — just work that already exists, handed to somebody slightly before they are ready, with a manager who stays reachable while they work it out.