What makes a LinkedIn hook actually work
A LinkedIn hook works when it promises a payoff the reader cannot get by scrolling past.

A LinkedIn hook is the opening of a post, the lines that appear in the feed before "see more" cuts the rest. It is also the only part of your post that competes with every other post on LinkedIn at once. Get it wrong and the rest of the writing never matters.
HookThe opening lines that appear in the LinkedIn feed before the "see more" expand action. For a reader who does not expand the post, it is the whole post.
What is the job of a LinkedIn hook?
The hook's job is to promise a payoff the reader cannot get by scrolling past. That is the entire spec.
Everything else people say about hooks (use a number, ask a question, start with a story) is downstream of that one rule. A number works when it makes the payoff feel concrete. A question works when it commits the writer to an answer the reader can't predict. A story works when the reader needs the rest of it to make sense of the opener.
When a hook fails, almost always it's because the writer described their own intent instead of the reader's payoff. "Excited to share a few lessons from..." is an announcement of an announcement. The reader has already moved on.
PayoffThe reason a reader stays past the fold. It is whatever the reader will know, feel, or be able to do by the end of the post that they didn't at the start.
Why do most hooks fail?
Most hooks fail in one of three ways, and they are easy to spot once you know what you're looking for.
They describe the topic instead of promising the payoff. "Three lessons from running a marketing team" tells you what the post is about. It doesn't tell you why the lessons matter, or which one will surprise you. Compare to "The first marketing hire taught me something I'd been wrong about for six years." Both are honest. Only one earns the click.
They start with a windup. "I've been thinking a lot about this lately, and I wanted to share..." is two lines of throat-clearing. The reader is on line one of the feed. They do not have patience for your throat to clear.
They lead with a template. "Ways to grow your audience" and "Things every founder should know" are frames, not hooks. A frame tells the reader what kind of post this is. A detail from the real story ("the candidate everyone wanted") tells them there is something here they have not read before.
What does a working hook look like?
Working hooks share three traits. They are specific, they commit, and they leave the reader unable to predict the next sentence.
Specific: "I rejected the candidate everyone wanted" beats "Hiring is hard." The first one has a story. The second one has a vibe.
Committed: "Here's the mistake I think every Series A founder makes" tells the reader you have a position. "Some thoughts on Series A hiring" tells them you're going to hedge.
Unpredictable: If the reader can finish the sentence after reading the hook, you've given them no reason to read the post. The hook should set up a question the post answers, not state the answer and elaborate.
How do you rewrite a flat hook?
The fastest rewrite is the four-step pass in this post's howTo block: identify the verb, name the payoff, make it concrete, cut the windup. Most flat hooks are flat because they're skipping step two.
If you only have time for one move, do step four. Delete everything before the verb and see whether the hook still makes sense. If it does, keep the shorter version.
When should you break these rules?
When the audience is small enough that the relationship does the work the hook is supposed to do. If you're posting for a small audience that already knows who you are and what you're working on, the hook can be a placeholder because the click is happening regardless. Most LinkedIn writing is not in that situation. Most of the feed is a stranger surface.
The other case is when the post itself is the hook. Single-line posts ("The interview question I will never ask again is: ___") can be their own hook because the entire post is one promise of payoff. That's a different format, not a different rule.
Frequently asked
- How long should a LinkedIn hook be?
- Aim for one line that makes sense on its own inside the feed preview. If the hook only lands after the reader expands the post, it is asking for the click before it has earned it.
- Is it OK to use a question as a hook?
- Yes, but only when the question is something the reader can't dismiss with a quick yes or no. An open question that promises a non-obvious answer gives the reader a reason to expand the post; a binary one lets them answer it and move on.
- Should a hook contain a number?
- Only when the number comes from the real story and is true. A count used as a frame ('X ways to grow') reads as a template. A figure from your own experience reads as specific, as long as you can stand behind it.
- Can a hook reuse the title of the post it's introducing?
- It can, but you're paying double for one effect. Better to use the hook to commit to the payoff and let the title do something else, like name the surprising piece.
More posts
All posts →- LinkedIn's Post Proofreader edits your draft. It will not write it.LinkedIn's Post Proofreader polishes an English draft you have already written, for Premium Career and Premium Business members only, so it can save you editing time but leaves the hard part, deciding what to say from your own work, with you.
- AuthoredUp alternatives: when you want more than a LinkedIn editorAuthoredUp is the best fit for people who write their own LinkedIn posts and want formatting, a feed preview and detailed analytics; people usually look elsewhere when they want posts drafted for them, a tool that works outside Chrome, or a library of other people's top posts.
- Supergrow alternatives, including simpler options for LinkedInSupergrow is a full LinkedIn content system with AI interviews, voice notes, scheduling, engagement, analytics and team approvals; if you want fewer moving parts, a simpler tool fits better, whether that is a chat that drafts from your notes, a formatting editor for posts you write, or a plain scheduler.