Problem Sections That Prove the Pain Is Shared (7)

What a social-validation problem section actually is

A social-validation problem section is the decision to prove the pain is widely shared, not just to describe it. A plain problem section tells the reader the current setup is slow, scattered, or wasteful. A social-validation section shows how many other people are stuck in the same place: the share of users who give up, the percentage of projects that fail, the number of buyers who walk away for the same reason. That evidence is what turns a private "maybe it is just me" into a public "this is a known problem," which is a far easier place to sell a fix from.

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

• An aggregate behavior stat. One figure that shows the problem is a pattern, not a personal slip. Bulkmark leads with 97% of saved items never opened again, a number about everyone's behavior, so the reader reads it as a shared habit rather than their own laziness.
• A stat pulled from a cited report. A figure with a named source behind it, so it reads as research. UserEvidence opens with 67% of buyers ruling out a vendor over untrustworthy evidence, sourced from its Evidence Gap Report, which lands harder than an unattributed claim would.
• A headline that frames the pain as universal. A line that tells a specific audience everyone like them has felt this. Edgee Fallback Models opens on "three failure scenarios every Claude Code user has experienced," so a developer nods before reading the detail.
• A set of recognizable scenarios. Everyday situations, sometimes tagged to roles, that let each reader find their own version of the struggle. UserEvidence lays out real chat scenarios tied to the Sales Rep, the Content Marketer, and the CEO, so the pain feels shared across a whole team.

Why it works

People often sit with a broken setup because they quietly suspect the fault is theirs. An aggregate number breaks that suspicion. When Nautis shows that 54% of founders burn out, or Deep leads with up to 84% of digitalisation programmes failing, the reader learns the wall is one most people hit, not a sign they are bad at their job. The shame that kept them from acting drops, and looking for a fix stops feeling like an admission of failure.

The proof also borrows the credibility of scale. A figure about the crowd is harder to wave off than a claim about the reader alone, because it reads as something measured across many people rather than a line written to sell. Once the reader accepts that the problem is real and common, the section has earned the right to introduce the fix, and the reader is listening instead of bracing.

How the best problem sections do it

Across the scored examples below, the pattern that lands is a number that is clearly about other people, and clearly believable. The strongest sections point the figure at the crowd, so the reader hears "you are not alone," and they ground it so it reads as evidence rather than a boast. UserEvidence ties its 67% of buyers to a named Evidence Gap Report, so the stat carries a source. Bulkmark uses 97% of saved items never reopened, an aggregate behavior number nobody can pin on the reader personally. Edgee Fallback Models skips the stat entirely and frames the pain as something every Claude Code user has already lived through, which validates by recognition instead of by percentage. The move is the same each time: make the reader feel seen, and make the shared pain hard to dismiss.

This angle rarely stands alone. Proof that the pain is common gets sharper when it also puts a number on the pain, and it aims straight at the reader when the section speaks to one persona's specific pain. You can see the full range in the problem section gallery.

100/100

Common mistakes

10/100

The usual failure is a validating stat with no source and no scale the reader trusts: a round percentage floating free of any report or any behavior the reader recognizes, so it reads as a number someone made up to scare them. The second failure is proof that widens the wound and then abandons it, piling on how bad and how common the problem is without ever signaling that a way out exists, which leaves the reader anxious rather than ready to act. The best examples avoid both by grounding the figure and aiming it at a situation the reader already lives with, the way Nautis, UserEvidence, and Bulkmark do.