The Hidden Cost of Being Easy to Work With

Reliable. Collaborative. Emotionally steady. In many teams, these qualities make someone easy to work with. They are also the qualities that make extra work almost disappear into a person's day.

You clarify the brief. You follow up when ownership is unclear. You soften a difficult message so two colleagues can keep working together. None of these actions is especially dramatic. By the end of the week, though, you have carried work that never appeared on the project plan.

People often bring a version of this question to coaching: I am capable and still performing, so why am I becoming more exhausted? One place to look is the difference between the work a role names and the work a team has learned to expect.

Capability becomes an assumption

A dependable person is often asked first when a situation becomes ambiguous. The request may be reasonable. The difficulty is the pattern it creates: each successful rescue makes the next rescue easier to assign.

There may be no deliberate exploitation. Colleagues trust you to make something work. You may also value being helpful. Those two facts can obscure the point at which contribution becomes default ownership.

I think of the extra burden as a collaboration tax. It has several forms. Emotional buffering means absorbing tension and adjusting a conversation so work can continue. Decision ambiguity means becoming the temporary owner of an unresolved question. Self-compression means reducing your own preferences to preserve momentum.

Any one of these can be an appropriate part of collaboration. Trouble begins when they become continuous, unacknowledged and unevenly distributed.

The missing question is capacity

The helpful person's question is often: how do I make this work? It is useful to add another: do I have the capacity, authority and time to own it?

That question brings limits back into the decision. It also distinguishes kindness from an unlimited commitment. You can care about a colleague's problem without becoming its permanent coordinator.

Start by noticing what repeatedly lands with you. Is it the same unclear decision? The same difficult handoff? The same interpersonal repair? When a pattern repeats, it may need a team agreement rather than another private act of effort.

Faster tools can leave the last mile untouched

AI can make drafts and summaries easier to produce. Someone still needs to resolve conflicting expectations, check what matters and decide what happens next. If that last mile repeatedly falls to the same person, faster production can increase their burden.

The useful management question is therefore broader than whether a tool saves time. Who receives the new output? Who verifies it? Who handles the exceptions? What existing work will stop?

Without those decisions, the person who is good at integration becomes the place where the system deposits its unfinished thinking.

Make the contribution visible

A sustainable change begins with a clear description. Name the coordination or repair work, estimate what it displaces, and ask who should own it. A boundary becomes easier to discuss when it refers to an actual trade-off rather than a general declaration that you need to be stronger.

Reliability is valuable. Protecting it is part of managing a team well. The aim is to keep collaboration possible without requiring one person's capacity to remain invisible.

This week, notice one moment when your willingness to help is treated as an assumption. What would need to be made explicit for that contribution to remain a choice?