Every chapter in Subtract to Ship follows the same three-part structure. Not because I am rigid. Because the structure works — for teaching, for retention, and for getting the reader to actually do something instead of just nodding along.
The format is called Surface-Test-Ship. Surface the problem. Test the framework. Ship the result. Three phases that move a reader from understanding to action in a single sitting.
I am sharing it here because the format is not just for books. It works for blog posts, workshops, presentations, consulting deliverables, and any situation where you need to teach someone something and have them actually use it.
Why Most Educational Content Fails
Most business content falls into one of two traps:
Trap 1: All theory, no action. The reader learns a concept, nods, bookmarks the article, and never applies it. The content was interesting but not actionable. It created understanding without creating movement.
Trap 2: All tactics, no context. The reader gets a list of steps but does not understand why they matter or when they apply. They follow the steps mechanically and get mediocre results because they cannot adapt when the situation does not match the instructions exactly.
Surface-Test-Ship avoids both traps by integrating theory and action into a single flow. The reader understands the problem (Surface), applies a framework to their own situation (Test), and produces a tangible output (Ship). By the end, they have not just learned something — they have done something.
Phase 1: Surface
The Surface phase makes the problem visible. Not in abstract terms. In the reader’s own experience.
The structure:
1. Open with a specific story or scenario. A person. A place. A moment. Something concrete that the reader can picture and, ideally, recognize from their own life.
From Subtract to Ship: “Maria is a nurse in Vienna. She’s good at her job. Her patients trust her. Her colleagues respect her. She’s been thinking about starting a business for seven years.”
The reader does not need to be a nurse in Vienna. They need to recognize the pattern: someone capable who has been stuck. That recognition is the hook.
2. Name the problem precisely. Not a vague category (“marketing is hard”). A specific, named problem with a clear description of how it shows up.
“Most founders spend 95% of their time building and 5% distributing. They create excellent products that nobody knows about.”
The precision matters. Vague problems produce vague solutions. Specific problems produce specific frameworks.
3. Show why the default approach fails. Explain what most people try and why it does not work. This eliminates the reader’s existing assumptions and creates space for a new framework.
“The instinct is to market harder. Run ads. Post more. Try everything. But spreading effort across every channel means no channel gets enough attention to produce results.”
By the end of the Surface phase, the reader should be thinking: “That is exactly my situation.” If they are not, the Surface was too generic or too abstract.
Phase 2: Test
The Test phase introduces the framework and has the reader apply it to their own situation. Not hypothetically. Actually.
The structure:
1. Present the framework. Clear name. Clear components. Visual if possible. The reader should be able to draw the framework on a napkin from memory.
“The Scored Channel Decision Framework has five criteria: Audience Presence, Content Fit, Cost to Test, Measurability, and Compounding Potential. Score each from 1-5.”
2. Walk through a worked example. Show the framework applied to a real business. Not your business (unless it is relevant) — a business the reader can relate to. Step by step. Nothing skipped.
“For a B2B consulting firm in Vienna, LinkedIn scores 5 on Audience Presence, 4 on Content Fit, 5 on Cost to Test, 4 on Measurability, and 3 on Compounding. Total: 21.”
3. Prompt the reader to apply it. Give them a direct instruction: “Now score your own channels. Use the table below.” Provide a template, a worksheet, or at minimum a clear format they can replicate.
This is where most content creators get nervous. They teach the theory and leave the application to the reader. That is a mistake. The Test phase must include an explicit instruction to apply the framework right now. Not “consider applying this.” Apply it.
In Subtract to Ship, every chapter has a specific exercise embedded in the Test phase. The reader has a pen in their hand (or a cursor on a template) and they are doing the work while they read.
Phase 3: Ship
The Ship phase produces a tangible output and a commitment to the next step.
The structure:
1. Define the output. What should the reader have created by this point? A scored channel list. A one-page customer profile. A documented SOP. Name it specifically.
“You now have a scored list of marketing channels with a clear winner identified.”
2. State the next action. One specific action the reader should take within the next 48 hours. Not “implement this” — that is too vague. Instead: “Post on your top-scored channel three times this week.” The Ship phase is also where the ship it ugly mindset matters most — the reader’s output does not need to be perfect, it needs to exist.
3. Connect to the bigger picture. Show how this output connects to the next framework or the larger system. This creates momentum and makes the reader want to continue.
“Your scored channel list feeds into the Content Engine, which gives you a system for producing content for that channel consistently.”
The Ship phase is non-negotiable. Without it, the reader has learned something but produced nothing. With it, they have a tangible artifact and a clear next step.
Using Surface-Test-Ship for Blog Posts
The format scales down naturally:
Surface (300-500 words): Hook story or scenario. Name the problem. Show why the default fails.
Test (800-1200 words): Present the framework. Walk through an example. Give the reader a template or prompt to apply it.
Ship (200-400 words): State the output. Give the next action. Connect to related content.
This structure produces articles of 1,300-2,100 words — the range that performs best for educational content. Long enough to be substantial. Short enough to finish in one sitting.
Every framework article on this site follows this structure. If you go back and read the subtraction audit guide or the owner dependency score, you will see Surface-Test-Ship in each one. The subtraction audit is a particularly good example because the Surface phase names a problem most founders feel but cannot articulate.
Using Surface-Test-Ship for Workshops
For live events, the format becomes even more powerful because you can enforce the Test and Ship phases in real time.
Surface (15-20 minutes): Tell the story. Name the problem. Get heads nodding in the room.
Test (30-45 minutes): Present the framework, do the worked example, then say: “Now open your laptops. You have 20 minutes to apply this to your business.” Walk the room. Answer questions. Help people through the sticking points.
Ship (10-15 minutes): Ask three people to share their output. Celebrate the work. State the next action. Provide the resource for continued work.
A 60-90 minute workshop following this format produces more lasting behavior change than a 4-hour lecture, because the participants leave with something they built — not just notes they will never revisit.
Using Surface-Test-Ship for Consulting Deliverables
The format works for client-facing documents too:
Surface: Here is your current situation. Here is the specific problem we identified. Here is why your previous approach did not solve it.
Test: Here is the framework we recommend. Here is how it applies to your specific business. Here is the analysis with your data.
Ship: Here is what we built for you. Here is the specific next action. Here is how this connects to the next phase of the engagement.
Clients who receive deliverables in this format report higher satisfaction and higher implementation rates. The format respects their intelligence (Surface), demonstrates rigor (Test), and produces actionable results (Ship).
Why the Order Cannot Change
Surface must come before Test. If you present the framework before the reader understands the problem, they have no motivation to learn it. “Here is how to score marketing channels” means nothing to someone who has not yet recognized that their multi-channel approach is failing.
Test must come before Ship. If you ask for a next action before the reader has applied the framework, they do not have the context or the artifact to act on. “Post three times this week” only makes sense after they have scored their channels and identified the winner.
Surface creates the motivation. Test creates the artifact. Ship creates the action. Each phase depends on the one before it.
Takeaways
Surface-Test-Ship is a three-phase structure for any educational content: surface the problem, test the framework by applying it, and ship a tangible result with a clear next action.
Use it for blog posts, workshops, presentations, and consulting deliverables. The format works because it integrates theory and action — the reader or participant does not just understand something new, they have produced something new.
Start your next piece of content with a story that makes the problem visible. Introduce a framework the reader can apply immediately. End with a specific output and a specific next step.
The content that changes behavior is not the content that teaches the most. It is the content that gets the reader to act before they finish reading. Surface-Test-Ship is built for exactly that.
