A Big Problem Needs a Smaller Research Question

“How can corruption in Ukraine be eradicated?” sounds like a worthwhile research project. Working on it is harder than agreeing that it matters. As soon as you start gathering material, the question breaks apart: which corruption, in which institution, at what level, over what period?

In the research-design chapter of Writing Policy Analysis Is for Everyone, Anna Yungen and Kateryna Zarembo begin with this trap. You can collect a great deal of accurate information without getting closer to an answer. The problem lies in a question that allows you to keep adding material indefinitely.

Importance does not determine scope

The authors distinguish a problem from a research question. A problem can be stated as a claim: a city has polluted air; a sector has corruption risks. A question must define the work the researcher actually undertakes.

For the corruption example, the book suggests narrowing the focus to a particular institution or area of its activity. This does not mean declaring other corruption less important. It means choosing boundaries within which you can gather evidence, compare explanations and prepare an answer.

There is a refreshingly modest implication: the seriousness of analysis is not measured by the size of the problem on its cover. A grand subject can conceal undefined work. A smaller question makes it easier to say which conclusion the author takes responsibility for.

What someone can do with the answer

This handbook is primarily concerned with policy analysis and recommendations. The authors therefore suggest looking for a call to action within the question. Studying what parents mean by children behaving well and asking how to encourage parents not to hit children are different tasks. Some material may overlap, but the answers serve different purposes.

That is a boundary between genres. A descriptive question is not inherently bad; it may be entirely appropriate in academic research. But if you promise a recommendation for a decision, description alone may fall short. Before collecting data, it helps to know what kind of answer the data should support.

Consider an editorial example. Instead of asking “what is wrong with our organisation’s communication?”, ask “which recurring questions from new members should an instruction sheet answer before the next intake?” The second question cannot explain the whole organisation. It does name an audience, material to examine, an output and a deadline. This applies the book’s logic; it is not a case from the book.

Can the work be finished?

Another check concerns the time, data and knowledge the researcher actually has. The authors recommend defining geographical, temporal and institutional boundaries. A study of parking in one city and a study of parking across a country may share a word in their titles but require very different resources.

The book includes a practical suggestion from Tetiana Kyselova: try dividing the main question into two or three subquestions that can be answered directly. If each one produces another entire system of questions, reconsider the scope.

This is not a numerical test of scientific quality. Two subquestions can be poor ones too. The technique helps by exposing hidden work before it consumes the calendar.

Narrowing the question does not remove the need for a literature review. The authors warn that the impression that nobody has researched a subject often comes from an insufficient search. Earlier studies may change the question again. Refining it is part of research, rather than proof that the initial idea failed.

What to take from it today

The strength of this passage is that you can immediately test your own plan against it. What problem does it name? What bounded question does it answer? Which decision needs the result? What evidence is missing before the work can be finished?

For a Ukrainian civic organisation, newsroom or research team, these are concrete questions about a future document. They do not depend on every institution and circumstance in the book’s examples remaining unchanged. Those examples remain examples of their time; they do not establish how the institutions operate today.

If you already have a question, read this chapter beside your plan. If you only need a reminder not to take on everything at once, you can keep the central idea without buying another handbook: the boundaries of the question determine which answer you can justify.

Source and limits

Писати аналітику може кожен, Vikhola; the research-design chapter by Anna Yungen and Kateryna Zarembo. The reading covers question-setting, limits on scope, key concepts and the start of the literature review. The organisational communication example is an editorial illustration. The recommendations have not been separately evaluated in present-day institutions. The book’s title is rendered in English for this page; the source edition is Ukrainian.