I spent last week reading a 1983 advertising book. I am not treating its figures as a current study of feeds. What I kept was a practical mechanism: state the benefit, make the claim specific, do the homework, and let the reader judge.
When I say most posts fail this test, I mean that as an editorial judgment from the drafts I read, not a measured claim about every feed.
Cleverness can earn a reaction. It does not tell a reader why to stay.
The check I keep returning to is simple: after the first two lines, can someone say what they will get from the piece?
If the answer is no, the writing may still be stylish. It may even be true. But the reader has not been given a reason to continue.
The promise test
A promise is a concrete payoff stated early.
“This will show you the check I run before publishing.”
“By the end, you will know how to tell a real bottleneck from an imagined one.”
That is different from a title or a clever hook. A title names the subject. A hook creates movement. A promise tells the reader what the movement is for.
I have learned to look for the promise before I edit anything else. What is this piece helping the reader see, decide, build, or avoid? If I cannot answer in one sentence, the draft is usually trying to carry too much.
This does not mean every opening needs to sound like a sales page. It means the reader should not have to reverse-engineer the value of the next five minutes.
A personal story can make a promise. So can a question, a warning, a practical test, or a surprising distinction. The form can change. The reader still needs a clear reason to proceed.
Specifics do the convincing
Generalities make writing feel finished before they make it useful.
“Build a better system.”
“Write high-quality content.”
“Use the right tools.”
None of those sentences gives me much to work with. They point toward an idea without showing its shape.
Specifics do more. They give the reader something to picture, test, or disagree with.
In a cloud tutorial, “this is easy” is not much help. A command, its output, the permission it needs, and the failure you might see are useful. In a writing guide, “be more clear” is weaker than showing the vague sentence, the revised sentence, and the decision that made the revision better.
I try to replace broad praise with evidence from the work itself. What happened? What did I measure? What changed? What did not change?
There is one boundary I do not want to cross: never invent a number to make a paragraph look rigorous. False precision is still false. If I do not have a measurement, I can describe the observation plainly or leave the number out.
Plain words lower the toll
Writing becomes harder to read when the sentence is asking the reader to decode the writer before reaching the idea.
I notice this most when I am trying to sound more authoritative than I feel. A complicated word gives the sentence a temporary shine. It does not necessarily give the reader a clearer picture.
The fix is usually ordinary language.
Say “old-fashioned” if that is what you mean. Say “the service could not reach the database” instead of hiding the failure behind a phrase like “an inter-service connectivity degradation event.” Say “I do not know yet” when the evidence stops there.
Plain words are not a concession to an unsophisticated reader. They are a way of respecting the reader’s limited time and making the claim easier to inspect.
Short paragraphs help for the same reason. They make the next idea visible. They do not guarantee that the idea is good, but they remove one unnecessary obstacle.
Homework gives the writing a surface to stand on
The strongest detail in a piece usually comes from contact with the subject.
For me, that contact might be a lab, a failed command, a study note, a conversation, a draft that did not work, or a decision I had to make myself. Those experiences do not automatically produce good writing. They give me material that is more useful than a summary assembled from the surface.
A technical post about permissions is stronger when I can show what changed between users and where the access stopped. A piece about study is stronger when I can describe the session that looked productive but left me unable to explain the concept later. A writing post is stronger when I show the sentence I cut and why it was weakening the point.
The work is the homework.
That is also why I am suspicious of ideas that arrive already polished. If I have not tested the claim against anything, I may be repeating a phrase rather than reporting an observation.
The question I ask is not, “Can I make this sound interesting?”
It is, “What have I actually looked at closely enough to say?”
The opening has a job
The first line does not need to be loud. It needs to make the next line worth reading.
A story can do that. A concrete problem can do it. A contradiction can do it. A specific result can do it.
What usually fails is an opening that gestures toward importance without giving the reader anything to hold.
“Everything is changing.”
“We are living through an unprecedented time.”
“Most people are doing this wrong.”
These may introduce a real argument, but by themselves they ask the reader to supply the subject, the stakes, and the reason to care.
I would rather start closer to the actual thing.
“I kept adding study time, but I was still relearning the same concepts.”
“I bought the powerful setup before I had a workflow that could use it.”
“I knew what each AWS service did, then froze when I had to combine them.”
Those lines do not promise a universal answer. They promise a specific investigation. That is enough to begin.
Length is not the decision
I used to treat shortness as a virtue on its own. Now I think the better question is whether each paragraph earns its place.
A short piece can be empty. A long piece can be generous. Neither length proves value.
If the opening is unclear, more paragraphs only make the reader spend longer discovering that the piece has no direction. If the opening is clear and the details keep answering the reader’s question, a longer piece may be exactly right.
My editing question is simple: does this paragraph move the promise forward?
If it adds evidence, a distinction, an example, or a necessary qualification, it stays. If it repeats the mood of the paragraph before it, I cut it, even when the sentence is good.
Good sentences still have to serve the piece.
Do not brag when you can show
Claims about being the best are easy to write and hard to trust.
The alternative is not false modesty. It is demonstration.
Instead of saying a workflow is reliable, show the check that catches failure. Instead of saying a project proves skill, show the problem, the trade-off, and the evidence that the result worked. Instead of calling an idea transformative, explain what decision it changed.
This is the standard I want for my own writing. Let the reader decide what the work is worth after seeing enough of the work to judge it.
One clear next step
A piece can teach, persuade, or change how someone sees a problem. It can also ask for an action.
If I want the reader to try the command, run the audit, reply, subscribe, or apply the test to their own draft, I should say so plainly.
One useful next step is usually enough. Five competing calls to action turn the ending into another decision the reader has to make.
Sometimes the right ending is no call to action at all. That is still a decision. What matters is that the absence is intentional.
How I use the test now
Before I send a draft out, I run four checks:
Can I state the reader’s concrete payoff in one sentence?
Have I replaced broad claims with details someone could inspect?
What is my evidence of contact with the subject?
What should the reader do next, if anything?
Then I read the first paragraph by itself.
If it sounds clever but does not tell me where the piece is going, I rewrite it. If the promise is larger than the evidence, I narrow the promise. If the piece depends on a number I cannot verify, I remove the number. If the ending introduces a new idea instead of completing the opening one, I keep editing.
The promise test is not a formula for making every piece sound the same. It is a way to stop hiding uncertainty behind style.
Say what the reader will get. Use details you can stand behind. Do the work before claiming the lesson. Write plainly enough that the idea can be checked.
Cleverness may make a line noticeable. A real promise gives the piece somewhere to go.