How Scientists Ask Questions

Before your team collects a single new measurement, your supervisor asks you a deceptively hard question: what, exactly, do you want to know? Not is something wrong with the water, since that is too vague to ever answer. She wants a question specific enough that data could actually settle it.

You spend the afternoon in the station's map room turning a vague worry into a real research question: has nitrate concentration (the amount of a nitrogen-based chemical in the water) in the Millhaven community well increased over the past five years, beyond what normal year-to-year variation would explain?

A good research question names a specific variable (the thing you are measuring, like nitrate concentration), a specific place or group (the Millhaven well), and a specific kind of change (an increase beyond normal variation). Vague questions, like is the water bad, cannot be answered with data because nobody agrees on what would count as an answer.

Notice the question does not yet say why nitrate might be rising. That comes later, as a hypothesis (an educated guess you can test). The question just has to be answerable, one way or another, by looking at real measurements.

It is like the difference between asking a friend, are you okay, versus asking, does your stomach hurt right now. The first question is kind and caring, but it is hard to act on. The second question has a clear yes or no answer that tells you exactly what to do next. Researchers aim for the second kind of question.

Turning a vague concern into an answerable question is often the single most valuable thing an experienced researcher does before a project starts. Funding agencies, journal reviewers, and research supervisors will almost always ask a version of what, exactly, are you trying to find out, before looking at any results.

In your own words, explain why is the water bad is a worse research question than has nitrate at well GW-14 risen since 2020.