01 · The Question
Should the Risk of Not Finishing Change the Research Question You Choose?
Imagine two research questions. The first is intellectually exciting but requires permission from several organizations, successful recruitment of a difficult population, access to restricted data, and a method you have not yet learned. The second addresses a somewhat more bounded version of the same problem using evidence you can realistically obtain.
Should the possibility of completing the project influence which question you choose?
Yes, but this principle can be taken too far. Designing for completion does not mean choosing the easiest available topic or avoiding uncertain findings. Research necessarily contains uncertainty. The important distinction is between uncertainty that makes the inquiry intellectually valuable and dependencies that can prevent the inquiry from happening at all.
03 · What You Need to Know
Not All Research Risk Is the Same
Separate intellectual risk from completion risk
Some risk belongs at the heart of research. You may not know whether a hypothesis will be supported, whether a proposed explanation will survive analysis, what themes will emerge from qualitative material, whether an intervention will have the expected effect, or whether historical evidence will sustain an interpretation.
That uncertainty is often precisely why the research is worth doing.
Completion risk is different. It concerns whether you will be able to conduct enough of the planned research to answer the question credibly in the first place.
Intellectual uncertainty
You do not know what answer the evidence will support.
Completion risk
You may be unable to obtain or analyze the evidence required to produce a defensible answer.
A good project preserves the first while managing the second.
Research questions contain hidden dependencies
Every question implies a chain of conditions. If you ask about a difficult-to-reach population, you need a credible recruitment route. If you ask about several institutions, you need access to them. If you ask about a proprietary dataset, somebody must provide it. If you ask a technically demanding question, the required expertise and infrastructure must be available.
The more essential conditions that sit outside your control, the more fragile the project can become.
Dependency
Possible failure
Effect on the question
Participant recruitment
Too few eligible participants enroll
Planned comparisons or analyses may become untenable
Organizational access
Permission is delayed, restricted, or withdrawn
The intended setting or data may disappear
External dataset
Access agreement fails or data arrive incomplete
Central variables or analyses may become unavailable
Specialist expertise
Required support is unavailable
The planned analysis or procedure may not be executable defensibly
Longitudinal participation
Attrition is substantial
Planned temporal comparisons may weaken or fail
Equipment or software infrastructure
Access, reliability, or technical support fails
Data generation or analysis may be interrupted
Multiple linked studies
An early study is substantially delayed
Later studies dependent on it may also be delayed
A risk matters most when it is both likely and consequential
Not every possible problem deserves redesigning a thesis around it. A useful risk assessment considers at least two dimensions: how plausible the failure is and what happens to the research question if it occurs.
A minor scheduling delay that can be absorbed is different from losing the only organization capable of supplying the data. Likewise, difficult recruitment is more concerning when the question requires a precise comparison between several groups than when the design has credible alternatives.
Rather than asking, “Could something go wrong?”, ask: Which plausible failure would make the central question unanswerable?
Single points of failure deserve special attention
A single point of failure is an essential component with no workable substitute. Student research can accumulate these surprisingly quickly.
Suppose your question can only be answered if one company grants access to proprietary records. Until access is secure, the entire study rests on one decision made by somebody outside the research team. This does not automatically make the project unacceptable, but it should affect how you evaluate feasibility.
Where possible, consider whether dependence on one external organization can be reduced before the question is finalized.
Recruitment failure should be considered at question-design stage
Researchers commonly treat recruitment as an implementation problem. Yet the question itself may determine how vulnerable the study is to recruitment failure.
A question requiring three rare participant groups and adequate numbers in each has a different risk profile from one whose central contribution can still be investigated if one recruitment channel underperforms.
Where human participation is central, ask whether the research question can survive plausible recruitment failure . This does not mean weakening sampling standards after recruitment goes badly. It means designing a project whose intellectual core is not unnecessarily dependent on a fragile recruitment assumption.
Existing data can sometimes reduce completion risk
When appropriate data already exist and are legitimately accessible, secondary analysis may remove months of recruitment, data collection, and participant attrition. That can substantially change the project's risk profile.
But existing data are useful only when they can answer the question. A convenient dataset should not dictate a question for which its measures, sampling, provenance, or quality are inadequate.
The decision about using existing rather than collecting new data should therefore compare evidentiary suitability as well as logistical convenience.
Unavailable expertise is a form of completion risk
A project may have accessible data and still be fragile because its central analysis depends on expertise the researcher does not possess.
Learning new methods is a normal part of research training. The issue is degree rather than novelty. If the thesis requires highly specialized statistical modelling, laboratory procedures, languages, archival skills, software engineering, or qualitative methodologies, ask whether adequate training and supervision can be obtained within the project timeline.
If not, a question that depends on unavailable expertise may need redesign rather than optimism.
Time risk accumulates quietly
Researchers often estimate how long the research activity itself will take while underestimating everything around it. Ethics review can require revisions. Contracts and data agreements can move slowly. Recruitment may need several rounds. Data require cleaning. Analyses fail. Software behaves with its customary respect for deadlines.
Then the thesis still has to be written, reviewed, revised, formatted, submitted, and possibly defended.
A project that fits the calendar only if every stage proceeds at its optimistic estimate is not necessarily feasible. Completion planning should include plausible delays rather than treating contingency time as unused space.
Risk tolerance should differ between a thesis and a large research program
A funded research team may be able to absorb the loss of one site, replace staff, extend recruitment, purchase specialist support, or reallocate resources. A student often has fewer substitutes and a fixed degree timeline.
That is why a good student research question should not simply imitate the architecture of a large research project . The same dependency may have very different consequences when one student rather than a research program carries it.
Prioritizing completion does not mean minimizing difficulty
The opposite mistake is to optimize so aggressively for completion that the question loses scholarly value. A project whose answer is already obvious, whose analysis is routine, or whose contribution is negligible may be safe but inadequate.
The objective is therefore not minimum risk. It is a favorable relationship between scholarly value and avoidable completion risk.
Sometimes an ambitious project deserves its risk because the additional design element is essential to the contribution. Sometimes the same scholarly question can be answered through a simpler and more robust architecture. In that case, complexity needs a reason to survive.
04 · A Practical Example
When an Excellent Question Depends on Too Many Things Going Right
Hypothetical Example
A thesis dependent on several schools
A master's student wants to compare the effects of a new digital learning intervention across public and private secondary schools. The proposed design requires six schools, teacher participation, student recruitment, pre-intervention testing, an eight-week implementation, post-testing, and access to school records.
The research question is worthwhile, and none of these requirements is inherently unreasonable. The problem is that several are essential. If too few schools agree, one comparison may collapse. If school records cannot be shared, a planned outcome disappears. If implementation is delayed, the academic calendar may no longer permit completion.
Map the dependencies The student identifies institutional permission, teacher participation, student recruitment, record access, intervention timing, and follow-up testing as essential or potentially essential conditions.
Identify single points of failure The public-versus-private comparison requires successful recruitment in both sectors. Losing either group makes the original central question impossible to answer.
Protect the intellectual core The student determines that the central scholarly interest is the relationship between the intervention and a defined learning process, while sector comparison is useful but secondary.
Redesign the question The primary question is reframed around the central phenomenon within accessible schools, with institutional differences treated as a possible secondary analysis only if sufficient data are obtained.
Preserve methodological standards The revised plan defines in advance what evidence is required for the primary analysis rather than weakening criteria after recruitment outcomes become known.
The revised study may look less expansive, but its central contribution is more resistant to foreseeable operational failure. Importantly, this is not the same as changing the research question after seeing inconvenient results. The contingency is built into the research architecture before the evidence is collected.
06 · What This Means for You
Choose a Question That Can Tolerate Foreseeable Setbacks
Before committing to a research question, translate it into its essential dependencies. Then distinguish conditions you control, conditions you can influence, and conditions controlled almost entirely by other people or organizations.
A simple decision framework
If an essential resource is already secured and stable
Treat it as a relatively low operational risk while still considering plausible disruptions.
If an essential component depends on uncertain external approval
Secure it before committing fully or redesign the question so an alternative route remains possible.
If recruitment is difficult but several credible recruitment pathways exist
Plan those pathways in advance and determine what minimum evidence the design requires.
If one plausible failure makes the entire question unanswerable
Treat that dependency as a major design risk and investigate whether the question can be made more robust.
If reducing risk would also remove the project's meaningful contribution
Do not automatically simplify. Evaluate whether the contribution justifies the risk and whether additional support or contingency can make it manageable.
A useful exercise is to ask what you would do tomorrow if the project's most important external dependency disappeared. If the only answer is “choose a new thesis,” you have identified a substantial single point of failure.
You can also identify the minimum viable research question that would remain defensible . This is not necessarily the question you should pursue from the outset. It shows which parts of the project carry the contribution and which parts provide optional expansion.
Watch Out
Contingency planning must not become post hoc manipulation. Decide legitimate alternatives before problems arise where possible, document consequential changes, preserve methodological standards, and obtain any required supervisory, ethical, preregistration, or institutional approvals.
07 · A Quick Checklist
Stress-Test Completion Risk Before You Commit
Before finalizing the research question, check:
List every participant group, organization, dataset, site, approval, technology, and specialist resource essential to answering the question.
Identify which essential dependencies remain outside your direct control.
Ask what happens to the central question if each major dependency fails.
Verify important access and permissions rather than relying only on expressions of interest.
Develop credible recruitment or data alternatives where the design permits them.
Confirm that essential methodological expertise and technical support will be available when needed.
Budget time for approvals, failed recruitment attempts, data cleaning, analysis problems, writing, revision, and other realistic delays.
Distinguish intellectually valuable uncertainty from logistical fragility that contributes nothing to the research question.
Confirm that reducing completion risk has not reduced the project below the scholarly expectations of the degree.
11 · Cite this Guide
How to Cite This Guide
This guide is intended to be read, shared, and used in research, teaching, and academic work. If you draw on its ideas, explanations, or other content, please acknowledge the source by citing the guide. Doing so gives appropriate credit and helps your readers locate the original resource.
Recommended (Field Guide)
APA
MLA
Chicago
Copy Citation