The Twelve Mistakes That Sank a Company — Train the Judgment That Catches the Design in Time

Marcus and the Twelve Mistakes

  1. Confirmation bias — the filter that confirms what you already believe.
  2. Anchoring — the first number owns you.
  3. The availability heuristic — what comes to mind easily feels true.
  4. The Dunning-Kruger effect — the less you know, the more confident you are.
  5. The sunk cost fallacy — throwing good money after bad.
  6. Overconfidence bias — you’re worse at predicting than you think.
  7. The halo effect — one good thing makes everything look good.
  8. The bandwagon effect — social proof standing in for thinking.
  9. Negativity bias — bad news hits harder and sticks longer.
  10. The planning fallacy — you will take longer and cost more than you think.
  11. Status quo bias — the default option always wins.
  12. Fundamental attribution error — it’s your fault, but my circumstances.

Picture a founder — I’ll call him Marcus Chen, a composite built from a pattern that shows up constantly in failed startups, not one specific person. In 2019 he raised $2.4 million in seed funding for a technology company in Austin. By the end of 2021, that money was gone, the company was dissolved, and Marcus was sleeping on a friend’s couch running up credit card debt. He wouldn’t blame the market. He wouldn’t blame his investors. In the version of this story I want you to sit with, he’d put it simply.

“I made the same twelve mistakes over and over and didn’t know what any of them were called until it was too late.”

That sentence is the reason this episode exists, and it’s the reason you’re listening to it. Cognitive biases are not a soft topic for you. They are not a self-help buzzword. They are documented, replicated, peer-reviewed failures in human reasoning that destroy businesses, end careers, wreck relationships, and in extreme cases get people killed. Daniel Kahneman and Amos Tversky spent thirty years mapping these failures. They weren’t doing it so people could feel better about themselves. They were doing it because they wanted to understand why smart, educated, experienced people — people like you — make catastrophically bad decisions with disturbing regularity.

The answer they found: it’s not stupidity. It’s architecture. Your brain is built for speed, not accuracy. The shortcuts it uses to process the world fast — what Kahneman calls System 1 thinking — are the same shortcuts that betray you at the exact moments when precision matters most to you.

“It is remarkable how much long-term advantage people like us have gotten by trying to be consistently not stupid, instead of trying to be very intelligent.” — Charlie Munger

This episode is a field guide for you. Twelve biases. Each one named, defined, and shown to you through its real consequences. Stay with me through all twelve, because by the end I’m going to hand you the Decision Audit Protocol — a six-step process for catching your own mind before it gets you killed financially, professionally, or relationally. No therapy-speak. No “be kind to yourself.” Just the tools that actually work on you.

Here are the twelve you’re about to learn to catch in yourself.

Twelve. Let’s go through them one at a time, and I want you checking yourself against every single one.

Why Your Brain Lies to You By Design

The Decision Audit Protocol — brain thinking logic Before we go bias by bias, you need to understand the architecture of the problem you’re working with. Kahneman’s landmark 2011 book Thinking, Fast and Slow — built on four decades of research with Tversky — introduced the now-famous distinction between System 1 and System 2 thinking. System 1 is fast, automatic, pattern-matching, emotional. System 2 is slow, deliberate, logical, effortful. Here’s the critical point most people miss about themselves: System 2 is lazy. It outsources to System 1 by default. You are running on autopilot almost all the time, and your autopilot was calibrated for a savanna environment where the biggest decision you faced was whether that shadow in the grass was a lion.

It was not calibrated for you evaluating a forty-seven-page investment prospectus. It was not calibrated for you deciding whether to leave a six-year relationship, or choosing between two competing business strategies when both have incomplete data.

Dan Ariely, the behavioral economist at Duke, ran hundreds of experiments demonstrating what he called “predictably irrational” behavior — people making the same irrational choices in the same situations, repeatedly, despite being educated and intelligent. His conclusion was brutal, and it applies to you as much as anyone he studied: you don’t have occasional lapses in rationality. You have systematic, predictable, exploitable irrationality baked into how you process the world.

Philip Tetlock spent twenty years studying expert judgment — tracking the predictions of 284 professional forecasters across 82,361 forecasts. His 2005 book Expert Political Judgment demolished the idea that expertise protects you from bad reasoning. Experts were barely better than random chance at long-range predictions. The ones who performed best — what Tetlock later called “superforecasters” — were the ones who actively hunted for their own biases and corrected for them. That’s your model going forward. Not smarter. Better at catching yourself.

That’s the setup. Now let’s go through the twelve, one at a time, and I want you to notice which ones make you uncomfortable — those are usually the ones already running on you. One more thing before we start. You are not going to like every bias on this list. Some of them will feel like they’re describing someone else — a colleague, a rival, a stranger you read about online. Watch for that feeling specifically. It’s the bias blind spot showing up before we’ve even gotten to its formal name, and it’s going to be the single hardest thing in this whole episode for you to actually apply to yourself instead of to the nearest available target.

Confirmation Bias: The Filter That Confirms What You Already Believe

Confirmation bias is the one you’ve already heard of and almost certainly haven’t actually corrected for. You seek out information that confirms what you already believe. You dismiss information that contradicts it. You remember the hits and forget the misses.

Here’s what makes it lethal for you specifically: it’s invisible in the moment. You don’t feel like you’re cherry-picking. You feel like you’re doing research. You feel thorough. You feel like you’re building a case based on evidence. What you’re actually doing is building a prosecution, not an investigation. You’ve already decided the verdict, and you’re just assembling the facts that support it.

Marcus spent six months “researching” his target market before launch. He interviewed two hundred potential customers. Every interview that was enthusiastic, he treated as validation. Every interview that raised concerns, he categorized as “not the target demographic” or “they just don’t understand it yet.” The company collapsed. He went back through his own notes from those two hundred interviews afterward. The concerns were right there — documented, written down in his own handwriting — and he had simply never processed them as real data.

The academic record on this is comprehensive. Peter Wason’s famous 2-4-6 task experiment in 1960 showed that subjects who were given the number sequence 2-4-6 and asked to discover the underlying rule kept testing sequences that confirmed their initial hypothesis rather than sequences that might falsify it. The rule was simply “any ascending sequence.” But subjects repeatedly tested things like “even numbers” or “increases by two,” because they were seeking confirmation, not disconfirmation, and you would have done the same thing.

Tetlock’s superforecasters beat this bias by adopting what he calls “active open-mindedness” — deliberately seeking out the strongest version of the opposing argument before finalizing a judgment. Not the weakest version. Not the strawman. The strongest version. Here’s how you fight it: before any major decision, write down the three strongest arguments against the choice you’re leaning toward. Not weak objections you can dismiss with one hand — the strongest objections from the most credible critics you can find. If you can’t do this, you’re operating on confirmation bias, not information, and you should know that about yourself before you act.

Anchoring: The First Number Owns You

The Decision Audit Protocol — decision crossroads choice Anchoring is Kahneman and Tversky’s demonstration that the first piece of numerical information you receive — even if it’s completely arbitrary — shapes every subsequent estimate you make.

In one of the most striking experiments, subjects were asked to spin a wheel of fortune that was rigged to land on either 10 or 65. They were then asked: what percentage of African nations are in the United Nations? People who spun 10 guessed around 25%. People who spun 65 guessed around 45%. The spinning wheel had nothing to do with the question. It was pure random noise, and it still moved the estimates by twenty percentage points. It would move yours too.

In your salary negotiations, whoever names the first number sets the anchor. In real estate, the listing price is an anchor. In legal damages, the plaintiff’s initial demand is an anchor. Ariely demonstrated in Predictably Irrational that he could get MIT Sloan MBA students to anchor their willingness to pay for consumer goods — wine, chocolates, wireless keyboards — to the last two digits of their Social Security numbers. People with high SSN endings were willing to pay significantly more for the same products than people with low endings. Their Social Security numbers were setting their prices, and they never noticed it happening.

You do this too, constantly. If you’re an entrepreneur, you anchor your fundraising valuation to the first term sheet you receive. If you’re an employee, you anchor your salary expectations to your previous salary rather than your market rate. If you’re an investor, you anchor your entry price to what you originally paid for an asset rather than what it’s actually worth now.

Here’s how you fight it: before entering any negotiation or making any numerical estimate, write your own number down first, based on your own analysis. Do this before you receive any external information. Once you see the other party’s number, your anchor is set — you can’t unsee it. The only protection you have is to set your own anchor before theirs ever reaches you.

The Availability Heuristic: What Comes to Mind Easily Feels True

The availability heuristic is Kahneman and Tversky’s term for your tendency to assess the likelihood of events based on how easily examples come to mind. If you can think of lots of examples quickly, the event feels common to you. If examples are hard to find, it feels rare.

The problem: your ease of recall is driven by recency, emotional intensity, and media coverage — not by actual frequency. After a plane crash, you dramatically overestimate the risk of flying. After a shark attack makes the news, beach attendance drops. After you personally know someone who was robbed, you overestimate urban crime rates. The information that’s most vivid and accessible in your memory skews your probability estimates, often by enormous margins.

This operates constantly in your business decisions. If you recently read three success stories about companies that pivoted to video content, you’ll overestimate the success rate of that strategy. If you personally know an entrepreneur who built a company from nothing through sheer hustle, you’ll overestimate the role of hustle relative to timing, capital, and luck. The stories you know best — the ones most cognitively available to you — become your mental model for what’s normal, whether or not they actually are.

Gary Klein, the cognitive psychologist who spent decades studying decision-making in high-stakes environments — firefighters, military commanders, intensive care nurses — documented how availability bias shows up in expert judgment. Experienced professionals pattern-match to similar cases they’ve seen before. If the most memorable similar case in your own memory was an outlier, it skews your read of the situation in front of you right now.

Here’s how you fight it: replace availability with base rates. Before making any probability estimate based on examples you can think of, go find the actual statistical base rate for the outcome you’re estimating. The base rate is the ground truth. Your mental examples are a biased sample, and you should treat them that way.

The Dunning-Kruger Effect: The Less You Know, The More Confident You Are

The Decision Audit Protocol — bias blind spot David Dunning and Justin Kruger published their seminal 1999 paper “Unskilled and Unaware of It.” It demonstrated that people with low competence in a domain systematically overestimate their ability, while people with high competence systematically underestimate theirs. The mechanism is straightforward: the skills required to evaluate quality performance in a domain are the same skills required to produce quality performance. If you lack the skills, you lack the ability to recognize your own deficiency. You can’t see what you can’t see.

This isn’t about intelligence. Dunning and Kruger’s experiments covered logical reasoning, grammar, and humor appreciation, and the pattern held across all of them. Bottom-quartile performers estimated they were in the 62nd percentile. Top-quartile performers estimated they were in the 70th — underselling their own actual 86th-percentile standing.

Picture a man I’ll call Derek, another composite — he’d spent fifteen years as a regional sales manager before deciding to start a restaurant. He had eaten at thousands of restaurants. He had opinions about restaurants. He was absolutely certain he understood the business. He lasted eight months. What he didn’t know — what he couldn’t know, because he didn’t know enough to know what he didn’t know — was everything that happened between the front door and the plate. Labor scheduling. Food cost variance. Health department compliance. Equipment maintenance. Supply chain management. Cash flow timing. He was operating with massive confidence in the ten percent of the domain he could actually see, and you might be doing the same thing right now in something you haven’t examined closely enough yet.

Here’s how you fight it: actively seek feedback from people who operate at the top of any field you’re entering. Not encouragement — feedback. The gap between what you think you know and what you actually know only gets revealed by engaging with people who are at the level you’re trying to reach. Their questions will show you what you’ve never even considered.

The Sunk Cost Fallacy: Throwing Good Money After Bad

You’ll hear this covered in far more depth in a future episode, but it belongs here too, because it’s not just an economic error for you. It’s a cognitive architecture failure. The sunk cost fallacy is your tendency to keep investing in something because of what you’ve already invested in it, rather than because of its future prospects for you. The past investment is gone. It cannot be recovered. The only rational question left is: what’s the best use of your resources going forward? But the psychological weight of your past investment distorts that calculation for you every single time.

Kahneman’s loss aversion research — the finding that your losses are felt approximately twice as powerfully as equivalent gains — is the foundation underneath this. Abandoning a losing investment forces you to realize the loss psychologically, right now, in the present tense. Continuing the investment lets you maintain the fiction that you haven’t lost yet. Your brain chooses the fiction almost every time.

Marcus’s startup died six months after it should have. He knew at month eighteen that the core product wasn’t finding product-market fit. He had the data sitting right in front of him. He kept going for six more months because he’d already burned through $1.8 million and couldn’t psychologically accept that the remaining $600,000 would also disappear. Those extra six months cost him everything, including the time he could have used to start something new with the capital he had left.

Overconfidence Bias: You’re Worse at Predicting Than You Think

The Decision Audit Protocol — chess strategy thinking Overconfidence bias is distinct from Dunning-Kruger. It’s not about your skill assessment. It’s about your prediction accuracy. When you express 90% confidence in a prediction, you’re right about 70% of the time. When you express 99% confidence, you’re right about 85% of the time. You are systematically overconfident in your own forecasts, and so is everyone you know.

Tetlock’s twenty-year study of expert forecasters is the definitive dataset here. Across 82,361 forecasts from 284 professional analysts, political scientists, and economists — people whose literal job was making predictions — the average expert performed barely above chance. And critically, the most frequently cited, most publicly prominent experts performed the worst. Confidence and accuracy were negatively correlated. The louder the voice, the worse the forecast tended to be.

Annie Duke, who spent years as a professional poker player before becoming a behavioral economist, talks about this in Thinking in Bets. Poker forces a reckoning with this bias because you get immediate feedback. You can make an excellent decision and lose the hand. You can make a terrible decision and win. The feedback loop is there, and it’s relatively clean. In most of your life, the feedback loops are slow, noisy, and easy to rationalize away. That’s why your overconfidence goes uncorrected for decades if you let it.

Here’s how you fight it: assign probability ranges to your predictions rather than binary yes or no. Instead of “this will work,” say “I estimate a 65% chance this works, with a margin of error of plus or minus 20%.” Then track your predictions. After six months of tracking, look at your own calibration. If everything you said had a 70% chance happened 90% of the time, you’re underconfident. If it happened 40% of the time, you’re overconfident. Calibration training — which Tetlock used with his superforecasters — measurably improves your prediction accuracy over time.

The Halo Effect: One Good Thing Makes Everything Look Good

The halo effect is your tendency for a single positive characteristic to make you rate all of someone’s other characteristics positively too. Physically attractive people get assumed to be more intelligent, more competent, more ethical, and more likable. Successful companies get assumed to have better management, better culture, and better strategy — often without any independent evidence for those claims. A person who gives a confident, polished presentation gets assumed to have sound ideas underneath it, whether or not they actually do.

Kahneman identified this as one of the most pervasive sources of cognitive noise in organizational decision-making. If you’re hiring, the halo effect means a candidate who interviews well gets rated highly across all competencies, even the ones you never actually assessed in the interview. If you’re investing, a company with a hot brand gets a higher valuation multiple from you regardless of whether the underlying unit economics support it. If you’re following a leader, a charismatic founder gets deference on technical decisions where their charisma provides zero relevant information to you.

Picture a second composite — I’ll call her Priya, built from a pattern common among people who join startups for the wrong reasons. She joined a startup as VP of Marketing because the CEO was impressive. He was articulate, Harvard-educated, and had raised significant capital from recognizable funds. She assumed those things meant his business judgment was sound. After eighteen months, she understood that his fundraising ability was completely disconnected from his ability to actually run a business. He was excellent at one specific skill — pitching venture capitalists — and she had halo-effected that single skill into a global assessment of his overall competence.

Here’s how you fight it: evaluate people and opportunities on individual dimensions independently. When you assess a job candidate, score them on communication separately from technical competence, separately from leadership history, separately from cultural fit. Don’t let your overall impression contaminate your individual category scores. The same principle applies when you’re evaluating companies, strategies, and partners.

The Bandwagon Effect: Social Proof As a Replacement For Thinking

The Decision Audit Protocol — psychology cognitive error You are a profoundly social animal. Your brain is wired to treat consensus as evidence of truth. If everyone around you believes something, your brain treats that as strong evidence the thing is true. This was adaptive for you in small tribes where social knowledge was reliable. In modern environments, where mass media, social platforms, and marketing can manufacture the appearance of consensus, it becomes a vector for large-scale manipulation of you specifically.

The bandwagon effect is what drives financial bubbles. When asset prices are rising, everyone around you seems to be making money in that asset. Your social network confirms it. Your media confirms it. Your availability heuristic kicks in — you can easily think of people who got rich. Your confirmation bias kicks in — you notice the success stories and discount the skeptics. And then the bandwagon effect makes the whole thing feel like obvious truth to you: everyone knows this is the right move, so it must be.

Robert Shiller at Yale won the Nobel Prize partly for documenting the psychological mechanisms behind speculative bubbles — the ways that social contagion, narrative, and group consensus drive asset prices far beyond fundamental value. This isn’t a story about isolated irrational actors out there somewhere. It’s a story about how consensus reasoning — trusting what everyone around you believes — can be catastrophically wrong for you when the consensus itself is irrational.

Dan Ariely’s experiments on social norms demonstrated that your choices are heavily influenced by descriptive social norms — what you believe other people are doing. Hotels that told guests “the majority of guests in this room reuse their towels” got significantly higher towel reuse rates than hotels that gave environmental arguments instead. The social proof was more persuasive to people than the reasoned case.

Here’s how you fight it: separate “this is popular” from “this is correct.” These are different claims that require different evidence from you. The popularity of a belief is not evidence for its truth. Before you accept a consensus view, ask yourself: what’s the actual evidence for this position, independent of how many people hold it?

Negativity Bias: Bad News Hits Harder and Sticks Longer

Kahneman’s research on loss aversion found that your losses feel roughly twice as painful as equivalent gains feel pleasurable. That’s the financial expression of a deeper negativity bias that operates across all of your experience. Negative information gets more processing, more memory encoding, and more behavioral weight from you than equivalent positive information ever does.

This was adaptive for you once. Predators, poisons, and social rejection were more immediately costly than equivalent gains were beneficial. Your brain evolved to overweight threats. In modern environments, this bias systematically distorts your risk assessment, causes you to miss opportunities because of exaggerated fear of downside, and creates persistent psychological damage from negative events you never quite recover from properly.

The practical consequences for you are widespread. Risk-averse decision-making that prevents you from taking necessary action. An inability to take career risks because your fear of failure outweighs your sense of the potential upside. Relationship damage driven by your tendency to remember criticisms longer and more vividly than compliments. News media that’s optimized for threat and negativity, because that’s what your brain processes most intensely — which then feeds back into a distorted sense of threat in you as the audience.

Picture a man I’ll call James — a different composite from anything you’ve heard in other episodes. He spent four years in a corporate job he described as “fine but not fulfilling.” He had a business idea he was confident was strong. He talked himself out of pursuing it repeatedly, because of the downside scenarios he could construct in his head. The scenarios were real risks, but they weren’t as large as he was experiencing them emotionally. His negativity bias was multiplying the felt weight of the downside by roughly two, relative to his own intellectual assessment of it. He eventually did the calculation explicitly and realized the worst case was recoverable. He made the move. Four years later, the business was generating three times his old corporate salary.

Here’s how you fight it: when you’re evaluating risks, explicitly multiply your emotional assessment of the downside by 0.5 before you act on it. Your gut is overcounting the loss. Then ask yourself: is the worst-case outcome actually survivable? In most decisions involving career risk, financial risk, or relationship risk, the worst case is recoverable. Your loss aversion is treating survivable setbacks as catastrophes, and you need to correct for that consciously.

The Planning Fallacy: You Will Take Longer and Cost More Than You Think

The Decision Audit Protocol — clarity rational mind Kahneman and Tversky documented this specifically about you: you consistently underestimate the time, cost, and difficulty of your future tasks. Even when you know from experience that similar tasks have taken longer than expected. Even when you’re explicitly trying to be pessimistic. Even when you’re an expert doing the estimating.

The Sydney Opera House was projected to cost $7 million and open in 1963. It opened in 1973 at a cost of $102 million. The Channel Tunnel between England and France came in eighty percent over budget. Edinburgh’s Holyrood Parliament building was projected at £40 million and cost £431 million. These weren’t amateur projects run by incompetent people. They were large-scale professional endeavors managed by experienced teams, and every one of them displayed the same planning fallacy signature: systematic underestimation of time and cost, exactly the kind you’d produce yourself.

Kahneman’s explanation involves the distinction between the inside view and the outside view. When you plan a project, you’re working from the inside view — you’re imagining your specific project, your specific team, your specific circumstances. Your inside view generates optimistic scenarios by default. The outside view asks a different question: what’s the base rate for similar projects? How long do projects like this actually take? How much do they actually cost? The outside view is almost always more accurate for you, and almost always more pessimistic than you’d like.

Here’s how you fight it: use reference class forecasting. Before you estimate a project’s time and cost, go find the actual outcomes of similar projects. What’s the average overrun? What’s the worst-case overrun? Apply those ratios to your own estimate. If you think something will take three months and similar projects on average take twice as long, your working estimate should be six months. Build your plans around realistic timelines, not the optimistic ones you’d naturally reach for.

Status Quo Bias: The Default Option Always Wins

Status quo bias is your preference for the current state of affairs. Departures from the current state get perceived by you as losses, and loss aversion makes losses feel twice as costly to you as equivalent gains. The result: you systematically stick with defaults, resist change, and fail to make moves that would actually benefit you, because the psychological cost of changing feels larger to you than the psychological benefit of improving.

Richard Thaler, who won the Nobel Prize in Economics in 2017 for his work on behavioral economics, demonstrated the power of defaults repeatedly. When employees are automatically enrolled in 401k plans and must opt out, participation rates are dramatically higher than when they must opt in instead. The default option commands compliance regardless of which direction it points. Organ donation rates differ dramatically between countries based primarily on whether the default is opt-in or opt-out, not based on cultural attitudes toward donation at all.

In your own decision-making, status quo bias shows up as the career you stay in too long, the city you don’t move from, the relationship you don’t leave, the strategy you don’t abandon. Your current state feels safe to you not because it is safe but because changing it triggers your loss aversion. You’re treating the absence of change as risk-free when it often carries the highest risk of all for you: the slow compounding of a bad situation you’re too comfortable to escape.

Here’s how you fight it: reframe the status quo as an active choice you’re making. You’re not “keeping things the same.” You’re choosing your current situation again today, right now, actively. Ask yourself: if you didn’t already have your current job, your current relationship, your current city, your current strategy, would you choose it fresh? If the answer is no, you’re choosing inertia over judgment, and you should call that what it is.

Fundamental Attribution Error: It’s Your Fault, But My Circumstances

The Decision Audit Protocol — judgment assessment smart The fundamental attribution error was documented extensively by social psychologists Lee Ross and Edward Jones. It’s your tendency to attribute other people’s behavior to their character and your own behavior to your circumstances. When someone else fails, you decide it’s because they’re incompetent, lazy, or flawed. When you fail, you decide it’s because of bad luck, difficult circumstances, or external factors beyond your control.

This error runs in both directions for you. You overattribute other people’s success to their inherent qualities — their intelligence, their drive, their talent — while underweighting the role of circumstance and luck in their outcomes. And you underattribute your own failures to your own choices while overweighting the external factors, every single time.

The practical damage to you: you fail to learn from your mistakes because you’ve already externalized them. You misjudge your competitors, your collaborators, and your employees because you’re reading their character from their behavior without accounting for their circumstances. You overestimate your own exceptionalism — believing your successes are mostly attributable to you and your failures mostly attributable to the world — when the actual evidence usually shows something far more mixed.

Annie Duke addresses this directly in the context of poker. Bad players tell themselves that losses are bad luck and wins are skill. Good players track their decisions independently of outcomes. The question for you isn’t “did I win or lose?” — because luck contaminates that signal. The question is “did I make the right decision given the information I had at the time?” That’s the decision-quality metric that actually improves over time for you, regardless of whether any individual outcome went your way.

Here’s how you fight it: after any significant failure, run a post-mortem on yourself that explicitly separates the role of your own choices from the role of external circumstances. Write down three things you did that contributed to the outcome. Then write down three external factors. The goal is honest accounting, not self-flagellation. But it’s also not deflection. Take your fair share of the causation, and no more than your fair share.

The Decision Audit Protocol

  1. Name the decision clearly. Write out the decision you’re making in one sentence. If you can’t do this, you don’t have a clear decision — you have a fog. Get specific before anything else.
  2. Identify your current lean. Before gathering any additional information, write down which way you’re currently leaning and why. This surfaces your priors and makes them visible to you.
  3. Run the bias checklist. Go through all twelve biases and ask yourself which of these is most likely to be affecting your thinking on this specific decision. You’ll typically find two or three that are clearly active in you. Name them explicitly.
  4. Steelman the opposition. Write the three strongest arguments against your current lean. Not weak objections — the strongest version of the opposing case you can build. If you can’t do this convincingly, you haven’t done enough research yet.
  5. Find the base rate. For any prediction embedded in your decision, find the actual base rate for similar situations. What percentage of businesses in your sector survive year three? What percentage of people who attempt this career transition succeed? Ground your estimates in actual data, not in the examples that come most easily to your mind.
  6. Assign a probability and write it down. Make your confidence explicit. “I estimate a 70% chance this decision leads to outcome X within eighteen months.” Track these over time. Calibration is your only real defense against overconfidence, and calibration requires a track record you actually keep.

These twelve biases don’t operate in isolation on you. Marcus’s startup death was a combination of at least seven of them working together. Confirmation bias in his market research. Overconfidence in his forecasts. The planning fallacy in his runway projections. The sunk cost fallacy in continuing past the inflection point. The availability heuristic based on startup success stories he happened to know personally. Status quo bias in refusing to pivot the product architecture. And fundamental attribution error in how he read his competitors’ failures.

The Decision Audit Protocol is a six-step process I’m going to give you now for running a bias check on any major decision. This is what Tetlock’s superforecasters actually do, translated into a practical tool you can use today.

This process takes you twenty minutes for a major decision. For smaller decisions, a five-minute version — just steps one, three, and four — is enough. If you’re under real time pressure and can’t run the full process, use the compressed version instead. Which bias is most likely affecting me right now? What would someone who disagrees with my current lean say? And what’s the actual base rate for this type of outcome? Those three questions take you under three minutes, and they address the three highest-probability failure modes — confirmation bias, overconfidence, and the availability heuristic — that drive most of your bad snap decisions. Over time, this becomes automatic enough that it runs in your head in seconds. The goal isn’t to make your decisions slower. The goal is to make the biases visible to you long enough for your System 2 to override your System 1 at the moments when it actually matters.

The Compound Effect and the Bias Cascade

The Decision Audit Protocol — mental model framework Here’s what I want to leave you with on this part: these biases don’t just affect your individual decisions. They compound. Marcus didn’t make one bad decision. He made dozens of medium-quality decisions, each nudged slightly off course by one or more of these biases, and the cumulative drift destroyed everything he’d built.

The researchers who study expert judgment — Tetlock, Kahneman, Duke — all arrive at the same conclusion about you: the gap between good decision-makers and bad decision-makers isn’t intelligence. It isn’t education. It’s metacognition — your ability to think about your own thinking, catch your biases in real time, and correct for them before they compound on you.

One of the most important insights from Kahneman’s later work — particularly his collaboration with Olivier Sibony and Cass Sunstein on Noise: A Flaw in Human Judgment, published in 2021 — is that your biases rarely operate in isolation. They cluster. They amplify each other. They create what Kahneman calls “bias cascades,” where one biased judgment sets up the conditions for the next one in you.

Here’s how a bias cascade actually worked in Marcus’s situation, step by step. It started with the availability heuristic: he personally knew three startup founders who had succeeded with initially skeptical markets. Those success stories were cognitively available and vivid to him. They established his prior belief that market skepticism was normal and could be overcome with persistence. That belief activated confirmation bias: as he conducted market research, he weighted positive signals as validation and negative signals as the predictable skepticism he’d already been told to expect. The confirmation bias created a false picture of market opportunity, which then activated overconfidence — he was certain the opportunity was real because his own research confirmed it. The overconfidence drove the planning fallacy: he planned a runway based on optimistic adoption assumptions rather than base-rate adoption data. And the planning fallacy set up the eventual sunk cost trap: he was six months further along and two rounds of funding deeper before the signal was clear enough to break through the whole bias stack.

Each bias in that cascade made the next one more likely. The availability heuristic seeded the confirmation bias. The confirmation bias fed the overconfidence. The overconfidence enabled the planning fallacy. The planning fallacy enabled the sunk cost trap. This wasn’t seven independent mistakes. This was one mistake — a failure to challenge the initial optimistic prior — that cascaded through seven bias amplifiers into a catastrophic outcome. The third step of the Decision Audit Protocol, running the bias checklist, is specifically designed to catch cascades like this by forcing you to consider multiple biases at once rather than addressing them one at a time. If you identify confirmation bias in your own market research, immediately ask yourself: has that also fed my overconfidence in my timeline estimates? Has it affected my assessment of competitive risks? Your biases rarely travel alone. When you catch one, go hunting for its partners.

Gary Klein’s pre-mortem technique deserves a mention here too, because it’s built for exactly this. Before any major decision is finalized, Klein recommends you imagine it’s twelve months in the future and the decision has resulted in failure. Ask everyone involved to write down, individually, before any group discussion, the specific reasons for that failure. This technique sidesteps the social pressure toward optimism that corrupts most forward-looking assessments, and it surfaces the concerns people already know but are reluctant to voice out loud when the person leading the room is clearly enthusiastic about the plan.

Tetlock’s Hedgehogs and Foxes

Tetlock’s work with expert forecasters deserves a closer look from you, because it destroys one of the most comforting myths about cognitive bias: the myth that expertise protects you from it. Tetlock spent two decades tracking the predictions of professional forecasters — economists, political scientists, intelligence analysts, financial strategists — people whose entire careers were built around making accurate predictions about the future. The dataset was eventually 82,361 forecasts from 284 experts. The results were remarkable for their consistency: expert forecasters performed barely above chance on long-range predictions of twelve months or more, and their performance didn’t improve with additional credentials, experience, or access to information.

The variation that did emerge wasn’t between experts and non-experts. It was between two cognitive styles that Tetlock, drawing on Isaiah Berlin, called hedgehogs and foxes. Hedgehogs know one big thing — they have a grand organizing theory of how the world works, and they run every prediction through it. Foxes know many small things — they’re comfortable with uncertainty, they draw from multiple frameworks, they update regularly, and they’re deeply skeptical of grand unified theories. Foxes dramatically outperformed hedgehogs across the entire dataset. And here’s the cruel irony for you to sit with. The hedgehogs — the bold, confident, theory-driven analysts — were the ones who appeared most frequently in the media. They received the most invitations to testify before legislatures and boards, and they commanded the highest fees. Confidence sold, regardless of its actual relationship to accuracy.

The bias implications here are direct. Hedgehog thinking is confirmation bias institutionalized — a grand theory that filters all incoming information through its own lens, treating confirming evidence as support and disconfirming evidence as noise. Overconfidence is the hedgehog’s natural posture, because strong theoretical frameworks generate strong certainty. And the halo effect operates at the social level: confident, theoretically coherent experts attract the kind of attention and authority that makes their predictions seem more credible than their actual track record warrants.

The practical implication from Tetlock’s more recent work — the Good Judgment Project and the training program that followed it — is that fox-style forecasting is teachable, and it’s teachable to you specifically. The specific techniques that improve your accuracy include actively seeking out views that challenge your current model, and breaking complex questions into component sub-questions with known base rates. They include regularly revisiting your predictions to update them as new information arrives, and expressing your predictions as probability ranges rather than confident point estimates. None of these are cognitively demanding. They’re procedural disciplines anyone can adopt, including you. What makes them rare isn’t difficulty. It’s the cultural prestige that rewards hedgehog-style confidence over fox-style calibrated uncertainty.

Annie Duke’s Poker Framework Applied to Your Decisions

Annie Duke’s contribution to the decision-making literature — specifically in Thinking in Bets — is applying poker’s forced accountability to your general decision-making. Poker is unusual among human endeavors in that it gives you fast, unambiguous feedback that separates decision quality from outcome quality. In any given hand, you can make the best possible decision — fold the mathematically dominated holding, call the pot-committed range at the right odds, raise the value hand at the appropriate sizing — and still lose. You can make a terrible decision and still win. The outcome isn’t a clean signal of your decision quality. Over thousands of hands the signal emerges, but on any individual hand, luck contaminates it completely.

The critical insight this generates for you: in poker, you cannot evaluate decision quality by outcome. You have to evaluate it by process — by whether the decision was correct given the information available to you at the time you made it. That forced separation of decision quality from outcome quality is exactly what you need in your business and life decisions. It almost never happens naturally, because most people engage in what Duke calls “resulting” — evaluating your past decisions based on whether they worked out rather than on whether they were right given what you knew at the time.

Resulting corrupts your learning in two ways. When a bad decision produces a good outcome through luck, you reinforce the bad decision instead of correcting it. When a good decision produces a bad outcome through bad luck, you punish the good decision instead of reinforcing it. Over time, resulting means your decision-making process drifts toward whatever produced good outcomes in the specific cases you personally experienced, regardless of whether those processes are actually sound in general. Your sample of personal experience is small and noise-contaminated. Calibrating your process to it, rather than to sound reasoning principles, is how intelligent people like you develop systematically bad decision habits that feel good, because your memory of them is selective.

Here’s the practical application for you. After any significant decision, evaluate it twice. First: given the information available to you at the time, was your process sound? Did you consider the relevant alternatives? Did you seek out disconfirming evidence? Did you anchor on a base rate rather than an optimistic inside view? Was your probability estimate calibrated? Second: what actually happened, and what does that outcome tell you about the quality of your process? That second evaluation is only useful to you after the first one has been completed honestly, because the outcome will contaminate your assessment of the process quality if you do it in the wrong order. Review the hand before you check the card that would have won. The order matters more than you’d think.

Priya and the Halo Effect, In Full

Earlier I introduced Priya to you, the VP of Marketing who joined a startup because of the halo she projected onto a charismatic CEO. Her full story shows you several biases operating simultaneously, and it’s worth walking through more completely.

Priya had spent eight years in corporate marketing at large consumer brands before the startup opportunity appeared. The CEO — call him Jordan — had an extraordinary resume. A Harvard MBA, two previous startups, a well-viewed TED Talk on innovation culture, and a fundraise that included logos from three of the most recognizable venture capital firms in the country. When Priya met him, she experienced what she’d later describe as immediate intellectual attraction — the sense that this was someone thinking at a different level from most people she’d encountered in her career.

The halo effect was operating at multiple levels on her simultaneously. Jordan’s fundraising success — which required exactly one specific skill, selling a vision to investors — was haloed into a general judgment about his business ability. His Harvard credential was haloed into operational competence. His TED Talk eloquence was haloed into strategic clarity. The prestigious investor logos on the cap table were haloed into validation of the business model itself. Each of these was a separate cognitive error on Priya’s part. They were stacked on top of each other, and together they produced an overall assessment of Jordan that was significantly higher than what any individual piece of evidence, examined on its own, would have actually supported.

The availability heuristic was active too. Priya personally knew two people who had joined early-stage startups with impressive-resume founders and had significant financial outcomes from it. Those stories were cognitively available to her. The much larger population of people who’d done the same thing and had far worse outcomes wasn’t available to her at all — she didn’t know those people personally, and none of them had TED Talks.

Confirmation bias completed the picture. In her due diligence, she talked to the references Jordan provided. They were all positive, as references provided by the person being evaluated will always be. And she ran a competitive analysis that confirmed the market opportunity she already wanted to believe in. What she never gathered: what Jordan’s previous employees actually thought about working for him, not the formal references but the people who’d actually done the work. What his operational track record on the previous startups really looked like underneath the fundraising headlines. What the customer acquisition economics looked like at companies most similar to this one in stage and model.

Eighteen months in, having mapped the full picture for herself, Priya described the experience as an education she wouldn’t have chosen but wouldn’t trade either. She learned specifically which information to gather and which information to generate herself rather than accept as given. She learned to separate the halo signal from the underlying competence signal by evaluating each dimension independently, rather than letting her overall impression dominate. And she learned to track her own reasoning process in real time. She’d notice when she was feeling the pull of a halo effect, and she’d deliberately slow down and ask herself what the specific evidence for this specific claim actually was, independent of her overall impression of the person.

That last habit — slowing down when you feel the pull of a halo — is the most practically transferable lesson from her experience, and I want you to take it with you. The halo effect produces a specific felt quality of seeing: a sense that everything about a person or opportunity is illuminated, that the pieces all fit together, that the picture is clear and coherent. That felt quality of clarity is your signal to become more skeptical, not less. Genuine clarity comes from your independent evaluation of individual components. The felt sense of coherence the halo effect produces is a manufactured artifact of your own cognitive architecture. It feels like you’re seeing clearly. You’re not.

Building Your Decision Infrastructure

  1. A pre-decision checklist. The three-question rapid version of the Decision Audit Protocol, run as a standing habit for any decision above a threshold of importance you define for yourself.
  2. A prediction journal. A record of your predictions with assigned probabilities, reviewed quarterly for your own calibration.
  3. An adversarial advisor. At least one person in your life whose explicit role is to challenge your reasoning rather than support your conclusions. Not someone who tells you you’re wrong just for the sake of opposition. Someone with good judgment who has your permission to push back and will actually use it.

Everything in this episode — the twelve biases, the Decision Audit Protocol, Tetlock’s superforecaster research, Duke’s poker framework — points you toward the same conclusion: high-quality decision-making requires infrastructure from you. It requires deliberate structures you maintain even when, especially when, they feel unnecessary to you in the moment. The moments when you most feel like you don’t need them are typically the moments when you need them most. Those are the moments when your System 1 is running hot, when your confirmation bias is operating at high intensity, when your overconfidence is highest and your monitoring is lowest.

Your minimum viable decision-making infrastructure has three elements.

The adversarial advisor is the most important and least commonly maintained element of all three for most people. Most of us naturally surround ourselves with people who share our worldview and tend to confirm our judgments. That’s comfortable and socially smooth. It’s also a permanent confirmation-bias amplifier working against you. Picture the person who consistently asks you whether you’ve considered the strongest counterargument. The one who asks what would need to be true for the opposite conclusion to be correct, or what the base rate actually is for this type of outcome. That person is worth more to your long-term decision quality than any amount of additional information you could gather on your own.

Marcus, in the version of this story I want you to carry with you, eventually built exactly this. He found a business partner for his second company whose explicit role, at the start of every major decision, was to argue the opposing case as convincingly as possible before any plan got finalized.

“It slows things down sometimes. But it’s never slowed us down by more than a few days on any single decision. And it’s already stopped us from making two decisions that I was certain were right, and he convinced me were wrong — and he was right both times. The few days we lost were nothing compared to what we would have lost on those decisions.”

That’s the payoff of the infrastructure for you. Not every decision, not a dramatic transformation of your entire reasoning architecture, but the specific, high-consequence decisions where your biases are most active and the stakes of getting it wrong are highest. Your infrastructure catches those decisions for you. Over a career, over a life, those caught decisions compound into a substantially better trajectory for you. That’s the return on your investment. That’s what Kahneman, Tversky, Tetlock, Ariely, Klein, and Duke have spent their careers trying to make available to people willing to use it. The question is whether you will.

And the data on this is encouraging for you: you cannot eliminate your biases, but you can measurably reduce their impact through deliberate practice. Tetlock’s superforecaster training program improved prediction accuracy by roughly 50% over control groups using structured debiasing techniques — reference class forecasting, active open-mindedness exercises, and prediction tracking with calibration feedback. Your biases stay in your cognitive architecture permanently. What changes is your ability to catch and correct for them before they determine your behavior for you.

Why Debiasing Is Hard: The Neuroscience Underneath

Understanding why these biases are so resistant to correction in you requires a brief look at the neuroscience underneath them. Kahneman’s System 1 versus System 2 framework is a functional description, not a strict neurological one, but it maps reasonably well onto what neuroscientists have discovered about your brain’s architecture. Your amygdala and associated limbic structures generate fast emotional responses in you — threat detection, reward anticipation, social evaluation — on timescales of milliseconds. Your prefrontal cortex, the seat of your deliberate, analytical reasoning, operates on timescales of seconds to minutes. System 1 is always faster in you.

Your prefrontal cortex doesn’t suppress System 1. It monitors it. Under conditions of cognitive load, time pressure, stress, fatigue, or emotional arousal, that monitoring capacity degrades in you. This is why you make your worst decisions when you’re exhausted, when you’re angry, when you’re under deadline pressure, or when you’re deeply emotionally invested in an outcome. The conditions under which your decisions matter most — high stakes, high pressure, high emotional weight — are precisely the conditions under which your debiasing capacity is most compromised.

This has a direct practical implication for you: run the Decision Audit Protocol at your best cognitive state, not at the moment of peak urgency. Major decisions made at 11pm after a stressful day, in the middle of a heated argument, or under an artificial deadline imposed by the other party are decisions made with your monitoring capacity already degraded. If you can delay the decision to a better cognitive state without incurring a catastrophic cost from the delay, you should. Manufactured urgency — the pressure to decide right now — is both a manipulation tool other people use on you and a bias amplifier in its own right. It degrades your System 2 capacity at the exact moment you need it most.

Sleep deprivation specifically has a documented impact on your bias susceptibility. Matthew Walker’s research at UC Berkeley, documented in Why We Sleep, shows that even moderate sleep restriction — six hours a night for two weeks — produces cognitive impairment equivalent to two full nights of sleep deprivation. Your subjective sense of your own performance stays completely unchanged the entire time. You don’t feel impaired. You are impaired. Your confirmation bias strengthens, your anchoring effects intensify, and your overconfidence in your own judgment increases even as your actual judgment quality degrades underneath you. That’s not a metaphor. It’s a measurable, documented phenomenon in your own brain.

Your practical debiasing protocol has to include environmental controls, not just cognitive tools. Protect your sleep when major decisions are pending. Avoid making irreversible commitments during your peak emotional states. Build cooling periods into the space between your decision-making and your decision-execution. These aren’t luxury behaviors for people with endless time. They’re risk management for people, like you, who can’t afford catastrophic decisions.

What Organizations Get Wrong

  1. Decision hygiene protocols that separate information gathering from judgment, to prevent anchoring.
  2. Independent assessments from multiple evaluators before any group discussion happens, to prevent a cascade off the first speaker’s framing.
  3. Systematic use of reference class forecasting inside your own planning process.
  4. A deliberate adversarial role — someone assigned to argue the opposing case, with the explicit goal of surfacing confirmation bias before any decision gets finalized.

Kahneman’s Noise addresses the organizational dimension of bias management at length, and the findings apply directly to whatever team or company you’re part of. Organizations have two problems: bias and noise. Bias is systematic error in one direction — always overestimating, always undervaluing a category. Noise is random error — inconsistency in judgments that should be consistent. Both destroy decision quality, and they require different interventions from you.

The standard corporate approach to both problems is almost entirely wrong. After-the-fact reviews, lessons-learned sessions, and retrospectives all generate useful information about what went wrong. But they don’t address the structural biases that will produce the same errors in your next decision cycle. The information generated by retrospectives feeds your availability heuristic for the specific failures reviewed. That may actually make your next decision more afraid of those specific failures, while remaining blind to the bias structures that created them in the first place.

The interventions that actually work, according to the research Kahneman cites, are structural. Here’s what you can build into your own team.

Amazon’s approach to this — documented by Brad Stone in The Everything Store and elaborated in multiple accounts of the company’s management culture — addresses this through structural interventions you can borrow directly. The six-page narrative memo requirement forces analytical rigor before meeting discussions, reducing your ability to substitute an enthusiastic presentation for actual evidence. The “disagree and commit” norm makes explicit that voicing disagreement is expected and respected, not evidence of disloyalty. Neither of these is a debiasing technique on its own, but both reduce the social cost of the behaviors that let debiasing actually happen.

The cultures that produce the best collective decision-making — whether in organizations, investment partnerships, or scientific teams — share one common feature: they treat intellectual challenge as a contribution, not a threat. They have low social cost for saying out loud that the room might be in confirmation bias, or for asking what the actual base rate is for projects like this one succeeding on a first attempt. Building that culture is the highest-use investment you can make in your own decision quality, whatever environment you operate in. It’s also one of the hardest, because it requires the people at the top of any hierarchy to model intellectual humility, and the people at the top of most hierarchies got there partly through the kind of confident certainty that’s the enemy of genuine debiasing.

The Bias You’re Most Likely Skipping Right Now

Here’s a meta-point worth making explicit to you. As you’ve listened through this list of twelve biases, you’ve almost certainly been mentally exempting yourself from the most relevant ones while readily accepting the ones that feel less personally threatening to you. That’s itself a cognitive bias — the bias blind spot, documented by Emily Pronin at Princeton, which is your tendency to recognize biases in others more readily than in yourself.

Pronin and her colleagues found that the bias blind spot operates through a specific mechanism in you: when you evaluate your own judgment, you use introspective access to your intentions and reasoning process, which feels transparent and rational to you. When you evaluate someone else’s judgment, you can only observe their behavior and outcomes, which makes their bias visible to you. Because you have access to your own reasoning and it feels sound to you, you conclude you’re less biased than other people, even when the actual decision-quality evidence says otherwise.

The bias blind spot resists correction in the usual ways. Telling you about it doesn’t fix it. Telling you you’re susceptible to biases doesn’t reduce your blind spot. The only correction that actually works involves an external feedback loop — someone outside your own decision-making process who can observe your reasoning and flag it when your behavior diverges from your stated process. This is why accountability structures, prediction tracking, and advisory relationships aren’t optional extras for you. They’re the feedback mechanisms that make self-correction possible once your internal monitoring has already failed.

Marcus, reflecting on his startup’s collapse, put it this way: “The people who told me the truth — the investors who passed, the consultants who said the market wasn’t there — I thought they didn’t understand the vision. I thought I was seeing something they couldn’t see. That’s the bias blind spot in its purest form. I was the one who couldn’t see. I just didn’t know it.”

He went on to build a second company. Smaller, more focused, no venture funding, operating profitably in year two. When he identified what actually changed, he’d put it this way: “I hired a coach whose only job was to tell me when I was fooling myself. And I made myself listen.” That’s the Decision Audit Protocol running on a human substrate. It’s also the most expensive, and often the most effective, version of the protocol available to you.

Here’s a smaller, cheaper version of that same idea, one you can start using this week without hiring anyone. Pick one person in your life, right now, who has never once told you what you wanted to hear just to keep the peace. You know who it is. It might be a sibling. It might be an old friend from before you had anything worth protecting. Send them one message today. Tell them you’re working on catching your own blind spots, and ask them to say something they’ve noticed about how you make decisions that you’ve probably never wanted to hear. Not a compliment. Not encouragement. The thing they’ve been sitting on. You will not enjoy reading the answer. Read it anyway, twice, before you respond to it. That single message costs you nothing and gives you something no book, including this episode, can give you on its own: a mirror held by someone who isn’t inside your own head.

Building a Decision Quality Culture, and the Close

The highest-use application of everything in this episode isn’t individual for you. It’s cultural. Your ability to make good decisions is constrained not just by your own biases but by the social environment you’re making decisions inside of. Organizations, teams, families, and peer groups all carry implicit norms about what kinds of challenges to conventional wisdom are acceptable. In most social environments, those norms actively suppress the exact debiasing behaviors that would improve your collective decision quality.

Consider what it takes for you to actually run the Decision Audit Protocol in a corporate meeting room. Step three requires you to voice the biases you believe are affecting your own thinking out loud. Step four requires you to articulate the strongest case against the direction the group is leaning. Step five requires you to surface base rates that might challenge the optimistic assumptions the plan is built on. All of these are socially uncomfortable acts for you in most organizational cultures. They risk you being seen as disloyal, pessimistic, or obstructionist. The social cost of these debiasing behaviors suppresses their use exactly in the high-stakes group settings where you’d need them most.

Kahneman’s final major work, Noise, closes with a simple but devastating observation: the best decision-making systems he studied were the ones that deliberately constrained individual judgment rather than celebrating it. They built checklists, protocols, and review structures that forced systematic information gathering before individual assessment, prevented anchoring on the first available opinion, and required explicit confrontation of disconfirming evidence. They treated the individual human mind — even the expert individual human mind, even yours — as a bias-generating machine that needed to be systematically corrected for, not as a reliable instrument to be trusted at face value.

That’s the frame this entire episode has been building toward for you. You are a bias-generating machine. So am I. So is every person you know. The question was never whether you have biases — you do, they’re documented, they’re architectural, and they’re not going away. The question is whether you’ll build the protocols, the external feedback loops, the cultural norms, and the individual habits that catch them before they make your decisions for you.

The twelve biases are named for you now. The Decision Audit Protocol is in your hands. The research is clear. What happens next is entirely up to you.

You don’t need to memorize all twelve names tonight. You need to remember that your mind is not a neutral instrument, that it was built for speed under conditions that no longer apply to most of what you’re deciding, and that the men who decide well are not the ones with the fewest biases. They’re the ones who built a habit of catching their own. That habit is available to you starting with the very next decision you make, not some future decision once you feel ready. Ready is not a precondition here. The protocol works whether you feel ready for it or not, and that’s precisely the point of building it as a habit instead of waiting on your own motivation.

We will be back next week.

For more on the decision-making frameworks that underpin this work, there’s the episode on First Principles Thinking, where we break down how to reason from the ground up instead of by analogy. And if you want to understand why you stay in bad situations even when you already know they’re bad, the episode on the Sunk Cost Fallacy is essential listening. If you want to understand how manipulation exploits these exact biases from the other direction, the episode on Dark Psychology connects directly to everything covered here. And you can browse the full Mindset Tools library on this site for the frameworks that build on all of it.


Tags


You may also like

{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}

Get in touch

Name*
Email*
Message
0 of 350