“The output of a manager is the output of the organizational units under his or her supervision or influence.”
Andy Grove, High Output Management
One of the harder leadership calls is deciding who should take on important work. The easy answer is to give the hardest project to the strongest person, and sometimes that is exactly right. If the work is urgent, company-critical, politically delicate, or on the critical path for several other teams, the business may need the highest-confidence execution you can assemble.
If that is always the answer, though, nobody else grows. Meaningful projects start collecting around the same few trusted people: the tech lead, the senior engineer, the reliable person who can rescue almost anything. The work gets done, but the organization quietly becomes more dependent on a small group. You have delivery, but not development; output, but not bench strength.
Growth Is Part Of Delivery
It is tempting to treat people development as something separate from delivery: first the team gets the work done, then people grow when things calm down. The trouble is that things rarely calm down long enough for that plan to work.
People develop through real work: projects with stakes, decisions with consequences, ambiguity they have to navigate, and feedback that arrives while the work is still alive. That does not mean every project should become a stretch assignment. It means leaders have to treat growth as part of the system.
Not Every Project Is A Good Stretch Project
Some work carries too much immediate risk to use as a learning vehicle. If a project is on the urgent critical path for multiple teams, has a narrow launch window, carries a major customer commitment, or has very little room for correction, the company may need the strongest possible lead, not the person who would benefit most from the experience.
Growth work still has to be real work.
That is not a failure to develop people; it is part of the judgment. The mistake is turning that judgment into a permanent excuse. If every project is too important for anyone new to lead, the organization has no safe way to build new leaders.
What Makes A Good Growth Opportunity
A good stretch project is not just a harder project handed to a less experienced person. It usually has a few helpful traits:
- Real importance. The work matters enough that the person can feel the impact.
- Manageable blast radius. If things go sideways, the damage is recoverable.
- Clear support. The person has access to a manager, tech lead, mentor, or experienced partner before the work is off track.
- Stable cross-functional support. Partner teams understand the goal and can engage consistently.
- Visible decision points. There are moments where the person can practice judgment, not just execute a checklist.
- Enough time to learn. The schedule has room for feedback, correction, and iteration.
You do not need every one of those conditions for a stretch assignment to work. But a project with none of them is higher risk, and that risk may not be obvious until the person is already struggling. The project should be real enough to teach something, with enough support that the person has room to learn.
Focus The Stretch
One of the best ways to calibrate growth is to notice how many dimensions are stretching at once. Someone can stretch technically, in ambiguity, in stakeholder communication, in project leadership, in planning, or in risk management. More than one may be new, but it helps to know which dimension is the primary stretch and which parts of the work need stability.
A good stretch assignment has a primary stretch and enough stability around it.
A good stretch assignment might pair technical challenge with a simple stakeholder environment, or project leadership with a familiar technical surface area. It might give someone cross-functional responsibility with a senior engineer nearby for architectural support.
The question is where discomfort will help them grow, and where stability will help them succeed.
The Strongest Person Still Has A Role
Growing someone else does not mean removing your strongest people from the system. Often the better move is not to give the whole project to the most senior person, but to use that person differently. They can review the plan, identify risks, coach the person doing the work, join key design reviews, or act as escalation support.
That kind of support lets someone else lead with real guidance nearby. The senior person is still helping protect the work, but they are also helping build the next person who can carry more responsibility.
Choose Project Leads Based On Urgency And Importance
Stephen Covey’s urgent-important distinction is useful here. When work is both urgent and important, that is often the moment for your stars. The fire is real, the timing matters, and the cost of being wrong may be high.
Non-urgent but important work can be a much better candidate for development. It still matters, but the schedule usually leaves more room for planning, feedback, correction, and support.
The development you skip today becomes the capacity problem you create for tomorrow.
If development is ignored long enough, it becomes urgent in the worst way: a key person leaves, a senior engineer burns out, the same bottleneck appears every planning cycle, or a team has nobody ready to take on the next level of work.
Questions Before Assigning Stretch Work
When assigning work, “Who is the safest person to give this to?” is a fair question, but it is incomplete.
Better questions are:
- How critical is this project, really?
- What is the cost of being wrong?
- Who would grow from taking it on?
- What support would make that responsibility reasonable?
- What part of the work must be senior-led, and what part can be delegated?
- If this kind of work always goes to the same person, what capability are we failing to build?
Those questions keep delivery and development in the same conversation, even when the right answer is still to put your strongest person on the work.
Deliver And Develop
When leading a team, I try to balance what is best for the company in the short term with what builds the team for the long term. That means growing individual contributors through meaningful and challenging work while recognizing that some assignments carry more risk than others.