Three decisions a reader brings to a guides library, and the three sections that answer them
Most readers who arrive at a fantasy guides library bring a single decision with them. They want to know whether to pick the captain before the toss or after. They want to know whether the salary cap is a constraint or a suggestion. They want to know which of two contests on the splash page is the safer first session. The library is large because the topic is large, but the reader does not need the whole library for the next decision. The reader needs the section that pays for that decision first.
The path below treats three sections of a typical walkthrough as three answers to three different reader questions. The rule section answers the "what does the format actually do" question. The worked example answers the "how does the rule look in a session the walkthrough never named" question. The checklist answers the "what do I do in the next ten minutes" question. A reader who knows which question they are asking will know which section to read first, and the rest of the walkthrough will fall into place behind it.
Nothing here claims a current event, live offer, current contest, current scoring update or named brand partnership. The decision map is built from the stable parts of any fantasy contest: a squad size, a salary cap, a captain multiplier, a deadline and a single session length. The exact numbers in the worked example are illustrative, not live, and the only items worth carrying out of this piece are the three questions and the three sections.
Decision one: "I have never opened a contest of this format before."
The first decision is the one a first-time reader brings, and it is the one a library most often answers with the wrong section. A reader who has never opened a fantasy contest of a given format is not asking "what does this rule mean in a worked example." A reader who has never opened the format is asking "what does this format do that the splash page does not already say." The answer to that question lives in the rule section of a walkthrough, not in the worked example and not in the checklist.
The reason the rule section is the right answer is that the rule section names the format's vocabulary before it names anything else. The vocabulary is what a first-time reader needs. Without the vocabulary, the worked example reads as a sequence of unexplained terms, and the checklist reads as a list of commands the reader cannot evaluate. With the vocabulary, the worked example becomes a way to test the vocabulary, and the checklist becomes a way to apply it. The rule section is the section that turns a walkthrough from a document a reader has to translate into a document a reader can act on.
Scenario test: take the rule "your captain's points are doubled, and your vice-captain's points are doubled if the captain does not play." A reader with no prior vocabulary reads the rule and knows what a captain is and what doubling means in this context. A reader who skips the rule and reads the worked example first meets a sentence like "with the captain doubling against a target of 168, the multiplier lifts the side by 22 points." The reader without vocabulary stops at "target of 168." The reader with vocabulary keeps going. LetsGame editors treat the rule section as the only acceptable first section for a first-time reader, because the rest of the walkthrough cannot do its job without it.
Decision two: "I have read the rules, and I want to know how they play out in a session."
The second decision is the one a reader who has already read the rule section brings, and it is the one a library most often answers with the wrong section as well. A reader who has the vocabulary and now wants to test it is asking "how does this rule behave when the format meets a session the walkthrough never named." The answer lives in the worked example, not in a second pass through the rule section and not in the checklist. A second pass through the rule section gives the reader the same vocabulary they already have. The checklist gives the reader a list of commands the reader cannot yet evaluate. The worked example is the only section that lets the reader test the vocabulary against a session that is not the reader's own.
A working worked example has three small marks. The example names the inputs. The example names the trade-off between the inputs. The example names the moment the trade-off becomes visible in the session. A worked example without the inputs is an opinion piece. A worked example without the trade-off is a recap. A worked example without the moment is a worked example that has not finished the second paragraph. LetsGame editors read every worked example for the three marks before publishing, because the section that fails one of the marks will fail the reader's decision.
Scenario test: a reader who has read the rule about the captain's multiplier now wants to know what the rule looks like in a chase versus a defending total. The worked example walks the captain decision through one specific session: a target of 168 in a twenty-over contest, a captain picked after the toss who bats second, and a multiplier that lifts the captain's contribution by a worked number of points. The reader who carries the three marks away from the example will recognise the same shape in a session with a different target, a different captain and a different multiplier. The reader who only carries the worked numbers away will recognise the shape only in the worked session.
Decision three: "I have the rules and the example, and I have ten minutes before the deadline."
The third decision is the one a reader who already has the vocabulary and has already seen the worked example brings, and the answer is the checklist. The reader who has both the rule and the example does not need a third reading of either. The reader needs the short, ordered list of actions that turns the rule into a finished submission before the deadline. The checklist is the only section that gives the reader that list without adding vocabulary or worked numbers the reader has to re-process.
A working checklist has three small marks as well. Each item names an action. Each item names the deadline the action sits inside. Each item names the failure mode if the action is skipped. A checklist without deadlines is a to-do list. A checklist without failure modes is a sequence of preferences. LetsGame editors write every checklist to those three marks because the section that fails one of the marks will produce a reader who follows the list and then cannot tell whether the list worked.
Scenario test: a reader with a deadline in ten minutes opens the checklist and reads four items. First, pick eleven players, with three or four all-rounders. Second, fit the salary cap, with the top six taking no more than half the purse. Third, set the captain after the toss, not before. Fourth, set the vice-captain for the case the captain does not play. Each item carries a deadline in the reader's session and a failure mode the reader has been warned against. The reader who finishes the checklist in eight minutes has a submission ready at the deadline, with the vocabulary and the worked example still available for the next contest.
Why the decision order matters, and what changes if the reader answers in reverse
Reading in the order rule, example, checklist is the order that matches a first-time reader, a reader who has the rules and wants to test them, and a reader who has both and needs to act. Reading in any other order produces a different reader and a different outcome. Checklist first produces a reader who can copy the commands but cannot evaluate them when the contest returns an unexpected result. Worked example first produces a reader who can recognise the shape of the worked session but cannot name a different session the same way. Rule section first is the only order that builds the vocabulary the next two sections rely on, and it is the only order that lets the rest of the library carry forward.
The reversal that costs the most is the checklist-first reversal. A reader who treats the checklist as the entire walkthrough will finish a first session having followed the commands and learned nothing about the commands. The second session will return an unexpected result and the reader will not be able to diagnose it, because the vocabulary and the worked example were never built. The reader will, in most cases, blame the checklist. The checklist did not fail. The reader skipped the section that gave the checklist its meaning.
LetsGame editors read walkthroughs in the order that matches the reader's first question. The decision map above is the order LetsGame editors would recommend to a reader who asked which section to start with. The order is not a ranking. The order is a triage that pairs a reader's specific decision with the section that pays for it first, and lets the other two sections wait for the second and third session.
When the reader's decision is uncertain, and the section that catches the misroute
Not every reader arrives with a clean decision. Some readers arrive with two or three at once, or with a decision that does not match any of the three above. The cheapest triage for an uncertain reader is to ask, in one sentence, "what is the next action I have to take before the browser tab closes." If the answer names a specific action, the reader has decision three and should open the checklist. If the answer names a specific session the reader wants to recognise, the reader has decision two and should open the worked example. If the answer is a question about the format itself, the reader has decision one and should open the rule section.
The triage has a fourth case that does not fit the three decisions above: the reader who has no decision at all. A reader with no decision is a reader who opened the library because the page looked interesting, and the right section for that reader is the glossary, not any of the three. The glossary is the section that lets a reader with no decision build the vocabulary without committing to a session. LetsGame editors treat the no-decision case as a fourth entry point that sits beside the three decisions, not underneath them.
The reader who skips the library and the order that fails first
Some readers open a single walkthrough and skip the library. The single-walkthrough reader is the most common reader LetsGame editors write for, and the single-walkthrough reader fails in one of three predictable places. The first failure is at the rule section, where the reader stops reading because the vocabulary is not yet interesting. The second failure is at the worked example, where the reader skips the trade-off paragraph because the worked numbers look finished. The third failure is at the checklist, where the reader follows the commands without reading the deadlines and produces a submission that misses the contest window.
The first failure is the cheapest to prevent, because the rule section can be re-opened. The second failure is the most expensive, because the trade-off paragraph is the section that pays for the rest of the walkthrough. A reader who skips the trade-off paragraph will not know what the rule is wrong about when the rule is wrong. The third failure is the one LetsGame editors warn against most often, because the deadline is the part of the checklist that does not survive a re-read. A reader who reads the checklist once and forgets the deadline will fail the next session at the deadline, not at any earlier point in the checklist.
The path the article recommends for a single-walkthrough reader is the same path it recommends for a library reader. Read the rule section once. Read the worked example once. Read the checklist once. Read the trade-off paragraph twice. Read the deadline in the checklist three times. The repetition is the cost of skipping the library, and the cost is smaller than the cost of a contest window missed at the deadline.
Using the decision map on a walkthrough you have never opened
The practical use of the decision map is the first sentence test. Open the walkthrough, read the first paragraph, and ask which of the three decisions the first paragraph is answering. If the first paragraph is naming a format vocabulary term, the first paragraph is answering decision one and the walkthrough should be read in the order rule, example, checklist. If the first paragraph is naming a session the reader has not played, the first paragraph is answering decision two and the walkthrough should be read in the order example, rule, checklist. If the first paragraph is naming an action the reader has ten minutes to take, the first paragraph is answering decision three and the walkthrough should be read in the order checklist, rule, example.
The first-paragraph test is a triage, not a rule. A walkthrough that opens with a rule paragraph and a deadline in the same sentence is asking for two decisions at once, and the reader has to choose which decision to honour first. LetsGame editors honour the deadline first and the rule second, because the deadline is the part that does not survive a re-read. A walkthrough that opens with a worked number and no rule paragraph is asking for decision two without decision one, and the reader has to back-fill the rule paragraph before the worked number does useful work. The first-paragraph test catches both cases and lets the reader re-order the walkthrough in the first minute.
Readers who want to add the next walkthrough to a working reading list can move from this decision map into the rest of the guides library at LetsGame guides, where the walkthroughs are listed in the order a reader who knew which decision they were bringing would read them in.
