Monday Post-Mortem: What Last Week's Lineup Actually Cost You

Monday morning in fantasy football usually goes one of two ways. You won, so you feel good about your decisions. Or you lost, so you feel bad about them. Either way, you probably have the causality backwards.

Week-to-week outcomes in fantasy are heavily influenced by variance: injury luck, touchdown variance, game script randomness. A manager who made three bad decisions and got lucky can easily beat a manager who made three good decisions and got unlucky. If you use wins and losses to evaluate your decision quality, you're measuring the wrong thing.

The post-mortem is how you separate the signal from the noise.

What a post-mortem actually measures

A post-mortem has one core function: calculate the optimal lineup after the week's games are final, then compare it to the lineup you actually set.

The gap between your optimal lineup and your actual lineup is your lineup efficiency. If you scored 98 points and your optimal lineup would have scored 118, you left 20 points on the bench. That gap represents lineup decisions: bench swaps you didn't make, starts you misjudged, flexes you got wrong.

Importantly, this gap is measured in points, not in "the right call." With hindsight, you could always optimize. But the difference between a 5-point gap and a 25-point gap tells you something real about your decision process, not just the outcomes.

The three decision types that show up in a post-mortem

A meaningful post-mortem breaks down the week's point cost by decision type:

Lineup decisions. The clearest category. You started Player A; your optimal lineup would have started Player B instead. The point cost is the difference in their actual scores. If you started a WR who scored 6 and benched one who scored 19, that's a 13-point lineup decision. Was it clearly wrong given the information you had on Sunday morning? Or was it a reasonable call that went against you? The post-mortem surfaces the number; you provide the context.

FAAB decisions. This is harder to measure but important. If you failed to add a player who was available and would have started, the post-mortem should calculate what they would have contributed. If you spent $24 on a player who produced 4 points while a $3 player produced 18, that's a resource allocation mistake, and the gap tells you how big.

Trade decisions. The most lagged category. A trade made in Week 6 might not show its true cost until Week 10. But tracking the production of players you gave up versus players you received, week by week, tells you whether the deal is working or not, and whether the original analysis was sound.

Decision quality score: separating skill from luck

The most useful output of a post-mortem is a decision quality score: a single number that reflects how well you executed given the information available to you, not given the information you'd have with hindsight.

The distinction matters. Starting a healthy RB1 who happens to get injured in the first quarter is not a bad decision. It's bad luck. Starting a player who was listed as questionable on Friday and sat out is a bad decision; you had the information to make a different call.

A good decision quality score weights decisions by what was knowable at the time:

• High penalty for decisions where the data clearly pointed one way and you went the other.
• Low or no penalty for decisions where the information was genuinely ambiguous.
• Moderate penalty for decisions where you had some signal but ignored it.

Over the course of a season, your average decision quality score tells you more about your fantasy skill than your win-loss record does.

How to run your own post-mortem

Monday morning, after scores finalize:

1. Pull your actual lineup scores. What did each starter produce?
2. Rebuild the optimal lineup from your roster. Looking only at players you had available, not waiver wire adds, what was the best possible lineup? What did it score?
3. Calculate the gap. How many points did you leave on the bench? Which players?
4. Ask the pre-information question. For each player in the gap: given what you knew on Saturday night, was the decision reasonable? If yes, flag it as variance and move on. If no, flag it as a process error.
5. Check FAAB decisions. Who did you add this week? Who did you miss? What did they produce?
6. Log one process improvement. Based on this week's errors, what specific thing will you do differently next time?

The whole exercise should take 10–15 minutes. The value grows over the season as you identify and fix process errors.

The common mistakes a post-mortem reveals

The consistent ceiling-chaser. Every week, the post-mortem shows the manager started low-floor boom-or-bust players who busted instead of reliable producers who delivered. This is a floor undervaluation pattern, and it's fixable once you see it.

The injury-report ignorer. The post-mortem repeatedly shows points left on the bench because the manager started questionable players who then sat out, even though the status was flagged. The fix is a harder rule: if a player is listed doubtful or out by Saturday, they don't start.

The waiver paralysis manager. Every week, a player the manager passed on produces strong points. The FAAB recap shows consistent under-bidding on players who clearly had value. The fix is recalibrating bid amounts against actual production, not gut feel.

The variance-blamer. Manager consistently attributes losses to bad luck rather than process. The post-mortem keeps showing the same pattern of errors week over week. Variance is real; consistent variance patterns usually aren't.

Using the post-mortem to improve over the season

The post-mortem isn't useful in isolation. It's useful as a data set. By Week 8, if you've done one every week, you have eight weeks of decision error data. The patterns become clear: do you consistently underperform on lineup decisions? FAAB? Both? Are your errors concentrated in a specific position?

That's the information that makes you meaningfully better over the course of a season, not just better in the abstract. If the post-mortem repeatedly flags lineup errors at the same position, the start/sit decision framework is the right place to look for systematic fixes. If the errors keep showing up on the bench side (wrong holds, wrong drops), a weekly bench audit builds the habit of evaluating those spots before the errors happen.

The managers who improve the most over a long fantasy career are the ones who treat each week as a data point in their own decision-making history and use that data to fix their specific failure modes.

Fantasy Upside tracks the top fantasy football podcasts and articles every day and sends you the week's key themes every Tuesday afternoon, free. Subscribe here.