3

Problem statement

How to justify need with data, specifics, and sources — not "pain".

4 quiz questions

What a good problem statement looks like

A problem statement answers: what exactly is the problem, how big is it, whom does it affect, why has it worsened now, and what will happen if nothing is done. This is the most critical section — a weak problem statement sinks the rest of the application no matter how good it is.

Anatomy of a strong problem statement

•Specific audience: "IDPs from Donetsk Oblast aged 35-55", not "vulnerable groups".
•Specific problem: "lack of access to psychological support in district centers", not "difficult situation".
•Quantitative data with sources: official statistics, UN, research, surveys — all with references.
•Context of worsening: why right now? War, reform, demographic shift, finding from research.
•Consequences of inaction: what happens if the problem is not solved — in terms of specific people.

Data vs stories: the golden mean

A strong problem statement combines two registers: macro data (numbers showing scale) and a micro story (a concrete case that gives the problem a face). Just data — dry statistics; just a story — anecdote. Together — compelling.

Example of combination

"According to IOM IDP monitoring (Q4 2025), 47% of IDPs in Chernihiv Oblast reported symptoms of anxiety disorder. Olena from Bakhmut, displaced to Chernihiv in July 2024, describes: 'I wrote to the social services center three times, and I'm still waiting for the first consultation'."

If you cannot name a source for a specific number in your problem statement — it's not data, it's a guess. Delete or find a source.

What to avoid

•Slogans and pathos: "youth is our future", "children deserve happiness".
•Jumping to the solution: "therefore we want to launch a project..." — solutions belong elsewhere.
•Generalization without data: "most", "many", "often".
•Describing yourself instead of the problem: "our organization has 10 years of experience..."
PreviousNext Module