Back to Blog
7 min read

The Pre-Mortem: Running One on a Polymarket Thesis Before You Size Up

A post-mortem examines what went wrong after the contract resolves against you. A pre-mortem asks the same question before you place the bet. On a venue with Hill α = 1.28, it is cheap insurance against the size mistakes that actually end careers.

Where the technique comes from

Gary Klein, a psychologist who spent decades studying decision-making under time pressure (firefighters, military commanders, trauma surgeons), introduced the pre-mortem in the late 1990s. Klein's observation: people are much better at explaining a failure that has already happened than at anticipating one that has not (Klein, 2007, "Performing a project premortem," Harvard Business Review).

The trick is to move the question from "what could go wrong?" to "assume this trade lost. Explain why." The framing activates the explanatory circuit instead of the defensive one. Klein's reported result: pre-mortems increased the number of surfaced failure reasons by roughly 30 percent compared to standard risk assessment.

Why it works on a prediction-market position specifically

A Polymarket trader sizing into a $5,000 position on an ETH price contract has three characteristic failure modes: probability is miscalibrated, the contract resolves on mechanics the trader did not fully read, or the position size is so large that any outcome other than the intended one is operationally ruinous. Standard pre-trade checklists catch the first two unevenly. The pre-mortem frame catches all three at once.

The exercise also forces the trader to distinguish thesis risk from size risk. These are different questions. A thesis can be correct on probability grounds and still generate a position that is too large for the bankroll under fat-tail payoffs. Convexly's finding that Hill α on realized Polymarket PnL sits at 1.28 (Edge Score Methodology V1) means variance is not a reliable sizing input. A pre-mortem reveals whether the trader's sizing survives the fat tail, independent of whether the thesis was right.

Worked example: a $5K ETH contract

A trader with $50K in deployable capital has been watching a Polymarket contract on "Will ETH close above $3,500 on March 31?" The contract trades at 42 cents. The trader's view: ETF inflow data and an upcoming protocol upgrade push the fair probability closer to 56 percent. The initial sizing plan is $5,000, or 10 percent of bankroll.

Ten minutes of pre-mortem output, written independently:

Failure mode 1. Contract resolves on a specific exchange feed. Trader has not actually read which one. If the oracle reads from a venue with a different close than the market the trader watches, the trade can resolve against the thesis directionally even if ETH finishes above $3,500 on the trader's reference exchange.
Failure mode 2. A macro shock (Fed surprise, regulatory headline) drops ETH 15% in a session. The 56 percent probability was estimated under a "no systemic shock" assumption. The probability in a shock regime is closer to 30 percent.
Failure mode 3. Protocol upgrade is delayed by a week, crossing the resolution date. A positive outcome for the network becomes a negative outcome for this specific contract.
Failure mode 4. Size. At 10 percent of bankroll into a single event, a full loss permanently impairs the ability to take the next three high-conviction bets, regardless of whether this specific probability estimate was correct.

Three of the four failure modes are contract-mechanics or tail-shock risks the original thesis did not price. The fourth is a sizing error that is independent of the thesis being right. The trader's post-exercise revision: cut size to $2,000 (4 percent of bankroll), and actually read the resolution oracle before sizing further.

The procedure, step by step

Step 1. State the position. Contract, direction, size, and the explicit probability estimate. Write it down. Vague theses survive pre-mortems by mutating.
Step 2. Set the clock forward. "It is the day the contract resolved. This position lost the full stake. Write down every reason why."
Step 3. Write independently, then compile. If trading with a partner, each person writes before sharing. This is the step that fails most often and it is the one that matters most. Anchoring to another person's first item cuts the output quality sharply.
Step 4. Classify. Each failure reason is either thesis risk (the probability was wrong), mechanics risk (the contract resolved on something the trader did not model), or size risk (the loss is survivable only if size was smaller). Different failure classes produce different revisions.
Step 5. Re-price, re-size, or skip. The pre-mortem should reliably produce one of three outcomes: lower probability estimate, smaller size, or no position at all. An exercise that leaves every number unchanged was not a real pre-mortem.

Pairing pre-mortems with the confidence estimate

A useful discipline after the exercise: write down the revised probability estimate. In the ETH example above, the initial 56 percent view drops to roughly 48 percent once the macro-shock and mechanics modes are priced in. At 48 percent on a contract trading at 42 cents, the edge is thin. The position either needs to be smaller, or it is not a position at all.

Convexly's operator takeaway argues for exactly this kind of discipline: the wallets driving the top of the Polymarket leaderboard are running fewer, more concentrated positions, not more ideas (see the operator's takeaway). The pre-mortem is the filter that does the cutting.

See how your wallet scores.

The analyzer flags over-sizing against a fractional-Kelly baseline and shows the concentration pattern of realized PnL. Free, no signup.

Sources.Klein (2007), "Performing a project premortem," Harvard Business Review, September. Convexly (2026), Edge Score Methodology V1.