Three Moves, and Only Three
You now know what a module is: a reusable assembly that is whole on its own and able to become a part of something larger. The natural next question is the practical one. You have a module. What can you do with it?
There are three moves, and only three.
The answer is unusually clean. There are three moves, and only three. You can combine modules into something bigger. You can repackage a module into a different form. And you can swap one piece for another. Every act of reuse in this book is one of these three, or a few of them together. The rest of the book is mostly the patient work of learning to do each one well, but you can hold the whole map in your head right now, because it has only three roads on it.
The fastest way to feel all three is to watch them happen in one place, so step into a kitchen for a moment before we return to the course.
Combine, repackage, swap. Every reuse you will ever do is one of these three.
Combine: Building Up
The first move is the one you already met in Chapter 2. Combine means putting chunks or modules together to make a larger module.
In the kitchen, you combine ingredients into a dish. Flour, butter, sugar, and heat become a pastry. Then you combine dishes into a meal: the pastry joins a main and a side and becomes a dinner. Each step takes complete pieces and assembles them into a bigger complete piece. The dish is whole, and it becomes a part of the meal. The meal is whole, and it could become one part of a week’s menu. This is just the ladder from Chapter 2, seen as an action rather than a picture. Combining is how you climb it.
Your course is built by combining. Chunks combine into a lesson; lessons combine into the course; the course could combine with others into a program. When you combine well, the result holds together as one thing rather than feeling like parts bolted side by side, and most of Part II of this book is about exactly that, how to combine chunks into a module that is genuinely one whole and not a list.
The Module Is Not the Package
Before the second and third moves, you need one distinction, because without it they do not make sense. It is the difference between a module and its package.
The module is the lesson, the thing you are actually delivering: the idea, the argument, the recipe, the outcome. The package is the form you deliver it in. Take the compound-interest lesson. The lesson, the actual content and the way it teaches the idea, is the module. But you can deliver that same lesson as a live talk, a short video, a written handout, a slide section, or a quiz. Those are five packages around one module. The lesson did not change. Its clothing did.
The same split is obvious with a recipe. The dish is the module. The recipe printed in a cookbook, filmed as a thirty-second video, and boxed as a meal-kit card are three packages around the one dish. Once you can see the module as separate from its packaging, the last two moves open up, because both of them work by holding the module fixed and changing something around it.
Package The form a module is delivered in. The lesson is the module; the talk, the video, or the handout is the package around it.
Repackage: Re-Dressing Sideways
The second move is repackage. Repackaging means keeping the module the same and changing its form.
This is the move people most often miss, and it is where an enormous amount of hidden reuse lives. You spent real effort getting the compound-interest lesson right. Repackaging says: that effort should pay off in every format, not just the one you first built. So the same lesson becomes the webinar segment, then the PDF, then the short video, then the email, then the chapter. You are not teaching five different things. You are dressing one thing five ways for five different occasions.
The kitchen makes the move vivid. One dish can be plated for a quiet dinner, scaled up for a banquet, simplified into a meal-kit, and stripped down for a food-truck window. It is recognizably the same dish each time. What changes is the presentation, the portion, the setting. And here is the quiet reward that makes repackaging worth its own part of the book: improve the dish itself, and every version improves at once. Fix the lesson, and the webinar, the PDF, and the video all inherit the fix, because they were only ever packages around the one module. You will see this again and again. Work spent on the module pays out across every package forever.
Swap: Substituting a Part
The third move is swap. Swapping means replacing one piece with another while the larger whole keeps working.
This is the move that makes your work survive change instead of being destroyed by it. Suppose a tax law changes and the number in your investing lesson is now wrong. You do not rebuild the lesson, and you certainly do not rebuild the course. You swap the one chunk that went stale, the figure, and everything around it holds. Or suppose a whole lesson has been overtaken by the field. You swap the entire lesson for a new one, and the course survives the substitution because the lesson was a clean, self-contained part to begin with. You still have the class. You replaced a component, not the machine.
In the kitchen, swap is the most ordinary thing in the world. You are out of one herb, so you substitute another and the dish still works. A dish stops selling, so you pull it off the menu and slot in a new one, and the menu is still a menu. Swapping works at every altitude: trade a single ingredient, or trade a whole dish; update a single figure, or replace a whole lesson. What makes swapping painless, at any level, is clean boundaries, the same self-containment that made the piece a module in the first place. A piece with tangled edges cannot be pulled without tearing what it was attached to. A clean one lifts right out, and another drops right in.
One Sitting, All Three
Step back and watch the whole kitchen at once, because it shows you that the three moves are not separate disciplines you switch between. They are three things you do with the same parts, often within minutes of each other.
You combine ingredients into a dish. You repackage that dish for tonight’s particular table. Halfway through, you swap an ingredient you have run out of. Build up, re-dress, substitute. Combine, repackage, swap. The dish, the meal, and tomorrow’s version all come out of those three moves applied to a stock of components you keep on hand. The cook is not creating from nothing on each plate. The cook is assembling, re-dressing, and substituting from inventory, which is precisely the shift this whole book is pushing you toward.
And the moves fold into one another; you rarely use just one at a time. You repackage a module that was itself built by combining. Inside that repackaged version you swap a single chunk for a fresher one. A combination gets re-dressed, a re-dressed piece gets a part substituted, a substitution drops a newly combined module into an old arrangement. Most real work is several of these moves at once. That is exactly why it is worth learning each one cleanly first: once you can combine, repackage, and swap on their own, you can run them in any mix without losing track of what you are doing or what you are reusing.
The three moves are really three questions. Combine asks what larger whole these pieces can form. Repackage asks what other form this same module could take. Swap asks what piece can change while the larger whole stays intact.
Where the Book Goes From Here
That is the entire map, and it is small enough to carry everywhere. Combine to build bigger wholes. Repackage to deliver the same module in many forms. Swap to replace a piece without rebuilding the whole. Reuse is what all three make possible, because each one lets the work you already did show up again somewhere new.
The rest of the book takes the three moves one at a time and goes deep. The next part is about combining: how to take your chunks and build them into a module that holds together, does one job, and stands on its own well enough to be reused later. Everything after that, the repackaging and the swapping, depends on having modules worth reusing in the first place. So that is where we turn next, to the move of building up, and to the first real skill of assembly: turning a handful of chunks into a single, clean module.