You propose a workflow change in a leadership meeting. Before the sentence lands, someone leans back, arms folded, and delivers the verdict: 'We tried that before.' Five words. No data. No context about what was actually tried, when it was tried, or why it failed. Yet those five words carry more organisational weight than a quarter's worth of efficiency data. They shut down conversation with the authority of lived experience — even when that experience is a decade old, poorly remembered, and irrelevant to current conditions. In firms where process inefficiency quietly drains 20–30% of annual revenue, this reflexive resistance isn't merely frustrating. It is strategically dangerous.

The 'we tried that before' resistance is an organisational defence mechanism that conflates past failure with future impossibility. Overcoming it requires leaders to separate legitimate institutional memory from emotional inertia, then create structured environments where process change is evaluated on current evidence rather than historical narrative.

Why This Phrase Carries So Much Power

The phrase derives its authority from a cognitive shortcut we all share: loss aversion married to narrative memory. When someone recalls a failed initiative — even vaguely — the emotional residue of that failure feels more real than any spreadsheet projecting future gains. Behavioural economists have documented this extensively. The pain of a past loss weighs roughly twice as heavily as the prospect of an equivalent gain. In organisational settings, this asymmetry multiplies because failed changes often left behind interpersonal damage: blame, restructured teams, bruised reputations.

Consider the operational reality. Research consistently shows that 60% of business processes are never documented, living only in employees' heads. When a previous attempt at change failed, there is rarely a written post-mortem explaining precisely what went wrong. Instead, the failure becomes tribal knowledge — a story passed between colleagues, simplified with each retelling until it becomes an unassailable axiom. 'We tried that' becomes organisational scripture, immune to interrogation.

The phrase also functions as a status signal. The person invoking it positions themselves as the institutional memory keeper — someone whose tenure and experience grant them veto power over newer voices. In hierarchical cultures, challenging this claim feels like challenging the person's value to the organisation. So people stay silent. The process remains broken. And the company continues spending an estimated 27% of productive time on workarounds for systems everyone privately acknowledges are failing.

The Hidden Cost of Unchallenged Resistance

When 'we tried that before' goes unchallenged in a meeting, it doesn't simply kill one proposal. It teaches every person present that proposing change carries social risk without proportionate reward. Over months and years, this dynamic creates what I call improvement silence — a state where teams observe dysfunction daily but have learned that flagging it produces nothing except personal exposure. The McKinsey finding that cross-functional handoffs cause 60% of process delays becomes permanently entrenched because nobody dares suggest redesigning those handoffs.

The financial arithmetic is stark. Process mapping exercises consistently identify 25–35% waste in existing workflows. If a team of ten knowledge workers generates £600,000 in annual output, that waste represents £150,000–£210,000 in unrealised value — every single year. Multiply that across departments and the figure dwarfs whatever the 'failed' initiative cost a decade ago. Yet the emotional memory of that one visible failure outweighs the invisible, distributed, ongoing cost of inaction.

There is a compounding dimension too. Companies with documented, actively managed processes grow at twice the rate of those without them. Every quarter that resistance delays improvement, the gap widens between the organisation and its better-managed competitors. The resistance doesn't merely preserve the status quo — it actively erodes competitive position. Employee turnover accelerates as high-performers leave for organisations that feel less stuck, and each departure costs roughly twice the departing employee's salary, partly because undocumented tribal knowledge walks out with them.

Distinguishing Legitimate Caution from Emotional Inertia

Not every invocation of 'we tried that before' is illegitimate. Organisations do accumulate genuine wisdom through failure. The critical skill for leaders is distinguishing between evidence-based caution and reflexive resistance. Evidence-based caution sounds specific: it names dates, describes the methodology used, identifies the precise failure point, and acknowledges what has changed since. Emotional inertia, by contrast, is vague, absolute, and resistant to follow-up questions.

A useful diagnostic technique involves three questions asked without confrontation. First: 'What specifically was tried, and when?' This separates genuine memory from inherited narrative. Second: 'What was the identified reason it didn't work?' This distinguishes between flawed execution and flawed concept — a crucial difference, since most process changes fail not because the idea was wrong but because implementation lacked structure. The DMAIC framework from Six Sigma exists precisely because Define and Measure must precede Analyse, Improve, and Control. Many 'failed' attempts skipped straight to Improve without proper diagnosis.

Third: 'What has changed in our business since then?' Organisations evolve continuously. The technology landscape shifts. Team composition changes. Client expectations transform. A process change that failed in 2018 with a different team, different tools, and different market conditions has almost no predictive validity for 2026. Process standardisation reduces error rates by 50–70% when implemented with proper methodology — but only if the methodology accounts for current conditions rather than historical assumptions.

Building a Culture That Evaluates Rather Than Vetoes

The antidote to reflexive resistance isn't ignoring institutional memory — it's formalising how that memory gets used. Progressive organisations create what might be called an evidence threshold: any claim that a change 'was tried before' must be accompanied by documentation. If no documentation exists — and remember, 60% of processes are undocumented — then the claim has no more weight than any other untested hypothesis. This isn't dismissive; it's intellectually honest.

Practically, this means implementing lightweight post-mortem protocols for every significant process change, successful or not. When the next iteration of an idea arrives years later, there's an actual record to consult rather than a campfire story. Process owners who review quarterly improve efficiency by 15% year-on-year precisely because they create this institutional clarity. They know what was tried, what worked, what didn't, and why — with specifics rather than mythology.

Leaders should also reframe the conversation from binary (try/don't try) to experimental. The Theory of Constraints teaches us to find and fix the bottleneck — not to redesign everything simultaneously. A pilot approach to process change — small, time-bound, measurable — sidesteps the emotional weight of 'we tried that' because it isn't proposing the same grand overhaul. It's proposing a contained test. Bottleneck elimination in the top three processes typically yields 80% of possible efficiency gains, which means even modest pilots in the right areas generate disproportionate returns.

The Leader's Role in Navigating Resistance

Senior leaders set the tone for how organisations handle dissent around change. If you visibly reward 'we tried that before' contributions without requiring evidence, you are actively incentivising stagnation. If you dismiss them entirely, you lose genuine institutional wisdom. The calibrated response acknowledges the concern, requests specifics, and commits to incorporating those specifics into the next attempt's design. This approach validates the person while refusing to let unsubstantiated claims dictate strategy.

One technique I recommend to executive clients involves separating the 'what failed' discussion from the 'should we try' discussion. Hold them in different meetings with different emotional registers. The first meeting is purely forensic — a respectful excavation of what happened, documented clearly. The second meeting takes that documentation as input alongside current data about process performance. The average SMB has 47 manual processes that could be partially or fully automated. When leaders present current automation possibilities alongside historical context, the emotional narrative loses its monopoly.

Critically, leaders must also model vulnerability about their own past decisions. If you led the initiative that failed previously, acknowledge it directly. Explain what you'd do differently. Demonstrate that failure is data, not identity. This single behaviour — a senior leader treating past failure as input rather than shame — transforms how teams relate to process change. It moves the culture from the ad hoc stage of the Process Maturity Model toward repeatable, then defined, then genuinely managed improvement.

Moving Forward: From Resistance to Structured Improvement

The organisations that break free from 'we tried that before' culture share a common characteristic: they make process performance visible. When workflow automation delivers an average ROI of 400% within the first year, the argument for experimentation becomes difficult to dismiss with anecdote alone. Visibility means dashboards, regular reporting, and — most importantly — connecting process metrics to outcomes people care about: client satisfaction, revenue, and personal workload.

A single well-documented standard operating procedure saves 2–3 hours per week per team member who uses it. Frame that concretely for your organisation. If eight people follow one documented process, that's 16–24 hours recovered weekly — nearly an additional full-time equivalent of productive capacity, extracted from thin air by simply writing down what good looks like. The resistance to doing this work is almost never rational. It's emotional residue from past disappointments dressed in the language of pragmatism.

Start with a single process. The one everyone complains about. Map it using Lean methodology — identify which steps add value and which exist purely from inertia. Document it properly. Measure the before and after. Only 4% of companies have integrated their processes end-to-end, which means the competitive advantage of even partial improvement is enormous. When the next person says 'we tried that before,' you'll have something more powerful than memory: you'll have data from last month showing exactly what works.