top of page

When the Story Meets Reality.

Updated: Jun 5

LEANN Chronicle · Monday 12 January 2026

January's first week is kind. It lets us believe in clean breaks and fresh starts. We write the plan. We announce the change. We feel the clarity.

Then week two lands.

The inbox refills. The calendar tightens. Energy dips before lunch. The gap between what we said we'd do and what we're actually doing becomes uncomfortably visible.

This is where most leadership stories collapse, not because the vision was wrong, but because the story was written for week one only.

What your story is missing.

Most leaders start the year with a headline: "We're going to be more innovative." "We're prioritizing culture." "This is the year we scale."

But headlines don't carry you through a difficult Tuesday when nothing is working and everyone is tired.

You need a plot. And every plot worth following includes the part where things get hard.

A complete leadership story doesn't just describe the destination. It names what will try to stop you. It acknowledges the friction before it arrives. It prepares people for the moment when motivation fades and only commitment remains.

If your narrative doesn't include resistance, people will interpret normal difficulty as abnormal failure. They'll assume something is broken when, in fact, everything is working exactly as change works.

Why resistance isn't the problem, your reaction to it is.

Leaders introduce new strategies and expect immediate alignment. They roll out new processes and expect seamless adoption. They cast vision and expect belief.

Then resistance appears. Questions appear. Silence appears.

And because the story was told as if change happens in a straight line, the leader starts reacting instead of leading. They push harder. Explain louder. Blame faster.

Week two reveals whether your story has structure or just enthusiasm.

The question that changes everything.

Stop asking: "How do I get people to change?"

Start asking: "What story would make this change feel safe, meaningful, and worth the effort?"

People don't resist change because they're difficult. They resist because change threatens things they care about:

  • Competence. "Will I look incompetent while I learn this?"

  • Belonging. "Will I still fit here if I do this differently?"

  • Stability. "What else will break if we change this?"

  • Status. "What will I lose that I've worked to build?"

If your story doesn't address these fears, your plan will be received as a threat, no matter how brilliant it is.

Five questions to test your narrative this week.

Use these on yourself, your team or your organization:

1. What's the real tension right now? Not the goal, the obstacle. The fear. The trade-off no one wants to name.

2. What are we pretending is easy? Identify the part that will take longer, cost more or require skills we don't yet have.

3. What does success look like by Friday? Make the next win small, visible and repeatable. December is too far away.

4. What must stay true about who we are, even as we change? This protects identity. Identity protects momentum.

5. What's the next sentence everyone needs to be able to say? If your team can't repeat it simply, they can't carry it consistently.

Week two is where your story becomes real.

The first week is where we announce the story.

The second week is where we prove we believe it.

If you're feeling the drag right now, don't treat it as a sign you've failed. Treat it as the moment your narrative meets reality and gets the chance to prove it was built for this.

Rewrite the story with the resistance already in it. Then lead anyway.

Ready to go deeper? Mimi Kalinda's Echoes of Influence offers practical tools for leaders who negotiate, persuade and drive results through story. Available now on Amazon.

Recent Posts

See All
The 3 Tests of a Leadership Narrative.

Most leadership communication fails not because the facts are unclear, but because meaning is left to chance. This Storytelling and Leadersahip Chronicle unpacks the three tests of a credible leadersh

 
 
 

Comments


bottom of page