How to Write an Opening That Earns the Next Paragraph
Openings fail in five predictable ways. Six patterns that work, why the throat-clearing paragraph exists, and a test for whether yours does anything.
The short answer
Openings fail in five predictable ways: throat-clearing, defining a term nobody asked about, announcing what the piece will do, opening on the most general statement available, and burying the real start in paragraph three. Six patterns work instead - the scene, the claim, the question, the number, the objection and the direct answer. Write the opening last, once you know what the piece actually says.
The opening has one job: make the next paragraph feel necessary. Not to summarise, not to establish context, not to announce what the piece will cover. Just to create a reason to keep going.
Almost every weak opening fails because it is doing one of those other jobs instead — and because the writer needed to write it in order to find the real beginning, then left it in.
The throat-clearing paragraph
Most first drafts open with a paragraph that exists to get the writer started rather than to get the reader started.
In today's increasingly complex business environment, effective project management has become more important than ever. Organisations across every sector are grappling with tighter deadlines and more distributed teams. Understanding the fundamentals of project management is therefore essential for anyone looking to succeed in a modern workplace.
Nothing there is false. Nothing there is information either. It is a runway — the writer circling until they had enough altitude to say something. Runways are useful during drafting and dead weight afterwards.
The test: delete your first paragraph. Read the piece starting from the second. If nothing is lost, the first paragraph was a runway. This works startlingly often — I would guess on more than half of first drafts.
Sometimes you need to delete the first three paragraphs. The real opening is usually the first sentence where you stopped explaining and started asserting.
Five ways openings fail
The definition. Opening by defining your subject. "Project management is the practice of planning and executing work to achieve specific goals." Nobody who searched for this needs the definition, and anybody who does can get it faster elsewhere.
The context-setting sweep. Establishing the broad landscape before narrowing to the point. It feels rigorous. It reads as delay. Start narrow and let context arrive when it becomes necessary.
The rhetorical question. "Have you ever wondered why some projects succeed while others fail?" It defers the point by a sentence and asks the reader to do work before receiving anything. Occasionally the tension is worth creating; usually it is a warm-up the writer needed and the reader does not.
The table of contents. "In this article, we'll explore three key strategies for improving your workflow." The headings already did this. A sentence spent on navigation is a sentence not spent on content.
The unearned stakes. "Getting this wrong could cost your business everything." If the stakes were real you would name them specifically. Vague catastrophe reads as marketing.
Four of these five are among the structural patterns models overproduce, which is why generated openings feel so uniformly familiar — see 12 sentence patterns that make prose sound machine-made.
Six openings that work
1. The specific incident
Start with something that happened.
The migration was supposed to take three weeks. On day nineteen we discovered that the customer records had two different formats for phone numbers, and neither was documented.
Concrete detail does the work of an entire context-setting paragraph, because a reader can infer the situation from the specifics. It also signals immediately that the writer has been there, which no amount of asserted expertise achieves.
2. The contradiction
Name something that should not be true but is.
The most reliable predictor of whether a project ships on time is not the size of the team, the quality of the plan, or the experience of the lead. It is whether anyone is allowed to say the deadline is wrong.
This works because it creates an obligation. Having claimed something counterintuitive, you have to explain it, and the reader wants to see whether you can.
3. The direct answer
If the reader came with a question, answer it in the first line.
Yes, you can appeal an AI-generated accusation, and most appeals that include version history succeed. Here is what to preserve and in what order.
Deeply underused, because writers feel they should build to the answer. For anything reference-shaped, giving it away immediately is the correct move — the people who need the detail keep reading, and the people who only needed the answer got it. Both are served.
4. The stated problem
Name the difficulty the reader is actually in.
Grain overlays usually look wrong, and most people can see it instantly without being able to say why.
The reader recognises their own situation, which buys you the paragraph in which you explain it.
5. The correction
Take a common belief and dismantle it.
Raising the ISO does not add noise to a photograph. It amplifies a signal that already had noise in it.
Related to the contradiction, but sharper — the reader may hold the belief you are correcting, which makes continuing feel necessary rather than optional. Only use it when a genuine misconception exists. Inventing one to knock down is a hollow move readers can feel.
6. Straight in
Skip the opening entirely and begin with the first real point.
The most useful thing in an AI accusation is a record of the writing happening.
For short pieces and practical guides this is frequently the best choice. There is no rule that an article requires an introduction. Many of the best ones simply start.
The first sentence is not the opening
A distinction worth making. Advice about "hooks" tends to focus on the first sentence, but the unit that matters is the first paragraph — specifically, whether it establishes a reason to read the second one.
A brilliant first sentence followed by three sentences of context-setting has wasted the brilliance. A plain first sentence followed by a specific, surprising second sentence works fine.
What creates momentum is an unresolved obligation. Something has been claimed that requires explaining, or asked that requires answering, or described that requires resolving. The reader continues because the paragraph is not finished with them.
Read your opening and ask: what has this promised? If the honest answer is "that the article is about the topic in the title," there is no obligation and nothing pulling the reader forward.
Write it last
The most practical advice here, and the most ignored.
You usually cannot write a good opening before you know what the piece argues, because a good opening is a promise about the argument. Write the body first, discover what you are actually claiming, then go back and write an opening that sets it up.
This also solves the throat-clearing problem structurally. Draft with whatever placeholder gets you moving — a heading that says OPENING, a sentence you know is bad — then replace it once the piece exists. The runway was never meant to be part of the finished thing.
Two revision passes
The deletion pass. Cut the first paragraph and read from the second. Then cut two and read from the third. Stop when something is genuinely lost. Whatever survives is your real opening, and it is usually two or three paragraphs into the draft.
The promise pass. Read only the opening and write down, in one sentence, what it promised. Then read the whole piece and write down what it delivered. If those two sentences do not match, one of them needs to change — and it is usually the opening, because the body is where you found out what you actually thought.
For the layer underneath this — how sentence length creates the emphasis that makes an opening land — see sentence rhythm. For the habits that make openings recognisably yours rather than generic, finding your writing voice.
An opening is one decision among several that separate flat prose from prose worth finishing. The others are in how to write like a human.
Common questions
- How do I write a good opening paragraph?
- Give the reader a reason to want the second paragraph. That usually means creating an unresolved obligation — a claim that needs explaining, a question that needs answering, or a specific incident that needs resolving. Not summarising what the article covers, which the headline already did.
- What is a throat-clearing paragraph?
- The opening a writer needs in order to start, as opposed to the one a reader needs. It sets out general context, defines the subject, or asserts that the topic is important. Test it by deleting it and reading from the second paragraph: if nothing is lost, it was a runway. This is true of more than half of first drafts.
- Should I start an article with a question?
- Usually not. A rhetorical question defers the point by a sentence and asks the reader to do work before receiving anything. Occasionally the tension is worth creating, but most of the time it is a warm-up the writer needed. Ask a question only when the reader is genuinely already holding it.
- How long should an introduction be?
- Shorter than you think, and for practical guides often zero. There is no rule that an article requires an introduction; many strong ones simply begin with the first real point. If your opening runs three paragraphs before making a claim, two of them are probably runway.
- Should I write the opening first or last?
- Last, in most cases. A good opening is a promise about the argument, and you usually cannot make that promise before you know what the piece argues. Draft with a placeholder that gets you moving, then replace it once the body exists and you have discovered what you actually think.
- What is the best type of opening?
- Depends on the piece, but six work reliably: a specific incident, a contradiction, a direct answer to the reader's question, a plainly stated problem, a correction of a common belief, or simply starting with the first real point. The direct answer is the most underused for anything reference-shaped.
Keep reading
Does an Em Dash Mean AI Wrote It?
The em dash became an accusation in 2025. Models overuse one construction, not the mark — and deleting yours is the wrong response.
Why Your Work Emails Sound Like AI
Corporate email conventions produce exactly the patterns people now read as machine-written. Which habits to drop, and what to write instead.
Active and Passive Voice: When Each One Is Right
Most advice says avoid the passive, which is wrong. How to tell them apart, the four cases where passive is better, and the one where it is dishonest.