Stretch Assignments: Examples and How to Use Them
What a stretch assignment is, 20 examples by skill, how to scope one without causing burnout, and how small businesses use them to develop and keep people.
Stretch Assignments
How to develop and keep good people using work you already have, at 5 to 50 employees
One of the best employees I ever had told me, in her exit interview, that she had been bored for about eight months. I had no idea. Her work was excellent, she never complained, and I had read all of that as contentment. What it actually was: someone who had stopped growing and had quietly started looking.
The frustrating part is that the work she wanted existed. We had a vendor selection nobody had time for, a process that everyone complained about and nobody owned, and training that lived entirely in two people's heads. Any one of those would have been a genuine challenge for her. I had simply never thought to offer them, because in my head those were my problems and her job was her job.
That is what a stretch assignment is: real work that sits beyond what someone can currently do, given to them on purpose. This guide covers what it means, twenty examples grouped by the skill they build, how to scope one so it develops rather than damages, and how to run the debrief that turns the experience into a capability.
What Is a Stretch Assignment?
A stretch assignment is a piece of genuine work given to an employee that sits deliberately beyond their current skills or experience, so that completing it builds a capability they did not previously have. The difficulty is not a side effect. It is the mechanism. The capability comes from working through the gap rather than from being taught about it.
Three things separate a stretch assignment from ordinary work. It is beyond current capability, so the person will struggle with parts of it. It is real, meaning the business needs the outcome and a poor result would matter. And it is intentional, with someone having decided that this person should develop this capability rather than the work simply landing on whoever was available.
The concept sits at the centre of how professional capability actually develops. The Center for Creative Leadership, whose Lessons of Experience research produced the widely used 70-20-10 framework, places challenging assignments in the largest of the three categories: most professional development comes from demanding work rather than from courses. The specific ratios have never been empirically validated, but the direction is well supported, and the practical implication is clear. If you want someone to grow, the lever is the work, not the training budget. Our 70-20-10 learning model guide covers the framework and its limitations.
Stretch Assignment vs Delegation, Stretch Goals, and Stretch Roles
These four terms get used interchangeably and mean different things. The distinctions matter because each requires a different amount of your time and carries a different risk.
| What It Is | Person Can Already Do It? | Manager Time | |
|---|---|---|---|
| Stretch assignment | Real work beyond current ability, given to build a capability | No, and that is the point | Goes up. Support, unblocking, and review are part of the design. |
| Delegation | Work handed to someone who can already do it, to free up the manager | Yes | Goes down. That is usually the objective. |
| Stretch goal | An ambitious performance target above comfortable achievement | Yes, at a lower level of output | Roughly unchanged. It is about effort against existing work. |
| Stretch role | A job someone is promoted into before they are fully ready | Not yet, across the whole role | High and sustained. This is a much larger commitment than an assignment. |
| Workload increase | More of the same work | Yes | Unchanged. This is not development, whatever it is called. |
The last row is worth naming directly, because it is the most common substitution. Giving someone twice as much of what they already do is not a stretch assignment, and describing it as one is the fastest way to make the term meaningless inside your company. If the work does not require a capability they lack, it is a workload change.
Why Stretch Assignments Matter More at Small Scale
Large companies have to manufacture developmental experiences. They run rotation programmes, build leadership academies, and construct projects partly so that high-potential people have somewhere to grow. It is deliberate and it is expensive.
A small business has the opposite problem and therefore the opposite opportunity. There is always more work that genuinely needs doing than there are people to do it. The vendor selection nobody has time for, the process everyone complains about, the customer relationship that defaults to the founder, the training that has never been written down. Every one of those is a developmental experience that already exists and is currently unstaffed.
This matters because the alternative development levers at small scale are weak. You cannot offer a promotion track with five defined levels. You often cannot match a larger employer on salary. What you can offer is scope: real responsibility, sooner, on things that matter to the business. That is a genuine competitive advantage in retention and it costs nothing except the discomfort of letting someone else do a thing you would do faster.
20 Stretch Assignment Examples, Grouped by Skill
These are chosen to be realistic at 5 to 50 employees, which rules out most of what appears in enterprise lists. There is no rotation programme here and no international assignment. Every one of these is work that probably already exists in your business and is currently done by whoever is most senior, or not done at all.
Choose based on the capability you want to build, not on which task you most want off your desk. Those two sometimes coincide and frequently do not. The individual development plan guide covers how to identify which capability matters for a specific person, and cross-training covers the adjacent case where the goal is coverage rather than growth.
Choosing the Right Person
Three factors have to be present together. Missing any one of them turns a development opportunity into a problem.
| Factor | What to Look For | What Happens Without It |
|---|---|---|
| Capacity | They have room, or you can create room by removing something specific | The assignment gets absorbed into evenings and weekends, and burnout follows |
| Motivation | They have said they want more scope, or asked what comes next | It reads as being volunteered for extra work, which produces compliance rather than engagement |
| A plausible gap | Beyond them, but where you would give it roughly even odds of going well | Too small and nothing is learned. Too large and the failure damages confidence rather than building it |
The motivation factor is the one founders most often assume rather than check. Someone quietly excellent at their job may want exactly that and nothing more, and pushing them into a stretch reads as dissatisfaction with their current work. Ask directly, in a conversation that is not a performance review, and make declining genuinely acceptable. A stay interview is a good setting for it.
One warning about selection patterns. The person who says yes most readily is usually the one already carrying the most, and repeatedly stretching your strongest performer is how strong performers end up leaving. Spread these deliberately, including to people who are competent but not obviously your top performer, because that group has the most room to grow and is most often overlooked. The high potential employees guide covers identification beyond current output.
Scoping It Without Causing Damage
Six checks before you hand anything over. A stretch assignment that fails these does not produce a smaller amount of development, it produces a demoralized person and a business problem.
The fifth check is the one that gets skipped and causes the most harm. Adding a challenging new project on top of an already full workload is not a development opportunity, it is an unfunded mandate. The person will protect the visible new thing and absorb the overflow personally, and you will not find out until either the regular work fails or they do. Decide explicitly what will not get done, and say it out loud so nobody is guessing.
Supporting Without Taking It Back
The failure mode here is specific and common. The person struggles, you know how to do it, and you step in. Three weeks later you are doing the work with their name on it, and the development has not happened.
The third step is where most managers struggle, particularly founders who are fast at the work. Answering a question directly takes thirty seconds and answering it with questions takes ten minutes. The ten-minute version is the entire point of the exercise. The workplace coaching guide covers the questioning technique in more depth.
Spotting Burnout Before It Happens
Stretch assignments produce burnout through a predictable route: capacity was not created, the person absorbed the difference personally, and the output looked acceptable until it suddenly did not. The signals arrive well before the failure.
The first signal is the most reliable and the most counterintuitive. A person who asked constantly in week one and asks nothing in week five has usually not become competent. They have concluded that asking is being read as struggling, and have decided to solve things alone regardless of cost. When you notice this, ask directly about workload rather than progress, because the answer to how is it going is almost always fine.
The intervention is straightforward once you see it: remove something else, extend the deadline, or reduce the scope. All three are acceptable and none of them is a failure. What is not acceptable is noticing and waiting to see whether they cope. The employee burnout guide covers the wider warning signs.
The Debrief That Makes It Count
Without a debrief, a stretch assignment is just a project that happened. The conversation at the end is where the experience turns into a capability the person can name, which is what makes it transferable to the next thing.
Do the debrief within a week of the end, while detail is still recoverable. Also make the outcome visible to the team, particularly when it went well, because a stretch assignment that nobody notices teaches everyone else that taking on hard things is invisible. The employee recognition guide covers doing this without it becoming performative.
The Stretch Assignment Template
A working document covering scoping, the handover conversation, check-ins, and the debrief. Copy or download it and use one per assignment.
Part 3 is the one to be honest about. If you cannot name something that will be removed or allowed to slip, the assignment will be paid for out of the person's own time, and that is the version that ends badly regardless of how well everything else is designed.
When Not to Use a Stretch Assignment
They are not a universal tool, and using one in the wrong situation makes things worse rather than neutral.
| Situation | Why a Stretch Assignment Fails Here | What to Do Instead |
|---|---|---|
| The person is already overloaded | There is no capacity to create without something breaking | Fix the workload first. A stretch on top of overload is how you lose someone. |
| They are struggling in their current role | Adding difficulty to an existing difficulty compounds it | Address the current performance issue directly. Development comes after stability. |
| You need the work done well, right now | Development requires tolerance for a worse outcome than an expert would produce | Do it yourself or give it to whoever is best. Not everything can be a development opportunity. |
| It is really a permanent role change | Framing a promotion as an assignment avoids the conversation about title and pay | Have the actual conversation. Employees notice this framing and correctly read it as avoidance. |
| The person has said they do not want it | Development that is imposed produces compliance, not growth | Believe them. Ask again in six months. Not everyone wants an expanding role and that is legitimate. |
| You are hoping they fail so you can act on it | This is a performance decision wearing a development costume | Manage the performance issue directly. This approach is transparent to everyone including them. |
The fourth row deserves emphasis because it is the one that quietly destroys trust. When a stretch assignment becomes permanent additional responsibility with no acknowledgment, the employee reasonably concludes that development language was used to obtain extra work for free. Every subsequent offer will be read through that lens, by them and by anyone they talk to.
Common Mistakes
| Mistake | Why It Happens | The Fix |
|---|---|---|
| Adding it on top of a full workload | The new work is exciting and the existing work is invisible | Name what gets removed or what will slip, before the assignment starts. This single step prevents most failures. |
| Not saying it is a stretch | It feels like it might undermine their confidence | The opposite is true. Unnamed difficulty reads as personal inadequacy, which is far more damaging. |
| Taking it back when they struggle | You can do it faster and the struggle is uncomfortable to watch | Struggle is the mechanism. Support with questions, and only step in when the consequence stops being recoverable. |
| Always choosing the same person | They say yes and they deliver | Your most reliable person is the one most at risk of leaving from overload. Spread these deliberately. |
| No defined end point | It started as a project and drifted | Set a date and a deliverable at the start. Without an end, it becomes a permanent scope change nobody agreed to. |
| Skipping the debrief | The work is done and attention has moved on | The debrief is where the experience becomes a capability the person can name and reuse. Fifteen minutes within a week. |
| Treating a failed assignment as a verdict on the person | The outcome was visible and disappointing | Debrief on which of the four causes applied: no capacity, gap too large, support missing, or objective unclear. Usually it is the scoping. |
| Making it invisible | Announcing it feels like unnecessary ceremony | If nobody notices, everyone learns that taking on hard things goes unrecognized. Make the ownership and the outcome visible. |
The thread through most of these is that a stretch assignment is a design problem, not a generosity problem. Offering someone a challenge is the easy part. Creating the capacity, naming the difficulty, holding back from rescuing, and debriefing properly are the parts that determine whether anything develops. The employee development guide covers how stretch assignments fit alongside the other levers.
The recurring work around this is keeping track of who has taken on what, what capability it built, and what was agreed about what comes next. FirstHR holds development plans, check-in records, and review history against the employee record, so the conversation about what someone was promised does not depend on anyone's memory of a hallway conversation eight months ago.
Frequently Asked Questions
What is a stretch assignment?
A stretch assignment is a piece of real work given to an employee that sits deliberately beyond their current skills or experience, so that completing it builds a capability they did not have. It is genuine work the business needs rather than a training exercise, it has a defined scope and end point, and the person is expected to struggle with parts of it. The difficulty is the mechanism: the capability comes from working through the gap, not from being told about it.
What is an example of a stretch assignment?
Common examples include leading a project that requires two parts of the business to agree on something, owning a customer relationship end to end including the difficult conversations, redesigning a manual process with real authority to change it, running the weekly team meeting for a quarter, building and delivering training on something they know well, making the hiring recommendation for a role in their area, or covering a manager's responsibilities during a planned absence. The best examples at a small business are usually work that already exists and is currently done by whoever is most senior.
What is the difference between a stretch assignment and a stretch goal?
A stretch assignment is a piece of work that develops a capability the person does not currently have. A stretch goal is an ambitious performance target, usually a number, set above what is comfortably achievable. The assignment is about growth through new work; the goal is about effort against existing work. Asking a salesperson to hit 140 percent of quota is a stretch goal. Asking that same salesperson to design and run the onboarding for the next two hires is a stretch assignment.
How is a stretch assignment different from delegation?
Delegation moves work to someone who can already do it, usually to free up the manager's time. A stretch assignment moves work to someone who cannot yet do it, and the manager's time commitment often goes up rather than down because of the support required. If you hand over a task and expect it back done to standard with no involvement, that is delegation. If you expect to spend time unblocking, coaching, and reviewing, and the point is that the person becomes able to do something new, that is a stretch assignment.
How long should a stretch assignment last?
Long enough for real difficulty and short enough to have an end in sight, which in practice means about four weeks to six months. Shorter than a month rarely produces a genuine capability change. Longer than about six months and it stops being an assignment and becomes the person's job, which is fine if that is the intention but should then be recognized formally with a title or compensation change. Every stretch assignment needs a defined end point, even if the outcome is that the responsibility becomes permanent.
How do you choose who gets a stretch assignment?
Look for three things together: capacity, motivation, and a plausible gap. Capacity means they have room, or you can create room by removing something. Motivation means they have indicated they want more, which you find out by asking rather than assuming. A plausible gap means the assignment is beyond them but not absurdly so; roughly the level where you would give it a fifty to seventy percent chance of going well. Do not default to your strongest performer every time, because that is how strong performers end up carrying everything and leaving.
Can a stretch assignment cause burnout?
Yes, and the most common cause is adding it on top of a full workload without removing anything. The assignment is new and visible, so the person protects it by absorbing the overflow into evenings and weekends, and the output looks fine right up until it does not. Warning signs include a person who stops asking questions, whose regular work starts slipping, whose progress updates become vague, or who has simply stopped mentioning the assignment. Removing something else at the start prevents most of this.
Should stretch assignments come with more pay?
Not usually while the assignment is running, because it is development rather than a permanent role change and it has a defined end. What should happen is a conversation about what comes next before it starts, so the person knows whether success leads to a title, a permanent scope change, a pay review, or simply the capability itself. The version that damages trust is a stretch assignment that becomes permanent additional responsibility with no acknowledgment, which employees reasonably read as extra work obtained for free.
What if the stretch assignment fails?
Treat it as information about the scoping rather than a verdict on the person, at least the first time. Failed stretch assignments usually trace back to one of four causes: no capacity was created, the gap was too large, the support was not there, or the objective was never clear. Debrief specifically on which of those applied. A person who takes on a hard thing and does not fully succeed has still learned more than one who was never asked, and how you handle the shortfall determines whether anyone volunteers next time.
Do stretch assignments work at a small business?
They work better at a small business than at a large one, because the work is already there. At a fifteen-person company there is a constant supply of things that need doing and no obvious owner: a process that needs redesigning, a customer relationship nobody has time for, training that has never been written. A large company has to construct developmental experiences deliberately. A small business has more of them than it can staff, which turns a resourcing problem into a development opportunity.