The problem statement is the first section you draft and the section that most directly determines whether readers continue past the first page. A vague problem statement produces a white paper that sophisticated buyers dismiss in the first two minutes. A specific, urgent problem statement makes readers feel seen — and keeps them reading.
Why problem statements fail
The most common failure is stating a topic instead of a problem. “Enterprise data management is complex” is a topic. “Enterprise data teams spend an average of 37% of their time on data quality remediation — time that comes directly from analysis and reporting capacity” is a problem with a cost. One creates no urgency. The other creates a reason to keep reading.
The second most common failure is writing for the wrong audience. A problem statement written for a CTO who already understands the technical landscape reads as remedial to a CTO and as appropriate for a manager who needs the background. Know who is reading and calibrate the problem statement's assumed knowledge accordingly.
The four-part formula
A strong problem statement answers four questions in roughly this order:
1. Current state. What is the situation on the ground right now? Be specific about the audience (“mid-market manufacturers,” not “businesses”), the context (“operating with legacy ERP systems purchased before 2018”), and the observable behavior or condition (“are running inventory management processes built for predictable supply chains”).
2. Why it matters. What is this situation costing — in dollars, time, competitive position, or risk? Evidence belongs here. A statistic that quantifies the cost of the problem is the most powerful thing in a problem statement.
3. Cost of inaction. What happens to organizations that don't address this? This is where urgency comes from. Without a cost of inaction, buyers can defer indefinitely without feeling consequences. A specific cost of inaction (“organizations that delay cloud migration past 2025 will face integration debt that adds 40–60% to eventual migration cost”) creates the pressure that makes buyers act.
4. What changed. Why is this problem more urgent now than it was two or three years ago? A shift in technology, regulation, competition, or buyer behavior that made the problem worse. Without this, the problem reads as perennial and therefore deferrable.
Weak vs. strong examples
Weak: “Supply chain disruption has become a major challenge for companies across industries. Organizations need to adapt their operations to remain competitive in an increasingly volatile environment. Failing to address supply chain resilience can lead to negative business outcomes.”
Strong: “North American manufacturers lost an estimated $184 billion in revenue during 2021–2022 supply disruptions — and the inventory strategies most deployed in response made the underlying problem worse, not better. Companies that increased safety stock buffers by more than 30% saw carrying costs rise faster than disruption costs fell. The challenge is not inventory volume; it's visibility. And new freight routing volatility from 2024 onward means companies built around static supplier networks face a structural problem that will compound annually.”
The strong version names a specific audience, quantifies the cost, identifies the counterintuitive element (the common fix made things worse), locates the real problem (visibility, not volume), and signals urgency (compounding annually).
Length and placement
A problem statement section runs 300–450 words in a 3,000-word paper. It is the first section you draft (before the introduction, before the evidence). It should end with a sentence that bridges to the evidence section: “What follows is an analysis of how [specific dynamic] is [producing the problem] — and what the data suggests about the path forward.”
White Paper System's Argument Lock captures your problem statement before writing begins — every section that follows is written against it, maintaining urgency and specificity throughout. Try it for $15