How to Map a Chapter in Seven Minutes

Most people read chapters at the same speed they read magazines. That's a category error. Magazine articles are written for cover-to-cover linear consumption. Book chapters are written as structured arguments, and the way to read them well is to map them first and read them second. Here is the seven-minute ritual we use on every chapter that matters.

Minute 1 - Read the title twice

The title is doing more work than it looks. Read it once for the words. Then read it again and ask: is this a claim, a question, a label, or a story? Each answer suggests a different chapter shape. 'The Power of Compound Interest' is a claim. 'Why Do We Forget?' is a question. 'The Tools' is a label. The right shape for your map follows from this single decision.

Minute 2 - Scan the sub-headings

Most chapters in modern non-fiction have 3-6 sub-headings. Skim them. Don't read them carefully - just notice how many there are and whether they form a sequence, a list, or a mix. Write each one as a stub branch on your map, leaving plenty of space between them. Don't try to write the chapter's argument yet. Right now you're scaffolding.

Minute 3 - Read the first paragraph

Authors usually telegraph the chapter's purpose in the first paragraph. Read it carefully and write a one-sentence summary at the centre of your map. This is your chapter's centre of gravity. Every other branch will either support it, complicate it, or argue with it.

Minute 4 - Read the last paragraph

Most readers never do this. They should. The last paragraph is the author's chance to reinforce the chapter's takeaway, and reading it second tells you whether the first paragraph was honest. If the first and last paragraphs disagree, you have a chapter that's harder to map - but you've also caught a critical reading move: noticing when the framing shifts.

Minute 5 - Read the body, marking only key terms

This is where reading actually happens, but it happens differently than you're used to. Read fast. Don't underline. Don't highlight. Instead, when you hit a key term - a named concept, a number, a piece of evidence - write it as a leaf on the relevant sub-heading branch of your map. The map drives the reading, not the other way around.

Minute 6 - Add your reactions as a separate branch

While you read, your brain will generate reactions. Disagreements. Connections to other books. Memories. Don't put these on the chapter map - that's contamination. Put them on a 'side thoughts' branch off the centre. Most of your best ideas come from this branch, and parking them there keeps them safe while you keep reading.

Minute 7 - Close the map

Look at the page. Is each sub-heading branch supported by 1-3 leaves? If yes, you've understood the chapter. If a branch is empty, you skipped that section - go back. If a branch has 7+ leaves, you over-mapped - collapse the leaves into a single keyword. The goal is balance, not completeness.

The reason this works

The seven minutes are doing two things that ordinary reading doesn't. First, the map activates retrieval - every time you write a leaf, you're not transcribing, you're compressing. Second, the structure makes you read with a budget. You can't read every sentence carefully, so you triage. This is what good readers always do; the map just makes it explicit.

The first ten chapters you do this with will feel slower than ordinary reading. The next ninety will feel faster. By the time you've mapped a hundred chapters, you'll start doing it in your head and your maps will become highlights only of the chapters that resist being mapped - and those are usually the ones worth slowing down for.