By Michael Nagorski, Founding Partner, Double Loop Performance
Most bad decisions at work don’t look bad when they’re being made.
They look reasonable. They arrive with a deck, a spreadsheet, a few aligned voices in a leadership meeting. There might be a phrase like, “We’ve seen this before,” which carries the weight of experience and the authority of someone who has been around long enough to know. The decision feels grounded, considered.
That is exactly what makes cognitive bias so costly inside organizations. It doesn’t appear reckless. It shows up as certainty—closing a conversation before the right questions have been asked.
I have spent decades working inside organizations at the point where decisions get made, systems get designed, and teams are asked to change. What I notice, consistently, is that most leadership teams are put in place for their intelligence and lack mechanisms that help them see their own (flawed) thinking.
That gap is what this post is about.
The Problem Isn’t the Decision. It’s the Process Behind It.
There’s a distinction that doesn’t get enough attention in how organizations think about performance: the difference between a decision and the process that produced it. Most organizations are wired to evaluate outcomes. Did we hit the number? Did the hire work out? Did the initiative get adopted? Those are useful questions, but they miss the upstream issue.
Good outcomes can come from flawed decision-making. And bad outcomes can follow well-reasoned, well-structured choices that happened to meet market conditions, a competitor move, or bad timing.
If you only evaluate the outcome, you may be rewarding the wrong process, scaling the wrong lesson, or ignoring the pattern underneath the result.
This is where cognitive bias lives. And it doesn’t stay in one part of the organization. It shows up in who gets hired, who gets managed out, which initiatives receive funding, which problems leadership chooses to solve, which data gets taken seriously, which voices get heard, and which risks get ignored.
Understanding these patterns isn’t about being harder on yourself or your team. It’s about designing better conditions for clearer thinking. That is, at its core, what the Double Loop System is built to do.
What Cognitive Bias Actually Is at Work
Cognitive bias is a predictable pattern of distorted thinking that affects how people interpret information, evaluate options, and reach conclusions. The word “bias” can make people defensive, as if it implies bad intent or poor judgment. It doesn’t. These patterns are wired into how the human brain processes the world, especially under conditions of pressure, ambiguity, and high stakes, which describes most meaningful workplace decisions.
The shortcuts our brains use are often functional. They allow us to process information quickly, conserve mental energy, and act without needing complete data. The trouble starts when those shortcuts get applied to situations where the full picture actually matters—where the cost of a wrong answer is high and the margin for error is significant.
What follows is a working guide to the biases that show up most reliably in organizations. Not as a list to memorize, but as patterns to recognize—in meetings, in hiring conversations, in strategic debates, and in the moments before a major change initiative gets approved.
Confirmation Bias
Definition: The tendency to notice, seek, and interpret information in ways that support what we already believe.
Once we form an opinion, the brain shifts from exploring to defending. We pay more attention to evidence that confirms the story. We explain away evidence that doesn’t fit. We remember the data points that support our view and down weight the ones that complicate it. This happens automatically—not through deliberate dishonesty, but through the ordinary mechanics of human cognition.
The insidious thing about confirmation bias at work is that it hides inside experience. “I’ve seen this before” is a legitimate shortcut much of the time. A leader who has watched a dozen change initiatives fail for the same underlying reason is right to trust that pattern. But the same shortcut becomes a liability when it causes them to stop looking. Experience can become a filter that transforms the richness of a new situation into a familiar template, long before the template has earned the fit.
In organizations, confirmation bias often shows up in how problems get framed. A leadership team believes a sales initiative is struggling because the sales team lacks discipline. Every missed CRM update becomes evidence. Every delayed deal becomes evidence. Every manager’s complaint becomes evidence. But no one seriously explores whether the positioning is unclear, the qualification criteria are broken, the coaching cadence is inconsistent, or the sales process was designed for a different market than the one the company now occupies. The original belief becomes the diagnosis, the diagnosis shapes the plan, and the plan solves the wrong problem.
The question worth asking before any major decision: What evidence would change our minds here? If the honest answer is “nothing,” the team isn’t evaluating anymore. They’re defending.
The Halo Effect
Definition: The tendency for one positive trait, credential, or impression to cause an overestimation of overall capability or quality.
The halo effect is most visible in hiring and promotion decisions, but it operates across any situation where one strong signal gets extended far beyond its actual range. A prestigious employer. An impressive academic institution. A polished presence in a room. A past success at a well-known company. Any of those signals may carry genuine weight. The problem is when a single one of them begins to stand in for the whole person.
The brand becomes the proof. Confidence becomes competence. The résumé becomes the result.
What gets lost in that substitution is the harder question: can this person do the actual work in front of them? Not the work they did somewhere else, under different conditions, with more resources, with clearer market demand. The work here. Now. In this context. With these constraints.
Organizations that rely heavily on the halo effect in hiring tend to discover the same thing repeatedly—that the candidate who looked extraordinary on paper arrived to find a reality their prior success hadn’t prepared them for. The prior organization had built the infrastructure. The systems were mature. The market was established. Here, those things need to be built from scratch. That requires a different set of capabilities than navigating a well-developed operating environment, and the halo didn’t check any of it.
Similarity Bias
Definition: The tendency to favor people, ideas, and approaches that feel familiar or that resemble our own background, experience, or style.
Similarity creates comfort, and comfort creates trust—at least the feeling of trust. We extend more credibility to people who speak the way we speak, who have walked a path we recognize, who frame problems the way we frame them. We feel more confident in ideas that resemble the ones that helped us succeed. We see potential in people who remind us of ourselves at an earlier point in our career.
None of these is malicious. It operates largely beneath conscious awareness. What it produces, consistently, is an organizational tendency to select for sameness while calling it fit.
Fit is a useful concept when it describes genuine alignment—shared values, complementary capabilities, a real match between what someone brings and what the role requires. Fit becomes a problem when it becomes a synonym for “comfortable” or “familiar.” At that point, the organization isn’t selecting for excellence. It’s selecting for its own reflection.
The cost shows up when the organization genuinely needs a different answer. When the market has shifted. When the problem is unlike any previous problem. When the same profile of thinker, hired over and over, produces the same range of solutions. The people in the room are qualified. They are just not equipped to see what their collective blind spots have obscured.
Status Quo Bias
Definition: The preference for the current state of affairs, even when evidence suggests a different approach would produce better outcomes.
Status quo bias doesn’t announce itself. It tends to arrive dressed as stability, or as wisdom “let’s not fix what isn’t broken,” or “our people need predictability right now,” or “we’ve tried changing that before and it caused more problems than it solved.” Those concerns are sometimes legitimate. The status quo sometimes deserves to stay.
What status quo bias produces, distinctively, is a situation where the current system holds its position not because it has earned it, but simply because it already exists. The familiar option has an asymmetric advantage: it carries no transition costs, no uncertainty, no requirement to build a case for itself.
This is one of the largest operational barriers to meaningful change inside organizations. The broken meeting continues because “this is how we stay aligned.” The outdated process that everyone routes around rather than replaces. The unclear decision rights that generate confusion every quarter but that no one has the appetite to redesign. The legacy structure that made sense three strategy cycles ago and has been outliving its context ever since.
The question that surfaces status quo bias is simple and usually uncomfortable: What are we protecting by keeping this the same? When the honest answer is “our comfort with the current arrangement” rather than “the performance of the organization,” you’ve found the bias.
Anchoring Bias
Definition: The tendency for the first piece of information received to exert disproportionate influence over subsequent judgment.
The first number, first impression, first explanation, or first narrative tends to become the reference point. Everything that follows gets evaluated relative to it, even when that original anchor was incomplete, preliminary, or offered before the full picture had developed.
In organizational decision-making, anchoring is expensive because many workplace problems first surface through someone’s early interpretation—a leader’s initial read, a headline number in a dashboard, an anecdote from a customer conversation, a vendor’s framing of the solution. That first version gets absorbed. It shapes the questions that follow. It often determines which options appear on the table.
Consider a department that misses its quarterly target. The first explanation offered is that there isn’t enough pipeline. It may be partially true. But once the pipeline narrative anchors the conversation, the team immediately redirects toward lead generation, marketing activation, and seller activity metrics. Weeks pass. Only later does someone trace the actual deal losses and discover that the issue wasn’t volume—it was poor qualification, weak executive engagement in late stages, and a discovery process that failed to surface fit problems early enough. The organization spent months solving the first explanation rather than the real one.
Availability Bias
Definition: The tendency to overvalue information that is recent, vivid, emotionally memorable, or easy to recall.
Memorable and representative are not the same thing. The most available information—the customer complaint everyone heard about, the deal that fell apart dramatically, the team that rallied visibly, the executive story that gets repeated at every offsite—feels important because it’s easy to retrieve. That ease of retrieval gets confused for signal.
A senior leader hears three detailed, emotional complaints about a new internal process. The complaints are specific. The people who raised them are credible. The leader concludes that the rollout is struggling. But the broader data tells a different story: adoption is strong, cycle time is improving, and the complaints are concentrated in one function with a workflow that genuinely differs from the norm. The vivid complaints were real. They were also not the pattern.
This bias is particularly relevant when organizations make talent decisions, performance assessments, or strategic calls based on recent events rather than sustained patterns. The team that had a strong quarter after a rough year. The leader who was outstanding in a visible crisis and has been coasting since. The initiative that generated excitement at launch and has quietly stalled in implementation. Availability bias shapes what we think we know about each of them.
Sunk Cost Bias
Definition: The tendency to continue investing in something because of what has already been committed, rather than because the future return justifies continued investment.
Organizations are remarkably reluctant to stop. The larger the prior investment—in budget, in executive attention, in public commitment, in political capital, the harder it is to call something off. Past investment becomes the justification for future investment, even when the evidence has changed.
This dynamic is common in transformation initiatives. A company is launching a significant change program. Six months in, adoption is low. Managers are confused. Employees are routing around the new process. Technology is technically live, but the behavior hasn’t moved. Instead of pausing to understand what was misread, the organization doubled down. More training. More governance. More communication. More accountability mechanisms. The question becomes, “How do we get people to comply?” The better question—”What did we misunderstand about the work, the people, or the conditions?”—goes largely unasked because asking it would require acknowledging that the original investment may have been built on faulty assumptions.
The discipline this bias requires is learning to separate the past from the future. The investment already made is gone regardless of what you decide next. The only useful question is whether the next decision, the next dollar, the next month, the next leadership conversation—is still pointing in a worthwhile direction.
Authority Bias
Definition: The tendency to give greater weight to the opinion of a senior or high-status person, regardless of whether their evidence is stronger than anyone else’s.
Hierarchy is a feature of organizations, and it carries legitimate information about experience, responsibility, and accountability. But hierarchy also shapes what gets said out loud in a room—and perhaps more importantly, what doesn’t. When a senior leader forms a strong opinion early in a discussion, the room tends to reorganize around it. People edit themselves. Questions soften. The concerns that got voiced in the hallway before the meeting don’t surface inside it.
The result is that decisions can appear aligned when they’re actually compliant. The team didn’t disagree. They adjusted. There’s a difference, and it matters when the decision later meets reality.
This isn’t a problem of bad intent on the leader’s part. Most of the time, the senior person in the room is simply doing what they’ve been rewarded for doing: forming views and articulating them clearly. The issue is structural. A well-functioning decision environment needs to be designed so that the quality of an idea can survive separation from the status of the person who holds it.
Framing Effect
Definition: The tendency to make different decisions based on how the same information is presented, rather than on its actual content.
The frame precedes the solution. If a problem is framed as a people issue, the organization will look for accountability mechanisms, coaching, or talent changes. If the same problem is framed as a systems issue, the organization will examine processes, incentives, decision rights, and operating rhythms. The symptoms may be identical. The frame determines which interventions become visible.
Consider a team that consistently misses deadlines. Framed as an ownership problem, the response is performance conversations and accountability reviews. Framed as a capacity and prioritization problem, the response is a conversation about how work enters the system, how competing priorities get resolved, and how the team communicates overload before a deadline becomes a failure.
Neither frame is automatically correct. But only one of them leads to a structural diagnosis of what’s actually happening. The other leads to a people management conversation that may relieve pressure briefly and change nothing downstream.
Outcome Bias
Definition: The tendency to judge the quality of a decision based primarily on how it turned out, rather than on the quality of the reasoning that produced it.
This one is particularly relevant for organizations that take learning seriously, which is to say, organizations that want to get better rather than just luckier.
Good outcomes can come from poor decisions. The deal closes not because the sales strategy was sound, but because the buyer had an internal champion who pushed it through despite every obstacle. An initiative succeeds not because the change was well-designed, but because a few committed managers absorbed the dysfunction and shielded their teams from it. A hire works out not because the process was rigorous, but because the person was extraordinarily adaptable and grew into something the interview didn’t predict.
When the organization treats those wins as validation of its process, it scales the wrong lesson. It reinforces what felt right rather than what worked. The result, over time, is a culture that mistakes luck for skill and has no mechanism for telling the difference.
The corrective is not to ignore outcomes—they matter enormously. It’s to examine both what happened and how the decision was made. A successful outcome reached through flawed reasoning deserves as much scrutiny as a failed outcome reached through sound reasoning. Organizations that do this well build genuine learning into their operating rhythm rather than harvesting confidence from results they may not fully own.
How These Biases Show Up Across Major Organizational Decisions
It’s worth being direct about something: none of these biases live exclusively in the hiring process, even though that’s often where the conversation about workplace bias begins. They show up across the full range of consequential organizational decisions—and they compound.
When a company is deciding whether to let a leader go, for example, availability bias shapes what the decision-makers remember. Authority bias shapes whose view carries the room. Sunk cost bias makes tenure itself feel like an argument for continuation. Similarity bias may make the underperformance less visible if the leader is culturally well-matched to the people making the call. And confirmation bias will cause those who want a change to find evidence for it, just as it will cause those who want to protect the relationship to find evidence for that.
In major strategic initiatives, the compounding is even more pronounced. Confirmation bias shapes the original business case—the team finds evidence that supports the direction leadership has already indicated. Anchoring bias locks the scope of the initiative to the first version of the proposal. Authority bias silences the dissenting voices. Status quo bias protects the existing structure from being examined as part of the problem. Sunk cost bias keeps the initiative alive after the evidence has turned. Outcome bias causes the organization to take the wrong lesson when it ends, whether it succeeds or fails.
This is not a description of a dysfunctional organization. It is a description of a normal one. The question is whether the organization has a mechanism for interrupting the pattern.
The Double Loop Difference
The Double Loop System is grounded in a distinction that the psychologist Chris Argyris made decades ago and that most organizations still haven’t fully absorbed.
Single-loop learning is what happens when an organization detects a gap and corrects its behavior. The number is off, so we add more activity. The process isn’t working, so we are changing the agenda. The hire didn’t land, so we adjusted the job description. These are useful moves. They address the surface. What they leave untouched are the assumptions, the structures, the incentive patterns, and the decision-making habits that produced the gap in the first place.
Double-loop learning asks the harder question: Why does this keep happening?
Not just what went wrong, but what we believed led us here. What we were measuring that made this outcome invisible until it was obvious. What the organizational system was rewarding that made this behavior rational for the people inside it. What we are not saying out loud that would change the conversation if we did.
That second loop is where bias lives—and where it can be interrupted. Not eliminated. Human beings will continue to use heuristics and shortcuts. The brain is not going to stop being a brain. But organizations can design conditions that make flawed thinking easier to notice and easier to correct. Structured decision processes. Diverse perspectives that aren’t performative. Explicit criteria established before the options are evaluated. Pre-mortem conversations that ask what we’re most likely to be wrong about before we commit. Reviews that look at the reasoning behind decisions, not just the results.
This is the work. Not flashier frameworks or another leadership development program. The unglamorous, disciplined practice of looking at how the organization thinks before assuming the problem is in what it knows.
Five Questions Worth Asking Before the Next Big Decision
These are not a checklist. They’re an invitation to slow the room down long enough to see the thinking.
What have we already decided without saying it out loud?
Most organizations enter major decisions with a significant amount of pre-formed opinion. The legitimate question is whether that opinion has been tested or simply acted on.
What evidence are we overvaluing because it’s recent, familiar, or attached to someone with authority?
The most available information is often the loudest. Loud and important are not the same thing.
What evidence are we avoiding because it complicates the story we’d prefer to tell?
This one takes honesty. The evidence we don’t bring into the room is often as consequential as the evidence we do.
Who would see this situation differently, and have we actually asked them?
Not in a check-the-box way. In a way that creates genuine room for a different view to change something.
If this decision turns out to be wrong, what will we wish we had noticed today?
The pre-mortem is one of the more useful practices in decision-making research. It forces the group to think forward rather than defend the current position.
These questions don’t resolve anything by themselves. They open space. And in most organizations, space is the one thing the decision-making process doesn’t have nearly enough of.
A Final Thought
The hardest bias to catch is the one that feels like good judgment.
That’s not a critique of leaders. It’s a structural observation. The patterns described here are not character flaws. They are the normal operation of a human brain under the conditions that workplace decisions routinely create: time pressure, high stakes, incomplete information, social dynamics, and the legitimate authority of experience.
The goal isn’t to make people doubt everything they know. It’s to create enough reflective space—in individuals, in teams, in the operating rhythms of the organization—that the patterns have a chance to surface before they become the outcome.
That is what double-loop work is. Not a workshop. Not a framework. A practiced discipline of looking at the organization’s thinking, not just its results.
The work is slower, and it is harder. It also compounds in ways that single-loop fixes rarely do.
About The Author
Michael Nagorski is the Founding Partner of Double Loop Performance, an organizational development and leadership consulting practice based in Newark, Delaware. He works with executive teams, change leaders, and facilitators who are tired of talking about the right things and ready to actually do them.
Michael has spent more than 15 years helping organizations at inflection points — when they need to move differently without losing what made them good. That has ranged from designing decision-making frameworks for Fortune 500 sales organizations to building facilitation systems for senior leadership teams navigating strategy execution, technology adoption, and culture change.
His work lives at the intersection of facilitation design, behavioral science, and organizational accountability — with a strong bias toward the practical over the theoretical.
He holds graduate degrees from the University of Delaware in Organizational Development and Change and Business Administration, and is the developer of the MEET Funnel methodology for structured decision facilitation.
Contact Double Loop Performance or contact Mike directly through LinkedIn.