From Chunks to a Module

A Recipe You Keep, Not a Meal You Eat Once

The first of the three moves is combining, and this chapter is about the most basic version of it: taking a pile of chunks and building them into one module. Everything later in the book, every repackaging and every swap, depends on your having modules worth reusing, and modules do not appear on their own. You make them, deliberately, out of the units you already captured.

Start with the mindset, because it changes how you build. When you combine chunks into a module, you are not making one finished piece to use and discard. You are making something you intend to keep and run again. The difference is the difference between a meal and a recipe. A meal is cooked once and eaten; when it is gone, it is gone. A recipe is built to be made again, by you, next month, without starting over. Most people, when they assemble ideas, cook a meal. They write the lesson for Tuesday’s class and the work evaporates when Tuesday ends. This chapter is about writing the recipe instead, so the work survives the occasion that prompted it.

Building a module from chunks comes down to four moves:

1. Select the chunks that belong together.
2. Give the assembly one job.
3. Settle the order.
4. Add the connective tissue that makes it hold as one thing.

Take them in turn.

Select the Chunks That Belong Together

A module begins as a selection. You reach into your collection and pull the chunks that belong in this one assembly, and, just as important, you leave out the ones that do not.

Say you are building the lesson on compound interest. You go looking and you have more material than you think: a clean definition of compound interest, a vivid example of a small sum growing over decades, the common mistake people make in underestimating it, a contrasting note about how debt compounds the same way, a historical anecdote, a chart you once made. That is six or seven candidate chunks. The temptation is to use them all, because each is good. Resist it. Selection is as much about exclusion as inclusion. The historical anecdote may be wonderful and still not belong in this lesson, because it pulls attention away from the one thing the lesson exists to do.

How do you decide what stays? By the next step, which is really the controlling one.

Give the Assembly One Job

A module does one complete job. Not three jobs, not a job and a half. One. Before you order anything, say in a single sentence what this module is for, and let that sentence govern every other decision.

The job of the compound-interest lesson is: make the learner truly feel that small amounts grow into large ones over time, so they act sooner. That is the job. Now the selection almost makes itself. The definition stays, because they need it. The decades-long example stays, because it does the emotional work the job names. The common mistake stays, because naming it is what gets them to act sooner. The debt note stays only if it sharpens the main point and goes if it dilutes it. The historical anecdote, charming as it is, goes, because it serves a different job. A module with one clear job is easy to build, easy to recognize later, and easy to reuse, because you know exactly what it is for. A module that tries to do several jobs is hard to place anywhere, because it half-fits everywhere and fully fits nowhere. The job is the control point; selection, order, and connective tissue all answer to it.

This is the same instinct a comedian uses building a bit. Three jokes that happen to be funny do not make a bit. Three jokes about the same thing, building toward one comic idea, make a bit. The shared job is what turns a handful of laughs into a single unit you can drop into any set. The job is the glue.

Settle the Order

With the right chunks selected around one job, you arrange them. Order is not decoration; it is part of what the module does. The same chunks in a different sequence can teach well or teach badly.

For the lesson, the order has a logic: you need the definition before the example can mean anything, and you need the example to land before naming the mistake will sting, and you want the mistake last because it is the push to act, the note you want ringing when the lesson ends. That is one defensible order, and you settle it now, while you are building the recipe, so you never have to re-derive it on a Tuesday morning. Settling the order once is a large part of what you are saving. It was one of the expensive decisions from Chapter 1, the kind you used to make again every term. Make it deliberately, and it becomes part of the module forever.

A useful test is to ask, of each chunk, what has to be true in the reader’s head before this lands, and put whatever makes that true ahead of it. Sequencing is mostly the discipline of paying off setups before you rely on them.

Add the Connective Tissue

Selected, aimed, and ordered, your chunks are still a list. What turns a list into one thing is connective tissue: the short bridges that carry a person from one chunk to the next so the seams disappear.

This is the least glamorous step and the one that most determines whether the module reads as a whole or as parts stacked together. A sentence that hands off from the definition to the example. A line that turns from the example to the mistake. These bridges are small, but they are where assembly actually happens, the mortar between the bricks. Write them as part of the module, not as throwaway patter you will improvise live, because if you improvise them you will re-improvise them every single time, and the module will never quite be done. Written down, they make the lesson self-contained: it now flows on its own, without you standing there to talk between the pieces.

One caution. Keep the connective tissue light and internal. It should join the chunks to each other, not staple the module to one particular course. “Now that we understand compounding, here is the mistake” travels anywhere. “As we saw last week in the budgeting lesson” does not; it chains this module to one context and quietly destroys its reusability. The next chapter is largely about this distinction, but it starts here, in how you write the bridges.

Not Only Content

One widening before we close, because it matters for how much of your life this book reaches. A module is not only a piece of content. The same four steps build other kinds of reusable wholes.

The way you handle a difficult conversation is a module: a few moves you have learned, selected because they belong together, aimed at one job, run in a sensible order, with your own connective instincts between them. A decision rule you apply when an opportunity comes along is a module. A routine you run at the start of a project is a module. Anything you have figured out once and would rather not figure out from scratch again can be built into a keepable assembly the same way you built the lesson. Once you see modules as recipes you keep, you start noticing how many of them you have been cooking fresh every time.

What Comes Next

You now have the core skill of Part II: turning chunks into a module by selecting around one job, ordering for flow, and binding the pieces with light connective tissue, all built as a recipe you keep rather than a meal you eat once.

But not every assembly you build this way is actually good, and not every good one is built to last. A module can do its job today and still be too tangled, too sprawling, or too dependent on its surroundings to reuse tomorrow. So the next chapter looks closely at what separates a module that travels from one that is stuck where it was born. It lays out the anatomy of a good module, and gives you a short checklist to run any assembly against before you trust it enough to keep.