Back to Blog
content creation workflow
10 min read

Content Creation Workflow: My 90-Day Distribution Experiment

You publish a thoughtful Substack article, feel good about the work, then check the dashboard the next day and find 3 new subscribers and a handful of likes...

By Ian Kiprono

You publish a thoughtful Substack article, feel good about the work, then check the dashboard the next day and find 3 new subscribers and a handful of likes. The article wasn't necessarily weak. It appeared once, in one place, and disappeared beneath everything published after it. You're left wondering whether the answer is writing more, promoting harder, or accepting that every strong idea gets one brief chance to be noticed.

I tested that problem for 90 days. Before the experiment, I published one piece per week on one platform and averaged 50 views. During the test, I used one long-form article as an anchor, adapted it for Substack, Medium, LinkedIn, and X, and tracked views, engagement, subscriber conversion, time on page, and the work required at each stage. The biggest lesson was simple: a content creation workflow isn't just a way to write faster. It's a distribution system designed to help good ideas keep working.

The Content Hamster Wheel That Nearly Made Me Quit

A finished article could take an afternoon to produce and still be nearly invisible by the next morning.

I researched, outlined, drafted, and edited, then published on Substack and shared the link once. The next deadline pushed the piece aside. A day later, the dashboard showed a few likes and 3 new subscribers, while attention had already shifted to newer posts. My response was to create more, even though each idea had been used only once.

That pattern pointed me toward the wrong solution. I kept questioning my hooks, opinions, and topics. Those elements matter, but stronger writing cannot compensate for an operating system that gives an article no route beyond its first publication.

Before the experiment, the process was simple:

  • Choose a topic: Usually based on whatever felt urgent that week.
  • Write one article: Publish it on one platform.
  • Share once: Post a link, then return to drafting.
  • Move on: Start the next piece without reviewing what the previous one taught me.

The baseline was one weekly publication and 50 average views. I treated those figures as a personal starting point, not a universal benchmark. The test was whether a repeatable pipeline could make each idea more productive without turning every platform into a duplicate feed.

The problem wasn't a lack of ideas. It was a lack of planned reuse.

Why documentation changed the experiment

A widely cited benchmark says only 40% of B2B marketers had a documented content strategy in 2023. That finding connects to the practical problem I was trying to solve: a content creation workflow needs repeatable planning, drafting, review, distribution, and measurement steps. The benchmark and workflow definition are covered in this guide to content creation workflow.

I also reviewed how creators handle repetitive research and drafting tasks. The student AI assistance blog offers a useful perspective on applying AI while keeping human judgment in the process.

The system I tested started with one anchor article each week. Each article then became platform-specific material with a defined job. Substack carried the complete argument. A Note isolated one idea. LinkedIn framed the lesson for a professional audience. An X thread developed the reasoning conversationally. Medium gave the long-form concept another reading environment.

I recorded each handoff with a batching approach. See what batching is. Grouping writing, formatting, scheduling, and analytics reduced context switching and made weak points easier to inspect. The goal was not to publish everywhere indiscriminately. It was to decide before drafting how one idea could travel while keeping its meaning intact.

Planning Ideas That Actually Deserve Your Time

A distribution-first workflow starts before the draft. The question is not simply, “What should I write?” It is, “Which reader problem can produce one strong anchor piece and several useful platform-specific versions?”

I began with a content audit instead of a blank page. I reviewed my last 10 posts, ranked the top 3 by engagement rate, and examined the responses behind those results. Views showed reach, but replies, saves, clicks, and follow-up questions showed whether an idea deserved further development. I also looked for trending topics in my niche to check that proven angles still matched current demand.

A four-step infographic illustrating a content creation workflow involving auditing, brainstorming, prioritizing ideas, and scheduling content.

A practical idea scoring method

For each of the top 3 posts, I developed 4 to 5 follow-up angles. One could explain the process in greater detail. Another could challenge the assumption behind the original post. A third could turn a reader question into a practical lesson, while a fourth could present the same insight for a different platform.

Each idea received a quick score against three criteria:

  • Audience pain: Do readers already recognize the problem?
  • Distribution value: Can the idea support an anchor article, Note, LinkedIn post, or thread without becoming repetitive?
  • Production effort: Do I already have the evidence, examples, or experience needed to create it well?

That filter reduced ideation time from 3 hours to 45 minutes per piece during my 90-day experiment. These are observed workflow figures, not a universal benchmark. The improvement came from expanding subjects with demonstrated interest instead of inventing a new direction every week.

My planning sheet included the anchor topic, primary reader problem, central claim, supporting evidence, possible derivatives, target platforms, and publication status. I also used seasonal planning selectively. Teams that publish around events or recurring industry moments can browse the 2026 marketing calendar for timely prompts, then reject any date that does not fit the audience's actual concerns.

A useful idea must survive platform changes. I wrote down the job each version would perform before approving the topic. The anchor article carried the full argument. A Note isolated one practical observation. A LinkedIn post connected the lesson to professional work, while an X thread developed the reasoning in shorter steps. This test exposed weak ideas early. If an angle could not produce distinct value in at least two formats, it usually did not deserve a full production slot.

I kept the calendar intentionally small. One anchor piece entered production, and the remaining angles stayed in a queue until performance or audience feedback justified them. That constraint protected quality and gave each idea room to earn wider distribution.

Drafting and Editing Without Endless Revisions

A draft becomes expensive when nobody knows what “finished” means.

During the experiment, I used a time-boxed production sequence for each anchor article. I allowed 90 minutes for a 1,500-word draft and 30 minutes for editing. The purpose wasn't to rush the thinking. It was to prevent polishing from expanding into an undefined second writing project.

The anchor article structure

I outlined the article around one reader problem, one primary argument, and a small number of supporting sections. Each section needed to contain an insight that could stand alone later. That meant writing clear claims, concrete examples, and sentences that could survive outside the surrounding paragraphs.

A useful anchor structure looked like this:

  1. Problem: Describe the situation readers face now.
  2. Diagnosis: Explain why the common approach fails.
  3. Process: Show the repeatable method.
  4. Evidence: Add a result, observation, or source.
  5. Action: Give the reader a next step.

This structure helped me extract derivatives later because the article already contained natural units. A section could become a Substack Note. A contrast could become a LinkedIn post. A sequence of claims could become an X thread.

The editing pass had three checkpoints. First, I checked factual accuracy and removed claims that the draft couldn't support. Second, I checked whether each paragraph moved the argument forward. Third, I read the piece aloud to catch stiffness, repetition, and sentences that sounded unlike my normal voice.

If you've completed more than two revision passes, inspect the brief before you keep editing. The draft may be carrying a planning problem.

A multi-channel workflow guide recommends keeping only 20% to 30% of usual writing time for human polish after generating a draft package for different formats. The content-production workflow example provides that efficiency target, but the human review remains essential for voice, accuracy, context, and platform fit.

AI can help create an initial outline, identify repeated ideas, or propose variations. It shouldn't decide whether a claim is true, whether a point belongs to your argument, or whether a derivative still sounds like you. I found automated SEO writing tips useful as a prompt for process questions, but optimization never replaced editorial judgment.

The hard stop mattered. Once the article was accurate, readable, and aligned with its brief, I moved it to distribution. A perfect draft that never reaches readers has less practical value than a strong draft with a clear path to publication.

Repurposing One Piece Into Platform-Specific Content

Repurposing works when you preserve the idea and change the delivery.

In my test, one 1,500-word article became 8 pieces of platform-specific content in under 2 hours total. The count included 3 to 4 Substack Notes, 1 LinkedIn post, and 1 X thread, alongside the anchor asset and its additional long-form distribution. The point wasn't to paste the same paragraph into every channel. Each format answered a different reading behavior.

A diagram illustrating how a single long-form article can be repurposed into over twenty social media posts.

How I adapted the same argument

For Substack Notes, I extracted individual observations that could make sense without the full article. Each Note focused on one point, such as the cost of publishing an idea once or the signal that repeated editing reveals a weak brief.

The LinkedIn version emphasized the professional lesson and made the operational consequence explicit. It needed a clear opening and a useful conclusion, not a transcript of the article.

The X thread broke the argument into a sequence. The opening created a reason to continue, each post advanced one step, and the final post pointed toward the complete article. The thread wasn't shorter merely for the sake of length. It was sequential because the platform supports serial reading.

The adaptation process followed four checks:

  • Extract: Pull out claims, examples, objections, and practical steps.
  • Reframe: Choose the audience concern most relevant to the destination platform.
  • Rewrite: Change the rhythm, length, opening, and call to action.
  • Verify: Compare the derivative with the anchor to protect accuracy and voice.

A 2025 industry analysis reports that repurposing can save 60% to 80% of the time required to create content from scratch and that systematic repurposing can expand reach by about 300% by distributing one idea across audiences and formats. Those figures come from this analysis of content repurposing. They're directional benchmarks, not a guarantee that every repurposed asset will perform equally well.

The approach that failed was mechanical duplication. Copying the article introduction into a Note produced something technically accurate but socially lifeless. The approach that worked was extracting the underlying insight, then rebuilding it for the reader's context.

A detailed content repurposing workflow can help formalize those handoffs. A spreadsheet works too. The essential requirement is that every derivative has a job, a platform, and a review check.

Scheduling and Automating Cross-Platform Distribution

Publishing manually creates a hidden tax. You don't just write the post. You reopen the draft, format it, find the link, choose a time, publish it, and remember what should happen next. Repeating that sequence across Substack, Medium, LinkedIn, and X makes distribution feel like another full-time task.

I used a staggered release pattern:

  • Day 1: Publish the anchor article on Substack.
  • Day 2: Schedule the first Substack Note.
  • Day 3: Schedule another Note with a different insight.
  • Day 4: Publish the LinkedIn adaptation.
  • Day 5: Publish the X thread.
  • Later review: Decide whether the idea earned another angle.

The exact timing should follow your audience activity and the purpose of each post. I avoided releasing every derivative at once because simultaneous cross-posting made the feed feel repetitive and gave readers no reason to encounter the idea again in a new form.

Scheduling Substack Notes

Substack supports native scheduling for Notes on web, iOS, and Android. Creators can select a publishing time in their local timezone, and scheduled Notes remain in Drafts so they can be edited before publication, as explained in Substack's scheduling announcement.

The practical sequence is straightforward:

  1. Open Create and choose Note.
  2. Select the calendar icon on the web, or the scheduling control in the app.
  3. Choose the date and time.
  4. Confirm the schedule.
  5. Reopen the saved draft if the wording needs a final check.

Screenshot from https://www.narrareach.com

Native scheduling is enough for a focused Substack routine. A unified workspace becomes useful when the same anchor needs to move to several platforms, particularly when you're managing multiple drafts or a larger editorial calendar. Narrareach offers scheduling and cross-platform distribution for Substack, Medium, LinkedIn, and X, so creators can prepare those outputs from one place through its content distribution platform.

Automation should handle repetitive movement, not final judgment. I automated formatting and scheduling where possible, but manually checked hooks, links, claims, and tone before anything went live. That balance preserved efficiency without allowing a generic version to represent the original work.

Tracking Performance and Iterating What Works

The first useful analytics review happens after publication, but the important decision is what you do with the information.

I reviewed each asset after 7 days, comparing subscriber conversion rate, engagement rate, time on page, and the quality of responses. Views helped establish distribution, but they didn't tell me whether an idea deserved another version. A smaller post with strong reader intent could matter more than a larger post that attracted passive attention.

A practical review loop

I recorded each asset in a simple table with its platform, format, publication date, topic, views, engagement, clicks, subscriber movement, and notes from reader responses. I also tracked operational friction, including delayed approvals, broken links, or edits made after scheduling. That second layer showed whether the workflow itself was improving.

After each review, I made one of three decisions:

  • Expand: Create new angles when readers engaged or asked follow-up questions.
  • Maintain: Keep the topic in rotation when it performed adequately but lacked a clear signal.
  • Stop: End cross-posting when later versions produced weak response or felt repetitive.

The most useful pattern was doubling down on a winning subject rather than distributing every article equally. If one piece generated meaningful discussion, I created 2 to 3 new angles for the following week. Those angles could address an objection, show an implementation detail, or explain the same idea for a different audience.

An infographic titled Performance and Iteration showing data metrics, content strategies, and actionable improvement steps for marketers.

AI adds another reason to keep governance in the measurement loop. Digiday reported that 80% of surveyed creators used AI in their workflow, with 38.7% using it throughout the entire workflow and 44.2% using it in parts of the process, according to coverage of AI content workflows. That adoption makes voice consistency, factual review, attribution, and accountability operational requirements rather than optional polish.

The feedback loop should answer two questions: what deserves more distribution, and what should stop consuming your time? Cross-platform analytics guidance can support that comparison, but platform-native dashboards and a well-maintained spreadsheet can also give you a workable system.

A distribution-first content creation workflow turns publishing into a learning cycle. You create an anchor, adapt it thoughtfully, schedule it where readers already spend time, measure the response, and let the next plan reflect what the audience showed you.


Narrareach helps writers turn one long-form idea into scheduled Substack Notes, Medium articles, LinkedIn posts, and X content while tracking which versions drive engagement and subscribers. If you're ready to replace manual cross-posting with a repeatable distribution workflow, visit Narrareach and start free, or follow the process with native schedulers and return when you need one workspace for the whole pipeline.

Related Posts

Ready to scale your content?

Write once, publish everywhere with Narrareach