Don’t Rescue Everything Silently
I used to think fixing the problem was enough. It turns out that sometimes fixing everything yourself is part of the problem.
I used to do this all the time. Something wasn’t working, ownership wasn’t clear, another team wasn’t moving fast enough, or there was a gap somewhere nobody seemed to be dealing with. I would see it, get annoyed for a bit, and then just fix it.
Not because somebody asked me to. Mostly because I could, and because it often seemed easier than escalating it, having three meetings about it, waiting for someone else to take responsibility, or watching the same problem drag on for weeks.
So I would step in, figure out what was happening, talk to whoever needed to be involved, create some structure around it and get things moving again. For a long time I thought this was simply part of being good at my job. Maybe to some extent it was, but I also think I overdid it.
The problem is that if you’re constantly fixing things before anybody else really feels the consequences, the organization starts looking healthier than it actually is. Nobody sees the broken process because you’re compensating for it. Nobody sees that ownership is missing because you’ve temporarily become the owner. Nobody sees that the team doesn’t have enough capacity because you keep finding some way to make things work anyway.
And eventually nobody really sees what you’re doing either. They just see that things are working.
I used to find that very frustrating. I would think, how can people not see how much I’m carrying here? Over time I had to admit that sometimes the answer was simple: I wasn’t really showing anyone.
I thought the result should speak for itself
This has probably been one of my bigger professional mistakes. I’ve always had this belief that if you’re good enough, people will eventually figure it out. If you’re operating above your level, someone should notice. If you’re taking on responsibilities that weren’t originally yours, someone should connect that to your scope. If you keep solving difficult problems, recognition should eventually follow.
It sounds reasonable, but it doesn’t work particularly well, especially as you become more senior.
Your manager doesn’t see everything you do, and their manager sees even less. Months later, when promotion or compensation discussions happen, some of the people involved probably weren’t anywhere near the problems you solved. On top of that, some of your best work may have resulted in nothing happening at all. The incident didn’t happen, the project didn’t collapse, the conflict didn’t blow up, the person didn’t leave, the team became stable again.
That work matters, but from the outside it can be almost invisible.
If you quietly do all of it, you’re effectively expecting other people to reconstruct the whole before-and-after story themselves. Most of them won’t.
I started making the problem visible before fixing it
I don’t mean announcing every small thing on Slack or turning basic competence into a personal marketing campaign. I hate that too.
But if something is genuinely important, I’ve learned that it’s useful to say it while it’s still a problem. Something as simple as, “This is starting to become a risk. Here’s what I’m seeing and here’s what I think we should do,” is often enough.
Then I can go and do exactly what I would have done anyway. The difference is that people understand why the work exists, what was broken, and what changed afterward.
It also gives other people the chance to disagree, which is something I didn’t appreciate enough before. I used to see something broken and immediately decide that it needed fixing. But at a certain level, that’s not always my decision to make. Maybe the company knows it’s broken and doesn’t care enough about it right now. Maybe there is a bigger problem somewhere else. Maybe the ugly workaround is good enough for another six months.
If I silently fix it, I’m not only taking responsibility. I’m also deciding how organizational time and attention should be spent.
Escalating something doesn’t necessarily mean asking someone else to solve it for me. Sometimes it just means saying, “This is broken. I can fix it, but is this actually where we want to spend the time?”
That distinction took me a while to learn.
Where it became unhealthy for me
The worst version of this was taking on things I didn’t actually want to own.
Something needed doing, nobody else seemed to be doing it, so I would pick it up. I wouldn’t really say that I thought it was outside my role, or that it was materially expanding my responsibilities, or that I expected that extra scope to eventually be reflected somewhere.
I would just assume that all of this was obvious.
Then, months later, I would become frustrated and think, I’ve been doing all of this on top of my actual job and nobody seems to care.
The uncomfortable part is that nobody had actually agreed to the deal I had made in my head.
I had created a private contract: I’ll take this extra responsibility now, and eventually you’ll recognize me for it. The other side never signed it.
This is closely related to something else I’ve had to get better at: negotiating before I become resentful.
If I’m taking on something that materially changes my role, I try to say it while it’s happening. “I’m happy to take this on, but this is meaningfully increasing my scope and I want us to account for that when we talk about progression.”
That still doesn’t come naturally to me. Part of me still thinks I shouldn’t have to say it. But that way of thinking is exactly what caused the frustration in the first place.
Sometimes the organization needs to feel the consequence
There’s another part of this that I think is easy to get wrong.
Sometimes the responsible thing is not to immediately absorb every problem. If a team repeatedly fails to take ownership and I always step in, I’ve made the ownership problem easier to ignore. If we’re understaffed and I compensate by working more, I’ve made the staffing problem less visible. If another function consistently drops something and my team quietly picks it up, leadership may conclude that the operating model is working because, technically, things are still getting done.
That doesn’t mean deliberately letting things fail to make a point. I think that’s irresponsible. But there is a difference between protecting the company from a disaster and protecting the company from ever feeling the consequences of its own choices.
I used to blur those two things a lot because I felt responsible for keeping everything moving.
Now I try to be more deliberate about what I pick up. Sometimes I fix it. Sometimes I raise it. Sometimes I ask somebody else to own it. And sometimes I leave an imperfect system visibly imperfect for long enough that the people responsible for it can actually see that there is a problem.
I’m still someone who naturally wants to solve things, and I don’t think that’s going away. I don’t really want it to.
What has changed is that I no longer think quietly carrying everything is automatically evidence that I’m doing a good job. Sometimes it just means I’m making the organization dependent on work it doesn’t even know I’m doing, and then getting angry later because nobody understood how much I was carrying.
That’s not a particularly fair arrangement for either side.

Discussion about this post