Most “problem / solution” articles assume the reader has the problem and rush to the product. Good ones make the reader name their own problem — and only then suggest a path forward.
Who this is for
Content marketers building trust before pitching, founders writing about the problem space, SEO writers ranking on problem-stage queries.
When not to use these prompts
Don’t use these for product-led articles that just want to demo. Don’t use them when the “solution” is too narrow to serve the problem stated.
Prompt anatomy / structure formula
Every problem-solution prompt should carry six elements:
- Audience: one specific reader.
- Goal: one outcome — read / click / agree / share.
- Voice: 2-3 anchor adjectives.
- Constraints: word count, banned phrases, must-include facts.
- Format: paragraph, bulleted, headed, table.
- Examples: 1-2 tone samples — best lever for matching voice.
Best for
- Search-stage problem-solution article
- SEO long-tail problem article
- Sales enablement long-form
- Inbound funnel content
- Diagnostic / framework article
12 copy-ready prompt templates
1. Problem-first skeleton
Topic: `{problem}`. Audience: `{persona}`. Write outline: (1) Hook — recognise the reader's symptom, (2) Diagnose the underlying problem, (3) Why common solutions fail, (4) A better framework, (5) Worked example, (6) When to apply / not.Variables to swap: problem, persona
2. Symptom recognition opener
Write a 100-word opener that names 3 specific symptoms readers experience. Use second person ("You've noticed…"). Make them feel seen, but don't flatter. Skip "we all know that…".3. Why common solutions fail
List 3 common solutions to `{problem}` and why each falls short. Don't straw-man — pick real solutions readers may already have tried. For each: when it works, where it breaks, and what missing piece causes the break.Variables to swap: problem
4. Diagnose vs treat framing
Many readers want to fix `{symptom}`. Distinguish diagnose (what's actually happening) from treat (the action). Write a 200-word section explaining why treating the symptom without diagnosis fails — with one specific anti-pattern.Variables to swap: symptom
5. Framework introduction
Introduce a 3-4 step framework for `{problem}`. Each step: (a) name with verb, (b) what to do, (c) success signal. Don't make it an acronym unless one fits naturally — forced acronyms cheapen the framework.Variables to swap: problem
6. Worked example
Use the framework on a real-ish example. Use real names (not "Acme Corp") if you can, or invent specific details (50-person SaaS, B2B, churn at 7%). Walk through each step, show what changes, name the win condition.7. Anti-pattern callout box
Insert a "What's NOT this framework" callout. 3 things readers commonly do that LOOK like the framework but miss the point. Each: 1-line action + 1-line consequence.8. Edge cases / scope limits
Add a "when this won't work" section. Name 3 cases where the framework fails: too small, too large, wrong industry, regulatory boundary. Confidence over hedging.9. CTA without sales-iness
End with a CTA that respects the trust earned. Three variants: (a) further reading, (b) one specific next action they can do without us, (c) optional product CTA framed as "if you want, we can do X for you". Don't pitch first.10. Counter-thesis section
Some experts disagree with this approach. Add 150 words steel-manning the strongest counter-argument. Acknowledge cases where the counter-thesis is correct. Tone: confident, not defensive.11. Problem-solution headline test
Write 5 headlines for this problem-solution article. Variety: (a) symptom-led, (b) framework-named, (c) question, (d) outcome, (e) contrarian. Skip "The ultimate guide…".12. Trust-erosion audit
Audit my problem-solution article: (1) Where does it pitch too early? (2) Where does it assume the reader has the problem instead of helping them check? (3) Where do anti-patterns get straw-manned? (4) Does the framework actually do what the headline claims?Common mistakes
- Vague audience — output reads generic.
- No tone anchor — every variant comes back same flavour.
- No constraints — word count, banned phrases, length cap.
- Skipping examples — examples are the strongest signal for voice.
- Trusting first draft — AI lands on safe middle.
- Overusing AI clichés (“In today’s fast-paced…”).
- No fact-check pass — AI is confidently wrong sometimes.
How to push results further
- Give 1-2 tone examples; “be friendly” is noise.
- Constrain ruthlessly.
- Read aloud before publishing.
- Cut adverbs / adjectives that don’t carry weight.
- AI for drafts 1-2, human edit for 3 — and 3 is what ships.
- Anchor in a real person from your audience.
- Test the headline standalone.
Practical depth notes
Use these prompts as starting points, not final answers. For Problem-Solution Article Prompts That Earn Reader Trust, the useful extra work is to replace every generic placeholder with a real constraint: audience, channel, length, brand voice, examples to imitate, and examples to avoid. Run at least two versions with different constraints, then compare the outputs side by side instead of accepting the first polished response.
A good result should pass three checks: it is specific enough that another person could reuse it, it avoids vague praise or filler, and it gives you an editable artifact rather than a broad suggestion. If the output feels generic, add one concrete reference, one forbidden pattern, and one measurable success criterion before rerunning the prompt. Before saving a prompt as reusable, test it on one realistic input and one edge case. The realistic input proves the template can produce the normal deliverable; the edge case shows whether it handles messy constraints, missing context, or an unusual audience. Keep the better output, but also keep the failed version with a note on what was missing. That small failure log is what turns a prompt collection from a list of nice sentences into a practical working library. One final check: compare the finished result against the original goal in a single sentence. If that sentence is hard to write, the output is probably polished but unfocused. Tighten the goal, remove decorative language, and rerun only the weak section instead of regenerating the entire piece.
FAQ
- How long should this piece be?: Match the channel — shorter where attention is shorter.
- Can AI do the whole draft?: AI for first two passes, human for the third.
- How often refresh?: When audience or claims change, or quarterly for evergreen content.
- Should I publish without an edit pass?: No. AI is confident, not always correct.
- Single voice or per-channel?: One brand voice; channels shift tone axes within voice.
- Repurpose this prompt for other content types?: Yes — swap audience, goal, voice. Structure is reusable.
Related
- Blog outline prompts
- Case study prompts
- Article rewrite prompts
- Brand story prompts
- Writing & Copywriting Prompts hub
Tags: #Prompt #Writing #Problem-solution