How New Managers Can Share Stretch Assignments Without Playing Favorites

A high-profile project lands on your team’s roadmap. It has an unforgiving deadline, senior stakeholders, and enough ambiguity to expose every weak spot in the plan. You know who could probably handle it with the least supervision. You also know that giving the assignment to that same dependable person again may quietly narrow everyone else’s future options.

There is no perfect answer. Assigning the safest pair of hands may protect delivery this quarter. Assigning someone newer to the work may slow the start, require more of your time, and create a real possibility of mistakes. New managers often feel they must choose between fairness and results. That framing is too narrow.

Your job is to make the tradeoff visible, deliberate, and repeatable. A team does not need every developmental opportunity divided into identical pieces. It needs a working agreement for deciding who gets which kind of challenge, what support comes with it, and how the next opportunity will be handled.

Decide what the assignment is actually for

“Stretch assignment” can mean almost anything: a difficult project, a chance to present to executives, temporary ownership of a meeting, a cross-functional partnership, or extra work someone takes on because nobody else is available. Those are not interchangeable.

Before you decide who should do the work, name the assignment’s primary purpose. Is the immediate need reliable delivery? Is it building a specific skill? Is it giving someone exposure to a decision-maker? Is it testing whether a person wants more responsibility in this direction? The answer changes what a fair choice looks like.

The U.S. Office of Personnel Management describes developmental assignments as work intended to stretch people beyond their current skills and help them meet more complex requirements. It also treats development as broader than courses, including rotations, shadowing, on-the-job learning, and developmental relationships. That is a useful reminder that the most visible project is not the only route to growth. OPM’s career-development guidance offers a practical definition worth borrowing even outside government work.

Write a short assignment brief before you choose a person. It can be five lines:

• Business outcome: What must be true when the work is complete?
• Developmental value: What capability could this work help someone practice?
• Real exposure: Who will see the work, and does that person have a reason to notice it?
• Risk boundary: Which decisions need review, and which belong to the assignee?
• Support: What time, context, feedback, or backup will the person receive?

This prevents a common managerial mistake: calling extra work an opportunity after the fact. A task is not developmental simply because it is difficult. If a teammate has no authority, no feedback, no access to the relevant context, and no room to learn from the result, you have probably delegated output rather than responsibility.

There will be times when delivery has to come first. A customer escalation, a regulatory deadline, or a project already in trouble may require the person with the strongest relevant experience. Say so plainly. Do not dress up a risk-control decision as a development decision. The useful next step is to identify a smaller but meaningful responsibility that can prepare another teammate for the next comparable situation.

Build an opportunity map before the next big project appears

Managers tend to remember the people who are already visible: the person who speaks first in meetings, works similar hours, replies quickly in chat, or has a background that feels familiar. None of those signals reliably tells you who needs a particular development opportunity or who could do it with the right support.

Create a private opportunity map for your team. This is not a talent ranking and should not become a secret scorecard. It is a lightweight record that helps you see patterns you would otherwise miss. For each person, keep notes on four things:

• Capabilities they have already shown in work you have observed.
• A capability they want or need to build next.
• Recent opportunities they have had, especially exposure and decision-making responsibility.
• Conditions that would make a stretch workable, such as pairing, protected time, a technical reviewer, or clearer scope.

Ask for the employee’s view rather than completing this from your own impressions. A product analyst may want to become stronger at stakeholder management but have no interest in people management. An engineer may want a chance to lead a technical decision without being pushed into running the entire project. A quieter teammate may be ready for a senior audience but need advance context and a rehearsal, not a sudden invitation to present.

Google’s manager framework places career conversations and exploration of development opportunities within a manager’s responsibility to develop people. That matters because a manager cannot make a sound development choice from a performance review alone. You need current information about what someone is trying to learn and what kind of work would make that learning visible. Google’s guidance on developing managers is especially useful on this point: career growth belongs in ongoing management, not one annual conversation.

Keep the map private, but make the categories of opportunity understandable to the team. For example, explain that you will rotate chances to lead planning, represent the team in cross-functional meetings, own a defined decision, present a recommendation, and mentor a newer colleague. People should not have to guess which experiences count or wait for an informal invitation.

Do not rely solely on volunteers. Volunteering can be a helpful signal, but it is shaped by workload, confidence, past access to information, and a person’s sense of whether it is safe to say yes. Invite people directly when the assignment fits their stated direction. Then give them enough detail to choose honestly.

An opportunity process is fair when people can understand the criteria without being asked to disclose private circumstances.

Offer different kinds of stretch, not one prized assignment

When a manager has only one high-stakes assignment, it is tempting to treat it as the sole marker of trust. That creates a winner-and-loser story around a single project. Often, you can design more than one meaningful role without pretending all roles carry the same risk.

Imagine a team replacing a reporting workflow before the end of a quarter. Priya has led similar migrations and is the safest person to coordinate the whole effort. Mateo wants to build cross-functional influence but has mostly worked inside the team. June has strong technical judgment but little experience making recommendations to senior leaders.

The manager can give Priya overall delivery ownership while asking Mateo to lead the requirements discussions with finance and operations. June can own the recommendation on validation rules, present the tradeoffs at a decision meeting, and receive feedback afterward. Priya still carries the largest delivery risk, but the project no longer produces only one person’s growth.

There are three useful shapes for these assignments:

Give one person full ownership when the outcome requires it

Full ownership includes a meaningful decision, a clear outcome, and regular access to context. Use it when the person has enough foundation for the risk and when you can provide real support. Do not assign full ownership merely because someone has been asking for more responsibility; match the assignment to a capability they can practice, not to an abstract desire to prove themselves.

Give another person a defined workstream with real decisions

A workstream should have a boundary that matters. “Help with stakeholder communication” is vague. “Choose the rollout sequence for the support team, bring options to the Tuesday decision meeting, and own the final communication” is a developmental responsibility. The manager stays accountable for the outcome while the employee gets practice making judgments that affect other people.

Build exposure into the work rather than attaching it at the end

Do not ask someone to do the analysis and then remove them when the meeting with senior leaders begins. If the assignment is meant to build communication or strategic judgment, arrange for that person to explain their recommendation, answer questions, and hear the response. A manager can step in if the conversation goes off course, but should not automatically take the microphone.

Coaching helps here because it separates the manager’s answer from the employee’s thinking. In Google’s GROW coaching guide, the sequence moves from a goal to the current reality, options, and a commitment to action. Before assigning a workstream, ask: “What part of this would stretch you in a useful way?” “What support would you need to make a sound recommendation?” “What is the first decision you would want to own?” Those questions produce a better assignment than assuming every ambitious employee wants the same type of visibility.

Be alert to patterns in who gets invited into consequential work. In hybrid and distributed teams, comfort, proximity, and similarity can easily masquerade as readiness. Catalyst advises managers to avoid using those cues to distribute development and to track advancement opportunities, sponsorship, and stretch assignments rather than leaving access to informal patterns. Catalyst’s manager guidance for inclusive hybrid work makes the practical case for looking beyond who happens to be most present or most familiar.

Exposure without decision rights may teach observation, but it rarely builds ownership.

Make the decision explainable without turning it into a ranking

You do not owe the team a public account of every person’s development goals or current capacity. You do owe them a credible process. When assignments repeatedly go to the same people with no explanation, colleagues will create their own explanation, often correctly identifying that access follows familiarity rather than a clear standard.

Announce the work and the roles in terms of the work itself: “Priya is coordinating delivery because she has handled this system before. Mateo will lead requirements decisions with our partner teams. June will own the validation proposal and walk us through the recommendation next week.” This communicates that there are distinct responsibilities and that more than one person is trusted with meaningful work.

Then speak privately with people who were not chosen for the largest role. Avoid vague reassurance such as, “You’ll get your chance.” It asks them to trust a future you have not defined. Instead, name the relevant evidence, the gap that affected this assignment, and the next action you will take together.

You might say: “I chose Priya to coordinate this one because the deadline is tight and she has led this exact integration. I do not read that as a ceiling on your scope. You told me you want to build cross-functional leadership, so I would like you to lead the partner-team requirements work. We will review how that went in three weeks and look for the next project where you can own a larger end-to-end piece.”

The difference is concrete. You are neither promising a promotion nor asking someone to become more confident. You are connecting a current decision to observable experience and a next opportunity.

Sometimes the right next move is sponsorship rather than another internal task. Sponsorship is not generic encouragement. Catalyst defines it as a senior or influential person using their standing to help someone gain access to high-visibility assignments, roles, or promotions. Catalyst’s explanation of sponsorship draws a useful line between advice and advocacy. If your employee has done work worth seeing, introduce them to the leader who needs that context, name their contribution in the relevant room, or recommend them for a specific opportunity. Do not claim credit for creating access if all you offered was private praise.

Review the assignment as a team practice, not a one-time favor

A stretch assignment should have a beginning, a midpoint, and an ending. Without those points, it can become a vague extra responsibility that lingers after the learning value has disappeared.

At the start, agree on the decision rights, check-in rhythm, and escalation threshold. At the midpoint, ask what the person has learned, what is still unclear, and whether the scope is still challenging in the intended way rather than simply unmanageable. At the end, discuss the result and the process separately. A successful delivery can still reveal that the employee needs more practice with stakeholder conflict. A missed target can still show strong judgment, early risk-spotting, or an ability to recover from a poor assumption.

Record the evidence from the assignment in your opportunity map. This is especially important if performance reviews happen months later. “Demonstrated clear technical leadership” is easy to forget and hard to use. “Led the validation recommendation, revised it after finance raised a risk, and presented the final decision to the steering group” gives both of you something concrete to build on.

Once a quarter, review the map for concentration. Who has had exposure to senior leaders? Who has repeatedly handled invisible maintenance work? Who has been given decision-making practice, and who has only been asked to assist? You are not looking for identical histories. You are looking for unexplained gaps and a next decision you can change.

A promise to revisit someone’s growth needs a date, an assignment type, and a manager who will remember.

Run the next assignment with a clear agreement

• Write the outcome, developmental purpose, decision rights, and support before naming an assignee.
• Ask each team member what capability or type of responsibility they want to build during the next quarter.
• Choose whether the work needs one owner, a defined workstream, or a separate exposure opportunity.
• Tell selected people why the role fits their current evidence and what support is available.
• Give unselected teammates a specific next action instead of an open-ended promise.
• Hold a midpoint check-in that addresses both delivery risk and learning value.
• Review the distribution of visible, invisible, technical, and cross-functional opportunities every quarter.

The next time a prized assignment appears, ask yourself one practical question: if a teammate asked how this decision was made, could you explain the work, the evidence, and the support plan without comparing people’s worth? If the answer is yes, you have a decision the team can learn from—even when not everyone gets the role they wanted.

• Write the outcome, developmental purpose, decision rights, and support before naming an assignee.
• Ask each team member what capability or type of responsibility they want to build during the next quarter.
• Choose whether the work needs one owner, a defined workstream, or a separate exposure opportunity.
• Tell selected people why the role fits their current evidence and what support is available.
• Give unselected teammates a specific next action instead of an open-ended promise.
• Hold a midpoint check-in that addresses both delivery risk and learning value.
• Review the distribution of visible, invisible, technical, and cross-functional opportunities every quarter.