The Exhaustion of Always Having to Be the One Who Follows Up

It’s 9:14 PM. The only light in the room is from your laptop screen, throwing the clutter on your desk into sharp relief. You’re staring at a draft email, the cursor blinking patiently at the end of a sentence you’ve rewritten four times. It’s addressed to a colleague, the one whose input you need to finish the quarterly report that’s due, technically, tomorrow. The last time you asked was five days ago. You got a breezy “Will get to it!” and then silence. Now you’re sitting here, a familiar knot in your stomach, typing phrases into your search bar like "team member not responding to emails" and trying to find a way to write “Where is the thing you promised?” that doesn’t sound accusatory, or desperate, or like you’re the only person who cares if this project lands on time.

This specific kind of weariness isn’t just about being busy. It’s the emotional and cognitive load of being the designated “closer of loops.” You have been assigned, through a series of unspoken agreements, the role of project shepherd, chaser-in-chief, and the sole owner of institutional memory. The exhaustion comes from a pattern of unilateral responsibility adoption. You are the only one who consistently picks up the responsibility for a task that was, in theory, shared. It’s not just that you’re doing extra work; it’s that you’re carrying the mental weight for two.

What’s Actually Going On Here

When you’re the one who always follows up, you are unwittingly training your environment to rely on you as a human safety net. People don’t have to develop their own systems for remembering, tracking, or closing loops because they know, consciously or not, that you will do it for them. The project won’t fail, the client won’t be left hanging, the invoice won’t go unpaid. Why? Because at 9:14 PM, you will be the one staring at the blinking cursor, ensuring it gets done.

This pattern is incredibly stable because the system often rewards it. Your manager sees you as “reliable” and “a finisher.” You get the project over the line, and the organisation celebrates the outcome. It doesn’t see the dozen follow-up emails, the weekend check-ins, or the mental energy you spent worrying about someone else’s deliverable. In fact, the person who dropped the ball faces no negative consequences; the work got done anyway. The system, therefore, is perfectly designed to burn you out. It creates a dependency on your over-functioning, then praises you for it, ensuring you’ll do it again.

This creates a communication trap. You might be told, “I trust you to manage this project,” which you interpret as a mandate for autonomy. But what it really means is, “You are now responsible for the outcome, no matter who drops the ball.” You are given authority over a goal, but no real authority over the people whose contributions are required to meet it. So you’re left with one tool: chasing. You’re asked to lead without being given the power to direct, which forces you into the exhausting, low-status position of nagging.

What People Usually Try (and Why It Backfires)

When caught in this cycle, we tend to reach for a set of standard professional moves. They feel right, they feel polite, but they are the very things that keep the pattern going.

• The Gentle Nudge. It sounds like: "Just circling back on this..." or "Just wanted to gently follow up on my email below." This phrasing immediately frames your legitimate need as a minor, perhaps even annoying, interruption. It apologises for holding someone accountable and signals that you’re prepared to be patient, which is an invitation for them to keep procrastinating.

• The Vague Plea. It sounds like: "It would be great if we could get this finalised soon." This is a wish, not a request. It contains no specifics about time, dependencies, or consequences. Because it’s passive and indirect, it’s easy to ignore. The other person hears an abstract preference, not an operational requirement.

• Absorbing the Blame. It sounds like: "Sorry to bother you again, but I need your numbers for the report." This is the most damaging move. You are apologising for their failure to deliver. This positions you as the source of the awkwardness and them as the busy, important person whose time you are infringing upon. It reinforces the idea that your follow-up is the problem, not their lack of follow-through.

• Doing It Yourself. After multiple failed attempts, you sigh, find the data yourself, write their section of the report, or tell the client you’ll handle their request directly. This provides immediate relief but is a long-term disaster. You have just taught your colleague, and the entire system, that if they wait long enough, you will absorb their work.

What Shifts When You See It Clearly

Understanding this pattern doesn’t give you a magic phrase to make people more responsible. Instead, it prompts a fundamental perceptual shift. You stop seeing this as a problem with your “communication skills” or a personal failure to motivate others. You start seeing it for what it is: a structural problem with how responsibility is distributed and tracked.

The goal is no longer “How do I get this person to do their work?” It becomes “How do I make the consequences of this work not getting done visible to the person who is actually responsible for it?”

This shift moves you from being the system’s shock absorber to being its conductor. A shock absorber’s job is to soak up all the bumps so no one else feels them. It’s a smooth ride for everyone else, but the part itself wears down. A conductor doesn’t play the instruments; they clarify the tempo, signal the entries, and ensure each section understands its part in the whole. Your job isn’t to play the violin for the person who forgot it at home. Your job is to make their silence audible. You stop quietly absorbing the responsibility and start making the lines of accountability clear and explicit.

What This Looks Like in Practice

When you see the pattern clearly, you stop defaulting to the gentle nudge. Instead, you make small, precise adjustments to your language and actions. These aren’t scripts to be memorised, but illustrations of how to operate from a different stance, one of shared, explicit accountability.

• State the Dependency and the Consequence. Instead of asking if they’ve done it, state what you need and what happens next.

  “I’m at the point where I need your sales data to write the conclusion for the board report. I need it by 3 PM tomorrow to make the deadline. If I don’t get it by then, I’ll have to submit the report with a note that the sales data is pending.” This isn’t a threat. It’s a calm statement of operational reality. You are making the consequence their own.

• Make the Next Step Theirs. When you agree on an action, close the conversation by explicitly placing the responsibility for the next contact on them.

  “Okay, so you’re going to check with legal and get back to me by end of day Thursday. Great. I will wait to hear from you then.” You don’t add, “If I don’t hear from you, I’ll follow up.” The silence is the signal. You have handed the baton over. They are now responsible for closing the loop.

• Clarify Responsibility in the Room. When a task is assigned vaguely to “the team,” stop it before it starts.

  “Just to be clear, who is the specific person responsible for sending the final draft to the client? I want to make sure we all know who is closing that loop.” This prevents the diffusion of responsibility that so often leaves you holding the bag.

• Address the Pattern, Not Just the Instance. In a one-on-one with a manager or a team member, you can raise the dynamic itself as a process issue.

  “I’ve noticed that on our last few projects, I’ve been the one responsible for follow-up and tracking everyone’s parts. It’s taking up a significant amount of my time that I should be spending on my own deliverables. Can we establish a clearer system for how we track progress so that responsibility is shared?” This reframes the problem from a personal complaint to a systemic inefficiency.