LinkedIn rewards posts that hold attention. The longer someone stays on a post, whether they click "see more," read through to the end, or scroll through the comments, the more the platform surfaces it to others.
Every decision in the writing process should serve that goal: earn the first click, hold the reader through the body, and leave them with something worth remembering.
Step 1: Understand What Makes Someone Stop Scrolling
Your hook is the first 1-3 lines visible before the reader taps "see more." That tap is the single action your post needs to earn. Everything downstream, comments, shares, DM conversations, pipeline, depends on the reader getting past those first lines.
Think of a hook like a billboard on a highway. A billboard needs to be interesting enough that someone remembers it, maybe even pulls over. But a hot pink sign with nothing useful on it does not make anyone call the number. The same logic applies here.
A flashy opening that has no connection to the substance of the post generates a click at best and disappointment at worst.
What Separates a Strong Hook From a Weak One
The strongest hooks share a few traits:
- Specificity: They contain concrete details (a date, a number, a place, a person, a situation) rather than abstract framing. For example, "Three weeks into our engagement with a Series B fintech team, their CTO sent us a text at 11pm", compared to "Here is something I have learned about working with startups."
- Tension or surprise: They create a gap, something the reader needs to resolve by reading further. A question they want answered, a contradiction they want explained, or a situation they want to see play out.
- Direct connection to the body: The hook sets up a promise that the body has to deliver on. A hook that teases one thing and delivers another trains your audience to stop trusting your posts.
Types of LinkedIn Post Hooks
Hooks exist on a spectrum between two extremes. While both work, the right choice depends on the post, the topic, and how you naturally communicate.
| Type | What it looks like | When it works well |
|---|---|---|
| Descriptive | Three or more sentences. Heavy on context, dates, names, numbers. Drops the reader into a specific scene. | When the details themselves are interesting enough to hold attention. Personal stories, client situations, unusual events. |
| Punchy | One to two sentences. Compressed, direct, creates a gap. | When the idea is strong enough that a short framing raises an obvious question. Industry takes, counterintuitive claims, bold positions. |
Neither style is better than the other. What matters is that the hook earns the tap honestly and the body follows through.
What to Avoid in Hooks
- Rhetorical questions ("Have you ever wondered why...?"): These read as filler and pattern-match to AI-generated content.
- Throat-clearing openers ("Looking back on my career..." or "Early on, I realized..."): These delay the substance. Start with the substance.
- Absolute declarations without any grounding ("SaaS is dead." or "If you are not doing X, your company is finished."): These sound naive. Anyone thoughtful enough to hold a strong opinion should also be thoughtful enough to acknowledge nuance.
Step 2: Pick Your Post Type Before You Write
Every post should follow one of two structures, chosen before the writing begins.
Post Type 1: Framework Posts
A framework post teaches something. It takes an idea, a process, or a model and breaks it down into components the reader can understand, apply, or argue with.
Structure:
| Section | Purpose |
|---|---|
| Opening claim | A clear position that sets the direction of the post |
| Context | Why this matters, what prompted the thinking, or what problem it addresses |
| The breakdown | A numbered list, a set of principles, a process, or a model. This is the spine of the post. |
| Examples | Concrete situations that ground each point in something real |
| Closing insight | A final thought that connects back to the opening claim. No new threads. No announced lessons. Circle back. |
Example of a framework post:
When we began building Nexus OD, in [X month, X year], the goal was to give transportation professionals a way to see mobility clearly enough to make informed decisions and keep people safer. Turning that idea into a working product took years of learning, failing, and rebuilding. Here were the three biggest lessons and takeaways from that journey:
1. Building visibility is harder than building software.
The data was scattered across systems, formats, and agencies, so bringing it together was the real challenge. We had to build a platform flexible enough to connect to any data source, yet precise enough to deliver answers planners could trust. That took relentless testing, iteration, and partnership with agencies who were willing to push the boundaries with us.
2. As cliché as it may sound, simplicity wins.
Our early versions tried to do everything, but civil engineers just want a clear view into the data that matters. Nexus OD lets users click on a corridor and instantly see how trips begin, end, and flow across a region.
What fires me up most about this is that we’re squashing the belief that legacy companies like to uphold - the one that says information has to be siloed because “that’s just how it works.” When planners, engineers, and policymakers can all see the same data, it changes the way people collaborate.
3. The customer builds the product with you.
Every useful feature in Nexus OD came from feedback. Whether it was from people using the tool or challenging assumptions, they showed us what mattered. That directly informed how we designed Nexus to adapt to the different ways regions move: some think in corridors, while others think in trip paths. That flexibility comes down to 20% vision and 80% listening.
The best products are always the ones that start with what your customers need you to fix. That’s the framework we used to build Nexus OD, and it’s how we’ll continue to improve it.
Post Type 2: Storytelling Posts
A storytelling post uses a specific moment, scene, or experience to build trust, demonstrate humanity, or land an insight that would fall flat if stated as a plain claim.
Structure:
| Section | Purpose |
|---|---|
| The moment | A specific situation, memory, or interaction. When it was, who was involved, what the setting looked like. |
| The tension | What went wrong, what was confusing, what was surprising, what created friction. |
| The realization | What changed or became clear. This is the turn. |
| The takeaway | What the reader carries away; a grounded conclusion tied to the tension. |
Every story has an arc: setup, tension, resolution. If an experience comes across as flat when told out loud, the tension is buried somewhere. Where was the friction? Where did things nearly fall apart? Where was the difficult conversation? Those are the points to build the post around.
Example of a storytelling post:
The number one mistake early-stage startups make: hire too quickly.
It's tempting to think that your next hire is going to solve all your problems. But before you hire anyone, start with one question:
“What is their mission?”
When hiring, people often chase shiny resumes. Candidates that have had stints at successful companies. But is their experience even relevant?
To answer this, deconstruct the role you're opening up and ask: what must this person accomplish to truly have an impact?
For first-time founders, this can be especially hard because they've never done the job themselves so they don't even know what the role truly entails.
One solution: try to do the job yourself. The point is not to become an expert; think of it as going on reconnaissance for this role. You're scouting the situation so you know exactly what type of person you need to accomplish the mission.
Before we hired our first growth marketer, I ran growth marketing myself for 6-12 months. By background I'm a finance person. Ex-CFO. I'd never run influencer campaigns, never built a paid funnel, never thought deeply about hooks or creative strategy.
So I learned the hard way. Onboarded our first wave of creators myself, one call at a time. Spent my days in our Gambassadors Slack talking to power users, reviewing content, iterating on how we told our story. Worked directly with agencies, tried and discarded ideas, watched which scripts bombed and which formats quietly printed signups.
That period was uncomfortable. I felt like a beginner again.
But that was the point.
If you haven't done the work (even at small scale) you're hiring blind. You don't know which metrics actually matter, which tradeoffs are real, or what "great" looks like day to day. You'll over-index on resumes and buzzwords because you have nothing else to go on.
So next time you feel pressure to "scale the team," start with one question.
“What's the mission?”
How to Choose Between the Two
Ask one question before writing: "Am I teaching something, or am I showing something?"
- Teaching (a breakdown, a list, a model, a how-to): Use the framework structure.
- Showing (a moment, a conversation, a failure, an experience): Use the storytelling structure.
Do not try to do both in the same post. The structures serve different purposes. Mixing them produces posts that do neither well.
Step 3: Write With Specificity
The single biggest quality problem in LinkedIn content is vagueness.
Posts that say "we learned a lot" instead of "we learned that X does not work when Y is true." Posts that say "a client saw great results" instead of specifying the results. Posts that use words like "interesting" or "important" without explaining what made the thing interesting or important.
The Specificity Test
Every sentence in a post should do one of two things: say something concrete, or set up the next sentence to say something concrete. If a sentence does neither, cut it.
When specific details exist, a number, a date, a name (with permission), a place, a tool, a metric, use them. No one remembers "we improved our process." People remember "we cut the onboarding timeline from 6 weeks to 11 days."
Proprietary vs. Generic Content
A useful test for whether a post is worth publishing: could this have been written by anyone?
| Generic content | Proprietary content | |
|---|---|---|
| Source | Secondhand observations from reading the news | Firsthand experience from doing the work |
| Detail level | Broad advice that applies to everyone | Specific frameworks with enough detail that a reader could attempt to replicate them |
| Point of view | Restates consensus | Takes a distinct position backed by evidence |
If a post contains advice, observations, or framing that any person in the same industry could have produced without any unique experience, it is generic. If the post only works because of the specific things the author has seen, done, built, or failed at, it is proprietary. Proprietary content is the only kind worth producing.
Share the Sauce
A common objection from executives and founders: sharing too much of how they operate will give competitors an advantage. In B2B and service contexts, this fear is unfounded.
Sharing exactly how a process works (the steps, the logic, the tools) builds trust with the audience faster than anything else. It signals that the advantage is in the execution, not in keeping a secret.
Readers who learn from a post and go implement the advice themselves were never going to be clients. Readers who learn from a post and realize they would rather hire the person who built the framework: those are clients.
If a business moat is fragile enough that a LinkedIn post could destroy it, the moat was not protecting the business regardless.
Step 4: Get the Voice and Quality Right
The standard for executive LinkedIn content is that a post should sound like a polished version of how you actually communicate over a reinterpretation or a dramatization.
If you tend to hedge opinions with "I think" or "from what we have seen," the content should reflect that. If you speak in connected, flowing sentences rather than short staccato fragments, the post should flow the same way. If your natural mode is to circle back to their opening point at the end of a thought, the post should close the same loop.
The test: could you read this post out loud to your co-founder or your spouse and have it sound like something you would plausibly say? If not, the voice is off.
Common Quality Issues to Watch For
- Word repetition: If the same word appears more than once in a paragraph, or more than two or three times in a full post, vary the language. In a journalism piece, the subject's name does not appear eight times in a thousand words. "She," "her," the person's title, and the person's name rotate. The same principle applies to any term in a post.
- Identical sentence structures back to back: If two sentences in a row begin with the same word or follow the same grammatical pattern, the rhythm goes flat. Mix it up. Short sentences read better after longer ones.
- Announced lessons: Phrases like "the reason this works is simple," "here is why this matters," or "the truth is" are filler. They tell the reader a point is coming instead of making the point. Cut the announcement and deliver the substance.
- Empty hedging vs. honest hedging: "I think this is probably maybe worth considering" sounds uncertain and weak. "From what we have seen across 40 engagements, this tends to hold true" is honest about the basis of the claim while still committing to a position. Always hedge with evidence.
Step 5: Measure What Matters (It Is Not Virality)
Virality is the wrong goal for B2B executives and founders. A post that gets 200,000 impressions and zero qualified conversations is worth less than a post that gets 21 likes and drives three conversations with decision-makers who have budget.
Any executive investing in LinkedIn content will eventually need to justify the spend to someone. A VP of Marketing reports to a CMO or CEO. A founder reports to a board or to their own priorities. That justification needs to be grounded in pipeline attribution instead of vanity metrics.
The content strategy should be designed from day one around generating conversations. Track who engages with posts: profile visitors, new followers, commenters, people who send DMs. Identify which of those people fit the ideal customer profile. Reach out. Uploading a post is just the beginning.
Performance Evaluation - Viral vs. Editorial Content
Performance should be evaluated on a rolling basis across weeks and months. Some posts will hit, others will not. The content that performs well editorially (the thoughtful, specific, substantive work) is often not the content that goes viral. Virality tends to favor emotional triggers, contrarianism for its own sake, or format gimmicks. Editorial quality favors depth, specificity, and trust-building.
These overlap sometimes, but not reliably. Chasing the overlap leads to posts that are neither substantive nor viral.
The goal: Post consistently, with substance, and track whether the collective body of work is generating the right kinds of conversations over time.
Step 6: Take Positions Worth Reading
The content that generates real engagement for executives takes a position that is not consensus. Not contrarian for the sake of being contrarian (that is just another form of performance) but informed by experience that the audience does not have.
If every post agrees with what the audience already believes, nobody has a reason to engage. The post confirms what they knew and they scroll past. If a post presents a perspective that makes people think, "I am not sure I agree with that, but the logic is interesting," they stop. They read, comment, and come back.
How to Frame a Strong Position
Lead with a clear stance and hedge it honestly. "I think X, based on what we have seen across [specific context]." This signals confidence without pretending there are no counterarguments. It invites debate rather than shutting it down.
The posts that tend to build real followings over time are the ones where the author holds a position firmly enough to defend it, but loosely enough to hear someone out. That balance makes someone worth following.
Step 7: Find the Story in Any Industry
Executives in less flashy industries (logistics, insurance, accounting, compliance, heavy machinery, professional services) often worry that their work is not interesting enough for LinkedIn.
It is. Every industry has stories and tension. Every professional who has spent years in their field has encountered situations where something went wrong, something was harder than expected, or something they believed turned out to be false. Those situations are the raw material.
The problem is usually that the stories are being told flat, as a linear sequence of events with no tension highlighted. The fix is structural:
- Find the friction: Where did things nearly fall apart?
- Find the surprise: What turned out differently than expected?
- Find the difficult conversation: What was the moment where someone had to say something hard?
- Find the realization: What did the person learn that they did not know before?
A post about logistics that leads with a specific operational failure and what it taught the company is more interesting than a post about "innovation in the supply chain." A post about an accounting firm's decision to turn down a lucrative client because the engagement was misaligned is more interesting than a post about "values in professional services."