You write a post. You spend twenty minutes on it. You hit publish and check back an hour later to find two likes, both from people you know in real life. The post had a good idea in it. The idea was not the problem.
The structure was. Most LinkedIn posts fail before the third line because the writing makes no promise to the reader. There is no reason to keep reading. The feed moves on.
Structure is the one variable you control before you even have a great idea. These five frameworks give you a repeatable sequence for any topic, any industry, any day of the week.
Why frameworks work on LinkedIn
A framework is a sequence of moves your writing makes, in a specific order, to keep a reader moving forward. It is not a fill-in-the-blank template. It is a logic sequence you can apply to any topic once you understand what each part is supposed to do.
LinkedIn truncates posts after two or three lines. The reader decides in under ten seconds whether to click "see more." Without a structure that earns that click, even a genuinely useful post disappears.
LinkedIn also rewards dwell time. The longer someone reads your post, the more the algorithm distributes it. A framework keeps readers on the page. That is the mechanical reason structure matters here more than on most other platforms.
Frameworks vs. templates
A template tells you what words to use. A framework tells you what job each part of your post needs to do. Templates get stale. Frameworks stay useful.
AIDA: attention, interest, desire, action
AIDA is the oldest direct-response framework in copywriting. It was built for advertising, and it maps cleanly onto a LinkedIn post. Each letter is a stage, and each stage has one job.
This framework works best when your post has a commercial intent: a product announcement, an event, a lead generation post, or a call to book a call. It can feel too sales-forward for pure thought leadership, but for posts where you want a reader to take a specific action, it is reliable.
Attention
Your first line stops the scroll. Use a surprising fact, a short story opener, or a counter-intuitive claim. This line has one job: make the next line impossible to skip.
Interest
Connect the hook to something the reader already cares about. Make it relevant to their situation, not your product or service.
Desire
Show what becomes possible. Be specific about the outcome, not the process. Readers want to see the destination before they agree to the journey.
Action
Give one instruction. Comment, click, download, reply. One action only. Multiple CTAs split attention and reduce conversion on every option.
Attention: the first line
The opening line must create a gap the reader wants to close. Curiosity, surprise, or a specific number all work.
Interest: make it about them
Shift from your story to their situation as fast as possible. The reader is always asking: why does this matter to me?
Action: one clear ask
End with a single, specific instruction. Vague CTAs get ignored.
PAS: problem, agitate, solve
PAS is the go-to framework for posts that address a pain point your audience already feels. It works especially well for service providers, consultants, and anyone writing about common mistakes or frustrations in their field.
The three stages are straightforward: name the problem, make the reader feel the cost of that problem, then offer the solution. The middle stage is where most beginners go wrong. They skip the agitation and jump straight from problem to solution. The result is a post that feels flat, because the reader has not yet felt the weight of the problem.
Agitation is not about being negative. It is about making the cost of inaction concrete before you offer a way out. Without it, your solution feels unnecessary.
Where agitation crosses a line
Agitation tips into manipulation when you invent problems your reader does not actually have. Stay grounded in real frustrations your audience has told you about directly, in conversations, surveys, or comments. If you have to guess at the pain, you probably do not know your audience well enough yet.
Before-after-bridge: paint two pictures
Before-After-Bridge works by showing two states of the world: the current one and the desired one. Then it shows the path between them. It is the natural structure for client results posts, career pivots, and any story about transformation.
The "Before" stage needs to be honest and specific. If it sounds too polished, the reader will not see themselves in it. The "After" stage needs to be concrete, not aspirational. Numbers, timelines, and named outcomes work better than adjectives.
The bridge is the most important part. It should be specific enough to be credible but short enough to leave the reader wanting more detail. The bridge is where your method, insight, or offer lives.
Before-after-bridge structure
Before
Name the current pain or limitation honestly
After
Describe the outcome in concrete, specific terms
Bridge
Show the path, method, or insight that connects the two
Write a BAB post with AI
Claude / GPT-4I want to write a LinkedIn post using the Before-After-Bridge framework. Here is the result or transformation I want to write about: [describe the result, e.g., 'helped a client cut their onboarding time from 3 weeks to 4 days'] My target audience is: [job title or role] Write a LinkedIn post that: 1. Opens with a 'Before' that names the pain or frustration my audience recognises 2. Moves to an 'After' that describes the specific outcome in concrete terms 3. Ends with a 'Bridge' that hints at the method without giving everything away Keep the total post under 200 words. Use short paragraphs. No hashtags.
Insight-proof-pivot: the first LinkedIn-native format
Built for thought leadership posts where you lead with a point of view
The first three frameworks come from direct-response copywriting. This one was built for LinkedIn. Insight-Proof-Pivot outperforms AIDA and PAS for thought leadership because it leads with a point of view, not a problem or a product.
The structure has three moves. You state a specific, debatable insight. You back it with one concrete piece of evidence. Then you pivot to what that means for the reader right now.
The insight must be specific and debatable. "Content is important" is not an insight. "Most B2B content fails because it explains what to do but never why the reader has been avoiding it" is an insight. The difference is that the second one takes a side. Someone could disagree with it. That friction is what generates comments and shares.
This is the framework behind most high-performing thought leadership posts from LinkedIn-native creators. The pivot is what separates it from a regular opinion post. The pivot answers: so what does this mean for you, reading this right now?
The insight line
State a specific, debatable point of view in one or two sentences. If no one could disagree with it, it is not an insight.
The proof
Back the insight with one specific example, result, or observation. First-person data is more credible than vague attribution.
The pivot
Tell the reader what this means for them, specifically. Give them one concrete action or reframe they can apply today.
The pivot is not a summary
Most writers end a thought leadership post with a restatement of the insight. The pivot is different. It hands the reader something they can do with the idea before they close the app. That is what makes the post feel worth reading.
The micro-story arc: the second LinkedIn-native format
Built to connect, not convert
Personal stories with professional lessons consistently outperform pure advice posts on LinkedIn. The reason is pattern recognition. When a reader encounters a tension they have felt before, they stop scrolling. They want to know how it resolved.
The Micro-Story Arc compresses that pattern into five moves. Each move is short. The whole post can be under 200 words and still land harder than a 500-word advice thread.
This framework pairs well with career milestones, client stories, and any post that starts with "the day I learned." It is also the right structure for posts where you want to build trust rather than generate leads. AIDA is built to convert. The Micro-Story Arc is built to connect. Both are useful, but they serve different goals.
Scene
Place the reader in a specific moment. One or two sentences maximum. Name a time, a place, or a situation. Keep it concrete, not cinematic.
Tension
Introduce the problem, decision, or conflict. This is where the post earns its read. The reader needs to feel the stakes before they will follow you through the story.
Turn
Describe the moment something changed. A decision, a realisation, a result. This is the pivot point of the story. Be specific about what actually shifted.
Lesson
State what you took from the experience in one or two clear sentences. This is your insight. It should feel earned by the story, not bolted on.
Bridge
Connect the lesson to the reader's situation. Tell them how this applies to them, or ask a question that makes them reflect on their own version of the same tension.
The most common micro-story mistake
Writers spend too long on the scene. Two sentences is enough to set context. If you spend five lines describing the situation before the tension arrives, you have already lost most readers. Start as close to the conflict as possible. The scene exists to make the tension believable, nothing more.
Use the Micro-Story Arc when
Goal
Build trust and connection
Content type
Career moments, client stories, personal lessons
Tone
Honest, specific, reflective
CTA style
A question or open reflection
Best for
Audience growth, brand building
Use AIDA when
Goal
Drive a specific action or conversion
Content type
Offers, events, lead generation posts
Tone
Direct, benefit-focused
CTA style
One clear instruction
Best for
Pipeline, list building, sales
