Why people don't read — and what to do about it
The average web reader scans 20–28% of the words on a page (Nielsen Norman Group). They don't read top-to-bottom — they skim headings, bold words, bullets, and images looking for what matters.
So: give them something to skim. Every technique below is a way to pull meaning out of a paragraph and make it land faster.
Chunking — break the wall
The single highest-impact move is breaking long paragraphs into 1–3 sentence chunks. It turns a scary block into a scannable list of ideas.
Show 4–6 strong case studies. Not everything you've ever made.
Each case study needs four things: the problem, your process, the result, and your role.
Be specific about what YOU did if you worked with a team. Hiring managers skim fast.
Headings — a table of contents on every page
Headings are where skimmers land. Use them every 100–200 words so a reader can answer "does this section matter to me?" in under 2 seconds.
Before the interview
Research the company. Practice the STAR method.
During
Prepare 3 questions. Dress one notch up.
After
Thank-you email in 24 hours, mention something specific.
Bulleted lists — the fastest way to say many things
Any time your paragraph contains the words "and", "also", "as well as" more than twice, it's begging to be a list.
- Clear subject line
- One-sentence opener
- Why this role + company
- One line of proof
- Link to portfolio
- Direct ask for next step
Icon + text — visual anchors
Pair each item with a relevant icon. The icon becomes the "thumbnail" your eye finds on re-read; the label describes it.
- Clone the repo
- Install dependencies
- Run the dev server
- Open in browser
Big numbers — when data is the point
If a sentence contains a strong stat ("80% of users", "3× faster", "$2M saved"), pull the number out and make it 3× the size.
Callout boxes — the one thing to remember
If a paragraph contains the "big takeaway", promote it into a tinted box with a colored left border. Even speed-readers see those.
There are many approaches to pricing: cost-plus, value-based, competitor-based, tiered, penetration.
Pull quotes — lift the best sentence
Long articles benefit from a pull quote every few scrolls. It gives skimmers a reason to slow down and read the surrounding section.
The best advice I got was from a magazine editor.
"Treat every paragraph like it's being read standing up on a subway." — Magazine editor, circa 2015
If they can't follow it being jostled, you've lost them.
Tables — when you're comparing things
Whenever you find yourself writing "X has Y but Z has W" more than twice, it's a table.
| Tool | Free | Best for |
|---|---|---|
| Google Drive | 15GB | Collaboration |
| Dropbox | 2GB | Cheap paid |
| iCloud | 5GB | Apple users |
| Notion | ∞ | Docs & DBs |
Timelines — when order matters
Anything sequential (onboarding, project phases, career milestones) reads better as a vertical timeline than as prose.
Meet team, set up accounts
Ship a small bug fix
Shadow a teammate
Own your first feature
Flow diagrams — show the process
Use simple boxes and arrows for any "A → B → C" explanation. Even a single line of flow beats three sentences of description.
Info cards — one idea per box
When you have 3–6 parallel items (features, team members, values), put each one in its own card. Grids beat prose every time.
Progressive disclosure — hide detail until asked
Long FAQs and "optional explanations" belong in an accordion (<details>). The reader sees only the question; clicking reveals the answer.
What's your return policy?
30 days. Must be in original condition.
Do you ship internationally?
Yes — 80+ countries, 5–14 days.
Can I cancel my subscription?
Any time from account settings. No fees.
<details><summary> and the accordion works natively — no JS required.
Highlight key terms — let the scan find you
People don't read sentences, they read keywords. Put your 1–2 most important phrases per paragraph in bold or highlighted. The scanner's eye lands on them and reads the surrounding words.
Drop caps & whitespace — the magazine trick
Long-form writing (essays, articles) benefits from classic print techniques: a drop cap on the first letter, generous line-height (1.6–1.8), and max-width 65ch. Signals "this is worth reading."
The first time I saw a well-designed magazine article I understood why print kept its monopoly on long reading for so long.
Before you publish — the 10-point scan
Before hitting publish, reread your content with a skimmer's eye. If you can't answer the main question by only reading the headings and bold words, revise.
- No paragraph longer than 3 sentences
- Subheadings every 100–200 words
- Any 4+ item list is actually a
<ul>, not a sentence - Each section has a "key takeaway" in bold or a callout
- Numbers and stats are visually bigger than surrounding text
- Any comparison of 3+ things is a table, not prose
- Anything sequential is a timeline or numbered list
- Long FAQ entries are inside
<details>accordions - Key terms bolded / highlighted so skimmers find them
- Text max-width 65ch, line-height 1.6+ for readability
Go deeper
- How Users Read on the Web — Nielsen Norman Group's original research on scanning behavior
- F-Shaped Pattern — the classic eye-tracking study on how people scan content
- Butterick's Practical Typography — a free online book on typography that's a masterclass in readable writing
- Plain Language Guidelines — the official U.S. government guide to clear writing. Short and practical.
- Refactoring UI — book with dozens of before/after makeovers of text-heavy UI
Words first, then layers.
Write the full paragraph first. Then look for the list hiding inside it, the stat worth enlarging, the comparison begging for a table, the process crying for a timeline. Revision isn't failure — it's the visual design step.