There is a version of this that starts with a reasonable decision. The team is under pressure, the moment is wrong, the org is at its seams. You choose to carry. You set a horizon — next quarter, after this launch, once the restructure settles. You tell yourself it is temporary.
Then the quarter ends and the next one begins with the same weight. The launch closes and another opens. The restructure settles and a new priority surfaces. The horizon moves. And you are still carrying.
At some point, carrying stops being a strategic choice and becomes the shape of the role. That is a different problem — and it requires a different response.
Context
The person who carries well is, by definition, the person the org leans on. They are competent, composed, and reliable under load. They do not complain loudly. They resolve instead of escalate. They keep things moving when the system cannot keep itself moving.
These are the qualities that make someone valuable. They are also the qualities that make them invisible as a risk. The org does not see the accumulation because the carrying person is too good at making it look like normal operations.
The horizon shifts because no one is tracking it. Not maliciously — the org is simply optimising for continuity, and continuity is being provided. There is no forcing function to reassess the load until the person carrying it stops.
Insight
The horizon is a signal, not a solution. Setting a horizon on carrying is useful because it makes the choice conscious. But a horizon that keeps moving is telling you something: the structural condition that required the carrying has not changed, and the org has not been given a reason to change it.
The temporary becomes permanent when it is never named. Most carrying arrangements are implicit. No one said “please absorb this indefinitely.” No one agreed to it. It accumulated — through small decisions, through gaps that needed filling, through a person who was capable and present and did not say no. Because it was never named, it cannot be renegotiated. You cannot push back on an arrangement that does not officially exist.
The org will not self-correct without a signal. This is the part that is hardest to accept. If you are good at carrying, the org has no reliable signal that anything is wrong. Delivery continues. Quality holds. The system appears to be working. The only way the org gets accurate information is if you provide it — deliberately, specifically, and with enough clarity that it cannot be absorbed as a passing comment in a one-on-one.
At some point, fairness to yourself becomes the most important variable. The previous post drew a distinction between choosing to carry and defaulting to it. When the horizon keeps moving, you are no longer choosing. You are defaulting — and the default has compounded past the point where it is a strategic posture. It is now a sustainability question.
Implication
When carrying becomes the job, three things happen gradually and then suddenly.
Your capacity for strategic work shrinks. The operational load fills the available space, and the work that requires clear thinking, creativity, and long horizon — the work that actually develops you — gets squeezed to the margins.
Your signal value to the org degrades. You become the person who keeps things running, which is valuable, but you stop being the person who sees around corners and surfaces what is coming. The org loses your best thinking precisely because your best thinking is consumed by holding the present together.
Your relationship with the role changes. What started as investment becomes maintenance. You are no longer building — you are sustaining. For some people, in some seasons, that is fine. For most people over time, it is a slow erosion of the reason they took the role in the first place.
Action
Name the arrangement explicitly — to yourself first. Write down what you are carrying that is not formally your job. Not as a grievance — as an inventory. How long have you been carrying it? What was the original horizon? What changed? Clarity about the shape of the problem is the prerequisite for doing anything about it.
Surface the cost with specificity. Not “I am overwhelmed” — that is easy to absorb and hard to act on. Specific: “I am spending X hours per week on Y, which is not in my scope, and it is coming at the cost of Z.” Give the org the information it needs to make a real decision. Vague signals produce vague responses.
Reopen the horizon conversation. If you set a horizon that moved, name that it moved. “We said after the launch this would be revisited. The launch closed three months ago. I want to reopen that conversation.” This is not aggressive — it is precise. It treats the original agreement as real and holds the org to it.
Propose the structural fix, not just the relief. The most useful version of this conversation is not “I need less to do.” It is “here is what I am carrying, here is what it should look like structurally, and here is what needs to change for that to happen.” You arrive with a diagnosis and a direction. That is a different conversation than a complaint.
Decide what you are willing to do if nothing changes. This is the question most people avoid because the answer is uncomfortable. But it is the most important one. If you surface the problem clearly, propose the fix, and the org does not act — what then? You do not need to answer this loudly. But you need to have answered it privately. Without that answer, you are not making a choice. You are waiting.
What carrying beyond the edge actually costs
The org sees continuity. You absorb the cost of producing it.
The cost is not always visible in performance. It shows up in other places — in the quality of your thinking at the end of a long quarter, in the narrowing of what feels possible, in the slow shift from engagement to endurance. These are not dramatic signals. They are quiet ones. And by the time they are loud, the carrying has gone on too long.
You are allowed to put it down. Not abandon it — put it down deliberately, with a handoff and a conversation and a clear statement of what the org needs to build to carry it properly. That is not failure. That is the most honest service you can give an org that has been relying on you to carry what it should have been building.
The horizon that keeps moving is not a scheduling problem. It is the org telling you — without meaning to — that it has no plan to fix what you are fixing for it. That is the signal. What you do with it is yours to decide.