When something goes wrong at work, many capable people look inward first. What did I miss? What should I have done better? What do I need to fix about myself?

That instinct is useful up to a point. Ownership is part of leadership, and the best leaders I know are quick to own their part.

But when every missed deadline, tense meeting and unclear priority turns into a personal improvement project, something gets lost. You stop seeing the real cause. You work longer, apologize more and quietly absorb pressure that belongs somewhere else.

I have seen this pattern most often in strong engineers who move into management. They were rewarded for solving problems with their own effort. So when the team struggles, they reach for the same tool: more of themselves.

This issue is about telling the difference between what you should change in yourself and what you should change around you.

Self-fixing looks responsible from the outside. You take feedback seriously. You read another book on prioritization. You prepare harder for the next review. You take the difficult ticket yourself so the team does not fall further behind.

None of that is wrong on its own. The problem starts when it becomes the only response.

For example, imagine a team lead whose releases keep slipping. She blocks out her evenings, reads about time management and takes over the hardest work herself. The releases still slip. The real cause is that three stakeholders can add work to her backlog without any conversation about what drops out.

No amount of personal discipline fixes that. It is not a skill gap. It is a missing decision rule.

When you treat a system problem as a personal one, two things happen. The problem stays, and you get more tired trying to carry it.

Tip: Before you change your own habits, write one sentence describing the problem without mentioning yourself; if the sentence still makes sense, the cause may not be you.

Many self-fixing habits started as ways to stay safe. They work well enough in the short term, which is why they are hard to notice.

You prepare for every possible question so nobody can catch you out. Preparation is good, but when it is driven by fear of being exposed, it eats hours that should go to deciding and leading.

You accept the extra request because declining feels risky. Each yes looks small. Together they become a workload no one agreed to and no one can see.

A handoff fails, so you fill the gap yourself. It feels faster than raising it. But the gap stays in the process, and next time it falls to you again.

You polish every document and review every change because a mistake would reflect on you. The team learns to wait for your approval instead of building its own judgment.

Each of these patterns protects you a little today and costs you a lot over a year. They also hide information. When you absorb the problem, the organization never sees that something is broken.

Tip: Pick the one pattern above you recognize most and track for one week how many hours it costs you; numbers make the habit easier to discuss and change.

A simple way to break the reflex is to ask where a problem lives before deciding how to fix it. I use three places.

Most real problems touch all three. The point is not to blame the system instead of yourself. It is to put each part of the problem where it can actually be fixed.

In my experience, leaders who do this well still own their part openly. They just stop treating the other two parts as personal failings.

Tip: When you write a retrospective action, label it Me, Role or System; if every action on the list is Me, the review has probably stopped too early.

Boundaries often sound like self-care. In engineering leadership they are something more practical: they make ownership clear.

A boundary tells people what you will do, what you will not do, and what has to change for you to take something on. That helps everyone plan.

A few boundaries that work well for engineering leaders:

For example, imagine a manager asked to support a new initiative on top of a full roadmap. Instead of agreeing and working weekends, she lists the current commitments and asks her director to choose what moves. The answer may still be "do both", but now the cost is visible and shared.

Tip: Prepare one trade-off sentence you can reuse this week, so the next unplanned request gets a decision instead of an automatic yes.

If you fix yourself for every problem, your team learns the same habit. They hide process problems, work around broken handoffs and burn out quietly.

You can see this in retrospectives. When every action item reads "be more careful" or "communicate better", the team has learned that problems belong to individuals.

Leaders change this by asking a different question first: what in our system made this mistake likely? That question does not remove accountability. It makes room for fixes that last longer than one person's extra effort.

It also helps to say your own trade-offs out loud. When the team hears you decline something, or push back on a deadline with reasons, they learn that boundaries are part of the job.

Tip: In your next retrospective, ask "what made this likely?" before "who should do what?", and see how the action list changes.

Self-fixing can also keep you in the wrong place for too long. If you are constantly reshaping yourself to fit a role, it is worth asking whether the role fits you.

Growth should be chosen, not forced by every problem that lands on your desk. Pick one or two skills you deliberately want to build this year, and say no to improvement projects that do not serve them.

And when you notice that you keep fixing yourself to survive an environment that will not change, treat that as information. It may be time for a direct conversation with your manager about scope and support, or for a broader conversation about what comes next.

Tip: Write down the two skills you most want to build this year and check your calendar; if almost none of your time supports them, something needs to change.

Owning your part is good leadership. Treating every workplace problem as proof that you are not good enough is not.

The strongest leaders I know are not the ones who carry the most. They are the ones who put each problem where it can be solved, protect their team from the same habit, and keep enough energy for the work only they can do.

So the next time something goes wrong, ask one question before you start fixing yourself:

Where does this problem actually live?

Hit reply and tell me: what is one problem you stopped trying to fix by working harder, and what did you change instead? I read every answer.

Keep going, one small spark at a time.

Erwin