Growing Your People's Skills

In a small team, growth happens through the work itself. When you stretch someone without breaking them, you hand them a task that is slightly beyond what they

Level: Manager
Setting: Small team
Core skill: Stretch without breaking
Common pitfall: Only assigning easy work
Practice to try: A next-step development plan

What this looks like in real work

In a small team, growth happens through the work itself. When you stretch someone without breaking them, you hand them a task that is slightly beyond what they have done before, but not so far that they drown. It looks like giving a team member the lead on a small project that requires them to coordinate with one other person, when they have only ever managed their own tasks. Or asking someone to present their work to a client for the first time, with you sitting in the background. The stretch is real, but the safety net is invisible to others and obvious to the person growing.

You might see this when a junior designer is asked to run a feedback session, or when a quiet analyst is invited to facilitate a team meeting. The key is that the person has enough support to ask questions, make a few mistakes, and recover. In a small team, you cannot always create formal training programs, so the work becomes the curriculum. Your job is to choose assignments that build one new muscle at a time, not to throw someone into the deep end and hope they swim.

This also means you are paying attention to signals. You notice when someone is energized by a challenge versus when they are quietly panicking. You check in more often, but you do not hover. You let them own the outcome while you own the guardrails. That balance is what makes stretching sustainable rather than stressful.

Why it trips people up

Managers often fall into the trap of only assigning easy work because it feels safe. Easy work gets done quickly, with fewer errors, and it keeps the team running smoothly in the short term. When you are responsible for results and your team is small, the temptation to give every task to the person who already knows how to do it is enormous. You tell yourself you are being efficient, but you are actually starving your people of the experiences they need to grow.

Another reason this trips people up is that stretching someone requires you to tolerate discomfort. You have to watch someone struggle, ask questions you already know the answers to, and resist the urge to take over. That can feel like you are not doing your job. In a small team, there is no hiding behind layers of management, so your own anxiety about deadlines and quality can push you to play it safe. You might also worry that if you challenge someone and they fail, they will blame you or lose confidence.

Finally, many managers were never taught how to calibrate stretch. They either keep everyone in their comfort zone or they overcorrect and assign work that is far too advanced. The sweet spot is a moving target, and it changes from person to person and week to week. Without a deliberate approach, you default to what is easiest for you, not what is best for them. That is why the pitfall of only assigning easy work is so common, even among well-meaning leaders.

The mistake that quietly hurts

The mistake of only assigning easy work does not announce itself. There is no dramatic failure or obvious complaint. Instead, it shows up as boredom, disengagement, and eventually turnover. Your most capable people start to feel like they are not learning anything new, and they begin to look elsewhere for growth. Meanwhile, the people who could develop with the right challenge never get the chance, so their skills plateau. The team as a whole becomes fragile because only a few people can handle the difficult work.

In a small team, this mistake is especially costly because you cannot afford to have bottlenecks. If only one person knows how to run a certain process or handle a certain client, you are one vacation away from a crisis. By always giving easy work to the same people, you inadvertently create silos of knowledge and dependency. The quiet hurt is that you are not building a resilient team; you are building a team that relies on you to make every tough call.

Over time, this erodes trust. People sense when they are being underestimated. They may not say it directly, but they notice when challenging projects always go to someone else. They stop volunteering for new things because they assume they will not be chosen. The result is a team that plays it safe, avoids risk, and stops growing. By the time you realize what has happened, you may have already lost your best people, and the ones who stay may be the ones who are comfortable doing the same thing forever.

A practice you can repeat

One concrete, repeatable practice is to create a next-step development plan for each person on your team. This is not a formal HR document or a yearly review. It is a simple, living note that you keep for yourself and update every few weeks. For each person, write down one skill they are ready to stretch next, one specific type of task that would build that skill, and one support you will provide to keep them from breaking. The plan should be small enough to act on within the next month.

To use it, start by observing your team members in their current work. Ask yourself: what is the next logical challenge for this person? For example, if someone is great at executing tasks but has never led a project, the next step might be to let them plan and run a small initiative with a clear deadline. If someone is strong analytically but avoids speaking up in meetings, the next step might be to have them present a short update to the team. Write it down, then look for an upcoming piece of work that fits.

Once you have identified the opportunity, schedule a brief conversation to offer it. Explain why you chose them and what support they will have. Then, follow through by checking in regularly, but resist the urge to solve problems for them. After the task is complete, debrief together: what went well, what was hard, and what they want to stretch next. Update the plan and repeat. This cycle turns everyday work into a development engine, and it ensures you are not defaulting to easy assignments.

What to say and do

When you offer a stretch assignment, be clear about why you are asking this person and what kind of support they can expect. You might say, "I have a project coming up that I think would be a great next step for you. It involves coordinating with two other people, and I will be available to help you think through the plan." This frames the challenge as an opportunity, not a burden, and it signals that you are not abandoning them. Another phrase that works well is, "You have shown real strength in this area, and I would like you to take on a bit more responsibility. Let us talk about what you need from me to make it a success."

As they work, your actions matter as much as your words. Check in at agreed intervals, but do not micromanage. Ask questions like, "What is feeling tricky right now?" and "What is your plan for the next step?" rather than giving answers. If they make a mistake, treat it as a learning moment. You could say, "That did not go as planned, but here is what we can learn from it. What would you do differently next time?" This keeps the focus on growth rather than blame.

Finally, when they succeed, praise the specific stretch they took. Say, "I noticed how you handled that difficult conversation with the client. That was a real step up from your usual work, and it made a difference." This reinforces that you see their effort and that you value their development. If they struggle, reassure them that struggling is part of learning. "This is new territory, so it is normal to find it hard. Let us break it down together." Your consistent presence and belief in them are what make the stretch safe.

When the stakes get higher

As your team takes on more important work, the consequences of stretching someone too far become more serious. A mistake on a low-stakes task is a learning opportunity; a mistake on a high-stakes project can damage trust with a client or set the team back significantly. In these moments, you need to adjust your approach without abandoning development. The key is to increase the support and structure around the stretch, not to remove the stretch entirely. You might pair the person with a more experienced colleague, set more frequent checkpoints, or define clear boundaries for decisions they can make on their own.

When the stakes are high, be explicit about what success looks like and what the guardrails are. For example, you might say, "This client presentation is important, so I want you to lead it, but we will rehearse together twice beforehand, and I will be in the room to step in if needed." This gives the person a real chance to grow while protecting the outcome. You are not setting them up to fail; you are setting them up to succeed with a safety net. Over time, as they prove themselves, you can gradually remove the supports.

It is also important to recognize when the stakes are too high for a particular stretch. Not every opportunity is a good development opportunity. If the risk of failure is catastrophic and the person is not ready, it is wiser to give them a smaller stretch elsewhere and save the high-stakes task for someone with more experience. That is not a failure of your leadership; it is good judgment. The goal is to stretch without breaking, and sometimes that means choosing a different mountain to climb first.

Questions new leaders ask

Q: How do I know if a task is a stretch or too much? A: Look for signs of manageable discomfort. A stretch feels challenging but exciting; the person has some relevant skills and can ask for help. Too much feels overwhelming, and the person lacks the foundation to even start. When in doubt, start smaller and increase difficulty as they gain confidence.

Q: What if the person fails at the stretch assignment? A: Failure is part of learning, as long as it is not catastrophic. Debrief together, focus on what can be learned, and adjust the next step. If you provided support and they still struggled, that is information about where they need more development, not a reason to stop stretching them.

Q: How often should I be stretching my team members? A: There is no fixed schedule. Aim for a rhythm where each person has one meaningful stretch opportunity every few months, with smaller challenges in between. Pay attention to their energy and workload; stretching should not lead to burnout. The next-step development plan helps you keep track and rotate opportunities fairly.