Make Yourself Clear

The Tired Reader: Why Clear Writing Wins

It is 4:52 on a Thursday, and somewhere a woman named Dana is standing at her kitchen counter with her coat still on, holding her phone in one hand and a bag of groceries in the other. She has eleven minutes before she has to leave again. She has forty-one unread messages. She is not stupid, not lazy, not in a bad mood. She is simply tired, and she is in a hurry, and she has already decided—without knowing she has decided—that she will give each message about four seconds before she keeps it, files it, or lets it slide off the bottom of the screen forever.

Your writing is going to land in front of someone exactly like Dana.

Not a teacher with a red pen. Not a critic. Not a panel of judges sitting in a quiet room, savoring your phrasing. A person standing up, half-distracted, with the milk warming on the counter, who wants one thing from you and one thing only: to understand what you mean without having to work for it. The moment understanding starts to cost her—the moment she has to slow down, back up, reread a sentence to figure out who did what—she feels it as effort. And busy people protect their effort the way a thirsty person protects water.

This is the whole book in one image, so I am going to ask you to keep it. Picture the reader as tired. Picture them as hurried. Picture them as slightly skeptical—not hostile, just unconvinced, already half-expecting to be bored or confused. Everything else we do for the next twelve chapters comes back to that person and the small, exhausting price they pay every time we make them work.

Here is the idea I want to install before anything else, because once you have it, you can't unsee it.

Writing is a transfer of effort.

Think about what actually happens when you write something and someone reads it. You had a thought—whole, obvious, glowing—inside your own head. The reader does not have that thought. They have only the marks you left on the page. To rebuild your meaning, somebody has to do the work of turning those marks back into a clear idea. That work does not vanish. It is real labor, and it has to happen somewhere. The only question—the only one—is who does it.

You can do that work in advance, while you write. You can choose the plainer word, untangle the sentence, put the point up front, cut the part that wandered. That is tiring. It takes a few more minutes and a little humility. Or you can skip it, send the tangled version, and let the reader do the untangling on their end. That is also tiring—but now it is their tiredness, multiplied by every single person who reads it.

That is the Reader's Effort Principle, and it governs everything else: every word, every sentence, every section either does work for the reader or hands work to them. Clear writing is not a talent and it is not decoration. It is simply the decision to be tired first, so your reader doesn't have to be. The clearest writer in any room is almost never the cleverest. They are the one who agreed to do the lifting.

I want to be honest with you about why this is hard, because if I pretend it's easy you won't trust the rest of the book. It is hard because the work is invisible to the person who matters least: you. When you reread your own writing, your meaning is already loaded in your head. The sentence that makes a stranger stumble reads perfectly to you, because you are not decoding it—you are remembering it. You wrote "the report we discussed," and you can see exactly which report. The reader sees three reports and a question mark. You are, in a real sense, the worst possible judge of your own clarity, because you are the one person on earth who already understands what you meant.

Which brings us to the myth I most want you to drop, today, on page one.

The myth is that impressive-sounding writing is good writing. That long sentences and big words and a formal, important tone signal a serious, intelligent mind—and that plain writing signals a simple one. Most of us absorbed this in school, where the prize often went to whoever sounded the most like a textbook. So we learned to inflate. We learned to write "utilize" when we meant "use," "at this point in time" when we meant "now," "in order to facilitate" when we meant "to help." We learned to bury the one thing we wanted to say under a soft heap of throat-clearing, because saying it plainly felt naked, unprotected, like it wasn't enough.

Here is the truth that took me years to believe: big words and long sentences are almost never a sign of a powerful mind. They are usually a sign of effort being quietly dumped onto the reader. When someone writes "Pursuant to the aforementioned," they are not being smart. They are handing you their unfinished work and asking you to finish it. Real authority sounds calm and direct. The expert says, "Don't take this on an empty stomach." The amateur, trying to sound like an expert, says, "It is advisable that administration of this product not be undertaken absent prior caloric intake." One of those people knows what they're talking about. The other is hoping the fog will pass for depth.

Let me show you the difference, because this is a craft book and I'd rather show you than lecture. Imagine a project update that opens like this:

Pursuant to our prior correspondence and in an effort to ensure alignment going forward, I am writing to provide a comprehensive status update regarding the current state of the initiative, as well as to solicit your input on a number of outstanding items that will require resolution in the near term.

Read it as Dana. Coat on, milk warming, four seconds. What did it actually say? Strip away the suit it's wearing and you'll find a small, ordinary creature underneath: here's where things stand, and I need some things from you. Forty-some words and we have not learned one fact. The writer sounded busy and important. The reader is now doing the writer's job—wading through "pursuant" and "alignment" and "outstanding items," looking for the part that concerns her, and finding nothing yet but weather.

Now the same message, with the writer agreeing to be tired first:

Here's where the project stands and what I need from you by Friday.

Same facts. A fraction of the effort. Notice that the second version is not dumbed down—it has not lost a single thing the first one was actually carrying. It hasn't sacrificed intelligence; it has sacrificed posturing. It tells Dana, in her four seconds, exactly two things: there's a status here, and there's a deadline for her. She can decide instantly whether to read on now or after dinner. You did the sorting for her. That is the entire trick, repeated at every scale for the rest of your writing life: you sort, so the reader doesn't have to.

And here is the quiet payoff nobody warns you about. The plain version doesn't just help the reader. It makes you look better—more competent, more confident, more in command of your material—precisely because you were willing to drop the costume. The writer who can say a hard thing simply is the one we trust. We've all sat in a meeting where someone explained a complicated thing in plain words and the whole room relaxed, because finally somebody knew it well enough to make it easy. That person was not lucky. That person did the work in advance.

So how do you learn to see the effort, when you're the one human guaranteed not to feel it? You borrow someone else's tiredness. This is the single most useful habit in the book, and we will use it in every chapter from here to the end, so I want to name it now and ask you to start carrying it everywhere.

The test: read it as a tired, busy, slightly skeptical stranger—and watch for where they slow down.

That's it. You don't reread your writing as the proud author who knows what it means. You reread it as Dana—coat on, eleven minutes, already half-skeptical—and you pay attention to your own body. Where do you stumble? Where do your eyes jump back to reread a phrase? Where do you have to stop and ask "wait, who is they?" or "which report?" or "what does this actually want from me?" Every one of those little catches is a leak. It is a place where the work you skipped just landed on the reader. You will feel it as a small hitch, a half-second of friction, the sense of having to climb a step you didn't expect. Those hitches are not your reader being slow. They are your sentence being unfinished.

Most people never run this test, and not because they're careless. They don't run it because rereading as a stranger is genuinely uncomfortable—it means letting go of the warm certainty that you were clear, and looking at the cold marks on the page as if you'd never seen them. But that discomfort is exactly the price of clarity. You trade a little of your own ease now for a lot of your reader's ease later. That is the bargain, and it is always, always worth it.

Which is why I'm not going to ask you to fix anything yet.

That probably sounds backward in a book about writing better. But the first skill isn't fixing—it's seeing, and you can't fix what you can't yet see. So your only job at the end of this chapter is to learn what the leak feels like.

Here's the exercise. Find any message you actually sent this week—an email, a text, a note to a coworker, a reply to a teacher, anything with your own words in it. Open it. Now read it out loud, slowly, in the voice of the person who received it: someone tired, in a hurry, with forty other things pulling at them. As you read, do one thing only. Every time you slow down—every time you stumble, reread, or have to stop and think "what did I mean here?"—make a small mark. A circle, a dot in the margin, whatever. Don't rewrite. Don't apologize. Don't even decide whether it's good or bad. Just mark the spot where the effort leaked, and move on.

When you finish, look at the marks. That's the map. Every circle is a place where, without meaning to, you handed your work to someone else and hoped they'd carry it.

Tomorrow we'll start picking those places up, one habit at a time—the point, the reader, the shape, the sentence, the cut, the flow, the tone—each one a way to do a little more of the lifting yourself. But none of it works until you can see the weight. So tonight, just learn to see it. Read your own words as the tired stranger, find the spots where they slow down, and circle them.

That stranger is who you've been writing for all along. From here on, you're going to write for them on purpose.

Find Your One Point

Somewhere right now, a tired person is reading something you wrote, and they have stopped. Not because the grammar is broken. Not because the words are wrong. They've stopped because, three paragraphs in, they still don't know why they're reading. They scroll back to the top. They start again. By the second pass they aren't really reading anymore—they're hunting, scanning for the one line that tells them what you actually want. If they find it, they forgive everything before it. If they don't, they leave.

That hunt is the cost of a missing point. And it is the most expensive thing you can hand a reader, because it makes them do the job you were supposed to do.

Here is the uncomfortable truth this chapter is built on: most writing that confuses people is not confusing at the level of the sentence. It is confusing at the level of the idea. The writer sat down and started typing before they had decided what they were saying. They knew the topic. They did not know the point. And no amount of polish further down the line can fix that, because polish has nothing to grip. You can shorten the sentences, tidy the paragraphs, swap the stiff words for warm ones—and the thing still won't land, because there's nothing underneath holding it up. Structure can arrange a point. Style can carry one. Neither can invent one that was never there.

Think back to the principle this whole book turns on. Clear writing is a transfer of effort: every choice either does work for your reader or dumps work on them. A missing point is the purest dump there is. You hand the reader a pile of true, related sentences and a silent instruction—you figure out what matters here. Some readers will. Most won't bother. And the cruel part is that you'll never see them give up. The email goes unanswered. The report gets skimmed and shelved. The essay comes back with a low mark and a comment you don't understand. You'll blame your wording. The wording was a symptom.

So we start before the wording. We start with the point.

The one-sentence test

There is a single question that separates writing that's ready from writing that only feels ready. Finish this sentence, out loud or on paper:

What I really want my reader to understand or do is ___.

That blank is the whole game. Not "what is this about"—anyone can answer that, and the answer is always too big to be useful. About gives you a topic: the budget, the trip, the new policy, the novel. A topic is a field. A point is a flag planted in it. "This email is about the budget" tells your reader nothing they can act on. "I want my reader to approve the extra two thousand for printing by Friday" tells them everything.

Try it on the last thing you wrote. Be honest about how it feels. If you can finish the sentence cleanly, in one breath, you're ready to write—the rest of this book is about getting that point to your reader with the least friction. But if you reach for the blank and it slides away from you, if you find yourself saying "well, it's sort of about how, and also there's the thing with"—stop. That stumble is not a small problem to fix later. It is the signal that you are not ready to write at all.

You're ready to think.

That's not a failure. It's the most important move a writer makes, and almost nobody is taught to make it on purpose. We treat the blank page as a place to find the point, as if it'll surface somewhere around paragraph four if we just keep going. Sometimes it does. More often you discover your point at the end, after you've written eight hundred words aimed at nothing, and now you have to throw most of them out. Thinking first is cheaper. A point you find before you draft saves you the draft you'd have to rebuild around it.

The "So what?" drill

Finding the point sounds simple until you try it on something you actually care about. The trouble is that your first answer is almost never the real one. Your first answer is the topic wearing a costume. To get past it you need a small, slightly rude question, asked over and over until it stops being able to hurt you.

The question is: So what?

Picture a student—call her Priya—the night before an essay is due. She has chosen her subject, and she's proud of it, and she opens with a sentence that has the shape of a beginning:

Social media is a huge part of teenagers' lives today, with platforms like the popular ones being used for hours every day, affecting many areas including friendships, sleep, school, and mental health.

Read that as a tired, busy, slightly skeptical stranger. Where do you slow down? You slow down everywhere, because there's nothing to hold. It's a list pretending to be a thought. Everything is mentioned; nothing is claimed. There's no place in that sentence where you could disagree with her, which means there's no place where she's actually said anything. A reader can't argue with a weather report.

So Priya asks the question. So what? So teenagers use social media a lot—so what?

So it's having a big effect on them.

Better—there's a verb now, an effect. But it's still soft. Effect could mean anything; good, bad, large, small. So she asks again. An effect—so what? What kind, on whom, that matters?

So it's affecting their mental health, and a lot of that seems to be negative—they compare themselves to other people and feel worse.

Now we're moving. We have a direction: negative, mental health, comparison. But notice she still hasn't said the thing she believes. She's reporting a trend. A reader nods and waits. So she asks the rude question a third time, and this time she lets herself actually take a side:

So the problem isn't "screen time" in general—it's the comparison, specifically. Teenagers aren't harmed by being online; they're harmed by spending that time measuring their ordinary lives against other people's edited highlights. If that's true, then telling them to "use their phones less" misses the point. The thing to change is what they're doing on the phone, not how long.

Read that as the tired stranger. You don't slow down—you lean in. You might even disagree, and disagreement is a gift here, because it means there's finally something solid enough to push against. In three turns of one stubborn question, "social media and teens" became a single defensible sentence with a spine: the harm is comparison, not screen time, so the usual advice is aimed at the wrong target. That sentence can run a whole essay. Every paragraph now has a job—prove the comparison does the damage, show why duration is the wrong measure, follow it to what should change instead. The structure didn't have to be imposed. It fell out of the point, the way it always does once the point is real.

That's what "So what?" is for. It walks you off the topic and onto the claim. Keep asking until the answer is something a reasonable person could have answered differently—because the moment your point could have been otherwise is the moment it becomes worth reading.

One piece, one point

There's a second way the point goes wrong, and it's sneakier than having none, because it looks like having too much to say—which feels like a strength. You sit down to write the email about the project delay, and while you're there you also want to flag the budget, and remind everyone about the new file naming system, and gently raise that thing from last week's meeting. All real. All yours to say. So you say them all, in one message, and you watch it land like a dropped tray.

One piece of writing carries one core point. This is the rule that saves the most drafts, and the one writers resist the hardest, because it feels like it's asking them to say less than they know. It isn't. Supporting ideas are not just allowed—they're the body of the work; a single point with nothing beneath it is a slogan, not a piece. What the rule forbids is competing points: two ideas of equal weight both trying to be the reason the reader is there.

The difference is whether the ideas serve or compete. A supporting idea answers to the main point—it explains it, proves it, qualifies it, shows it in action. A competing point answers to nothing but itself; it wants its own paragraph, its own conclusion, its own slice of the reader's attention. Put two of those in one piece and they don't add up. They split the reader down the middle. Which one is this really about? The reader can't tell, so they hedge—they give half their attention to each and full attention to neither, and they leave remembering nothing in particular. Two points fighting for the lead is the single most common reason a draft comes out muddled. Not weak words. A divided spine.

You can feel the difference if you hold two sentences side by side. The project is two weeks late because the supplier missed a shipment serves the point about the delay—it explains it, the reader takes it in without effort, and it deepens the one thing the email is for. Also, going forward, everyone needs to save files under the new naming scheme serves nothing in that email; it's a fully formed second idea with its own purpose, its own audience attention, its own follow-up. It isn't worse than the first. It's just not this. Drop it into the delay message and the reader's eyes do a small double-take—wait, is this about the delay, or about file names?—and in that flicker of doubt you've spent the very attention you were trying to win.

The fix is almost embarrassingly simple. When you find a second point shouldering its way to the front, you don't have to kill it. You have to move it. If it's genuinely a separate point, it's a separate piece—a second email, a different section, another day's writing. The delay is today's message. The budget gets its own. Each one, alone, becomes clear the instant it stops competing. You weren't saying too much. You were saying it all in the same breath.

The sticky note

Here is the practice, and it costs nothing but the discipline to do it before you'd rather start typing.

Before your next piece of writing—any of it, the email, the report, the essay, the hard message you've been avoiding—write its point in one sentence on a sticky note. Not the topic. The point: what I really want my reader to understand or do is ___, finished, with a verb in it, sharpened by "So what?" until you could imagine someone reasonably disagreeing.

Then read your sentence and apply the test that makes the note honest: if it took you more than one sentence to write down, you don't have one piece. You have more than one. Those extra sentences aren't your point fighting to be complete—they're competing points that need their own notes, their own pieces, their own day. Split them. Keep the one that's truly today's. Set the rest aside where you'll find them when it's their turn.

Now stick the note where you can see it—the edge of your screen, the corner of the desk, wherever your eyes drift when you pause. You will pause. Everyone does, somewhere in the middle, when the draft has wandered and you can't feel where you are anymore. That's the moment the note earns its place. You look up, you read one sentence, and you know again what you're for. Every paragraph you write from then on gets measured against it: does this serve the note, or compete with it? If it serves, keep going. If it competes, it belongs on a different note. If it does neither—if it's just there, true and idle and aimed at nothing—it's the leak. It's effort piling onto your reader for no return, and now you can see it, because you finally have something to hold it up against.

A topic asks your reader to do the deciding. A point does the deciding for them, in advance, while they're still busy and tired and not yet sure you're worth the climb. That's the whole of this chapter, and it happens before you've written a single sentence worth keeping. Decide what you're saying. Say one thing. Write it where you can see it.

Then—and only then—you're ready to ask who you're saying it to.