People Management
Allocate Stretch Assignments Fairly Across Your Team
A completed fictional four-person allocation matrix, funded assignment agreement and two-round coverage review distinguish accepted development work from exploratory future ideas.
Allocate stretch assignments by defining the work and learning opportunity, asking employees about their interests, comparing task-specific readiness, and funding the support and workload changes each candidate would need. Record why you selected someone and when you will revisit opportunities for others. Being the quickest volunteer or most available after hours should not stand in for those decisions.
This LandOffer.ai guide uses an original fictional allocation matrix and a completed two-round review. Official university guidance was checked October 25, 2026. The people, projects, hours and outcomes below are invented teaching inputs. The matrix below is an editorial method for making managerial reasoning visible. It has not been validated as a way to eliminate bias and does not promise anyone a promotion.

Describe the opportunity before choosing the person
Write the deliverable, learning objective, duration, decision boundary and acceptance owner. Distinguish work that develops a new capability from additional volume of a familiar task. If success depends on expertise the assignee must already possess, decide what unfamiliar responsibility remains and why this is developmental rather than ordinary staffing.
LSE's guidance on ongoing development describes stretch work as adjacent to someone's role, appropriately challenging and supported by feedback. Its examples include modest responsibilities such as chairing a meeting. This supports designing a useful learning task without assuming that only a large, visible project counts. The guidance does not grant authority over another team's work.
Separate essential starting knowledge from skills the assignment is intended to build. Requiring prior experience of every task can reserve the opportunity for people who already had it. Removing all prerequisites can leave a learner carrying risk they cannot manage. Explain which knowledge gaps can be covered by pairing or smaller scope, who will review the work, and which gaps still prevent this particular assignment.
Also identify who owns operational consequences. An employee can coordinate a test-planning review without approving a production release. Naming that distinction keeps an educational assignment from becoming unbounded accountability for decisions outside the person's authority.
Ask about interests and constraints through a consistent process
Share the opportunity with the relevant team and give people a practical way to express interest or ask questions. Offer an asynchronous response as well as a conversation. Consider employees beyond those who speak first in a meeting, send frequent private messages or already have easy access to the sponsor.
Stanford's development-planning guidance connects employee abilities, interests and opportunities with organizational needs. It recommends collaborative career conversations, explicit support and follow-up, while warning managers against promising outcomes such as promotion or transfer. Those are employer-specific recommendations informing the questions here, not a guaranteed development process at another company.
Ask each person what capability they want to practice, what relevant experience they can point to, what support would help and which work would need adjustment. Keep the questions job-related. Employees do not need to disclose private personal circumstances to demonstrate commitment. A statement such as “I can participate within my agreed working hours if this task moves” gives you a capacity decision to solve.
Separate an employee's lack of interest in this assignment from lack of ambition. Someone may want deeper technical investigation rather than facilitation. Another may welcome the skill but need a smaller first step. Record the preferred skill and a date to revisit it. That gives you a future allocation question instead of a permanent label about potential.
Completed allocation matrix: four different development needs
In this fictional example, manager Eli needs a four-week test-planning review for a packaging-library upgrade, April 1–28. The assignee will gather test scenarios from two teams, explain gaps and facilitate a review. Release owner Marta retains production decisions. The learning objective is cross-team facilitation, not becoming the library's permanent support owner.
Eli shares the same brief and questions with four engineers. The starting requirements are enough familiarity with the test suite to understand the scenarios, the ability to document uncertainties, and participation within agreed working hours. Experience leading a cross-team meeting is something the assignment can teach.
| Employee | Expressed interest and relevant evidence | Stretch and support needed | Capacity and recent opportunities |
|---|---|---|---|
| Ren | Wants facilitation practice; authored reviewed test cases for the library | First cross-team review; needs agenda feedback and help handling a disagreement | Six hours weekly possible if optional test cleanup is deferred; no lead assignment in the previous two rounds |
| Dalia | Interested in another review; already led two comparable planning sessions | Limited new facilitation practice; would benefit more from deeper technical planning | Current migration work conflicts with the proposed six hours; Eli would need an explicit resourcing change, not evening work |
| Hugo | Wants profiling work and declines the facilitation role; has a reviewed investigation note | This assignment does not match the stated learning interest | Has some capacity, but available time does not create interest or make him the default choice |
| Sana | Wants validation experience; has drafted test cases with coaching, but not used this suite independently | Needs suite orientation and closer review before leading the full discussion | Four hours could be released; available coaching is currently one hour weekly, below the support Eli judges necessary for this full scope |
The matrix does not produce a total score or rank the engineers. Eli's recorded decision selects Ren because the task offers relevant new learning, the initial work evidence fits the starting requirements, and the required time and reviewer support can be funded. Previous opportunities inform the coverage discussion without creating an automatic entitlement to the next assignment.
Dalia's schedule is not treated as a lack of motivation. Eli considers moving her existing work, but records that this assignment would largely repeat recent practice while Ren has a supported first opportunity. Sana is not simply marked “not ready.” Her specific support gap is recorded so Eli can change the design of a later assignment. Hugo's preference remains profiling, not a forced consolation role.
The team receives the assignment's purpose and Ren's selection, without receiving this private comparison of everyone else's development conversations. Eli separately discusses each employee's own feedback and next action. In actual work, keep individual records within the employer's authorized development process; this public matrix uses only invented information.
Complete the support decision before the assignment starts
A fair-looking selection can still fail if the learner receives responsibility while someone else keeps all the time and resources. Name the work removed, the person approving that change, and the support owner's available hours. Mentoring cannot be assumed free merely because the mentor is experienced.
CU Boulder's goal-setting guidance includes equitable access to development, mentorship and stretch opportunities in its supervisor-goal examples. It also describes agreeing on support and resources in goal planning. This is an example of an employer assigning managers responsibility for development access; its goal counts, deadlines and performance-system requirements are not imported into this guide.
Eli and Ren complete the following agreement before April 1:
- Deliverable and boundary: Ren facilitates one two-team test-planning review and prepares the accepted scenario register by April 28. Marta accepts the register; she separately owns release readiness and production authorization.
- Time funded: Ren receives six hours each week. Eli defers the optional cleanup task that used those six hours; its deadline is removed from Ren's current commitments.
- Support funded: Dalia provides one hour weekly for agenda and scenario review. Eli cancels her optional one-hour documentation session during the assignment. She is a reviewer, not a silent second lead.
- Checkpoints and escalation: Eli reviews scope with Ren after week one and at the midpoint. Unresolved technical questions go to Marta; a disagreement Ren cannot facilitate comes back to Eli for support.
- End condition: Marta accepts or returns the register with specific gaps by April 28. Any follow-up work needs a new owner and allocation; Ren's ordinary workload does not acquire permanent coordination duties by default.
Ren accepts these terms. No late-night availability is part of the selection or agreement. If Dalia's funded hour disappears, Eli must change support, scope or timing instead of expecting Ren to cover the difference alone.
The agreement also states what feedback will cover: whether Ren represented both teams' scenarios, made uncertainty visible and led the discussion within scope. It contains no promise that one assignment establishes readiness for a higher title.
Completed second-round review: inspect access, support and follow-through
A distribution of names is not enough to evaluate development access. Record who heard about an opportunity, expressed interest, accepted, received the planned support and actually practiced the intended skill. Distinguish a future discussion from an offered or completed assignment.
At the fictional April 28 closeout, Ren has facilitated the review and delivered the accepted register. One scenario remained unresolved because a team had not confirmed its expected behavior. Marta accepts ownership of that question instead of calling it a failure of facilitation. Ren's feedback identifies a useful change: circulate disagreements before the meeting so participants can prepare. The record supports a completed coordination exercise, not a measured improvement in release quality.
For round two, Eli designs a smaller validation assignment for Sana: prepare three edge-case scenarios and host one paired walkthrough for a follow-up packaging change, May 6–26. Reviewer Jonas can provide two hours weekly because Eli defers his optional prototype for the same two hours. Eli also defers Sana's optional four-hour weekly issue-grooming cleanup for those three weeks; required issue triage remains in the team's normal coverage. Marta remains the technical acceptance owner; Sana is not given independent production responsibility.
The completed coverage review reads:
| Employee | Round-one result | Round-two decision and observed status | Next review |
|---|---|---|---|
| Ren | Accepted and completed facilitation with funded support | Returns to normal work; no automatic repeat lead role | Eli reviews the feedback and next learning interest on May 30 |
| Dalia | Not selected for a largely repeated learning task; provided one funded review hour weekly | No new stretch assignment assigned; discusses deeper technical planning with Eli | May 30 conversation to identify a suitable need and capacity, not a promised assignment |
| Hugo | Declined facilitation; preference respected | Profiling idea discussed, but no scoped work or reviewer allocated yet | Eli checks the actual need and resources on June 3; status remains exploratory |
| Sana | Full round-one scope not offered because necessary coaching was unavailable | Accepts and completes the smaller walkthrough with two funded review hours weekly | May 30 review of independent scenario writing and remaining support needs |
In the fictional walkthrough, Sana's first draft combines a missing package with an unsupported package version. Jonas asks her to separate the expected behaviors. She revises the three scenarios, and Marta accepts them as a planning input. The record does not claim that they were executed or prove the packaging change correct.

After two rounds, two people have completed different learning assignments; Dalia has received review practice but no new stretch of the kind she wants, and Hugo still has only a discussion. Eli records those gaps. It would be misleading to mark all four employees “developed” merely because everyone appears in a table. The review is evidence of follow-through and remaining constraints, not proof that allocation is now unbiased.
Revisit the system as well as the individual decision
Look for repeated patterns: the same people selected, the same people asked to maintain routine work, interested employees repeatedly deferred, or support promised and then withdrawn. Ask whether task design, notification, existing work allocation or reviewer capacity creates the bottleneck. Repeatedly choosing someone with prior experience can leave others without a supported way to gain that experience.
Keep essential operational work visible and properly owned. Do not move all maintenance onto someone not selected so another person can develop. If capacity cannot be released responsibly, narrow or postpone the stretch instead of creating hidden overtime or an unrecognized second job.
Before your next allocation, write the brief and compare interest, starting evidence, support and capacity consistently. Confirm the selected person accepts the scope and funded support before starting. Give others a dated review point and keep an unallocated future idea labeled exploratory. Use LandOffer.ai as the publisher reference for this guide; the next action is a supported internal assignment and a record you can revisit with your team.
Sources and Further Reading
- LSE: Supporting Ongoing Development — appropriate challenge, adjacent work, feedback and supported delegation.
- Stanford: Development Planning — employee interests, abilities, organizational needs, support and follow-up without promised promotions.
- CU Boulder: Goal Setting and Performance Planning — development access and support in published FY26–27 goal guidance; local rules are not generalized.


