Cash game players who transition to tournaments often have strong fundamentals. Their hand reading is developed. Their postflop play is sophisticated. Their understanding of equity and ranges is advanced. And yet they consistently underperform in MTTs relative to their cash game win rate.

The reason is not a gap in knowledge. It’s a specific mental habit that works perfectly in cash games and breaks catastrophically in tournaments. Alex Foxen gave it a name: instance tree mapping.

What Instance Tree Mapping Means — and Why Cash Players Don’t Do It

In cash games, stack depth is almost always 100 big blinds or deeper. Decisions unfold with time. If you 3-bet a hand and get 4-bet, you have room to maneuver — call, fold, 5-bet shove. Your options remain open because the SPR (stack-to-pot ratio) is high enough to allow multi-street play.

In tournaments, stack depth shifts constantly. You might begin a hand with 40 big blinds, 3-bet a value hand, and suddenly face a 4-bet from a player with 35 big blinds — which puts you in a shove-or-fold situation you hadn’t modeled when you decided to 3-bet. You’re committed to a spot you didn’t plan for.

Instance tree mapping is the practice of thinking through the full decision tree before initiating action. Before you 3-bet, you ask: if they 4-bet shove, what do I do? Before you flat call, you ask: if they c-bet this texture with pot-sized aggression, what’s my range’s response? Cash players don’t do this because they almost never need to. The stack depth makes post-action decisions manageable. At tournament stack depths, skipping this step is fatal.

The Exact Leak: 3-Betting a Hand You Can’t Call Off

Foxen’s specific example from the Bracelet Hunter interviews: a cash player sees AJo in late position against an early position open. In a cash game context at 100+ BBs deep, 3-betting AJo for value is reasonable — you’re ahead of much of the villain’s range, you have implied odds if they call, and you have enough stack depth to play post-flop.

In a tournament at 35–40 big blinds effective, the same 3-bet means something entirely different. If the villain shoves — which many players will do with a wide value range at this depth — you now have to call off 3-betting a hand that loses to most 4-bet-shove ranges. AJo crushes ATo but folds to 4-bet-shoves from TT+, AQ, AK. The 3-bet has put you in a spot where your best outcome is getting folds and your worst outcome is calling off 35 big blinds as a dog.

Foxen’s instruction is exact: “Before you 3-bet at 30–40 big blinds, ask yourself what you do if they shove. If the answer is fold, then you’ve already told yourself this isn’t a 3-bet spot. Either flat it or fold it — don’t put yourself in a position where the natural continuation costs you your stack.”

Ben Lamb’s Confession: $300,000 Buy-In, Checking Push-Fold Charts

Ben Lamb — 2011 WSOP Player of the Year, multiple Main Event final tablist — told a story in his Bracelet Hunter interview that every cash game player should hear. He had been playing primarily cash for several years, then entered a $300,000 high roller event. During the tournament, he found himself checking push-fold charts on his phone because he didn’t know what to do with KJo at 12 big blinds from the cutoff.

“I’m embarrassed to say it. But I hadn’t played short stack tournament poker in so long that the mechanical knowledge wasn’t there. All my cash game skills mean nothing when everyone’s under 20 big blinds and I’m guessing.”

This is the reality of the cash-to-tournament gap. It’s not that cash players are worse poker players. It’s that short stack tournament play is a distinct skill set that requires deliberate practice and instance tree mapping is the framework that makes it work.

Five Cash Game Players Tournament Mistakes: Where Instance Tree Mapping Breaks Down

1. 3-Betting Merged Ranges at Short Stack Depths

Cash players often 3-bet a merged range — good hands that want to play post-flop but aren’t strong enough to get stacks in pre. At 25–40 BBs in a tournament, this range doesn’t exist. Everything 3-bet is either a value shove, a 3-bet-fold, or a call. Merged 3-bets create spots where you’re pot-committed without wanting to be.

2. Flatting Strong Hands Pre-Flop

In cash, flatting KK pre to keep worse hands in is a standard line. At 30 BBs in a tournament, flatting KK and seeing a 5-way flop with an SPR under 2 means you’re playing a committed pot without an agreed-upon plan. Instance tree mapping would tell you: with KK at this depth, you want to get heads-up and leverage. Re-raise.

3. Bet Sizing Mismatch With Stack Depth

Cash players default to bet sizes calibrated for 100BB play. At 25–35 BBs, those sizes create accidental commitment. A 70% pot c-bet on the flop when the SPR is already under 2 means you’re effectively pot-committed on the turn regardless of what you hold. Instance tree mapping requires calculating SPR before choosing post-flop sizing.

4. Ignoring Stack-Based Range Adjustments in Opponents

Foxen makes this explicit: “Cash players assign static ranges to opponents. But at 20 big blinds, the guy who had AK at 100 big blinds now has a 20-big-blind range. Those are completely different things.” Instance tree mapping includes modeling how opponent ranges change as stacks shrink — not just your own decision tree.

5. Failing to Account for ICM When Modeling Tree Branches

In cash, the EV of a call is purely chip EV. In a tournament near a pay jump or bubble, the ICM adjustment on a marginal call can swing a +chip EV spot into a tournament-EV disaster. Cash players routinely make calls that are technically correct chip-wise and costly overall. Instance tree mapping in tournament poker must include “and what does this mean for my tournament equity?” as a final branch.

GTO LAB courses focus heavily on correcting tournament-specific leaks that many cash game players still struggle with:
https://elitepokerguide.io/gto-lab-courses-in-2026/

How to Build Instance Tree Mapping as a Habit

The CLC framework in The Closer addresses this through the Mechanics pillar — specifically the stack depth section. The core practice:

Before every 3-bet, 4-bet, or large open at sub-50 BBs effective, verbalize one question: “If they respond maximally, what do I do?” If the answer is fold, reconsider your action.
Calculate SPR immediately on every flop. Stack / Pot = SPR. Below 2: you’re in commit-or-fold mode. Between 2–4: one major bet commits. Above 4: room for multi-street play. Cash players rarely think in SPR. Tournament players must.
Study specifically at the 20–40 BB stack depth range. This is where cash players break. Use solver tools or study guides focused on this specific window — not just push-fold charts, but full range construction at these depths. Our guide on playing 10–25 BBs in MTTs is a starting point.

The Course Where This Is Fully Taught

The complete instance tree mapping framework — applied to real hands at real WSOP stack depths — is inside the CLC Bracelet Hunter. You watch Foxen articulate the concept and then immediately see it applied in Chance’s bracelet win hand history.

The Closer then builds the systematic Mechanics pillar around stack-depth decisions, including SPR-based bet sizing, short-stack 3-bet construction, and ICM-adjusted calling ranges.

Both are relevant to any serious cash player who wants to stop leaving results on the tournament table. Available at ElitePokerGuide.io with a forever license — no subscription.

Also read: Cash Game vs Tournament Poker — Full Strategy Comparison and the Advanced Cash vs Tournament guide.

🎫 Save on both courses: elitepokerguide.io/coupons

🃏 CLC Bracelet Hunter — Forever License
🏆 CLC The Closer — Forever License
🎫 Current Coupon Codes