The order moves from input to output: a question before reading shapes what you notice, one marked surprise supplies evidence, and the sentence, the disagreement, the experiment and the spoken explanation each consume what came before. Every step is small enough to finish in one sitting and specific enough to be wrong. Read the book once; work the strip six times.
Step 1: Ask before you open the cover
Before page one, decide what you want out of it. A question narrows attention: read with 'Why do habits survive stressful weeks?' in mind and the useful passages announce themselves, while the rest of the book stays background. Phrase it as something the book could actually answer, then write it on your checklist strip in ink so it stays in front of you. Vague questions like 'How do I improve?' pull vague notes. Skipping this step is the most common shortcut, and it costs you later: by step three you are asked to state the argument, and without a question to test it against, you end up paraphrasing the introduction instead of thinking.
Step 2: Flag the moment your model breaks
Surprise is the signal that something in your model changed, and it is easy to lose. With a question already written from step one, you have a filter: as you read, one passage will push back against what you assumed. When it does, fold the corner and write three words in the margin about why it surprised you, plus the page number. That beats highlighting, which mostly marks agreement and feels productive without recording anything you did not already think. People commonly overdo this and flag fifteen lines, which turns the book into a pile of unread markers. One idea, clearly marked, is enough to carry into the next step. Choose the one that made you pause, not the one that sounded smart.
Step 3: Compress the book to one sentence
Two steps in, you have a question and one marked surprise. Now compress the whole book into a single sentence of your own making, built with the word because or therefore. 'The author argues that X because Y' is a usable sentence; 'the book is about habits and systems' is a topic, not an argument. Test it by asking whether someone could disagree with your sentence. If nobody could, you have written a summary of the subject rather than a claim. The failure here is chapter-by-chapter summarising: good notes, no position. A table of contents rewritten in your handwriting is not comprehension. Write the sentence on the strip, then check it against your step-one question. If the book answered that question, your sentence should say so plainly.
Step 4: Find the load-bearing weak point
Agreement feels like understanding, which is why a book you nod through teaches you the least. Your single-sentence argument from step three now gives you something to push against. Pick exactly one claim you doubt or want verified, then write down what evidence would change your mind about it. If the author says deep work needs four uninterrupted hours, your line might read: 'Doubt it — I did my best writing in two 90-minute blocks last month.' Notice this is specific enough to test. Two failures are common here. Choosing a trivial nitpick, like a misused statistic, gives you nothing to think with. Choosing a claim so large that no week of reading or experimenting could touch it does the same. One arguable, checkable claim is the whole point.
Step 5: Convert one idea into a test
Now the book has to survive contact with a week. You have an argument (step three) and a doubtful claim (step four); the action comes from the argument, because that is the part the author is actually betting on. Write it with a day, a place, and an observable result: 'Thursday, before the 9am meeting, I will write the agenda first and note whether the meeting ran short.' Vague resolutions such as 'be more deliberate' cannot fail, so they cannot tell you anything. Another common stall is deciding to wait until you finish the book — by then the idea has faded into general impressions and you will never come back to it. One action, scheduled, with a result you'd be able to describe out loud next Sunday, is enough. Skip the second and third experiments.
Step 6: Teach it out loud, notes closed
Speaking without notes is the last filter, and it exposes the difference between recognition and recall. Set three minutes, find one person, and explain the book with your strip face down. Start with your step-one question, give the single-sentence argument, mention your one surprise, and finish with what you tried and what happened. Most people find a gap in the middle — often the causal link, the because in their sentence. That gap is exactly the part to reread, which is a far better use of an hour than starting the book again. Reciting your notes aloud is the classic dodge; it feels like explanation and tests nothing, because the paper is doing the remembering for you. No notes, no hedge words, three minutes.
A phone reminder disappears the moment you dismiss it and leaves no trace of whether it worked. A paper strip taped above the desk does not: the checklist visibly gets shorter as you cut steps off, and the final strip stays there until the book has produced something you actually use.