Somewhere in your organisation, right now, a decision is not being made because of something you said six months ago. You don't remember saying it. The context is long gone. But the guidance has hardened into a rule, and the rule is being enforced by people who have never spoken to you.

Newton's first law says an object in motion stays in motion until acted on by an external force. Leadership guidance behaves the same way. Once given, it keeps travelling in the direction it was thrown until something explicitly stops it. And most leaders never stop it, because they don't know it's still moving.

This is leadership inertia, and it's how guidance becomes folklore.

How folklore forms

You give feedback in a specific context, with specific constraints, to solve a specific problem. The person you spoke to internalises the lesson, but the lesson travels without its context. They tell their team. Their team tells the next team. Three retellings later, the situational guidance has become a principle, and the principle has become a rule.

You only find out when someone says "we can't do that." You ask why. They say "it's not allowed." You ask who decided that. They shrug, or worse, they cite you. And you have no memory of saying anything close to what is now being attributed to you.

This happens because organisations crave certainty. When a senior leader says something, teams convert it into a rule because rules are easier to follow than judgement calls. The folklore isn't malicious. It's a coping mechanism for working without complete information.

Giving direction with an expiry date

The fix isn't to stop giving direction. Leaders are paid to have opinions, and a team without direction is worse off than a team with imperfect direction. The fix is to give direction in a way that resists calcification.

Always give the why with the what. "Don't do X" is folklore-bait. "Don't do X right now because we're solving Y, and X creates Z problem for that goal" gives the next person enough context to know when the guidance no longer applies. The reasoning is the expiry date.

Name the scope. Be explicit about whether you're giving guidance for this decision, this quarter, this team, or forever. Most leadership guidance is situational, but staff treat it as universal unless you say otherwise.

Invite the contradiction. Tell people directly that if they think the guidance no longer applies, they should push back. The default in most organisations is to treat executive direction as permanent until explicitly revoked. You have to give people permission to challenge you, and then actually accept the challenge when it comes.

Hunting your own folklore

You also need to go looking for the folklore that already exists. The most useful question I've found to ask in skip-levels is "what are we not doing because of something I said?" It produces uncomfortable silences and then surprising answers. Half of what comes back I don't recognise. A quarter is situational advice that has long since stopped applying. The remaining quarter I'd still stand behind, but I now know which quarter is which.

Watch for the linguistic tells too: "we've always done it this way," "leadership doesn't want us to," "that's not allowed here." The absence of a name attached to the rule is the giveaway. Real decisions have authors. Folklore is anonymous.

The opposite force

If guidance keeps moving until something stops it, then part of leadership is the deliberate, regular application of opposite forces. Revoking old guidance. Updating the why. Killing rules that no longer serve the goal. None of this happens automatically, and none of it happens because the original context expired. It happens because you went and did it.

Most leaders are great at giving direction. Far fewer are disciplined about taking it back. The teams paying for that asymmetry are the ones bumping into invisible walls built from comments their leaders have long forgotten making.