|
Next to Nunn
Between the Work and the People
Erinn Gomillion | Leadership Development Partner
|
| Edition No. 2 | November 3, 2026 |
Why Your Strongest Person Is Doing Everything |
| Who gets the hard assignment, and why. |
| This edition looks at what happens when the same person gets every escalation, why it feels like good management, and how to match each assignment to both the work and the person. |
|
The Scenario |
| An escalation lands in your inbox at 4:45 PM on a Wednesday afternoon. The account is large, the customer is upset, and the details are messy. |
| You finish reading the first paragraph, and you already know who you are sending this to. You open a message to the same person who handled the last crisis, and the one before that. They say yes without hesitation, the way they always do. By midday Friday, the issue is resolved, and resolved well. You head into the weekend relieved that it is off your plate. |
| What you might miss is that putting out that fire took time from a strategic initiative your top performer is leading. They logged off late on Friday evening, exhausted, while the rest of the team logged off on time, having handled only routine tasks. |
Why This Feels Like Good Management |
| From the outside looking in, nothing looks broken. The work gets done, and it's easy to assume top performers are supposed to carry more. The customer is satisfied. Other departments know your team is reliable. Sometimes your strongest person really is the right fit because the situation demands their exact level of experience. But there is a massive difference between selecting someone with intention and defaulting to them out of habit. Those two choices look identical on a Friday afternoon, but they yield completely different results by the time annual reviews roll around. |
| Developing your team doesn't mean routing work to whoever can finish it fastest. Real development requires evaluating both the assignment and the individual, matching work based on capability, timeline, strategic risk, and growth goals. |
What Does "Right Fit" Actually Mean? |
| A solid assignment decision balances two distinct questions: |
| Fit for the work: What does this specific task demand: technical mastery, high-level judgment, key stakeholder relationships, or raw time? |
| Fit for the person: Where does this team member stand right now, and what does their development plan say they need to stretch into next? |
When You Only Ask About the Work |
| The work always lands on the person who has already proven they can do it. Your top performer stacks high-stakes problem-solving on top of their full-time role. A pace that looks sustainable in October turns into quiet burnout by March. Their growth plan might say they are ready to step into leadership, but the endless stream of tactical fires might be keeping them trapped in execution. |
| Meanwhile, the rest of the team remains on autopilot. Everyone quickly learns what you actually trust them to handle. Your entire operation becomes fragile: one resignation, one medical leave, or one bad week stalls everything that matters. |
When You Only Ask About the Person |
| The work always lands on the person with the "most potential," the enthusiastic team member who eagerly raises their hand for every challenge. But what happens when you hand that person a complex project that requires deep institutional knowledge or relies on delicate cross-functional relationships they haven't built yet? |
| Without the proper foundation or backing, they stumble, the client suffers, and you end up stepping in to salvage it anyway, reinforcing your belief that you should have just given it to your star performer in the first place. |
What Is Yours to Own |
| Before deciding the solution is simply to give everyone else harder work, look at where this habit actually comes from. It usually lives in one of three areas: |
| People. Ask yourself: Are you avoiding giving work to others because you genuinely doubt their capability, or because you want to avoid the time and patience it takes to coach them through it? A concern based on a mistake someone made eighteen months ago, or on how they handle boring, routine tasks, is just an assumption. Furthermore, if you cannot state in one clear sentence what each person on your team is building toward this quarter, you cannot delegate strategically. |
| Communication. Have you told each person what they are building toward, and why a stretch assignment went to someone else? When the last escalation went to your strongest person, did they know it was a choice, or did they assume it was theirs again? High performers often stay quiet longer than they should, so their silence doesn't mean the load feels fair. |
| Systems. Is your team structured to absorb unexpected, high-priority work, or does assigning an escalation feel like throwing a wrench into a delicate machine? Who has visibility into everyone's current bandwidth? If your team doesn't have clear, shared answers to these questions, every urgent task will automatically default to the person you trust the most. |
What to Do Before You Assign It |
Start with the assignment, then check the plan. |
| Before deciding who gets a project, write down what the work strictly requires. Then look at your team's development goals and ask who needs this experience next. If clear development goals don't exist yet, fix that first. It starts with one direct conversation with each person about what skills they need to sharpen this year. |
Put real structure around stretch assignments. |
| When you hand someone a task that stretches them, don't just hand over the work. Hand over the safety net. Explain why they are receiving the assignment, how it connects to their goals, what a successful outcome looks like, who they can lean on for advice, and when you will review their initial draft together. A stretch assignment without support isn't development; it's a trap. |
Reposition your strongest person. |
| Sometimes the right answer really is your top performer. But if their development plan involves moving into leadership, stop having them solve the problem directly. Have them coach another team member through it instead. That turns a routine fire into a double development opportunity: one person learns how to handle escalations, and your star learns how to lead. |
The Leadership Check Who on your team have you stopped giving critical work to, and what conversation are you avoiding with them? |
|
Two Moves for This Week Audit your recent handoffs: Look back at your last five high-stakes or difficult assignments. Write down who got each one. Beside each name, note whether that choice was based on a fit for the work, a fit for their growth plan, or pure habit. Design a supported handoff: Pick one upcoming assignment that you would normally default to your strongest person. Identify another team member whose growth plan aligns with that work, and outline the exact support checkpoints you will put in place before you hand it over. |
|
Closing |
| Your strongest person isn't the issue. They are doing exactly what you have trained them to do. The question is whether your delegation is driven by a clear plan or by habit. |
| Handing someone work they haven't done before feels risky, and it usually is. But defaulting to the same person every time carries a far bigger risk, one that stays hidden until your best person burns out or your team loses the capacity to operate without you. |
| If you're working out who on your team should take on the next hard assignment, send me a message and tell me which handoff you're weighing. |
| At Next to Nunn, I help leaders build strong teams and step fully into their leadership role. |
| To get Between the Work and the People as each edition comes out, subscribe here: https://api.leadconnectorhq.com/widget/form/vjbvXlHnVAEJakPZDnun |
 |
|
|
Privacy Policy | Terms of Use | Unsubscribe
|