Short answer: A stretch assignment develops leadership when it gives someone meaningful responsibility beyond their current routine, targets one or two specific behaviours, keeps business risk within clear boundaries and surrounds the work with feedback. Match the challenge to readiness, brief the assignment explicitly, protect learning time and review both delivery and behavioural evidence—not only whether the project succeeded.

Stretch assignments are often treated as a simple idea: give a promising employee a harder project and let experience do the teaching. That can create growth. It can also create hidden overtime, unclear accountability, avoidable delivery risk and a talented person who concludes that development means being left alone with an impossible job.

The useful question is not Is this assignment difficult? It is Will this assignment require the person to practise a capability the business needs, with enough support to learn and enough ownership to lead?

This article gives HR, L&D and people leaders a practical way to answer that question.

What counts as a stretch assignment?

A stretch assignment is real work designed to require a person to operate beyond a familiar pattern. The assignment might involve broader responsibility, a new stakeholder group, greater ambiguity, a change initiative or a decision with more consequence than the person normally owns.

The Center for Creative Leadership describes challenging assignments as experiences that place people in new or uncertain situations where they must act, see the results and adjust their approach. Common sources of challenge include unfamiliar responsibilities, creating change, influencing across boundaries and working with diverse groups.

That definition matters because a stretch assignment is not simply more work. It needs a developmental difference. Asking a strong analyst to produce twice as many reports stretches capacity. Asking that analyst to frame a recommendation, influence three business leaders and defend a trade-off may stretch leadership.

SEED's interpretation is that every stretch assignment should connect four things:

  • A live business outcome worth delivering.
  • A specific leadership behaviour the person must practise.
  • A bounded level of risk the organisation is prepared to carry.
  • A learning loop that turns action and feedback into a better next attempt.

This is consistent with Singapore's Institute for Adult Learning emphasis on embedding capability building into work processes, leadership practices and organisational systems—not treating learning as an activity that sits outside the work.

The evidence: more challenge is not always more development

A peer-reviewed study by D. Scott DeRue and Ned Wellman examined 225 on-the-job experiences across 60 managers. It found that developmental challenge and leadership skill development showed diminishing returns at higher levels of challenge. Access to feedback could offset those diminishing returns.

This does not mean difficult work should be avoided. It means difficulty is not a sufficient design principle. Past a certain point, adding ambiguity, visibility, workload or stakeholder complexity may create heat without creating proportionate learning.

CCL makes the same practical warning in its work on high-pressure development: getting the level of challenge right and providing support are both critical. An uncontrolled stretch can damage engagement and retention rather than accelerate growth.

For HR and L&D, the implication is clear: do not use a stretch assignment as a sink-or-swim test. Design it as a business assignment with a deliberate learning architecture.

Use the challenge-support calibrator

Before approving an assignment, place it on two dimensions: how far the work stretches the person's current capability, and how much useful support surrounds the work. The goal is not maximum challenge. The goal is productive stretch.

Support should not remove ownership. A sponsor who makes every hard decision turns the assignment into shadowing. Useful support gives the participant enough context, access and feedback to make better decisions while leaving the decisions they are ready to own with them.

Choose the assignment by capability—not by availability

The best stretch assignment is not necessarily the most visible project or the next urgent task no one else wants. Start with the behaviour the person needs to build, then find work that repeatedly calls for it.

Capability to developPossible stretch assignmentObservable evidenceRisk to control
Influencing without authorityLead a cross-functional improvement with no direct reporting lineMaps interests, surfaces trade-offs and secures explicit commitmentsUnclear sponsor authority or unresolved decision rights
Strategic judgementDevelop and defend a recommendation for a real investment decisionSeparates evidence from assumptions and explains the chosen trade-offA decision that is too irreversible for the person's current experience
Leading changeOwn one workstream in a broader implementationTranslates the change for affected teams, gathers signals and adjusts the planBeing made accountable for dependencies outside the workstream
Executive communicationPresent a concise decision brief to senior stakeholdersLeads with the decision, adapts depth and handles challenge without defensivenessNo rehearsal or access to the context behind the decision
Developing othersLead a small project team and coach two less experienced colleaguesSets outcomes, delegates judgement and gives specific feedbackRewarding personal rescue work instead of team development

If the target capability is still unclear, use SEED's guide to identifying manager capability gaps or the Training Needs Diagnostic before matching people to projects.

Write a six-part stretch assignment brief

An assignment should be briefed as clearly as any other important piece of work. Add the development contract instead of leaving it implied.

  1. Business outcome. State what must be delivered, why it matters and who benefits. Keep the outcome real; artificial projects rarely create the same judgement demands.
  2. Target stretch. Name one or two behaviours the person must practise. For example: frame an ambiguous problem, influence peers, make a reversible decision or coach others through delivery.
  3. Decision space. Clarify what the participant owns, what requires consultation and what must be escalated. Autonomy without boundaries is ambiguity; boundaries without autonomy are observation.
  4. Risk limits. Define the non-negotiables: budget, customer impact, legal or safety constraints, reputation, deadlines and dependencies.
  5. Support system. Identify the sponsor, subject-matter access, feedback sources, check-in rhythm and any just-in-time learning the participant can use.
  6. Evidence of growth. Decide how the participant and sponsor will know the capability is improving, even if the business outcome changes.

A useful one-sentence brief sounds like this: Lead the regional handover redesign so cycle time improves; practise aligning stakeholders with competing priorities; own the recommendation and pilot; escalate any compliance risk; review decisions fortnightly with the sponsor; and gather evidence from decision logs, stakeholder commitments and the retrospective.

The brief can sit inside a broader Manager Development Plan Template so the experience is connected to an explicit development goal rather than becoming an isolated project.

Check readiness without selecting only the safest person

There is a tension in assignment-based development. If leaders always choose the person most likely to deliver, the same experienced people receive every opportunity. If they choose only for development, the business may carry more risk than it understands.

Use five questions to make the trade-off visible:

  • Capability adjacency: Does the person have enough related experience to learn from this challenge, or would they first need basic technical knowledge?
  • Learning orientation: Do they seek feedback, test assumptions and adjust, or defend the first answer?
  • Capacity: What work will be stopped, delegated or delayed so the assignment is not merely added on?
  • Risk reversibility: Can early decisions be tested and corrected before consequences become difficult to reverse?
  • Support availability: Is a sponsor genuinely available to open doors, review judgement and intervene at the agreed boundary?

Readiness is not the same as perfect confidence. A stretch assignment should feel uncertain. The design task is to make the uncertainty learnable.

Build a support system that preserves ownership

Support is most useful when it helps the person notice and improve their judgement. Three short routines are often enough.

1. A pre-mortem before the work starts

Ask the participant and sponsor to imagine the assignment has failed. What likely caused it? Which assumption was wrong? Which stakeholder disengaged? Which decision arrived too late? Convert the answers into early signals and escalation points.

2. Decision reviews during the assignment

Do not use every check-in as a status meeting. Choose one consequential decision and ask: What did you notice? What options did you consider? What trade-off did you make? What would change your mind? This reveals leadership thinking without taking the decision away.

3. An after-action review at meaningful milestones

Review intended outcome, actual result, contributing choices and the next experiment. Capture learning while the context is fresh. Where several participants are taking stretch assignments, group coaching can provide a confidential space to compare patterns and rehearse the next move.

Measure two outcomes, not one

A developmental assignment has a delivery outcome and a learning outcome. Measuring only delivery can reward heroics, luck or a forgiving project. Measuring only learning can ignore the fact that this is real work.

Evidence areaQuestionPossible evidence
Business progressIs the assignment moving the intended outcome?Milestones, quality, stakeholder commitments, customer or operational signals
BehaviourIs the target leadership behaviour becoming more consistent?Observed meetings, decision briefs, delegation agreements, feedback from key stakeholders
JudgementAre decisions improving as ambiguity or pressure increases?Decision log, options considered, assumptions tested, escalation quality
Learning transferCan the person use the capability in another situation?A second application, manager observation or a new project with less support

Do not fabricate a return-on-investment number from weak proxies. If you need to build a broader measurement case, SEED's training effectiveness answer explains how to connect evidence to the business decision it should inform.

Common mistakes that turn stretch into strain

Giving the work without removing anything

Development should not be a euphemism for unpaid capacity. Agree what will stop, who will cover routine work and how long the assignment will last.

Keeping the development goal secret

Tell the participant why the assignment was chosen and what it is designed to build. Hidden tests create anxiety and make useful feedback harder to interpret.

Using failure as proof the person was not ready

Some business outcomes fail for reasons outside one person's control. Review the quality of diagnosis, decisions, influence and adaptation—not only the final result.

Choosing opportunities through informal visibility

If stretch assignments are allocated only through sponsorship behind closed doors, access can become uneven. Publish the capabilities, selection criteria and support available; then track who receives which experiences.

Making the sponsor the rescuer

A sponsor should create access, clarify boundaries and provide feedback. If the sponsor repeatedly takes over, the participant gains exposure but not ownership.

Implementation checklist for HR and L&D

  • The assignment solves a real business problem and has a named outcome owner.
  • The target capability and one or two observable behaviours are explicit.
  • The challenge is adjacent enough to the participant's experience to be learnable.
  • Decision rights, escalation points and non-negotiable risks are written down.
  • Routine workload has been reduced, delegated or reprioritised.
  • A sponsor has time, authority and a specific feedback role.
  • Check-ins review judgement and learning, not only task status.
  • Business evidence and behavioural evidence will both be captured.
  • The participant knows how the assignment affects performance evaluation and career decisions.
  • The organisation will review equitable access to developmental opportunities.

A practical rollout for a leadership programme

Stretch assignments work best when they are part of a learning journey rather than an optional activity added after a workshop. A simple sequence is:

  1. Diagnose: identify the business capability and the participant's next behaviour.
  2. Match: select real work with the right challenge, reversibility and stakeholder exposure.
  3. Contract: agree outcome, decision space, risk limits, capacity and support.
  4. Apply: let the participant lead while the sponsor observes agreed moments.
  5. Reflect: use feedback and decision reviews to improve the next attempt.
  6. Transfer: test the capability again in a different context with less support.

This approach complements formal learning rather than replacing it. A workshop can give people a shared language and a safe place to rehearse. Coaching can help them examine real decisions. The assignment gives the behaviour consequences, context and repetition.

For a complete programme architecture, see SEED's guide to designing a leadership development programme. If you need to connect learning design, workplace application and evidence across a cohort, explore SEED's Training Programme Design service.

Frequently asked questions

How long should a stretch assignment last?

Long enough for the participant to make decisions, receive feedback and try again. A focused assignment may run four to eight weeks; a broader project may take several months. Define milestones and review points rather than assuming a longer assignment is more developmental.

Should a stretch assignment be part of performance evaluation?

Clarify this before the work begins. If the assignment affects performance or promotion decisions, the person needs to know the criteria, support and risk boundaries. Do not invite experimentation while silently evaluating only flawless delivery.

What if the stretch assignment fails?

Protect non-negotiable risks, then separate project outcome from leadership evidence. Review what the participant noticed, decided, communicated and changed. A contained failure can generate strong learning; an unbounded failure signals a design problem as much as an individual one.

Can first-time managers take stretch assignments?

Yes, but the assignment should be adjacent to their current capability and bounded carefully. Leading a defined cross-functional improvement may be appropriate; owning a high-stakes enterprise transformation without sponsor access is not. Pair the experience with the role-practice approach in SEED's first-time manager programme guide.

Are stretch assignments a replacement for training or coaching?

No. Experience supplies context and consequence; training supplies shared concepts and rehearsal; coaching supports reflection and judgement. The strongest design uses each where it adds value instead of expecting the assignment to teach everything by itself.

Sources