Writing guide · 4 min read
The PAS Formula: How to Write Problem-Agitate-Solve Posts
Short answer
PAS (Problem, Agitate, Solve) is a three-part writing formula: you name a problem in the reader's own words, make it concrete by showing what it costs them, and then give one specific fix, all of which fits comfortably inside a 280-character post on X.
Key takeaways
- Write the problem the way your reader would say it out loud, not the way an expert would label it.
- Agitate with one concrete cost (time, money, a bad Thursday), never with fear or exaggeration.
- The solve has to be a real, usable step; a teaser that only points to a link breaks the formula.
- PAS fits best when the reader already feels the problem. For news or stories, pick another formula.
In this guide
Problem-Agitate-Solve is the formula to reach for when your reader has a frustration and you have a fix. It is short enough for a single post on X and structured enough that you can write one in five minutes. This guide shows how each part works, gives a template you can copy, and points out the places where PAS posts usually go wrong.
What is the PAS formula?
PAS is a three-step structure that names a problem, makes its cost concrete, and then offers one specific solution.
Each step does a different job:
- Problem. One sentence the reader recognizes instantly. It should sound like something they would type into a search bar or complain about to a friend.
- Agitate. One or two sentences that show what the problem costs: time, money, effort, a ruined plan. This is what makes the reader care about the fix.
- Solve. The fix, stated as plainly and briefly as you can. A reader should be able to act on it without clicking anything.
Here is the example from our formula library:
Your meal prep goes bad by Wednesday.
So Thursday is takeout, Friday is takeout, and half the containers go in the trash.
Cook two proteins and three sides on Sunday, but don't combine them until the day you eat.
Each line could stand on its own, and together they make a complete small argument.
How do you write the problem line?
Describe the problem in the reader's words and in the present tense, so they recognize it in under a second.
People skim. Nielsen Norman Group's research on web reading found that most readers scan for words they recognize before deciding to read closely. The problem line is your scan target.
Compare:
- Weak: "Many professionals struggle with suboptimal calendar management."
- Better: "Your calendar has three meetings at 2pm and none of them need you."
The second version uses the situation itself rather than a label for it. If you are tempted to write a category ("productivity", "workflow issues"), replace it with one specific moment.
How much should you agitate?
Agitate with one real consequence, described specifically, and stop there.
The agitate step is where PAS earns its reputation, good and bad. Done well, it turns a vague annoyance into something the reader wants solved today. Done badly, it piles on fear until the post reads like an ad for a supplement.
A few rules keep it honest:
- Use consequences the reader has actually experienced. "You re-read the same email four times" is fine. "Your career is slipping away" is not.
- Pick one cost. Two at most. A list of five consequences is a rant.
- Keep the numbers yours. If you mention a figure, it should come from your own work or a source you can link.
X's rules on platform manipulation are about fake or coordinated engagement, so a sharp agitate line will rarely be a policy problem. The risk is readers: people mute accounts that sound alarmist, and restraint here pays off.
What makes a good solve?
A good solve is a step the reader can take right now, small enough to fit in one or two sentences.
The most common PAS mistake on X is a solve that isn't one. "Here's how I fixed it 👇" followed by a link is a teaser. The reader feels the problem, then gets nothing in the post itself. Give the actual fix, then add the link for people who want more.
Strong solves usually have one of these shapes:
| Solve type | Example |
|---|---|
| A rule | "No meetings before 11am on Tuesdays and Thursdays." |
| A swap | "Use a paper list for today and the app for everything else." |
| A setting or step | "Use your email app's scheduled send for replies written after 8pm." |
| A question to ask | "Ask 'what decision does this meeting make?' before accepting." |
What is a fill-in template for PAS?
Use three slots: when [situation], [problem]; that means [cost]; instead, [fix].
A plain template you can adapt:
[Specific situation the reader is in.]
[What that costs them, in one concrete detail.]
[The fix, as one action.]
Worked example for a freelancer audience:
You send an invoice and hear nothing for 30 days.
Meanwhile rent is due and you're writing awkward "just checking in" emails.
Put the due date and a late fee in the first line of the invoice, and send a polite reminder on day 7.
That one comes to about 230 characters. If yours runs long, our guide to editing a post down to fit shows what to cut first. The formula builder has PAS as a preset and counts characters the way X does as you type.
When should you not use PAS?
Skip PAS when the reader doesn't feel the problem yet, or when you are sharing news, a story or an opinion.
PAS assumes a pain point. If your audience has never noticed the problem, the agitate step feels like you are inventing one. In those cases a "Myth, then fact" or "Hook, point, proof" post usually works better.
It also tires quickly. If every post on your account opens with a complaint, followers start to feel lectured. Mix PAS with stories, questions and observations; one PAS post in five is a reasonable rhythm.
How do you test whether a PAS post works?
Read each line on its own and ask whether a stranger would understand it and want the next line.
Before posting, run three quick checks:
- Cover the second and third lines. Does the first line alone make the right reader stop?
- Is the agitate line true for most of your audience, without exaggeration?
- Could someone follow the solve without clicking anything?
If all three pass, post it. If the solve fails, the post isn't ready. Our guide to writing hooks that earn the click covers the first-line check in more depth.
Questions
- What does PAS stand for in copywriting?
- Problem, Agitate, Solve. You state a problem, describe its consequences so it feels real, and then offer the solution. It is one of the oldest short copywriting structures and works well for posts because each part can be one or two sentences.
- Is PAS manipulative?
- It can be if the agitate step invents fear or exaggerates harm. Used honestly, it just describes a problem the reader already has in specific terms. Keep the costs real and checkable and the fix genuinely useful.
- How long should a PAS post be on X?
- Most PAS posts land between 150 and 260 characters. One line per part is usually enough. If the solve needs more than a sentence or two, turn it into a short thread with the fix spread over a few posts.
- What is the difference between PAS and Before-After-Bridge?
- PAS starts from a problem and ends with a fix. Before-After-Bridge starts from a past state, shows the improved state, then explains the step between them. BAB suits stories of change; PAS suits tips.