Every unit has one. The workaround nobody questions. The habit that got passed from preceptor to new grad so many times nobody remembers where it started, or whether it was ever actually right.
Ask why it's done that way, and you'll get the same answer every time: "That's just how we've always done it."
That sentence should make risk management people nervous. Not because tradition is bad, but because it's being used as a substitute for evidence. And in healthcare, habit and standard of care are not the same thing.
Where the Term Comes From
"Sacred cow" isn't just a catchy phrase, it's borrowed, and the borrowing is the point. In Hindu tradition, cows are considered sacred and protected from harm, tied to religious reverence around certain deities and to symbolism around nourishment and motherhood. The idiom took that idea and turned it sideways: by the late 1800s, English speakers were using "sacred cow" to describe an idea, tradition, or institution treated as untouchable, usually with a wink, because the thing being protected has nothing like the legitimacy of what the phrase originally referred to.
That's the irony worth sitting with. A sacred cow in an organization isn't protected by faith or history that actually earned it. It's protected by habit and by nobody wanting to be the one who asks the question. The reverence is real. The justification for it usually isn't.
The Sacred Cow Problem
A "sacred cow" is a practice that's survived so long it stopped being questioned. It's not written into policy, it's not backed by current evidence, it's just... there. Unexamined. Protected by inertia.
Sacred cows are dangerous precisely because they don't look dangerous. They look like competence. Efficiency, even. Nobody's cutting corners on purpose, they're just doing what's always worked, right up until it doesn't.
Here's what it tends to look like clinically:
- A task done a certain way because that's how the senior staff taught it, not because it's what the current policy says
- Unit culture quietly overriding organizational standards
- Workarounds that started as one-off fixes and became "just how we do it"
- Red flags getting missed because nobody's actually looking anymore, they're just going through motions
None of this shows up as a single dramatic failure. It shows up as a slow drift between what the policy says and what actually happens on the ground. And that gap is exactly where risk lives.
Why This Is a Governance Problem, Not a Training Problem
The instinct is to treat sacred cows as an education issue. Retrain, remind, move on. That misses the point.
If a practice has been running unchallenged for years, it's not because staff forgot the policy. It's because nothing in the system prompted anyone to check it against the policy. That's a structural gap, not a knowledge gap.
Real risk management asks a harder question: what mechanism exists to catch practices that quietly drift away from standards, before an incident forces the question?
If the honest answer is "nothing, we find out when something goes wrong," that's not a training problem. That's a governance problem, and it needs a governance fix: routine practice audits against current policy, a real channel for staff to flag "we do this, but I don't think it's actually right" without it disappearing, and leadership that treats "we've always done it this way" as a prompt to investigate, not an acceptable answer.
Staff Are the Ones Who Actually Know
Here's the part that gets skipped: the people who know exactly where the sacred cows are already work there. Frontline staff can usually tell you, without much prompting, which practices don't quite match policy, which workarounds everyone quietly relies on, which "we've always done it this way" nobody actually believes anymore. They just haven't been asked, or they've been asked once and watched nothing happen.
Auditing practices from the top down, without staff in the room, tends to catch the obvious stuff and miss everything else. The workarounds that only make sense in context, the ones a policy binder would never surface, live in the people doing the work every shift.
That means the fix isn't just an audit schedule, it's a real feedback loop: staff need a low-friction way to flag "this doesn't match what we're supposed to be doing" that doesn't feel like reporting a colleague or triggering a formal investigation. And when something is flagged, it needs a visible response, even if the answer is "we looked into it and here's why we're keeping it." Silence is exactly what teaches staff to stop flagging things.
Involve the people closest to the practice in deciding whether it should change, not just in being told it has. They'll spot the sacred cows faster than any audit will, and they're far more likely to help retire one they had a hand in questioning.
The Uncomfortable Part
Sacred cows usually get protected, not exposed. Questioning an established practice can read as questioning the people who've been doing it for twenty years, and most organizations would rather avoid that conversation than have it.
But that avoidance has a cost. When something does go wrong, "this is how we've always done it" doesn't hold up. Not with a regulator, not with an accrediting body, not in a courtroom. Habit was never a defense. It just felt like one, right up until someone had to prove it.
Where to Start
You don't need to audit every process in the building at once. Start smaller:
- Pick two or three practices your team treats as untouchable, the ones nobody's questioned in years
- Ask staff directly which ones they'd put on that list, they'll likely name a few you missed
- Check them against current policy and current evidence, not against "how it's always been"
- If there's a gap, ask why it exists and whether it's actually safer, or just familiar
- Build a regular cadence for this, so it's not a one-time exercise that fades by next quarter
Sacred cows don't get dangerous overnight. They get dangerous over years of nobody asking the question. Asking it now costs a lot less than answering for it later.