The post Carrying Less appeared first on Navigate Change.

Something about it keeps coming back, when you’re trying to focus, in the middle of something else, or your day is otherwise fine.

That’s usually a signal that there’s more going on than the moment itself.

When The Reaction Doesn’t Match the Moment

One of the patterns I see when clients are dealing with difficult people is that the reaction they create internally isn’t always proportional to what actually happened.

A short exchange can stay with you longer than a much bigger issue. A passing comment can carry more weight than a formal conversation. It doesn’t always make sense on the surface.

Which is why people tend to focus on the other person. They’re trying to make sense of why they said what they said, or why they behave the way they do.

That line of thinking feels productive, but it rarely resolves anything.

What They Actually Hit

Certain people have a way of landing on something specific.

It might be the person who interrupts just enough that you feel cut off. Or the one who dismisses ideas in a way that’s hard to challenge in the moment. Or someone who creates pressure without being explicit about it.

Individually, those behaviours are manageable. You’ve dealt with them before.

But every so often, one of those interactions lands differently. It touches something that was already there.

Often the reaction has less to do with the comment itself and more to do with what you feel it confirms. That you weren’t taken seriously, or that your effort didn’t matter.

It doesn’t have to be dramatic. Most of the time it isn’t. It’s just enough to make the interaction stick.

Why Your Mind Keeps Returning to It

When something lands at that level, your mind doesn’t treat it like a simple interaction.

It keeps returning to it, trying to resolve it. You think through what you could have said differently. You refine your response. You replay the moment, but usually with a different ending.

From the outside, it looks like you’re replaying the conversation. What you’re actually doing is trying to resolve what it stirred up. And because that didn’t start in that moment, it doesn’t fully settle there either.

Most people stay focused on the other person. They analyze the behaviour, question the intent, and try to figure out what’s behind it. It feels like understanding them will help you let it go.

But the more attention you give it at that level, the more it holds.

What Actually Shifts It

Letting it go doesn’t start with forcing yourself to stop thinking about it. That usually just pushes it further into the background where it keeps running.

It starts with being clear about what the interaction actually touched.

Say the person dismissed your idea in a meeting without much engagement. On the surface, it’s a minor thing. But if part of what you bring to your work is a genuine investment in getting things right, that dismissal doesn’t just feel rude. It lands on something that matters to you.

The replaying isn’t really about them. It’s your mind trying to recover something that felt brushed aside.

Once you can see that distinction, what belongs to them and what it activated in you, the intensity tends to drop. The interaction doesn’t disappear. It just stops taking up the same amount of space.

The Real Cost

Some people will always be difficult. That part doesn’t change.

What can change is how much of your attention they hold after the interaction is over.

And that’s usually where the real cost shows up. Not in the moment itself, but in everything that follows it.

The post Why You Can’t Let It Go (Even When You Know Better) appeared first on Navigate Change.

The post Don’t Let Someone Else’s Behaviour Become Your Problem appeared first on Navigate Change.

When a problem landed on your desk, you worked it through. When no one had the answer, you found it. That capacity to be self-sufficient, to not need much from others, felt like a superpower. And for a long time, it was.

But at a certain level of leadership, the skill that carried you here becomes the thing that quietly limits what’s next.

Self-reliance is one of the most quietly damaging patterns in senior leadership. Not because it looks like a problem. But because it doesn’t. It looks like strength. Capability. Drive. Which is exactly why it’s so hard to see and even harder to change.

It’s Not a Habit. It’s the Story You Tell Yourself.

Most leaders who don’t ask for help don’t experience it as a struggle. It’s just who they are.

This isn’t a bad habit they picked up somewhere. It’s how they learned to succeed. The pattern formed over years, often decades, of being the person who handles things. Many high achievers were rewarded early for figuring things out alone. The recognition went to the one who didn’t need help. Needing help felt like weakness. Independence felt like competence.

So it became a badge. And then, slowly, something you couldn’t put down.

When asking for help threatens the story you tell yourself, that you’re capable, that you handle things, it feels like self-preservation to avoid it. Questioning that pattern means questioning yourself. And most leaders don’t have a lot of appetite for that, especially under pressure.

Position makes it worse. The higher you rise, the fewer people feel safe enough to challenge you or offer help unprompted. The gap between what you know and what you need grows quietly, without feedback,  without you noticing.  And because no one names it, it continues.

What It Costs

The visible cost is straightforward. Leaders who carry problems alone solve them more slowly and less effectively. Decisions take longer. Execution gets harder. Good ideas that exist two levels down never surface.

But the less visible cost is where the real damage accumulates.

When a leader doesn’t ask for help, they send a signal whether they intend to or not: asking is a sign of not being up to the job. A team that watches its leader carry everything alone learns not to ask either. Not because they can’t, but because they shouldn’t. Problems stay hidden longer. Mistakes go unaddressed. People start managing up rather than solving sideways.

The self-reliant leader doesn’t just carry their own weight. They create an environment where everyone else carries theirs alone too.

That’s not a culture of capability. It’s a culture of isolation that looks like one.

The Irony Underneath It

The leader who won’t ask for help usually believes they’re protecting something. Their reputation. Their relationships. The impression that they have it handled.

What’s actually happening is the opposite.

Asking for help doesn’t signal weakness. It signals trust. It tells the people around you that their judgment matters, that you’re not above needing a perspective other than your own, that this is a team and not a performance. People who are asked for help feel valued. And they remember it.

The act the self-reliant leader is most carefully avoiding is one that would strengthen both their relationships and their results.

Where This Comes From

Patterns this persistent don’t stay in place because leaders are stubborn or blind. They stay in place because they’re protecting something real.

For most leaders who carry this pattern, what’s underneath it is a fear of being seen as less than. Less capable. Less certain. Less worthy of the position. That fear usually formed long before the current role and has been running quietly in the background ever since.

Understanding that doesn’t make the pattern disappear. But it does change what you’re actually working with. You’re not fixing a bad habit. You’re updating a story that once kept you safe and no longer serves the leader, you’re now being asked to be.

A Different Kind of Strength

At a certain level, leadership is a team sport. Your results are only ever as good as the people around you, and those people need to be trusted, developed, and leaned on.

The self-reliant leader, no matter how capable, is playing a team sport with a solo sport strategy.

The badge that served you so well on the way up isn’t the problem. The problem is not noticing when it stopped being an asset and started limiting you.

Putting it down isn’t weakness.  It’s the next level of the same competence that got you here.

The post Self-Reliance Is Costing You and Your Team appeared first on Navigate Change.

Resistant.

It shows up in performance conversations, in strategy post-mortems, in frustrated one-on-ones. The change was right. The direction was clear. And still, the team didn’t move the way you expected.

Before you accept that story, it’s worth asking a different question.

How many changes came before this one?

Not just the big structural ones. The reorgs, the pivots, the new priorities that quietly replaced the old ones. The initiatives that launched and then faded. The leaders who came in with energy and left before anything settled. The moments when the team reorganized around something, a shared way of working, a clear sense of who they were, and then had to let it go before it fully took hold.

Resistance looks like disengagement, cynicism, slow execution, blame between teams. So does exhaustion from incomplete integration.

The difference matters.

A resistant team is pushing back on direction. An exhausted team has stopped trusting that any direction will hold long enough to be worth committing to.

One needs a harder conversation. The other needs something to stabilize around.

I’ve been on both sides of this. Watching a team disengage from something I believed in. And being part of a team that had absorbed so much change that the next initiative, however good, felt like one more thing to survive rather than something to build together.

In both cases, what looked like resistance was really a system that hadn’t been given enough time to land.

When a team goes through significant change, there’s a period where the old way of operating no longer fits and the new one isn’t yet solid. Roles are unclear. Trust is thinner. The shared story about who the team is and what it’s doing hasn’t been rewritten yet.

That period needs time and containment to close.

If another change arrives before it does, the gap widens. The team stays in that in-between state longer. And the longer it stays there, the more that instability becomes the baseline, not a temporary condition but a culture.

The one thing worth doing differently:

Before launching the next initiative, ask your team, not in a survey but in a real conversation, what from the last change still feels unresolved. What’s still unclear. What they’re still carrying.

You don’t have to fix all of it. But naming it does something. It signals that you’re not just moving forward but paying attention to what got left behind.

That distinction is often what makes the difference between a team that can move with you and one that’s too tired to try.

The post The Difference Between Resistant and Exhausted appeared first on Navigate Change.