How to Write a Compelling Problem Statement

The problem statement is arguably the most important section of any grant proposal. It's your first real opportunity to show a funder why your work matters, and it sets the stage for everything that follows. When written well, reviewers are already invested in your proposed solution to the challenge. 

Below are the core elements of a strong problem statement:

1. Use Data Strategically

Every claim in your problem statement should be supported by credible, current data. Use a mix of national context and local specifics. Funders want to see that the problem is real and widespread, but also that it has particular urgency in the communities you serve.

• Cite recent sources: Avoid data that's more than five years old. Use the most current Census data, government reports, or peer-reviewed research available.

• Get specific and local: National statistics frame the problem; local data makes the case for your organization.

• Don't overwhelm with numbers: Two or three well-chosen statistics are more persuasive than ten. Choose the figures that are most striking and most relevant.

  
  

2. Name the Gap

A problem statement shouldn't just describe suffering; it should identify why existing services aren't enough. What is currently available? What's missing? Why is your organization's approach needed?

This 'gap analysis' is critical because it positions your proposal not just as a response to a problem, but as a response to an unmet need. It also demonstrates that you've done your homework and aren't duplicating existing efforts.

3. Center the Community

Many funders increasingly expect proposals to demonstrate that community members have been involved in identifying priorities and designing solutions. Where possible, incorporate voices from the community directly: survey results, testimonials (with permission), or findings from community listening sessions.

4. Connect the Problem to Your Solution

The end of your problem statement should flow naturally into your proposed intervention. By the time a funder finishes reading it, they should already be asking: 'So what are you going to do about it?' Avoid the temptation to lay out every detail of your program here, since that is what your project description is for. But do make clear that there is a logical, direct link between the problem you've described and the approach you're proposing.

Common Mistakes to Avoid

• Writing about your organization, not the community: The problem statement is about the people you serve, not your organization's history or accomplishments.

• Using jargon: Write for a reviewer who may not be an expert in your field.

• Being too broad: A problem statement that tries to address everything often ends up compelling about nothing.

• Forgetting to cite sources: Always include citations or footnotes.

  
  

A strong problem statement does more than describe a need and builds an argument. It moves a funder from 'this sounds interesting' to 'this is urgent and important, and I want to be part of solving it.' If you're struggling, try writing one paragraph as if you're explaining the problem to a friend who knows nothing about your sector.