RECURRING LOOP · Work & Achievement
Carrying It Alone
If you are doing alone what you could have asked for, it is not only a strong sense of duty. Giving it to somebody and then checking is more work than doing it yourself.
Does "Need any help?" get an immediate "No, I've got it"? Carrying everything alone is not only competence. Why you will not let go differs from person to person.
Why Doing Everything Yourself keeps repeating
Your list of things to do is, once again, the only long one. Work arrives in the meeting and much of it has somehow become yours. A teammate offers to take that, and "No, I'll do it" is already out. Then it is ten at night in the office, and "Why is it always me with this much work?" The answer is hard to accept: much of it you arranged yourself.
There are three reasons for holding on. The first cannot bear not seeing how it is going: once it has gone to somebody else, neither the quality nor the progress is visible, so they would rather be tired than not know. The second is not satisfied by anybody else's work: "By the time I've fixed it, I could have done it from scratch." And for the third, asking is an imposition. Handing work over means putting something on somebody else, so they work late instead of asking.
What carrying everything alone costs is not only your own exhaustion. The team never gets to improve, the organization comes to depend on one person, and that then holds you in place. This page finds why you cannot let go of the work, and gives each type the first step toward handing it over.
Does Doing Everything Yourself come in types?
| Type | One-line scene |
|---|
| Cannot-bear-not-seeing-how-it-is-going | “Cannot Bear Not Knowing How It Is Going” |
| Ends-up-doing-it-again-themselves | “Faster to Do It Again Themselves” |
| Cannot-bring-themselves-to-ask | “Cannot Bring Themselves to Ask” |
TYPE 1 · Cannot-bear-not-seeing-how-it-is-going
Doing Everything Yourself type 1 · “Cannot Bear Not Knowing How It Is Going”
Why this type appears
What keeps this person from handing work over is not the other person's skill. It is that they cannot bear work going on where they cannot see it. From the moment they hand it over, they can no longer see how far it has come, what has gone wrong, or when it will arrive, and the anxiety of that stretch costs more than the tiredness of simply doing it. So even after handing it over, the casual checking begins, and eventually they take it back. Over time, every part of the operation comes back to one person: they end up alone in the position that sets the team's pace, and every delay confirms that "it only runs when I'm watching." That certainty makes the next handover harder, and it settles in. The second type takes work back because the result cannot be trusted, and the third cannot bring themselves to ask. This person stops before quality is even in question, at one thing: not being able to see how it is going.
If these scenes feel familiar
A rush job comes in, and they start explaining it to a junior colleague, and halfway through, "It's faster to do it myself," and the file comes back. It is not the time spent explaining they cannot afford. It is the hours afterwards of not knowing what is happening. On a long-awaited holiday, the laptop opens. "Everybody is surely handling it, but where exactly is it?" Only looking can settle that, and each day without looking is worse than the last. The chart shows the work divided evenly, and follow where the tasks actually go and their name is at every important point. Everybody does their part, and somehow nothing gets finished without passing through them.
What makes it stronger or weaker
Tight deadlines, a mistake that would show immediately, work whose consequences fall to them, and no way to check partway: under those it is worst. It eases when progress becomes visible automatically at set times: with that in place, there is room not to intervene. When they can trust that the position will be there whenever they want to look, the urge to take it back quiets.
How it gets misread
It registers as wanting all the work, or as distrust, and the junior colleague checked on again and again hears that they are not rated. Inside, it is not the skill being doubted. It is the anxiety of the interval they cannot see, carried alone. Not keeping people down. They have simply never found a way to bear the hours they cannot see.
The smallest change to make
What works for this person is not handing over results only. It is arranging for progress to be visible at set times. A short update every other day, say: asking at any moment becomes looking at an agreed time. What caused the anxiety, not being able to see, is filled in, and taking it back has nothing to stand on. What matters is not giving up the right to look but turning constant watching into looking at planned times. Arrange the same updates for the second type and the outcome differs completely. With progress in full view, an interim result below their standard still gets rebuilt from scratch, and seeing it does not stop them taking it back. This works only where not seeing is the anxiety.
When this reading doesn't fit
If progress in full view brings you no ease, and the returned work keeps you up all night correcting it line by line, this is not your type. What catches you is not "visible or not" but "good enough or not." See the type who ends up doing it again themselves.
Grounding: Intolerance-of-uncertainty research, on difficulty enduring states where the outcome cannot be known
TYPE 2 · Ends-up-doing-it-again-themselves
Doing Everything Yourself type 2 · “Faster to Do It Again Themselves”
Why this type appears
This person does hand work over. But when what comes back is below their standard, they do not fix the weak parts. They start again. Which is how everything ends up back on their desk. What stops them is not being unable to see. It is having decided that the other person will not reach their level, a conclusion reached before the handover happens, so the handing over quietly gets abandoned in advance. And when it does happen, checking it finds the shortfall and they take over, because sending it as it is cannot be done. Over time the team learns that there is no point, since "it gets redone anyway," and starts submitting rougher work, which becomes fresh evidence that it cannot be trusted, and both sides expect less of each other. The first type stops at a process they cannot see. This person stops at a finished thing in plain view, at its level. The third cannot hand over out of guilt. This one hands over and takes it back, on quality.
If these scenes feel familiar
A junior colleague brings work over, saying they think it is done, and the file gets opened with modest intentions: fix a couple of places. But touching one part catches the eye on the next, and eventually every sentence and every figure has been redone by them. It was called a review and ended as a rewrite. The late nights on work that could have been handed over do not start from distrust either: what came in that afternoon was too rough to send, and bringing it up to standard became indistinguishable from starting again. The next day the junior hears, "I was in a rush so I just did it," and the real sequence started with a judgment: "Not at that level. It's not going out."
What makes it stronger or weaker
Work that carries their name and will be seen and judged is where it happens, especially where standards are clear and faults show plainly. It eases when what counts as good enough is fixed in advance, "This passes at eighty," and held there so it cannot rise. Also when the deadline plainly matters more than the finish and starting again is physically impossible.
How it gets misread
People say it plainly: "Trusts nobody, keeps all the work." The junior colleague, watching every submission get taken apart, stops trying. But what this person is attending to is the work rather than the person. Not malice. They cannot send out something below the line. In their own mind it rarely registers as taking somebody's work. It registers as responsibility: "My name is on this, and it can't go out like that."
The smallest change to make
What works here is not applying one highest standard to everything. Before handing anything over, decide which it is: "This one passes at eighty," or "This one I see through to the end." On work handed over, what counts as good enough is set lower and held there, which stops the standard rising while they are looking at it. The point is not abandoning standards but drawing the line before the work, so that opening the file does not raise it again. Give the same rule to the first type and the picture changes. Lower their standard as much as you like, the anxiety of the process they cannot see remains, and they take it back regardless. Lowering the standard works only where the level is what stops them.
When this reading doesn't fit
If the quality of what comes back is genuinely fine and what you cannot bear is not knowing where the work stands right now, checking and checking and taking it back, quality is not what catches you. See the type who cannot bear not seeing how it is going.
Grounding: Self-oriented perfectionism research, on standards a person sets themselves, read here in terms of giving work to others
TYPE 3 · Cannot-bring-themselves-to-ask
Doing Everything Yourself type 3 · “Cannot Bring Themselves to Ask”
Why this type appears
This person holds on to the work for neither reason. They feel that asking itself means putting one more thing on a busy person, and they cannot bring themselves to say it. They feel in advance what the other person would be taking on, and feel it as their own, and against that, enduring a little more themselves is simply easier. So instead of one sentence, "Could you help?", they work late. Over time it settles: "That one handles everything alone, always has." Everybody takes the devotion for granted and gets used to not sharing their work, and the people around them keep giving the work only to this person. The first type stops at the process they cannot see, the second at a result they do not trust. This one, at the moment of asking, first pictures the other person being put in an awkward position, and so does not say it.
If these scenes feel familiar
Work that would finish on time if the person at the next desk took part of it, kept instead, with "They're busy too, I can't ask them," and the evening alone begins. One sentence of asking is harder than several hours of working late. The late night on work that could have been handed over is not about the work either: all afternoon, "Could you take this?" stayed unsaid, and then the other person's tired face came to mind, and it stayed unsaid, and everything stayed with them. At the team dinner, asked why they did not say something, they laugh and say it was nothing. It was not nothing. Imposing was the thing they could not do.
What makes it stronger or weaker
The other person looking visibly busy, or being somebody who finds it hard to refuse, is what stops them, and the closer and more ongoing the relationship, the longer the sense of having imposed lasts, and the less they say. It eases clearly when the work is plainly part of somebody's role rather than a personal favor. With the asking removed, the guilt has nowhere to sit, and speaking gets easier.
How it gets misread
What everyone notices is responsibility itself: handles everything, never complains, must be fine. Under the visible devotion is an inability to put anything on another person. It is not love of work that makes it accumulate. It is taking on, for everybody, the discomfort that asking would create. And in situations where help is plainly warranted, permitting themselves to receive it is the one thing they cannot do.
The smallest change to make
What works here is removing the asking entirely. Arrange the work so that it moves not as a personal favor, "Could you do me a favor?", but as a matter of role: "This task belongs to that position." The personal element the guilt needs is gone, and instead of relying on the relationship, the defined role carries the work, and what used to be taken on as overtime goes where it belongs. Carried over to the first type, this does not hold. Divide by role as cleanly as you like, and the anxiety of not seeing the progress takes the work back within weeks, and the careful division is undone. Removing the asking lasts only for the person who could not ask.
When this reading doesn't fit
If asking is not the problem, and the words came out fine and what came back fell short so you ended up doing it again, this is a different difficulty. That is about quality rather than guilt. See the type who ends up doing it again themselves.
Grounding: Unmitigated-communion research, on putting other people's needs first without looking after one's own
Doing Everything Yourself: frequently asked
Q. But it genuinely is faster if I just do it myself?
This once, yes. And that is exactly where it goes wrong. Skip the explaining to save thirty minutes today, and the task stays yours from then on, costing thirty minutes every month. Handing work over is not a loss but something you get back: explain and correct once, and every repetition after that is what you gain. Count in quarters rather than in weeks and the answer reverses.
Q. What if the quality drops when I hand it over?
It will, at first, certainly. The question is where you take the drop. Hand over work where failing is safe first, the internal write-up rather than the client presentation, and check the direction partway rather than correcting at the end. This is not giving up your standard. It is practicing ways of reaching that standard that include other people.
Q. Asking is imposing, and I can't get the words out.
Here is what the third type misses: a request is not only something owed. It is also a sign of trust. Studies have repeatedly found that people who are asked a reasonable favor tend to think better of the person who asked, since they come to value the person they helped. And dividing work in a team is not a favor. It is the ordinary business of working together. Doing everything alone can itself say the opposite: "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, because handing over is a process rather than an event. Start by listing everything only you know and only you do, pick the single lowest-risk item, and pass it through three stages: written down, then done together, then done alone. One lands, then the next. It takes months. And leave it as it is, and holidays, promotions and new jobs all stay stuck to it.
How should you read this page?
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 show up in your trait combination, how strongly, and which first step fits you.
What other recurring patterns are there?
Archetypes where this pattern shows up often
These share the traits the measurement looks at. The list is calculated, not hand-picked.