Structuring a Textbook

A unit groups content that shares a conceptual foundation. Students should be able to state what a unit is about in one sentence — and that sentence should name a concept, not a collection of topics.

Units should progress from simpler to more complex, from concrete to abstract, from foundational to applied. Group by conceptual relationship, not by scheduling convenience or the chapters that fit in a given week.

Each unit should build on the previous one. If unit three assumes knowledge from unit two but not unit one, either reorganize or make the dependency explicit in the text.

A chapter is a self-contained learning unit: it introduces, develops, and consolidates one concept or skill. A student who completes a chapter should have a clear, stable understanding of that concept — not a half-formed impression they'll need to reconcile later.

Chapter structure should be consistent throughout the book: opening with learning objectives, developing content in a predictable order, closing with review or practice. Predictable structure reduces cognitive load — students spend less effort figuring out how to read and more effort on what to understand.

Each chapter should be completable in a manageable study session. If a chapter is too long to cover in one sitting, consider whether it's really two chapters.

Learning is cumulative. A term used in chapter five that wasn't defined until chapter seven is a structural error, not a stylistic choice. Map your prerequisites and enforce the order.

Strategic repetition is a feature, not a flaw. Concepts introduced in chapter two can be used in chapter five — and using them reinforces the earlier learning. Treat repetition as deliberate reinforcement, and signal it: "As we saw in Chapter 2..."

Don't assume students remember everything from previous chapters. Review key concepts at the point of use, especially for anything that will be built upon heavily.

Before drafting, list every concept the book will teach and draw arrows from each concept to the ones it depends on. This prerequisite map shows the order chapters must come in, and flags circular dependencies early, while they are still easy to fix.

Review the map with someone who teaches the course. They know where students actually get stuck, which is not always where the subject looks hardest on paper.

Terminology should be introduced once, defined clearly, and used consistently. If you change how you refer to something — different notation, different framing, a synonym — signal it explicitly. Silent inconsistency is one of the most common sources of student confusion.

Figures, examples, and case studies should be self-contained: explained where they appear, not assumed to be understood from context. A student who encounters a figure for the first time shouldn't have to search back through the chapter to understand it.

Write for the full range of students who will use the book. Give every figure a caption that explains its point, provide alternative text for images in digital editions, and choose examples from a range of contexts so that more students recognize themselves in the material. Clear, plain language helps every student, including those reading in a second language.

Imagine a chapter introducing supply and demand. A logical sequence: begin with a concrete scenario students recognize, such as concert ticket prices; define demand and show a demand curve; define supply and show a supply curve; combine them to explain equilibrium; then return to the opening scenario and explain what happened to the ticket prices.

Each step relies only on what came before. Equilibrium isn't mentioned until both curves have been explained, and the final return to the opening example shows students they can now explain something they couldn't at the start.

The chapter ends with practice problems that match its objectives: reading a demand curve, predicting what happens when supply shifts, and explaining a real price change in terms of both curves.

Worked examples, regular checkpoints, and end-of-chapter reviews tied to the objectives do the most work.

• Worked examples show the full reasoning behind a solution, not just the answer. Follow each one with a similar problem for the student to try, so they practise the same reasoning straight away.
• Checkpoints — short questions every few pages — let students test their understanding before moving on. Checkpoints help most immediately after a difficult concept, not only at the end of the chapter.
• Summaries, key-term lists, and review questions at the end of the chapter help with revision. Keep them aligned with the objectives stated at the start, so the chapter opens and closes on the same promises.