One Framework, Infinite Posts: How I Went from 3 Posts/Week to a Self-Running Content Machine

Six months ago, I had a problem I couldn't solve by working harder.

I'd been publishing consistently — Monday, Wednesday, Friday — but every Monday felt like starting from zero. Where did the ideas come from? How did I decide what to write about? Why did some weeks produce three solid posts while others left me staring at a blinking cursor for hours?

I was treating content creation like a creativity problem. Write more, think harder, be more inspired. It didn't work.

The real problem wasn't creativity. It was architecture. Once I built a simple framework for where ideas come from and how they multiply, the publishing schedule started running itself.

The Multiplication Problem

Here's what most content creators get wrong: they treat each piece of content as a standalone object.

You need a blog post, so you sit down to write a blog post. You need a newsletter, so you brainstorm topics for a newsletter. You need social posts, so you scroll through feeds looking for things to say.

Every piece is a separate invention. That's exhausting, and it's why most people burn out.

The alternative: build a system where one good idea becomes many pieces of content, automatically.

This isn't about repurposing. Repurposing is an afterthought — you wrote a blog post, now you chop it up for LinkedIn. It feels tacked on and usually produces mediocre versions of the original.

I'm talking about designing content with multiplication in mind from the start.

The Core Idea First

Every piece of content I create starts from a single, tight observation.

Not a topic. Not a theme. An actual sentence I could say out loud to someone in under 30 seconds.

Something like: "Most people build a second brain to capture, but forget to actually use it."

That's a complete thought. It's arguable. It has a point of view. It's the kind of thing that either makes someone stop scrolling or keeps them moving.

The test I use: could I explain this idea in a single message to a friend, without hedging or caveats? If I need three paragraphs to set it up, I don't have a core idea yet. I just have a topic.

Once I have the core idea, everything else becomes an elaboration of it.

The Three-Layer Expansion

Here's the framework that changed how I think about content:

Layer 1: The Core Observation

One tight sentence. This becomes the headline. It becomes the hook for social posts. It becomes the one thing a reader takes away if they forget everything else.

Layer 2: The Evidence Stack

Three supporting pieces that prove the core observation is true:

• A personal story where I was wrong about this
• A specific example from something I read, watched, or heard
• A concrete framework or method that emerged from the observation

This is where most content stops. They write the blog post, pack it with these three points, and call it done.

But the framework only works if you go further.

Layer 3: The Verticals

Once I have Layer 1 and Layer 2, I pull the same material into different formats — each one a complete piece, not a chopped-up version of the original:

• Short-form: The core observation + one sentence why it matters. (Tweet, LinkedIn post, Instagram caption)
• Newsletter: The observation + one of the evidence points, expanded into a story. (500 words, personal voice)
• Blog post: The full expansion — all three evidence points, fully developed, with a framework the reader can actually use. (1,000–1,500 words)
• Short-form video script: The observation framed as a question, answered in 60 seconds. (TikTok, Reels)

Same core idea. Different contracts with the reader. None of them a reduced version of the others.

A Real Example From Last Week

Last Tuesday I was reviewing my daily notes and noticed I'd been complaining about the same thing in three different contexts: my calendar, my task list, and my project management tool.

Three tools, three places, three versions of the same low-level anxiety about where things actually lived.

The core observation wrote itself: "The problem isn't too many tools. It's having a different tool for every version of the same problem."

That's Layer 1.

Layer 2 gave me: a story about the three tools I was juggling (and how I'd convinced myself each one was essential), an example of a client who'd done the same thing, and a simple test to know if your tool stack is solving a real problem or just distributing the chaos.

Layer 3 produced:

• A tweet: "If you have a task app, a notes app, and a calendar — and you still feel scattered — the problem isn't the apps. It's having a different home for every version of the same work."
• A newsletter section (400 words) about how I finally deleted one of my three tools
• This blog post, going deeper on the framework itself
• A 60-second Reels script where I held up three physical notebooks and talked about why I got rid of two

One Tuesday morning observation. Four pieces of content. All different. All true to the original idea.

Why This Works Better Than Planning

The old way: I'd plan a content calendar. Pick four topics for the week. Brainstorm what to say about each one. Write each piece from scratch.

This sounds organized. In practice, it meant I was generating from nothing, four times a week, indefinitely. No wonder Mondays were hard.

The framework approach: I find the observation first. That's the hard part. Once the core idea exists, everything else is extraction, not invention.

Learn more: Julian Shapiro's writing system breakdown covers the fundamentals of idea extraction. For a deeper dive on content repurposing, see Copyblogger's content framework guide.

The creative energy goes into finding the idea. The production energy goes into shaping it for different formats. These are different kinds of work, and separating them makes both easier.

How to Find Core Observations (The Real Skill)

If the framework is the architecture, finding core observations is the craft — and it's the part I get asked about most.

Here's what I've learned: observations live in friction.

When something frustrates you, confuses you, or makes you pause mid-sentence — that's an observation trying to form. The trick is writing it down before it evaporates.

My process:

1. Notice the irritation. Something feels wrong but you can't articulate why. Note it. "Why does X bother me?" Write the question.
2. Argue with yourself. The first version of an observation is usually too soft. Push back. "Actually, the real problem isn't X. It's Y." Keep going until you hit something specific.
3. Kill the abstractions. If your observation uses words like "better," "more effective," or "easier" — go back. What specifically is better? Who specifically benefits? Get concrete.
4. Test it on one person. Can you say this to a friend over coffee and have them react? If they nod politely without changing expression, the observation isn't sharp enough. If they say "wait, that's exactly what happened to me" — you have something.

The One Rule That Makes This Work

Everything above is tactics. Here's the underlying principle:

You can only multiply ideas you've actually thought about.

The framework doesn't generate insights. It extracts value from insights you already have, buried in your notes, your conversations, your Monday morning reviews.

If you're not capturing observations — if you're not noticing the friction, the contradictions, the small things that don't add up — the framework has nothing to work with.

Build the habit of noticing first. The content engine is just what happens when you have material worth processing.

Key Takeaways

1. Content multiplication starts with a single, tight observation — not a topic or a theme
2. Layer your content: core observation → evidence stack → verticals (short-form, newsletter, blog, video)
3. Different formats are different contracts with the reader, not different lengths of the same thing
4. The creative energy goes into finding the idea; the production energy goes into shaping it
5. Your observations come from friction — frustration, confusion, the thing that makes you pause mid-sentence
6. The framework only works if you're actually capturing material worth multiplying

Ready to stop inventing content from scratch? Subscribe to Clear Output — get the framework steps delivered to your inbox every week.