How to Choose a Stretch Assignment That Builds Your Career

A stretch assignment should give you a chance to practice a capability you need next. More work alone does not make an assignment developmental. Before accepting, clarify what you will learn, which decisions you will own, who will support you, and what will change in your existing workload. The best choice connects a real business need with a specific development goal and enough support to learn while delivering. Use the questions and assignment brief below to assess an opportunity before you commit, then keep a record of what the experience actually taught you.

Name the capability before choosing the project

Start with the responsibility you want to handle more effectively. You might need experience setting a project’s scope, coordinating several teams, presenting a recommendation to a decision-maker, coaching a colleague, or working through an unfamiliar customer problem. “Gain exposure” is too vague to tell you which assignment fits.

Use a recent example or feedback conversation to define the gap. If your manager says you need broader influence, ask whether that means involving another team earlier, handling disagreement, or securing a decision. The answer changes which opportunity will give you useful practice.

The Center for Creative Leadership’s guidance on experience-driven development describes challenging assignments as a way to learn through unfamiliar responsibilities and situations. It also emphasizes support, reflection, and feedback. That is the basis for evaluating both the challenge and the conditions around it. An assignment can be demanding without being well designed for learning.

Look for a decision you will actually get to own

Ask what you will be trusted to decide. A project can sound senior while giving you only administrative responsibility. Coordinating calendars for a strategic initiative is different from comparing options and recommending its scope. Both may be necessary work, but they develop different capabilities.

In a fictional example, an engineer wants to practice technical leadership. One opportunity asks her to handle extra implementation tickets. Another asks her to define the migration options, gather input from dependent teams, and recommend the sequence with an experienced lead available for review. The second has a clearer connection to the capability she wants to build.

Do not dismiss an assignment because it is small. Owning a bounded decision from beginning to end can provide better practice than attending a large initiative without responsibility for an outcome. Ask whether you will be able to explain what you chose, why you chose it, and what happened afterward.

Check the support and the cost to your current work

Find out who will provide context, review early decisions, and help when the assignment reaches the limits of your authority. A sponsor should be able to help resolve access or priority problems. A coach or experienced colleague should have enough time to discuss the work. Sometimes one person fills both roles; confirm what support they can actually provide.

Then discuss capacity. Which existing commitment will move, shrink, or be handed over? How much time is available? If the answer is that everything stays the same, examine whether the proposed scope is realistic. A development opportunity should not rely on an indefinite promise to absorb extra hours.

You can say, “I want the experience, and I can take responsibility for the pilot. To do it well, I would need to hand over the weekly reporting task or reduce the pilot to one team. Which adjustment makes sense?” This expresses interest while making the tradeoff visible.

Use these questions before saying yes

Review the opportunity with your manager or the person proposing it. You do not need a numerical score. Clear answers reveal the strengths and gaps in the assignment more effectively than a total that hides a missing sponsor or an impossible workload.

• Learning: Which specific capability will I practice, and why does it matter for my direction?
• Business need: Who needs the result, and what problem does it solve?
• Ownership: Which decisions and deliverables will I own?
• Boundaries: What remains outside my authority or the project’s scope?
• Support: Who can advise me, review early work, and remove obstacles?
• Capacity: Which existing responsibility will change to make room?
• Feedback: Who will observe the work and tell me how it is going?
• Finish: When will we review the result and decide what happens next?

If several answers are missing, negotiate the assignment before rejecting it outright. A broad, undefined request may become useful when you narrow the deliverable, name an approver, and add two review points. If nobody can provide the authority or support the work requires, the opportunity may need to wait.

Watch for moving finish lines. “Help until the process is fixed” can become a permanent extra responsibility. Define the initial phase and what completion means. If ongoing ownership is needed afterward, make that a separate discussion about role scope and workload.

Write a brief that joins delivery and development

Record the agreement in a place the participants can revisit. The brief should explain both the business outcome and the capability you are practicing. This makes it possible to discuss learning before the final result arrives.

• Assignment: Lead the next customer-research pilot for one product area.
• Delivery outcome: Produce a recommendation the product lead can use for the next planning decision.
• Development goal: Practice defining a research question and guiding a discussion across Product and Support.
• Authority: Own the interview plan; confirm external commitments with the product lead.
• Support: An experienced researcher reviews the plan and attends the first synthesis discussion.
• Capacity change: Another analyst takes the recurring reporting task during the pilot.
• Checkpoints: Review the research question before interviews and the recommendation before presentation.
• Closing review: Discuss the result, feedback, and next development step after the planning meeting.

This example is fictional. Its value is the relationship between the goal, actual responsibilities, support, and review. Replace each line with an agreement that is true for your work. A polished brief cannot compensate for participants who have not accepted the commitments written into it.

Learn during the assignment, not only at the end

Before an unfamiliar step, write down what you intend to try and what you want feedback on. Afterward, record what happened and what you would change. A few lines can help you distinguish a deliberate improvement from something that merely became easier through repetition.

For example, before the synthesis discussion, you might decide to separate observations from recommendations so contributors can challenge the evidence first. After the meeting, ask whether that structure made the choice clearer. Save both the useful feedback and the part that still needs work.

Use checkpoints to adjust the assignment itself. If the scope grows or a key supporter becomes unavailable, revisit the agreement. Learning through uncertainty does not require pretending the original conditions still exist. Raising the change early is part of taking responsibility for the work.

Close with evidence, including the unfinished parts

At the end, review delivery and development separately. The project may meet its business goal while revealing that you need more practice handling disagreement. It may also encounter a constraint outside your control while giving you meaningful experience in planning or decision-making. Explain both without treating either as the complete story.

Prepare a short account: the responsibility you took on, the decisions you owned, the support you used, the outcome, and the feedback you received. Identify what you can now handle more independently and where you still need guidance. “Completed a stretch assignment” tells a reviewer much less than this specific evidence.

Ask what follows. Does the experience support a broader responsibility, another focused assignment, or a change to your development plan? Avoid assuming that an assignment guarantees a promotion. Clarify how the organization evaluates the evidence and which additional conditions apply.

Bloomly can help keep your entries, feedback, and selected supporting material with the relevant Role. Use the record to prepare for the closing conversation while the details are fresh. Keep your contribution distinct from the work of teammates and include the lessons you would want to remember before accepting a similar challenge.

Choose a stretch assignment by the capability it lets you practice, the decisions you will own, and the support available. Make room for it in your workload and agree on a finish point before you begin. During the work, ask for feedback and record what changes in your approach. At the end, you should be able to describe both the result and the responsibility you can now handle more effectively. That is a useful basis for choosing the next step in your career.