He Thought the Reader Would Read It. They Won’t

A few weeks ago, I worked on a document for a client.

It wasn’t a sales pitch.
It wasn’t a proposal.
It definitely wasn’t a contract.

It was an early-stage document, designed to be read by senior decision-makers and, at best, trigger a follow-up conversation.

The client had already done a lot of thinking. Pages of it. Smart, thoughtful, well-articulated content that explained their model, their philosophy, and their experience in depth.

On paper, it should have worked.

In reality, it would have been skimmed.

The assumption “this is important, so they’ll read it properly” is usually wrong

The unspoken assumption was simple:

“This is important, so they’ll read it properly.”

They wouldn’t.

Not because the audience wasn’t capable.
Not because they weren’t interested.
But because interest doesn’t automatically buy attention.

Senior readers don’t start by reading.
They start by judging whether reading is worth the effort.

That judgement happens fast.

When there’s no presenter, adding too much text makes the document less readable

Because there was no presenter, the instinct was to add more text, which of course, is necessary as the text takes the role of the presenter. It is not a 1-for-1 replacement however and the amount of text you use is critical, and it is necessary to get the right amount.

Explain more.
Clarify more.
Make sure nothing was missed.

That instinct is understandable — and usually wrong.

Removing the presenter doesn’t turn a deck into an essay. It turns it into a filter.

The reader wasn’t deciding “yes or no” — they were deciding “continue or stop”

This document wasn’t meant to close a deal.

It was meant to answer one question:

“Is this worth a conversation?”

That’s a very different reading behaviour.

When the stakes are preliminary, readers aren’t auditing claims. They’re pattern-matching for judgement, credibility, and alignment.

Once they see those signals, they move on.

More explanation doesn’t help. It actually gets in the way.

The structure was asking the reader to work before they knew why

As we reworked the document, something became obvious.

Even though the reader was motivated, intelligent, and senior, there was too much text for the job the document needed to do.

Not because the content was bad.
Because the structure was asking the reader to work before they knew why.

So we did something counterintuitive.

We moved the argument into the slide titles.

Not labels.
Not topics.
Full sentences that told the story on their own.

If someone read only the headings, they would still understand:

• what the problem was
• why it mattered
• and what kind of thinking sat behind the solution

The body text became what it should have been all along:
optional proof, not mandatory reading.

Readers dive into detail only when they need evidence, clarity, or reassurance

Here’s something writers often miss.

Readers don’t read more when they’re interested.
They read more when they’re uncertain.

They drop into paragraphs when:

• a claim isn’t obvious
• they need evidence to support belief
• or the risk justifies scrutiny

If a statement makes sense immediately, aligns with experience, and comes from a credible source, they skip the explanation.

That’s not laziness.
That’s efficiency.

And in early-stage documents, readers don’t expect you to argue against yourself. Once belief forms, they don’t go looking for counter-evidence.

The “bring experience earlier” feedback was really a request for earlier credibility

At one point, the client pushed back slightly. Not on the logic — on the placement.

They wanted their experience to appear earlier, so the thinking didn’t feel abstract before the “who” was clear.

That wasn’t a request for more content.
It was a request for earlier credibility.

Once that was addressed, everything else flowed.

And crucially, we didn’t add pages.
We reweighted attention.

Most business writing fails because the writer assumes the reader shares their level of investment.

They don’t. Especially at the start of a relationship.

At that point, the document’s job isn’t to explain everything. If an investment by the reader is significant, the investment won’t happen from the initial document, it wil happen after further communication so teh prupose at that point isnt to be detailed. I cant overIt’s to make the next step feel obvious and safe.

That means:

• less explanation up front
• clearer judgement signals
• and a structure that survives skimming

Stories get read because they lower the cost of understanding. They work!

I cant overemphasise teh role of story. Data dumps when one page is largely unrelated to the next except it is additional data doesn’t engage people, it quickly turns them off, not engage them. In controlled experiments, it’s been found that readers are up to 22 times more likely to remember facts when wrapped in a story. Put simply,

Story-based formats significantly outperform pure exposition in comprehension and retention.

A story makes meaning obvious early, so the reader doesn’t have to work to decide whether it’s worth continuing.

That’s why, in this case, the document worked only once the story was visible without effort.

Not buried in paragraphs.
Not hidden in appendices.
Right there in the headings.

The most professional move is often removing text that isn’t needed yet

The better the thinking, the harder it is to let go of it.

But writing isn’t about preserving effort.
It’s about respecting attention.

Jobs once said:

“It’s not the consumers’s job to know what they want.”

Translate that into writing and you get:

It’s not the reader’s job to find the meaning.
It’s the writer’s job to surface it.

That’s judgement.