Problem Sections That Name a Specific Persona's Pain (36)

What a persona-specific problem section actually is

A persona-specific problem section is the decision to write the pain for one named reader instead of a general audience. A generic problem section says "managing work is hard." A persona-specific one names the reader and the exact pain that reader feels, so a product manager, a bid team, or a solo creator sees their own job on the screen rather than a problem in the abstract. The goal is not to describe a problem accurately. It is to make one reader think the page was written for them.

The best problem sections aim the pain in one of a few ways, often more than one at once:

• A named persona cue. A badge, role name, or rhetorical question that lets the right reader self-select. Deep opens a card with "I'm totally new to procurement digitalisation," and Omnibound asks "are you a marketer using generic AI," so the target buyer raises a hand before reading a word.
• A day-in-the-life scene. Prodpad builds each card from the product manager's week, from the stale slide-deck roadmap to Friday rework, so the reader watches their own job play back to them.
• Cards split by segment. Lokalise splits its audience by maturity so the solo manager and the stalled enterprise each land on their own pain, and Payaca splits by setup, spreadsheets on one side, a disconnected CRM on the other.
• A self-recognition prompt. Saleshandy stacks the wasted effort, then asks in handwriting "Feels like you?", which forces the reader to answer for themselves.

Why it works

A generic problem earns a generic nod and no motion. The reader agrees that the problem exists, then decides it is not quite their problem, and scrolls on. A pain written in the reader's own words earns recognition instead, and recognition is what makes a stranger's product feel built for the job the reader actually has.

Naming the persona also earns trust in the diagnosis. When a section describes a construction crew buried in paperwork or a sales rep who cannot tell a good lead from a bad one until the call, the reader concludes that the people behind the product understand the work. A fix offered by someone who clearly gets the day-to-day is far easier to believe than one that arrives aimed at no one in particular.

How the best problem sections do it

Nearly nine in ten of the problem sections in the library aim their pain at a specific reader, so the examples below are the disciplined end of a common move, not a rare one. Across them, what works is specificity of audience. The strongest sections name who feels the pain rather than describing it in the abstract: Synapsa writes for the sales rep who cannot separate good leads from bad until the call, Voltaiq ties each pain to battery OEMs rather than generic teams, and SignOnSite asks its construction and site-safety crews whether paperwork is getting in the way of the safety work. UserEvidence goes further and tags each pain to a named role, so the sales rep, the content marketer, and the CEO each find their own struggle on the same card.

The same section often carries more than one angle: many of these pages also set up a before and after or price the cost of doing nothing, and you can see the full range in the problem section gallery.

40/100

Common mistakes

10/100

The most common failure is a persona so broad it names no one. "For teams that want to move faster" describes everyone and reaches no one, so no reader leans in. The fix is to narrow until one reader recognizes their exact job, the way the best examples name the role, the tools, and the week. The second failure is naming the persona but then describing a generic pain: a card that says "built for marketers" and follows it with "save time and do more." The reader clocks the label, finds nothing that matches their real day, and moves on. Optise avoids this by writing the pain marketers actually feel, the tools that give no direction, the Dev who is too busy, the agency that is slow and burns the budget.