GSOE9011 Chap.5 From Research Gap to Question
From Research Gap to Question
A research question connects the literature gap to evidence the proposed method can produce. It should define the phenomenon or relationship, relevant system or population, comparison and boundary without assuming the desired answer. Operational terms make the question testable, while a feasibility check keeps scope within available time, equipment, access and expertise.
Every important phrase should map forward to an observation or analysis and backward to a reason in the literature.
What this chapter covers
- 01
Decision and knowledge problems
- 02
Empirical and methodological gaps
- 03
Non-leading wording
- 04
Operational definitions
- 05
Comparators and outcomes
- 06
Scope conditions
- 07
Feasibility boundaries
- 08
Question-to-method mapping
Worked example · free
Refining an advocacy question into a comparison
- +1Remove the assumed benefit and decide which sustainability-related engineering outcome is actually being studied.
- +1Name the intervention, baseline and controlled conditions supported by the literature and available resources.
- +1Specify measurable outcomes and the time or operating boundary needed for interpretation.
- +1Check that the proposed design can produce evidence for every phrase and that two plausible answers remain possible.
Key terms
- Research question
- A precise statement of the uncertainty the study will address with observable evidence.
- Operational definition
- A rule connecting an abstract concept to a specific measurement or classification.
- Comparator
- The baseline, alternative method or condition against which an outcome is interpreted.
- Leading question
- A question whose wording assumes or favours a particular answer.
- Feasibility boundary
- A limit created by time, access, equipment, data, expertise or ethical requirements.
- Proxy measure
- An observable indicator used when the desired construct cannot be measured directly.
From Research Gap to Question FAQ
What makes a research question answerable?
Its important terms can be defined, observed or compared within a feasible design. The question leaves room for more than one outcome and states enough boundary for the result to be interpreted.
How narrow should the question be?
Narrow enough for one coherent study to generate the needed evidence, but not so narrow that the result loses significance. Scope can be limited by system, condition, mechanism, outcome or comparison.
Can I use a proxy when the real outcome takes years to observe?
Yes, if literature supports the proxy's relationship to the desired outcome and the proposal states the limitation. A proxy changes the conclusion the study can support and should never be presented as the final outcome itself.
How does the question guide the proposal?
Its context drives the literature review, its terms determine variables and comparisons, its boundary shapes feasibility, and its intended answer determines the analysis and expected contribution.
Assessment move
Keep a one-page question map with five rows: context, gap, question phrase, evidence needed and decision enabled. Revise the rows together rather than polishing wording in isolation. Circle ambiguous terms and write operational definitions. Test feasibility against the actual term, equipment, data access and team capability. Remove causal wording when the proposed design supports only association.
Ask whether the comparator is fair and whether important nuisance conditions must be controlled or measured. Use the submitted research question as a consistency anchor through the draft and final proposal. If the method or literature changes materially, update the question explicitly rather than letting sections drift apart. Generate three rival versions before selecting wording.
One can narrow the system or population, one can narrow the outcome and one can narrow the comparison or mechanism. For each version, list the evidence needed, independent unit, feasible data source, likely analysis, useful conclusion and principal limitation. This exposes whether apparent precision is only verbal.
Conduct a noun audit by defining every substantive term and a verb audit by asking what design would justify words such as affects, improves, predicts or causes. Replace value-laden outcomes such as better, sustainable or robust with observable indicators and explain why those indicators matter.
Then conduct an outcome-reversal test: both an increase and a decrease should be plausible answers unless a directional hypothesis is explicitly justified. Match scope to available access. If the desired field population cannot be sampled, decide whether a laboratory proxy answers a narrower question or merely resembles the topic. Do not hide a change in inference behind similar terminology.
Build a phrase-to-method table in which each question element maps to a measurement, comparison or boundary. Ask a teammate to find an element with no evidence path and a method step with no question role. Repair both directions. Revisit the literature after the question is drafted, searching directly for the chosen comparator and conditions to ensure the gap remains credible.
Preserve dated versions and reasons for changes so later sections do not retain an obsolete question. Before submission, write the strongest conclusion the planned evidence could support and the strongest conclusion it could not support. If that boundary feels disappointing, redesign or rescope now rather than overclaim later.
