Does "want a hand?" trigger a reflexive "no, I've got it"? Carrying everything alone isn't just competence — why the hands won't let go differs by person.
Your to-do list is, once again, the only long one. Work rains down in the meeting and half of it has somehow become yours; a teammate offers 'should I take that?' and 'no, I'll do it' is already out. Then it's ten p.m. at the office — why is it always me with this much work? The answer, cruelly, is that about half of it is your own construction.
Three different reasons live in the gripping hand. The person anxious when work leaves their sightline — once it's out of their hands, neither quality nor progress is visible, so they choose the tired body over the blind spot: the eyes-on type. The person unsatisfied by anyone else's output — 'by the time I've fixed it, I could have done it from scratch' runs the numbers: the re-doer. And the person for whom asking is an imposition — handing work over feels like dumping a burden, so they choose overtime over a request: the burden-shy.
The cost of carrying alone isn't just your own burnout — the team loses its chances to grow, the organization becomes a machine that doesn't run without you, and that machine tightens around you in turn. This page finds why your hands can't release the work, then fits the first button of delegation to each type.
At a glance — which engine is yours
Type
One-line scene
Eyes-on
“Out of Sight, Unbearable”
Re-doer
“Easier to Redo It Myself”
Burden-shy
“The Ask That Won't Come Out”
ENGINE 1 · Eyes-on
“Out of Sight, Unbearable”
Why this engine runs
This person's inability to hand work over isn't about the receiver's skill. It's the state of work rolling along outside their sightline that they can't endure. From the moment of handover, they can no longer see how far it's come, what's gone sideways, when it will land — and the anxiety rising out of that invisible stretch weighs more than the fatigue of just holding on. So even after delegating, the casual status-check creeps in, and eventually the hands go back on. Over time, every thread in the operation gathers into their one hand: they end up sitting alone in the seat that sets the team's pace, and every backlog reconfirms 'see — it only runs when I'm watching.' That certainty makes the next handover harder, and the loop sets. The re-doer next door redoes because the output can't be trusted; the burden-shy can't open their mouth to ask; this person stops before quality is even in question — at one thing: the blind gap where progress can't be seen.
If these scenes feel familiar
A rush job comes in; they start walking a junior through it, then mid-explanation — 'faster to just do it myself' — and the file comes back. It isn't the handover time they can't afford; it's the hours afterward of not knowing what's happening. On a long-awaited vacation, the laptop opens. Everyone's surely handling it — but where exactly is it? Only the screen can settle that, and each unchecked day winds the restlessness tighter. The assignment chart shows work divided evenly; trace the actual flow of tasks and their name hangs at every critical junction. Everyone does their piece — and somehow a structure has assembled where nothing ships without passing through them.
What switches it on — and off
Fires hardest under tight deadlines and where a slip shows immediately — work whose consequences land straight on them, structures where mid-flight checks aren't possible. Loosens when progress becomes visible automatically at set intervals: with standing sightlines in place, the room to not intervene appears. When they can trust that any moment they want to look, the status will be there — the urge to repossess quiets down.
How it gets misread
People read work-greed, or distrust — and the junior, checked on again and again, hears 'you don't rate me.' But inside, it isn't skill being doubted. It's the anxiety of the unwatched interval, carried alone: not holding people captive — just never having found a way to endure the invisible hours.
The smallest lever
For this person, what works isn't results-only delegation — it's installing a dashboard where progress surfaces on schedule. A short status shared every other day, say: the anytime-interrogation converts into scheduled observation. The fuel of the anxiety — the invisible stretch — gets filled in, and the repossession urge loses its grounds. The key isn't revoking the right to watch; it's converting the real-time grip into a planned lookout. Install the same dashboard for the re-doer and the outcome differs completely: with progress in full view, an interim result under their bar still gets rebuilt from scratch — visibility alone doesn't stop the take-back. The seeing prescription earns its keep only where not-seeing is the anxiety.
When this reading doesn't fit
If progress in full view brings no ease — and the returned work keeps you up all night re-touching it line by line — this isn't your engine. Caught not on visible-or-not but on good-enough-or-not: the Re-doer's description will sound like your own story.
Grounding: Intolerance-of-uncertainty research — difficulty enduring states where the outcome cannot be known
ENGINE 2 · Re-doer
“Easier to Redo It Myself”
Why this engine runs
This person does hand work over. But when the returned output misses their bar, they don't patch the weak spots — they rebuild from zero. Which is how everything ends up back on their desk. The jam isn't 'I can't see the progress'; it's the verdict 'they won't hit my level' — a conclusion reached before the handover even happens, so the delegating quietly gets abandoned in advance. And when delegation does happen, the inspection step finds the shortfall and the hands go in; shipping it as-is isn't survivable. Over time the team learns: 'why bother, when it gets redone anyway' — and starts submitting rougher work, which becomes fresh evidence for 'see? can't trust it,' and both sides ratchet their expectations down in lockstep. The eyes-on type stalls at an invisible process; this person stalls at a finished product sitting in plain view — at its level. The burden-shy can't hand over for guilt; this one hands over and takes it back, on quality.
If these scenes feel familiar
A junior brings work over — 'I think it's done' — and the file gets opened with modest intentions: fix a couple of spots. But touching one part snags the eye on the next, and eventually every sentence and every figure has been re-set by hand. It was labeled review; it ended as a rewrite. The all-nighters on delegable work don't start from distrust either: the afternoon's submission was too rough to ship, and pulling it up to the bar became indistinguishable from starting over. Next day the junior hears 'I was in a rush, so I just did it' — but the real sequence started with a verdict: not at that level, not going out.
What switches it on — and off
Fires hardest on work that carries their name and will be seen and judged — and where standards are crisp and defects show plainly, the redo urge runs strongest. Loosens when a pass-line is fixed in advance — 'this clears at eighty' — and pinned so it can't creep. Also when the deadline flatly outranks polish and rebuilding is physically off the table.
How it gets misread
People say it plainly: trusts no one, hoards the work. The junior, watching every submission get razed, loses the will to try. But this person's center of gravity is the artifact, not the person — not malice; an inability to ship what's below the line. In their own head it rarely registers as taking someone's work. It registers as responsibility: my name is on this, and it cannot go out like that.
The smallest lever
What works here is exempting work from a single universal maximum standard. Before handing anything over, pre-sort it: 'this one passes at eighty' versus 'this one I see through to the end.' On delegated work, the inspection bar is set lower and pinned there — which severs the creep that ratcheted the standard up mid-review. The point isn't abandoning standards; it's drawing the line before the work, so opening the file doesn't re-launch the bar. Give the same device to the eyes-on type and the picture changes: lower their inspection standard all you like, the anxiety of the unseen process remains, and the hands reach back regardless. The lowered-bar prescription works only where the jam is the level.
When this reading doesn't fit
If the output quality is genuinely fine and what's unbearable is not knowing where the delegated work stands right now — checking, checking, and pulling it back — the snag isn't quality. Re-read the Eyes-on description; that one's yours.
Grounding: Self-oriented perfectionism research — self-imposed maximal standards, applied to the delegation setting
ENGINE 3 · Burden-shy
“The Ask That Won't Come Out”
Why this engine runs
This person's grip on the work comes from neither doubted skill nor invisible process. The act of asking itself registers as 'stacking one more load on a busy person's back' — and the mouth won't open. They pre-feel the burden the other person would feel, as if it were their own; weighed against that imagined load, enduring a bit more themselves is simply more comfortable. So instead of one sentence — 'could you help?' — they choose the overtime. Over time, the seat hardens: 'that one handles everything alone, always has.' The room takes the devotion for granted; not-assigning-to-them becomes the default; and the overload becomes structural, stacked on one person. The eyes-on type stops at the unseen process, the re-doer at the untrusted output — this one stops at the instant of forming the request, where the flicker of inconvenience crossing the other person's face is already visible, and the words get swallowed.
If these scenes feel familiar
Work that would end on time if the deskmate took a slice of it — swallowed instead, with 'they're busy too; I can't ask this of them,' and the night shift begins alone. One sentence of asking weighs more than several hours of overtime. The all-nighter on delegable work isn't about the deliverable either: all afternoon, 'could you take this?' rolled around the mouth — then the other person's tired face surfaced, and it went down unspoken, and everything stayed in their arms. At the team dinner, asked 'why didn't you say something?' — 'oh, it was nothing,' with a laugh. It wasn't nothing. Imposing was the thing that couldn't be done.
What switches it on — and off
Fires hardest when the other person looks visibly busy, or is someone who struggles to refuse — and the closer and more ongoing the relationship, the longer the 'I imposed' feeling lingers, the tighter the words get rationed. Loosens distinctly when the work is clearly the role's own share rather than a personal favor — with the human ask removed, the guilt has nowhere to sit, and speaking gets easier.
How it gets misread
People see responsibility incarnate — handles everything, never complains, must be fine. But under the visible devotion sits an inability to transfer weight to another human being. It isn't love of work driving the accumulation; it's swallowing, on everyone's behalf, the discomfort that asking creates. And in situations where help is plainly warranted, the license to receive it is the one thing they can't issue themselves.
The smallest lever
What works here is stripping the request-format off entirely. Route the work so it moves not as a personal plea — 'could you do me a favor?' — but as a role matter: 'this task belongs to that seat.' The human frame that guilt needs in order to interfere disappears; instead of leaning on the relationship, the defined role carries the work, and what used to be swallowed as overtime flows to its proper place. Carried over to the eyes-on type, this doesn't hold: divide by roles as cleanly as you like, the anxiety of unseen progress pulls the work back within weeks, and the carefully built division collapses. Deleting the ask-frame endures only for the person who couldn't ask.
When this reading doesn't fit
If asking isn't the problem — the words came out fine, but what returned fell short and you ended up redoing it — the grain is different. That's a quality snag, not a guilt snag: the Re-doer's description is closer to your story.
Grounding: Unmitigated-communion research — prioritizing others' needs while failing to claim one's own
자주 묻는 질문
Q. But it genuinely is faster if I just do it myself?
This once — yes. And that calculation is the trap. Skip the handover to save thirty minutes today, and the task is yours forever, billing thirty minutes every month. Delegation isn't a cost; it's an investment: pay the one-time price of explaining and correcting, and every repetition after that is the return. Stretch the accounting unit from this week to this quarter and the answer flips.
Q. What if the quality drops when I hand it over?
It will — at first, guaranteed. The question is where you absorb the drop. Delegate work sized to fail safely first (the internal write-up, not the client presentation), and manage checkpoints instead of outcomes (a direction check at thirty percent, not corrections after the end). This isn't abandoning your standard — it's practicing routes to the standard that include other people.
Q. Asking feels like imposing, and I can't get the words out.
Here's what the burden-shy miss: a request isn't only a relational debt — it's also an expression of trust. Research repeatedly finds that people who receive a reasonable request tend to like the requester more, not less (having helped someone makes them matter to us). And dividing work in a team isn't a favor — it's the basic motion of collaboration. Doing everything solo can itself broadcast the opposite signal: 'does this person not trust us?'
Q. It's already a structure that can't run without me. How do I unwind it?
Trying to hand it all over at once fails — a handover is a process, not an event. Start with inventory: list everything only you know and only you do, pick the single lowest-risk item, and pass it through three stages — documented, then done together, then done solo. One lands, then the next. It takes months. But leave the structure standing, and vacations, promotions, and job changes all stay hostage to it.
This page describes behavior patterns for self-understanding. It is not a medical or psychological diagnosis, and it does not replace professional care. If difficulties persist and disrupt daily life, please seek professional help.
This page describes the general shape of the pattern.
Complete the assessment to see which patterns actually fired in your trait combination, how strongly — and which levers fit you.