Give every piece of content a job

Most content problems don’t look like problems. A page can be well written, on brand, and approved by everyone who needed to approve it, and still fail the person reading it. Usually that’s because nobody decided what each part of it was supposed to do.

So here’s the rule: every piece of content gets a job. Not a topic. A job. “Talk about durability” is a topic. “Convince someone who just read a bad review that this will hold up” is a job. The topic gives you something to write about. The job tells you what to put in, what to leave out, and what the section has to accomplish before the reader moves on.

Start with the reader’s question

Before deciding what a page says, decide what the reader walked in wondering. Someone landing on a product page isn’t asking what the brand believes. They’re asking something narrower. Will it fit? Will it last? Is it worth the price compared with the one next to it? Those questions are the brief. If a section doesn’t answer one of them, or set up the answer, it needs a very good reason to stay.

That sounds obvious. In practice, a lot of pages are organized around what the business wants to say, in the order someone thought of saying it. The reader is left to do the sorting.

Decide what each section has to communicate

Once you know the questions, give each section one. A useful test is to finish this sentence: after reading this section, the reader should know ___. If you can’t fill in the blank, the section doesn’t have a job yet. If you need three blanks, it has too many.

Here’s a hypothetical. Picture a page for a reusable water bottle. The first section’s job is recognition: this is the bottle, and this is what makes it different, at a glance. The next section answers the leak question, because that’s the doubt most likely to stop a purchase. A later section covers cleaning, because owners ask about it after they buy, and answering it early makes the purchase feel safer. Each section can be short, because each one only has to do one thing.

Separate proof from promises

A promise tells the reader what to believe. Proof gives them a reason to believe it. “Built to last” is a promise. A clear photo of the seal, a plain statement of the materials, or a straight answer to “what happens if I drop it” is proof.

Promises aren’t useless. A headline has to make a claim. The trouble starts when a page repeats the same promise five ways and calls it persuasion. Every repetition costs attention and gives the reader nothing new to check. When you review a page, look for two things: places where a promise is standing in for proof that should be there, and places where the proof exists but is buried under the promise.

There’s a quieter version of the same problem: claims nobody can support. If the evidence for a statement isn’t there, the honest edit is to cut it, not to soften the wording until it sounds safe. A page with fewer claims that are all true reads as more confident, not less.

Make the next decision easier

Every section should leave the reader closer to a decision, even if the decision is “not this one.” That means ordering content by the sequence of doubts rather than by internal importance. It means putting the answer before the explanation. And it means ending each section so it hands off to the next question instead of trailing off.

A quick check: read only the headings, in order. If they tell the story of someone’s doubts getting resolved, the structure is working. If they read like the table of contents for a brochure, the reader is still doing the work.

Remove what has no job

This is the hard part, because content without a clear job usually has an owner. Someone requested it, approved it, maybe even likes it. But a section that doesn’t answer a question, prove a claim, or move a decision forward still takes up space, and on a phone, space is attention.

Cutting it isn’t a verdict on whoever made it. It’s a decision about what the reader needs. Sometimes the better move is to give the section a job instead: the brand story sitting in the middle of the page becomes the reason to trust the guarantee right after it. Often the better move is to let it go.

The job is the brief

Giving content a job isn’t only a writing technique. It keeps the brief, the layout, and the review pointed at the same thing. The writer knows what to write. The designer knows what to emphasize. And the reviewer gets a better question than “do I like it?”

The better question is “did this section do its job?” It’s simple enough to ask about any page, and surprisingly hard to answer honestly. That’s usually where the useful work starts.