· 6 minute read

Why Helpful Content Gets Forgotten

Solving a problem does not always make you memorable. An argument gives people something else to remember.

I'm grateful for the dad-like figure who posted a two-minute YouTube tutorial on how to install my washing machine. Clear instructions, perfect framing, solved my problem in one take.

I could not tell you who he was if my life depended on it.

That tutorial was useful to me in the moment, but I did not remember its creator. Other useful content has stayed with me. Solving a problem and being remembered are related, but one does not guarantee the other.

The logic of comprehensive content

Before I argue against it, I want to acknowledge why comprehensive content became the default. The logic made sense.

In SEO, an ultimate guide on a loaded topic could rank for hundreds of keywords. Sometimes thousands. One page pulling organic traffic for "how to start a blog," "blogging for beginners," "starting a blog," and dozens of related queries. The comprehensive approach wasn't just helpful. It was a traffic engine.

The same logic applied to video. An hour-long YouTube tutorial on how to build a WordPress website gave viewers a course-like experience for free. Massive value, massive watch time, massive reach. Creators built entire audiences on being the person who held your hand through the whole process.

This worked. For years, this was the proven playbook: address the search intent comprehensively, cover every angle, leave no gaps. If someone landed on your page with a question, they should leave with an answer.

I'm not dismissing this approach. It produced genuinely valuable content. It also trained us to optimize for coverage rather than memorability. People now have more ways to get an answer.

The AI shift

AI can adapt an explanation to the question you're asking and the details you provide.

Last month, I was setting up the Apple Developer Program. Configuring StoreKit, navigating Xcode, filling out forms I'd never seen before. A few years ago, I would have Googled each step, found articles or YouTube walkthroughs, and pieced together what applied to my situation.

Instead, I asked Claude. It walked me through step by step, adapting to my specific context. When I hit an error, it adjusted. When my setup differed from the standard flow, it accounted for that. No scrubbing through a 15-minute video to find the one part that mattered. No skimming five articles to piece together an answer. Just direct guidance for exactly what I was trying to do.

AI still gets things wrong. But a useful, personalized answer can change where people start looking for help.

Static Tutorial
One path for everyone
Scrub to find what applies to you
AI Guidance
Adapts to your situation
Responds to your specific context
The personalization gap

That's the challenge for a fixed tutorial: an AI conversation can respond to the particular problem you're having.

For that washing machine problem, I wanted to see a real person doing the job. A recorded demonstration gave me something a text explanation did not. That is a reason to choose a format carefully, not a claim that any format is permanently protected from AI.

What still sticks

Watch a TED talk that stays with you. Read a non-fiction book you still reference years later. Listen to a stand-up set that changes how you see something familiar.

They all share a structure: one central idea, with everything else in service of it.

Simon Sinek's talk isn't "about leadership." It's people don't buy what you do, they buy why you do it. Brené Brown's isn't "about emotions." It's vulnerability is the birthplace of connection. You absorb the thesis in a sentence. The supporting points reinforce it, illustrate it, make it stick.

What interests me is a perspective drawn from a person's experience: someone did the work and noticed something worth sharing. AI can help express or challenge the argument, but I want the underlying experience and evidence to be real.

Comprehensive content serves the immediate intent. Thesis-driven content shifts how you think. That can give you a reason to remember the person who made it.

Topic vs. thesis

A topic is what the content is about. A thesis is what the content argues.

"How to train for a marathon" is a topic. You could write a dozen pieces under that heading, all covering the same ground, none memorable.

"A marathon is a mental practice disguised as a physical one" is a thesis. Now there's an argument. Every training tip becomes evidence for the mental game. The reader absorbs a framework, not just a schedule.

Topic
Marathon training
Thesis
Running a marathon is mental, not physical
Topic
Meal prep for the week
Thesis
Meal prep removes decisions, not just cooking
Topic
Home organization
Thesis
Clutter is deferred decisions made visible
Topic
Photography basics
Thesis
Great photos come from patience, not gear
Topic
Personal budgeting
Thesis
Budgets fail when they fight your nature
Topic
Starting a garden
Thesis
The real yield is patience, not vegetables
Topic states subject. Thesis makes argument.

The thesis doesn't narrow the content. You can still be comprehensive. Now each section supports the same argument. Something the reader can hold onto when the details fade.

Finding the thesis

This is the hard part. Especially for established subjects where the conventional framing feels locked in.

What's the misconception? Most people think X, but actually Y. The thesis becomes the correction. "Most people think marathon training is about building endurance. Actually, it's about building mental tolerance for discomfort."

What's the transformation? If the reader fully absorbed this, what would change? Name that shift. "You'll stop organizing your closet and start making the decisions you've been avoiding."

What would you argue at dinner? If someone asked your opinion on this topic and you had to take a position, what would it be? The opinion you'd defend may be a good starting point.

What connects the tips? If you have eight tactics, ask: what do they share? What principle are they all evidence for? That principle might be the thesis.

When you don't need a thesis

Not all content needs to be memorable. Sometimes you just need to install a washing machine.

Just-in-time utility is a legitimate strategy. FAQ-style content that solves problems quickly. Reference material people bookmark and return to. Tutorials that walk through steps without editorializing.

This content doesn't need a thesis. It needs clarity, accuracy, and speed.

The mistake is assuming that solving a problem will automatically make someone remember your point of view. Useful reference material can build trust and bring people back. An argument gives them another reason to remember and share the work.

The bet

My bet for where content needs to go: utility wrapped in argument.

You can still be comprehensive. You can still serve the search intent. The piece needs a through-line. A central claim that gives the reader something to hold onto when the tips blur together.

A practical tutorial does not need a grand thesis. For the work I want to make, though, a clear argument gives people an idea they can explain to someone else.

In a world where AI can personalize utility on demand, the pieces that stand out are the ones that argued something worth remembering.

This is a working document. The thinking continues to evolve.