Naming Information Buckets by the Question They Answer
Most people who study a game like poker end up with a pile of material that is hard to use. Notes sit in one folder, links sit in another, and half-remembered ideas live in a notebook margin. The problem is rarely a lack of information. It is that the information is organized around where it came from or when it was saved, rather than around the moment you need it. This article takes a different angle: organizing your study material into buckets named after the questions they answer. The approach is general and applies to any body of learning material, and it asks you to do some of the thinking that makes material reusable.
Why Source-Based Filing Breaks Down
Filing by source feels natural. You save something from a particular place and put it in a folder with that place's name. The trouble appears when you try to retrieve it. You rarely remember where an idea came from; you remember what problem it helped with. A note about calculating pot odds might have come from a video, a forum thread, or your own review of a session, and searching by source name forces you to recall a detail you never needed to store.
Date-based filing has a similar weakness. A chronological archive tells you what you looked at in March but not whether the advice still holds or which situations it covers. Both systems organize material around the container instead of around the content's usefulness.
Naming Buckets After Questions
A question-based bucket is labeled with a specific question you want answered, written in plain language. Examples include: when should I widen my calling range from the button, how do I size bets on dry boards, or what do I do when an opponent check-raises every street. Each bucket collects every piece of material that bears on that question, regardless of where it came from.
The naming rule matters. A bucket called Betting is too broad to be useful, and a bucket called Ideas is a dumping ground. A good label is narrow enough that you can tell within a second whether a new item belongs there. If you can't write the question, you probably don't yet understand what the material is for, and that is worth noticing.
A Practical Filing Procedure
When you add a new item, work through a short sequence. First, state in one sentence what decision or situation the item helps with. Second, check whether an existing bucket already asks that question. If one does, file it there and add a brief note about its conditions, such as stack depth or table type, because advice that depends on context loses meaning without them. If none exists, create a new bucket with a specific question as its name.
Third, record the conditions under which the idea applies and the conditions under which it may not. This step is where most filing systems fail. Material stored without its limits invites misuse later. Fourth, review buckets periodically. Merge any two that answer nearly the same question, and split any that have grown so broad they no longer give a clear answer.
A simple checklist for each new item:
Is the decision or situation described in one plain sentence?
Does an existing question bucket already cover it?
Have I written down the conditions that make it applicable?
Have I noted any situations where it may not hold?
Is the bucket name still specific enough to be useful?
Comparing Question Buckets to Other Methods
Tag-based systems let one item appear under several labels, which helps with cross-cutting ideas but can produce clutter if tags multiply without discipline. Folder systems give a clean hierarchy but force a single location. Question buckets sit between the two: each item usually belongs in one primary bucket, with cross-references to related questions noted in plain text.
The tradeoff is upfront effort. Question buckets require you to articulate what you are trying to learn, which many people skip. But that articulation is valuable in itself. It shows you where your understanding is thin, because a bucket you cannot fill with useful material is a signal of a gap, not a filing problem.
Keeping the System Honest
Any organization scheme decays if no one maintains it. Set a light recurring habit, such as a short review at the end of each study week, to check that new items are filed under specific questions and that stale conditions have been updated. Ask of each bucket: could I answer its question from what is stored here? If the answer is no, the bucket needs more material or a sharper question.
The goal is not an elegant archive. It is a system in which the material you need most often is the easiest to reach, and in which you can see at a glance what you know and what you are still trying to figure out.