Studio note · 05 / Content systems
One finished idea can do six different content jobs.
In brief
Keep one source. Change the job.
Repurpose one evidence-backed source by adapting the lesson to the role of each channel. Keep the website Note canonical, write every version natively, and require exact approval before any social, newsletter, or visual item is published.
- Finish and verify one canonical source before creating channel versions.
- Give LinkedIn, Facebook, Instagram, X, newsletter, and YouTube different roles.
- Preserve the claim source, approval state, visual record, date, and public proof for every item.
- Measure each channel by the useful next action it was designed to support.
01
Repurposing begins after the source is finished.
Turning a loose thought into six drafts is not a content system. It is six places for the same uncertainty to spread. The source needs a clear claim, verified facts, a useful structure, and a finish line before the channel work begins.
For this system, a Studio Note is the strongest canonical source when the idea needs a durable explanation. A finished build record, a public video, or a released product can also lead when it carries the evidence. The source is where the complete version lives and where later corrections begin.
02
Canonical does not mean copied everywhere.
The source protects the full argument and the evidence. The channel version earns attention in the language and format people expect there. Copying the same caption across every platform ignores why somebody opened that platform in the first place.
Adapt the idea, not the facts. The central claim, limits, and source record stay stable. The hook, pacing, example, visual, and call to action may change because each version has a different job. If a shorter version cannot preserve an important limit, it should point to the source or not run.
03
LinkedIn teaches the professional lesson.
LinkedIn should contain a complete native lesson, not a teaser that withholds the useful part. Lead with the work problem, show the method or decision, name the limit, and give the reader one move they can use. One link to the canonical Note is enough when deeper context helps.
The professional version should connect the idea to adoption, leadership, production, or workflow ownership. It does not need a résumé paragraph or an invented business result. Authority comes from making the decision clearer and showing the operating logic behind it.
04
Facebook and Instagram carry different kinds of context.
Facebook earns the fuller personal bridge when a real story explains why the idea matters. The audience may know the music, the books, or an earlier chapter of the work. The post can connect that history to the current method without forcing a business pitch into every memory.
Instagram needs visual proof. A process clip, diagram, before-and-after asset, or concise carousel can carry the idea. If the source has nothing worth seeing, the system should skip Instagram instead of putting a paragraph on a portrait and calling it visual content.
05
X isolates the insight. The newsletter installs the habit.
X works when one sentence carries a useful distinction, or when a short thread earns each next post. It does not need the full setup from LinkedIn. The strongest line may be the rule, the exception, or the mistake that changed the process.
The newsletter has a different promise. It enters an inbox, so it should give the reader one workflow, one guardrail, and one action. The canonical Note can hold the full system. The email should make one part easier to use this week.
06
YouTube demonstrates only what can be shown safely.
A short video should reveal a decision, a visible step, or a finished artifact. A longer demonstration belongs only when the screen can be shown without employer data, private material, secrets, staged customer claims, or a fake result. A script cannot manufacture proof the source does not contain.
The video version needs its own opening, on-screen text, visual sequence, and close. Reading the Note into a camera may preserve the words, but it usually wastes the job video can do: let the viewer see the process move.
07
Approval and provenance travel with every version.
Each draft should retain the source moment, claim evidence, channel, exact copy, visual record when present, target time, approval state, and final public proof. If the copy or image changes after approval, that item returns to review. Approval of a text post does not approve a visual package.
This is where automation helps without taking over editorial judgment. It can create the channel-specific files, check required fields, move exact approved items into a queue, and log the public URL. It cannot decide that silence means yes, invent a result, or turn one approval into permission for every derivative.
08
This Note is the bounded example.
The source idea is simple: one finished idea can perform different jobs without becoming six unrelated messages. The canonical version is this Note. A LinkedIn adaptation would teach the professional content-system lesson. Facebook would need a genuine personal bridge. Instagram would use the six-job diagram. X would isolate one rule. The newsletter would give one reusable workflow. YouTube would demonstrate the queue only if the screen contains no private material.
Not every version has to publish. Each one must earn its place, pass its own approval rule, and preserve the source boundary. The useful measure is not how many channels received something. It is whether each published version completed the job it was designed to do without weakening the truth of the original.
Use the source
Continue with the relevant record.
- Read all Studio Notes → The canonical archive for Keith's practical AI and production writing.
- Use The Finish Loop → Define, make, judge, revise, and ship the source before multiplying versions.
- Review the finished-work record → Public evidence for the work behind the content rather than unsupported outcomes.
Put the idea to work