Content

You can't work for Twitter, Elon Musk is different
You can't work for Twitter, Elon Musk is different
You can't work for Twitter, Elon Musk is different

Turn Your Work Documents Into Endless Content

Image

Florian (Flo) Pariset

Founder of Mind the Flo

You don’t have a content problem.

You have a translation problem.

Every week you ship decisions, trade-offs, and hard-earned clarity inside specs, tickets, PRDs, meeting notes, and user stories. Then you open LinkedIn or your newsletter draft and feel like you’re starting from zero again.

That’s backwards.

Your best content is already written (just not for the internet)

If you’re building something real, your team is producing “content” all day long. It’s just trapped in work formats.

A spec is a narrative. It has a before, an after, and the constraints in the middle.

A ticket is a micro-story. Something was broken, you investigated, you fixed it, you learned.

A user story is literally a story: a person, a job-to-be-done, a struggle, and an outcome.

That’s everything people want to read. You just need to reframe it.

Why “creating content from scratch” always loses

When you start with a blank page, you force yourself to do three expensive things at once.

First you need a topic. Then you need a point of view. Then you need proof.

But your work docs already contain all three.

They’re full of real constraints, real decisions, real mistakes, real customer language, real numbers, and real trade-offs. That’s why they’re valuable. And that’s why they’re infinitely easier to turn into content than random inspiration.

The workflow: turn one document into ten pieces of content

This is the simplest way I’ve found to make content sustainable while building a product.

Step 1: Pick a source document with tension

Don’t start from “what’s new.” Start from “what changed our mind?”

Great source docs have one of these:

A decision you debated.

A trade-off you accepted.

A bug that taught you something.

A feature request you said no to.

A metric that surprised you.

Step 2: Extract three angles

From a single doc, you can usually pull three strong angles.

The lesson. What you learned.

The process. How you reached the decision.

The principle. What you’ll do differently next time.

Once you have those, distribution becomes easy.

Step 3: Map angles to formats

One angle becomes a short post.

Two angles become a thread.

Three angles become a newsletter section.

All three together become a blog post.

That’s the “endless content” part: you’re not inventing, you’re packaging.

Concrete examples (so you can steal this)

Let’s make it painfully practical.

From a product spec

Take a spec titled “Onboarding v2.”

Your LinkedIn post is: the one onboarding assumption you were wrong about.

Your newsletter is: the three experiments you ran and what they proved.

Your blog post is: the full narrative, including the trade-offs you accepted and what you cut.

From a bug ticket

Take a ticket titled “Sync lag on mobile.”

Your short post is: how a tiny bug revealed a bigger architecture issue.

Your thread is: the debugging path and the dead ends.

Your blog post is: what you changed in the system to prevent the class of issue.

From user stories

Take five user stories that all point to the same friction.

Your short post is: the one sentence your users keep repeating.

Your newsletter is: a mini “what we heard / what we built / what’s next.”

Your blog post is: the deeper product philosophy behind the change.

The real leverage: you speak once, your workspace moves

This is the part that still feels like cheating.

When your work already lives in Notion, you can treat it like a content database. Specs, tickets, and user stories become source material you can query and reuse.

And if you don’t want to do the repackaging manually every time, this is exactly the kind of workflow I’m building Notis for: take what’s already in your workspace and turn it into publishable drafts without the blank-page tax.

If you’re building, you’re already creating content

The game isn’t “how do I post more?”

It’s “how do I stop letting my best thinking die in internal docs?”

Start small. Pick one spec or one ticket this week. Extract one lesson. Publish one post.

Then do it again next week.

That’s how you turn work into distribution without adding a second job to your life.

Huseyin Emanet

Flo is the founder of Mind the Flo, an Agentic Studio specialized into messaging and voice agents.

Break Free From Busywork

Delegate your busywork to your AI intern and get back to what matters: building your company.

Break Free From Busywork

Delegate your busywork to your AI intern and get back to what matters: building your company.

Break Free From Busywork

Delegate your busywork to your AI intern and get back to what matters: building your company.