Things to Consider

01. Rewards and punishments

The weekly win, standing jump, or league-chat status is the paycheck. That incentive makes you start the boom-or-bust flex for “upside” or drop a quiet 11-point player for a lottery-ticket handcuff. Experts and waiver-wire articles get paid in clicks when you chase the name they just hyped. Non-financial rewards matter more than they look: you do not want to disappoint the version of yourself that “knew” the player was due. Ask what the advice-giver gains if you add or start the player, then ask what you gain besides points.

02. Liking and loving

You like the player’s college, his team, or the story, so you start him over a clearer matchup or refuse to drop him for a better available option. Affection becomes evidence. Remove the name and restate the facts: “WR with 3.2 targets per game on a 1-3 team.” If the start or hold suddenly looks worse, liking was doing part of the work.

03. Disliking and hating

A player or team that burned you last year, or a rival owner’s favorite, gets ignored on the waiver wire even when the snap counts and targets are obvious. You sit a productive player because you cannot stand the quarterback or the coach. Force the second look: what would the numbers say if a neutral name were attached?

04. Avoiding doubt

Saturday night injury designations, weather, or unclear snap-share reports create stress. You lock a lineup early just to end the uncertainty instead of waiting for the late-afternoon practice report. The same impulse makes you submit a waiver claim on the first hyped name so the decision is over. Separate the urgent action (set a lineup by kickoff) from the final conclusion (the player’s role may still be unresolved).

05. Avoiding inconsistency

You started him last week, so you start him this week even though the matchup flipped. You added him Tuesday, so dropping him Friday feels like admitting the claim was a mistake. Write the conditions that would get him benched or cut before the week begins, then compare Sunday’s evidence to that note instead of the story you told yourself after the add.

06. Curiosity

Treat a surprise—three targets, a sudden snap-count drop, an unexpected goal-line vulture—as the start of the next question rather than a one-week blip. Keep a short log: “Expected 14 points, got 4. What changed in usage or scheme?” Curiosity keeps the first plausible label (“he’s in a slump”) from becoming permanent.

07. Kantian fairness

It feels unfair that one owner keeps hitting every good waiver add, or that a veteran “deserves” more time than the rookie who is actually out-snapping him. Fantasy scoring is not a fairness system. State the rule that should apply to every comparable player—start the higher projected points, drop the lower-rostered option with worse upcoming usage—then check whether you would still accept that rule if the names were reversed.

08. Envy and jealousy

Another owner’s waiver add just scored 28. Your unchanged 12-point starter now feels like a loss. You overbid the next similar player or sit your own steady option because someone else’s flex “got lucky.” Write your objective (highest expected points this week) before you look at anyone else’s score.

09. Reciprocation

A league-mate floated a start/sit take that once worked, or an analyst you follow “gave” you a good call last month. The small courtesy makes you more likely to follow the next recommendation or to leave a player on the wire that they might want. Evaluate the claim or the add as if no prior favor existed.

10. Influence from mere association

A player on a high-powered offense or with a famous name gets started even when his actual routes or snaps are declining. Bad news from a beat writer you dislike gets discounted. High ownership itself starts to look like quality. Separate the association from the cause: did the offense produce the points, or did this specific player?

11. Pain-avoiding denial

The snap count has fallen three weeks in a row, and the coaching quotes are lukewarm, but you keep starting him because sitting him would make the earlier decision official. Intelligence supplies better stories: “they’re easing him back,” “the script was negative.” Ask what the film and usage would look like if the feared conclusion were already true.

12. Excessive self-regard

Your eye test or “I watched the red-zone snaps” outweighs the projection and the target share. The player already on your roster feels more valuable than the identical player sitting on waivers (endowment). You remember your good start/sit calls more vividly than the bad ones. Use the actual snap, target, and air-yard numbers and a second source that did not make your original claim.

13. Overoptimism

The start/sit write-up contains the perfect matchup, the “volume is coming,” and the bounce-back narrative. It leaves out the stalled route participation, the vulture backfield partner, and the two-score deficit script that usually kills his touches. Write the failure case first: what does 4 points look like and how often has that happened in similar spots?

14. Overreaction to loss

You sat a player who exploded or started one who laid an egg. The missed or wasted points feel like something already in your possession that was taken. Next week you start every volatile option or drop a serviceable player after one quiet game to “stop the bleeding.” Ask what the roster spot would be worth if the player were not already yours.

15. Social proof

Expert consensus, Twitter, and the league’s start-rate percentages all point at the same flex. You start him even though your other option has a quieter but more certain floor. On waivers, the entire league streams the same defense or handcuff, so you do too. Collect the raw usage numbers before you look at how many people are already starting or adding the player.

16. Contrast misreaction

The available waiver player looks attractive only because the rest of the wire is worse. Your bench option looks startable only because the alternative had an even tougher matchup last week. A player’s role can shrink 8 percent per week without any single dramatic announcement. Set the required snap or target threshold before you look at this week’s menu.

17. Stress

Sunday-morning inactive lists, late injury designations, or a two-game losing streak produce a different decision-maker than Tuesday-night research. The panicked last-minute swap or the “I have to do something” waiver claim is the heavy-stress version. Set simple rules in advance: inactive = sit, snap share below X two weeks in a row = drop candidate.

18. Availability misweighing

Last week’s 35-point explosion or the viral highlight clip outweighs six weeks of 9-point medians. The injury-report sentence that is easy to remember beats the dull snap-count table. Before locking the lineup, ask which relevant fact is missing because it is old, quiet, or hard to screenshot.

19. Use it or lose it

If every week you simply copy an expert’s start/sit list, the ability to read route participation, blocked-lane rates, or weather-adjusted passing volume atrophies. Schedule the actual work: open the snap and target tables yourself at least once a week. Recognition of the names is not the same as still being able to evaluate the roles.

20. Drug influence

The dopamine hit of a successful waiver add or a last-second news alert can become its own reward. Checking the wire or Twitter every hour starts to look like research while it actually narrows attention to the most vivid new name. The practical rule is the same as Munger’s: treat the compulsion itself as a warning that judgment is already impaired.

21. Aging

A veteran’s past reputation still wins the start/sit argument long after the current target share has collapsed. Your own earlier success with “this type of player” gets more weight than this week’s usage. Evaluate the present snaps, routes, and red-zone looks, not the historical label.

22. Authority

The popular analyst’s “must-start” or the ranking site’s projection makes a questionable flex feel safer than your own numbers. The title does the work that the evidence should do. Require the authority figure’s claim to stand without the name attached: show the snap trend, the opponent’s tendency, and the weather.

23. Twaddle

League chat, podcast recaps, and your own notes fill with “the opportunity is there,” “trust the talent,” and “he’s due” without a snap count, a target share, or a condition for sitting him. End the research session with one written sentence: who starts, who sits, and the single usage number that decided it. If that sentence cannot be written, more talking has not helped.

24. Respect for reasons

“I’m starting him because the expert said so” or “because he scored 20 last week” has the shape of a reason. Demand the mechanism: targets, air yards, opponent coverage rank, or game-script projection. Then ask what result would prove the reason wrong this week.

25. The Lollapalooza effect

The most expensive lineup and waiver mistakes rarely stem from one tendency. After two quiet games, the high-rostered player is still started because incentives demand points this week, authority says “buy low,” commitment says you already used the roster spot, social proof says everyone else is starting him, and the prior losses raise the cost of changing course. The same stack appears on waivers: recency plus availability plus envy plus the need to “do something” after a loss produces the overbid on a player whose role is still unclear. When several ordinary pressures point the same way, the ordinary start/sit or add/drop becomes the decision that costs three weeks.

The largest errors in fantasy football rarely come from one bias acting alone. They come from several ordinary tendencies lining up and shoving you in the same direction until a bad decision feels inevitable.

That is the Lollapalooza effect on a Sunday lineup or a draft board.

A common version looks like this. You used a high pick on a running back or receiver because the preseason tape looked explosive, the experts had him ranked there, and ADP treated him as a locked-in starter. Week 1 he gets eight carries and 22 yards. Week 2 is similar, plus a fumble. You start him again in Week 3.

No single force explains the second and third starts. Incentive-caused bias pushes for speed: you need the points this week, the prize pool or bragging rights matter, and sitting a “stud” feels like wasting the pick. Authority shapes the procedure: every podcast and ranking site says the volume is coming and this is a buy-low. Commitment and consistency preserve the plan: you already told yourself (and maybe the league chat) this was your guy. Social proof mutes objections: he is still rostered and started in the vast majority of leagues, so dropping or benching him looks like you are the one who is wrong. The early failures raise the felt cost of stopping. Admitting the miss now means you already lost those weeks for nothing.

The same stacking happens on draft night. Recency and availability make last year’s late-season heater or one viral preseason run feel more real than the underlying metrics. Anchoring locks you to ADP or an expert board. Confirmation bias lets you collect only the quotes that support the reach. A positional run in the room triggers FOMO and herding. None of those tendencies by itself would make you take a player two rounds early. Together they produce the overdraft that sits on your bench in November.

That is why the list of tendencies matters. A start/sit call or a third-round selection becomes most dangerous when several of them form one extraordinary pressure. The manager who survives is usually the one who notices the pile-up and refuses to let the combination finish the job.