Why Teams Stop Noticing Inefficiencies (And How to See Them Again)

Ask a tenured employee what is slowing their team down and you will often hear: "Honestly, nothing major." Ask the person who joined three weeks ago and you will get a list. Same company, same processes, very different answers.

We see this pattern in almost every company we walk into, and it is not about new hires being naive or veterans being wrong. It is a well-documented psychological pattern. When friction sticks around long enough without causing a visible failure, the brain quietly reclassifies it from "problem" to "how things work here." The workaround becomes the workflow. After a while, nobody on the team can see it anymore.

The research on this pattern comes from sociology of aerospace disasters, behavioral economics, and 50 years of experimental psychology. The lessons apply directly to why growth companies keep running operations that anyone outside the building would call broken.

What does it mean when teams normalize friction?

Normalization of friction is the organizational process by which inefficient, duplicative, or error-prone work becomes culturally accepted as normal because it has not caused an obvious failure. The workaround stops registering as a workaround. The team defends it when challenged.

The concept originates with sociologist Diane Vaughan, whose 1996 book The Challenger Launch Decision introduced the term "normalization of deviance." Vaughan studied how NASA engineers progressively accepted O-ring damage on Space Shuttle flights that should have prompted a launch halt. Each flight that did not explode became evidence that the observed damage was acceptable, until the 1986 Challenger disaster proved otherwise. The same pattern repeated at NASA in 2003 when foam strikes on the Columbia shuttle had been observed for 22 years and treated as a non-issue, right up to the moment Columbia broke apart on reentry.

Vaughan's argument was not that NASA engineers were careless. The problem was structural. When a deviation from correct behavior does not immediately produce catastrophe, it gets absorbed into the definition of normal. The next deviation is measured against the new, looser standard. Repeat this enough times and the organization can drift a long way from safe without anyone feeling they made a wrong call. Operations inside a growth company rarely blow up. They just get slower, more expensive, and more dependent on individual heroics to keep moving. The mechanism is the same.

Why do senior hires see bottlenecks faster than tenured staff?

Senior hires see bottlenecks faster because they have not yet habituated to them. A newcomer's brain still tags unusual steps, redundant handoffs, and awkward tool switches as novel. A tenured employee's brain has compressed those same steps into a single automated routine and stopped flagging them.

Psychologists call this habituation: the gradual decline in response to a repeated stimulus. It is useful in most of life. You would go crazy if the hum of your refrigerator felt new every morning. It is damaging in operations because the brain habituates to time waste the same way it habituates to background noise.

Asana's Anatomy of Work research makes the tenure effect measurable. New hires spend nearly twice as much time on duplicated work as tenured teammates, not because new hires are less efficient, but because they are more willing to call it duplicated work. Tenured staff have reclassified the same activity as "how the finance review cycle runs." They still do the duplicated work. They just do not see it as a problem anymore.

This is why companies get their sharpest operational critiques during a new executive's first 90 days and then lose that clarity. The window closes as the new hire starts calling the friction "the finance review cycle" along with everyone else. For a structured way to capture those observations before they fade, see how to run an operations audit in 5 days.

How does normalization of deviance apply to operations?

Normalization of deviance applies to operations any time a workaround, manual step, or error-prone handoff gets repeated without causing an immediate, visible failure. Each repetition without catastrophe reinforces the belief that the current process is acceptable, which lowers the threshold for accepting the next workaround.

Consider a finance team reconciling two billing systems by hand because the integration never got built. Month one, someone flags it. Month three, it is "the reconciliation." Month twelve, it is on the job description. Month twenty-four, a new finance hire suggests fixing it and gets told "that is how we do close here." In under two years the task has drifted from temporary workaround to defended institution, with no one making a conscious decision along the way.

The same drift happens with manual data re-entry, Slack-based approval chains, and the shared spreadsheet that silently runs a critical function. None of them fail catastrophically in any given week. All of them compound. For a catalog of the friction patterns this produces, see the 7 most common operational bottlenecks in growing companies.

What is status quo bias, and how does it lock in bad processes?

Status quo bias is the documented preference for keeping things as they are, even when a clearly better option exists. William Samuelson and Richard Zeckhauser coined the term in a 1988 paper in the Journal of Risk and Uncertainty after running experiments that showed people systematically choose the existing option at rates far higher than the option's actual merits would predict.

Samuelson and Zeckhauser traced the bias to loss aversion, sunk cost thinking, cognitive dissonance (changing it means admitting the old way was bad), and regret avoidance (a failure after a change feels worse than a failure after doing nothing).

In operations, status quo bias sounds like: "We looked at new tools two years ago and it was not worth the migration." "The team knows this process." "If it is not broken, why break it?" The last phrase is the tell. A process that eats 12 hours a week on manual reconciliation is broken. It just is not broken in a way that sets off alarms, so the cognitive cost of changing it feels higher than the ongoing cost of living with it.

Why does learned helplessness quietly entrench friction?

Learned helplessness is a psychological state, first identified by Martin Seligman and Steven Maier at the University of Pennsylvania in 1967, in which repeated exposure to an uncontrollable negative situation causes a person to stop trying to change it, even when change later becomes possible.

Seligman's original experiments were on dogs, but the workplace parallel is straightforward. An employee flags a broken process in their first year. Nothing changes. They flag it again in year two. Leadership says it is a priority, then deprioritizes it. By year three, they stop flagging. By year four, they forget it was ever a complaint. Organizational researchers call the resulting silence "acquiescent silence," and identify it as a direct downstream effect of learned helplessness in the workplace.

The cost shows up in Gallup's State of the Global Workplace 2024 report. Gallup found that only 21% of employees globally are engaged at work, down from 23% the prior year, a two-point drop representing an estimated $438 billion in lost productivity. Disengaged employees do not report friction. They absorb it. A company running on disengaged absorption looks stable from the top because no one is complaining. Underneath, every process is degrading.

What does the data say about how much friction is hiding?

The data consistently shows that knowledge-work organizations lose 20 to 40 percent of capacity to work that produces no external value. Several large-sample studies converge on this range from different angles.

Asana's Anatomy of Work Index found knowledge workers spend 60% of their time on "work about work," the coordination overhead of chasing updates, switching tools, and attending meetings that do not advance real output. Asana also measured 209 hours per worker per year lost to duplicative work. McKinsey's Organizational Health Index, built on more than 8 million survey responses from 2,600-plus client organizations, finds that top-quartile-health companies deliver roughly three times the total shareholder returns of bottom-quartile peers. The gap between healthy and unhealthy operations is not small.

The implication: in a typical growth company, somewhere between one and two days per employee per week is going to work the organization has stopped noticing. For a concrete walk-through of where that time disappears, see finding operational friction.

Why do smart teams defend broken processes?

Smart teams defend broken processes because the process is entangled with their identity, their past effort, and their relationships. Attacking the process can feel like attacking the people who built it, maintained it, or succeeded in spite of it.

A few forces compound here. Sunk cost thinking is the obvious one: the team has spent months or years making the current process work, and discarding it devalues that investment. Then there is expertise identity. The person who knows how to work around the broken process has status because of that knowledge. Fix the process and the status dissolves. And social cohesion matters too. The workarounds often exist because a specific relationship makes them possible, so pointing at the workaround can feel like pointing at the colleague.

None of this is malicious. It is the predictable result of humans working in the same system for a long time. The fix is not to override the instinct through willpower. It is to introduce structures that let the team examine the process without examining themselves.

How to re-see your operations

Re-seeing operations requires deliberately recreating the outsider effect that new hires provide naturally. A few tactics do this reliably, and each one works because it bypasses the habituation, status quo bias, and sunk cost instincts that keep friction invisible.

Run a fresh-eyes audit

A fresh-eyes audit is a time-boxed review of a workflow conducted by someone who does not normally work on that workflow. Pull a finance person into a sales-to-onboarding review. Pull a sales leader into a close-the-books review. Ask them to document every step that seems strange, slow, or redundant, without worrying whether their observations are "fair."

The output is a list of friction points that the owning team has stopped seeing. Expect the owning team's first reaction to be defensive. That defensiveness is the signal that habituation has taken hold. The audit worked.

Use reverse brainstorming on your own process

Reverse brainstorming inverts the usual question. Instead of "how do we make this process better," ask "how would we make this process worse." List every answer. Then check how many of the answers describe things you already do.

This works because status quo bias protects "what we do" but not "what would be bad to do." Strip the defensive layer and teams will name the ten-year-old workaround as a clearly bad idea instead of "how we handle it." The exercise takes 45 minutes and usually surfaces three to five friction points the team already knew about but had stopped saying out loud.

Conduct a process tear-down

A process tear-down is a documented end-to-end walkthrough of a workflow, where the team describes every step, every tool, every handoff, and every decision point out loud, in front of observers. Narrating the process to someone who has not lived inside it forces the narrator to notice the steps their own brain had compressed into "just what happens."

The tear-down surfaces two categories of friction: steps the team knew were wasteful but had stopped complaining about, and steps the team did not realize were wasteful until they said them out loud. For a full five-day version of this method applied across a company, see how to run an operations audit in 5 days.

Audit your manual workarounds specifically

Manual workarounds are the easiest early signal of normalized friction because they almost always started as temporary. Any shared spreadsheet that two departments both update, any Slack channel routing tasks that should route themselves, any recurring calendar event for a check a system should trigger, is a workaround that stopped being temporary. For a deeper breakdown of what those workarounds cost, see the hidden cost of manual workarounds.

Key takeaways

Teams stop noticing friction for four reinforcing reasons. Habituation: the brain stops flagging repeated non-catastrophic events. Normalization of deviance, per Vaughan's NASA research: each workaround that does not fail becomes the new baseline. Status quo bias, per Samuelson and Zeckhauser: keeping the current process feels safer than changing it. Learned helplessness, per Seligman and Maier: after enough unsuccessful attempts to fix something, people stop trying.

The result is that growth companies routinely run operations where 20 to 40 percent of capacity gets absorbed by work the team has stopped seeing as wasteful. The people closest to the work are the least equipped to find it.

The fix is structural, not motivational. You need outsider perspective, inverted questions, or the forced narration of a tear-down. Pick one and run it this quarter. You cannot think your way out of habituation from inside the process that created it.