If asking someone to do their job feels uncomfortable, the role is already broken.
This is a structural failure, not a communication one. In a functioning team, delegation is invisible -- it's the default rhythm of work. When it starts requiring courage, something upstream has failed: role clarity, capability fit, or mutual trust. Usually you know which one. That's why the ask feels awkward.
The Absorption Trap
The instinct is to route around the problem. "I'll just do it myself -- it'll be faster." This is true exactly once. After that, it compounds. Every time you absorb someone else's scope, you erode the mapping between titles and contribution. The team learns the real org chart without anyone saying it out loud. Accountability becomes a polite fiction.
Worse, the person whose work you're absorbing doesn't experience the consequence of their gap. They experience stability. The feedback loop that might have forced growth or forced a conversation gets quietly disconnected.
Coaching Moment or Replacement Moment
The diagnostic matters. A clarity gap looks different from a capability gap, and the interventions are opposite. Clarity gaps respond to explicit expectations, written scope, and short feedback cycles. Capability gaps don't. Investing six months of coaching into a capability mismatch doesn't develop the person -- it delays the decision you already know you need to make.
Most leaders frame this as a binary: coach or fire. The more useful question is temporal. If you gave this person perfect clarity and three months, would you bet on them closing the gap? If the honest answer is no, the kindest move -- for them and for the team -- is to act on that now.
The Tell
The discomfort itself is the signal. You don't hesitate to ask a strong performer to take on their responsibilities. The hesitation means your subconscious has already made the assessment. The rest is just mustering the will to act on it.
Stop absorbing. Start diagnosing.