Skip to main content
Published: 2026-09-12 · Last reviewed: 2026-09-12 · Reading edit: 2026-09-12 A workshop contains a useful explanation, but someone who missed it needs a quick checklist. You can reuse the idea while changing the way it is presented. Start with the new reader’s task, keep the evidence and important caveats, and rebuild the piece for that task.

​
Establish the source of truth

Start from a strong, current asset with clear rights and supporting evidence. Identify its central argument, example, limitations, and intended action. If those are unclear, edit the original before multiplying it.

​
Adapt without distorting

  1. Extract the essential idea. Write one sentence explaining the claim and another explaining its conditions. Keep those together throughout adaptation.
  2. Decide what the new version helps someone do. A checklist helps execution; a short video demonstrates movement; a diagram explains relationships; a social post opens a discussion. Format follows the task.
  3. Rebuild the structure. Write for the destination rather than cropping arbitrary passages. Give a short piece enough context to stand alone and an appropriate link to the complete explanation.
  4. Preserve evidence and rights. Carry necessary qualifications, attribution, and customer permissions into the new piece. Approval for a private presentation does not automatically cover a public advertisement.
  5. Review native usability. Check captions, text size, alternative text, reading order, and mobile rendering. A slide that was legible on a projector may be unreadable in a feed.
  6. Keep the versions up to date together. Record derivatives against their canonical source, with owners and update triggers. When a claim changes, find and revise the versions that still repeat it.

​
Worked example

A fictional article explains why a routing system needs a fallback owner. It becomes a one-page checklist for administrators, a short screen recording showing a failed match, and a discussion post asking how teams detect unassigned inquiries. The recording uses test data and includes the product version. The post retains the caveat that fallback ownership must respect territory and availability rules. None of the derivatives claims that adding a fallback alone guarantees faster revenue.

​
Derivative register

​
Review value rather than output count

Check whether the derivative helped its intended task: checklist use, successful setup, meaningful replies, or qualified progression. Ten weak fragments are not an improvement over one clear guide. Retire redundant versions when maintaining them becomes more costly than the access they provide.

​
Try it with your own work

Choose one strong article. Write down what a reader could do with a checklist, diagram, or short recording that is harder to do with the original. Make only that version first.

​
Sources and scope

The example is fictional; any numbers illustrate the method rather than a benchmark. Adapt the worksheet to your own situation. Content distribution · Video Chapter guide · All playbooks
Copyright © 2026 Ivan Xu. All rights reserved. See the copyright and reuse terms. Canonical source: github.com/weilun88313/B2B-Playbook