Why Useful How-To Articles Fail to Resonate

“I know I’m writing useful content, but
why does nothing stick after reading?”

When writing how-to articles,
have you ever felt that sense of unease?

I have.
And for quite a long time, too.

This article is written for:
・People who write how-to articles but get little response
・People who feel that even though their content is useful, readers just end up thinking, “So what?”
・People struggling to break free from an AI-like tone
in their writing.

It was useful, but somehow felt like someone else's problem

A while ago, I went back and read through my past notes.

My honest impression was this:

The content is dense.
What I’m saying isn't wrong.
It has far more information than poorly made AI-generated articles.

But—
I couldn't make it feel personal.

Reading it from a reader's perspective,
“I see, but so what?”
There were many articles that left me with that feeling.

That moment was quite painful.

I talked about the reader's perspective, but I was off the mark

Up until now, I have
“The reader's perspective is important”
“Condescending how-to advice doesn't sell”
I’ve been quite vocal about things like that.

And yet,
when I looked at my own articles objectively,
they were slightly off.

The cause was simple.

The focus of the articles
“Look at how much I’ve thought about this”
“Look at how much I understand”
was leaning too much toward that.

Unconscious self-centeredness.
And the kind I wasn't even aware of.

Why how-to articles are the most difficult

How-to articles are actually the most difficult.

Being condescending doesn't work.
Just sharing personal experiences isn't enough.
And yet, just explaining things leaves the reader behind.

It is not about pulling the reader along, but rather
whether you can stand beside them.

This is the turning point in design.

Does it start with "I also stumbled here"
instead of "This is the correct answer"?

Does it say "When I was in this situation, this is what I thought"
instead of "If you do this, it will go well"?

Know-how is
something to be shared, not taught.
Recently, I have finally come to think so.

The true nature of AI-like writing is not the amount of information

It is often said that
"AI-like articles lack depth of information,"
but that is not necessarily true.

On the contrary,
there is plenty of information, but no warmth.

That is why
after reading it,
you end up thinking, "So, what am I supposed to do?"
and it goes nowhere.

If there is noroom for the reader to project themselvesthen
no matter how correct it is, it will not resonate.

This is the same for both AI and humans.

Things to keep in mind when writing how-to articles from now on

When I write how-to articles in the future,
this is the one point I intend to be strongly conscious of.

"Where is the reader stuck right now?"

Instead of standing as someone who has succeeded,
can I stand in the position of someone
who is just about to take action?

A distance that illuminates the path slightly ahead,
but never pulls away.

How-to articles
are not meant to pull.
I think they need to be designed to walk together.

Articles that are useful but fail to resonate
are not a result of lack of effort or lack of talent.

It is just that the perspective is slightly off.

As someone who writes how-to content,
there was a time when I wrote thinking I "understood."
While talking about the reader's perspective, my own position
was actually half a step too far ahead.

So, from now on,
instead of teaching, stand by their side.
Instead of pulling, move forward together.

A know-how article is
not a place to show off how great you are, but
a piece of writing that descends to the 'position where one can act' for those who are lost.

Now that you have finished reading this article,
where do you feel you are standing?
Your likes and follows are a great source of encouragement.