How to write a LinkedIn hook that stops the scroll
The first line decides whether anyone reads the second. Patterns that work on LinkedIn, and a few that quietly don't.
LinkedIn truncates a post after two or three lines and shows a "see more" prompt — everything before that fold is your entire hook. Get that wrong and the rest of a genuinely good post never gets read.
What works
- A specific, credible claim. "I turned down a $40k raise" gets read because it's specific and slightly surprising. "Here's something I learned about my career" doesn't, because it's generic.
- A short, declarative first line. LinkedIn readers are scanning between meetings — a first line that's one clear sentence outperforms one that's trying to set up a whole scene.
- Numbers and outcomes. "We cut onboarding time from 3 weeks to 4 days" hooks harder than "we improved our onboarding process," because it's concrete and verifiable-sounding.
What quietly doesn't work
- "I don't usually post about this, but..." This has become a recognizable pattern that reads as a setup for engagement-bait rather than genuine vulnerability, even when it's sincere.
- Vague inspiration openers ("Some thoughts on leadership") — too broad to create curiosity about what specifically you're going to say.
- A hook that oversells what the post delivers. LinkedIn's professional audience is quick to call out a post that promised a lesson and delivered a platitude — and the comments will say so.
The shape of a good LinkedIn hook
Most working LinkedIn hooks do one of three things in the first line:
- State a specific, slightly counterintuitive result. "We stopped doing daily standups and shipped faster."
- Name a real mistake or failure plainly. "I almost fired my best engineer over a misunderstanding."
- Ask a question your audience actually debates. Not a rhetorical throwaway — a real tension people in your field disagree about.
Format matters as much as wording
Short paragraphs — sometimes single sentences — read better on LinkedIn's narrow feed column than dense blocks of text. Your hook line should stand alone as its own paragraph; don't bury it at the start of a longer block where it loses its visual weight.
A quick test before you post
Read only your first line, out of context, and ask: would this make a stranger scrolling past want to know what happens next? If the answer requires the second or third line to make sense, the hook isn't done yet — move the real point up to the first line and let the setup follow it, not precede it.