Organizing Poker Study Material Around Unanswered Hands
Most poker players collect more study material than they can use. Hand histories pile up, articles get bookmarked, and notes from old sessions sit in folders that nobody opens. The problem is rarely a shortage of information. It is that the material is organized around where it came from or when it was saved, which tells you nothing about what you should do next. This article describes a different starting point: organizing your study material around the decisions you have not yet resolved. Each category becomes a question, and each piece of material either helps answer that question or it does not belong in the active set.
Why source-based and date-based filing fails
Filing notes by source, such as a particular video series or a book, feels tidy at first. The trouble appears when you sit down to study. A source folder tells you that a concept came from a certain place, but it does not tell you which of your current spots it applies to. You end up rereading material you already understand while the decisions that cost you the most stay untouched.
Date-based filing has a similar weakness. Sorting by when you wrote a note preserves a timeline of your thinking, which can be interesting for personal reflection, but it does not help you find what matters for an upcoming session. A note from three months ago about a river bluff may be more useful today than one written last week about a preflop open, and a date sort will never surface that connection.
Topic-based filing, such as putting everything under preflop, postflop, or tournaments, is closer to useful but still incomplete. Topics are broad, and a broad folder tends to become a dumping ground. You may have forty notes under postflop, most of which do not address the specific question you are facing.
Building a question-first structure
A question-first structure starts from a short list of open decisions. Write each unresolved decision as a plain question, phrased so that a note could answer it. Examples include: when should I check-raise a single-raised pot on a dry board, or how often should I defend the big blind against a late-position steal in a particular format. Each question becomes a category, and only material that bears on that question goes inside.
Keep the list short, ideally between five and ten open questions. A long list signals that the questions are too granular or that you are trying to cover everything at once. When a question is resolved to your satisfaction, move its notes into an archive rather than deleting them, since the reasoning may matter again later. New questions come from your own review of play, not from whatever you happened to read recently.
Each note should carry a small amount of metadata: the question it serves, the situation it describes, and one sentence stating what you concluded. A hand history with a short annotation is more useful than a long transcript without one. The goal is that a note can be understood without reopening the original material.
Sorting the existing pile
Most players already have a backlog, so the question is how to sort it without spending weeks on the task. Start by taking the ten most recent items you saved and asking, for each one, which open question it serves. If none fits, mark it as reference-only and set it aside. You do not need to process the entire backlog in one sitting. Spend a fixed block of time, perhaps thirty minutes a week, and stop when the time is up.
Expect that a good portion of the material will be reference-only. That is normal. Reference material is useful when a specific situation calls for it, but it should not crowd the active set. Keeping a separate reference area lets you find things when needed without making them compete for attention with the questions you are actively working through.
A practical checklist for ongoing maintenance
Use the following checklist after each session or review block. First, list any decision you were unsure about during play, in one line each. Second, check whether each line matches an existing open question; if not, add a new question if it recurs or note it as a one-off. Third, file any new notes under the question they serve, with a one-sentence conclusion. Fourth, review the active questions and archive any that you feel you have resolved, moving their notes to the archive with a date. Fifth, confirm that the active set still holds between five and ten questions; trim or merge if it has grown too large.
A second, shorter checklist helps before you study. Pick one open question. Find the notes filed under it. Read your conclusions first, then the underlying material only where a conclusion seems unclear. Finish by writing one sentence about what you will test in your next session. This keeps study tied to play instead of drifting into passive reading.
Review the system itself every month or so. If you find yourself consistently unable to file notes, the questions may be too vague. If notes pile up under a single question, that question may need splitting. Adjusting the structure based on how it actually works is more effective than trying to design the perfect system at the start.
Keeping the system honest
A question-first system only works if you let it change. Questions should be retired when they are answered, replaced when they stop mattering, and rewritten when they turn out to be the wrong question. The organization serves your study, not the other way around. If a structure starts requiring more upkeep than the study it supports, simplify it.
Finally, be wary of treating a tidy folder as evidence of progress. Filing a note is not the same as learning from it. The useful test is whether, during play, you can recall the conclusion for the decision in front of you. If you can, the organization is doing its job. If you cannot, the answer is usually to shorten the note, revisit the question, or test the idea in a few sessions before moving on.