Somewhere in your organisation, right now, a decision is not being made because of something you said six months ago. You probably 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.

This is one of the more uncomfortable side effects of executive leadership. The higher up you sit, the more your offhand comments calcify into doctrine. A piece of feedback you gave to one person in one meeting becomes "the VP said we don't do X here." A nuanced trade-off you reasoned through becomes a flat prohibition. By the time it reaches the team actually trying to ship something, the why has been stripped out and only the rule remains.

I've come to think of this as Newtonian culture. Guidance, once given, continues in the direction it was thrown until an equal and opposite force is applied. And most leaders never apply that opposite force, because they don't know their original guidance is still in motion.

How folklore forms

The mechanism is simple and almost always invisible to the person who started it. 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 ever saying anything close to what is now being attributed to you.

This happens because organisations crave certainty. Ambiguity is exhausting. 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 the cognitive load of 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 to reduce ambiguity, 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.

Three things help. First, always give the why with the what. "Don't do X" is folklore-bait. "Don't do X right now because we're trying to solve 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.

Second, 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. "For this project" and "as a general principle" are very different statements, and the difference rarely survives the retelling unless you spell it out.

Third, invite the contradiction. Tell people directly that if they think the guidance no longer applies, they should push back. This sounds obvious, but the default in most organisations is to treat executive direction as permanent until explicitly revoked. You have to actively give people permission to challenge you, and then you have to actually accept the challenge when they bring it. If you say "push back" but punish the pushback, you've made the folklore problem worse, not better.

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 of what I do recognise was situational advice that has long since stopped applying. The remaining quarter is guidance I'd still stand behind, but I now know which quarter it is, which is the point.

Skip-levels and engineering all-hands are the cheapest place to find this. You can also watch for the linguistic tells in planning documents and design reviews. Phrases like "we've always done it this way," "leadership doesn't want us to," and "that's not allowed here" are all flares for folklore. The absence of a name attached to the rule is the giveaway. Real decisions have authors. Folklore is anonymous.

The opposite force

The Newtonian framing matters because it points at the actual job. If guidance continues until an equal and opposite force is applied, 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 still bumping into invisible walls built from comments their leaders have long forgotten making.