03 · What You Need to Know
Research readiness is stage-specific
One reason researchers struggle to decide whether they are ready is that “starting the research” can mean several different things.
You may be ready to begin detailed protocol development without being ready to recruit participants. You may be ready to pilot an instrument without being ready to use it in the main study. You may be ready to seek data access without being ready to conduct the analysis.
A better question is:
Ready for what?
| Next stage |
What generally needs to be sufficiently ready |
| Detailed study design |
Research question, evidence requirements, broad feasibility, and methodological direction |
| Protocol development |
Broad design, population or evidence source, major procedures, and enough stability to make operational decisions |
| Formal review or approval |
The documents and decisions required by the responsible reviewing body |
| Recruitment |
Applicable approvals, eligibility, recruitment procedures, participant materials, access, and operational readiness |
| Main data collection |
Sampling or selection logic, instruments, procedures, data management, analysis-relevant decisions, quality procedures, and required authorization |
| Analysis |
Usable data, documented preparation, and an analytical approach appropriate to the question and design |
Readiness therefore moves with the project. You do not need to solve every problem that will arise six months from now before completing work that is safe and useful today.
The research question should be stable enough to organize the study
You are probably not ready to move into execution if the research question changes substantially every time you discuss the project.
The wording can still improve. The literature may later justify refinement. Exploratory methodologies may permit greater evolution than confirmatory designs.
What matters is whether the question is stable enough to determine what evidence is relevant and what kind of study you are actually building.
If changing the question would currently require changing the population, instruments, design, data source, and analysis all at once, the project may still be in foundational planning.
Return to the decisions that follow from settling the research question before committing heavily to downstream work.
You should be able to explain the path from question to evidence
A useful readiness test is surprisingly simple:
What evidence will answer the research question, where will that evidence come from, and how will the study allow you to interpret it?
If you cannot answer those questions without changing the subject to software, instruments, or statistical tests, more conceptual planning may be needed.
You should not necessarily have every procedure finalized at this point. You should have a defensible study logic.
For example, saying “I will use a survey because quantitative research is more objective” does not establish the necessary connection. Explaining that the question requires estimating particular characteristics or relationships in a defined population, that those constructs can be measured appropriately, and that a survey can feasibly obtain the required observations is much closer to a research design.
The study should pass a feasibility test before you make expensive commitments
A scientifically attractive design is not ready if it cannot realistically be implemented.
Before major commitments, check whether the necessary participants, cases, records, data, sites, equipment, expertise, software, funding, personnel, and time are plausibly available.
Feasibility should not be confused with certainty. You may not know exactly how many participants will respond each week. You should, however, have enough information to judge whether the recruitment target is plausible and enough contingency to respond if the estimate is wrong.
In some projects, important uncertainty cannot be resolved through planning alone. A pilot or feasibility study may be needed to examine whether recruitment, retention, procedures, intervention delivery, measurement, or other elements can work as intended. Methodological guidance for pilot and feasibility studies recommends defining relevant progression criteria prospectively so that evidence from preliminary work can inform whether a larger study should proceed, proceed with modification, or not proceed.
Do not wait for certainty where only empirical work can provide the answer
Planning has a natural limit.
You can debate whether potential participants will understand an instruction, but eventually pretesting may provide better information. You can estimate recruitment feasibility from records and stakeholder discussions, but a feasibility study may reveal what actually happens. You can speculate about whether a laboratory procedure will work reliably under field conditions, but at some point it needs to be tested.
When the remaining uncertainty is inherently empirical, another planning meeting may not reduce it.
The appropriate next step may therefore be a controlled test rather than more speculation.
Importantly, the test should match the uncertainty. If you are unsure about survey comprehension, pretest the survey. If you are unsure about recruitment, investigate recruitment feasibility. Do not automatically conduct a miniature version of the entire study merely because something remains uncertain.
Use explicit progression criteria when feasibility is genuinely uncertain
For projects requiring formal feasibility work, it can be useful to decide in advance what evidence would support progression.
Contemporary guidance for pilot and feasibility studies describes progression criteria as prospective benchmarks used to inform whether researchers should proceed, proceed with changes, or stop. Relevant criteria may concern recruitment, retention, acceptability, implementation or fidelity, and other study-specific feasibility issues.
This logic can be adapted cautiously beyond formal pilot trials.
Suppose your uncertainty is whether enough eligible participants can be recruited from one institution. Instead of vaguely “seeing how recruitment goes,” decide what recruitment performance would make the planned main study plausible and when that performance will be evaluated.
The criterion should be justified rather than selected merely because it produces the desired answer. Guidance on external randomized pilot trials recommends considering progression criteria early, connecting them to feasibility objectives, and interpreting them alongside contextual information rather than treating every threshold mechanically.
The decisions that determine what data will exist should no longer be vague
As you approach main data collection, the readiness threshold rises sharply.
You should know what population, cases, documents, records, specimens, or other sources of evidence the study concerns. Sampling or selection procedures should be sufficiently specified. Instruments and measures should be ready for their intended use. The information needed for the planned analysis should be represented in the collection process.
This is where the distinction between planning and recoverability becomes important.
If an unresolved decision can result in information never being collected, it probably should not remain unresolved when data collection begins.
Before crossing that boundary, review what needs to be fixed before data collection starts.
Ethical and institutional prerequisites are readiness conditions, not optional planning tasks
You are not ready for an activity that requires authorization if that authorization has not been obtained.
Depending on the project, this may include ethics approval, site permission, data-access authorization, contractual arrangements, regulatory requirements, participant consent procedures, or other institutional conditions.
The exact requirements vary substantially across jurisdictions, institutions, funders, data providers, and research settings. Verify them with the responsible authority rather than assuming that a study is exempt, that one approval substitutes for another, or that authorization can be obtained retrospectively.
Schedule pressure does not change the readiness criterion. If recruitment requires prior approval, the project is not ready to recruit merely because the planned recruitment date has arrived.
The data-management system should exist before the data need it
A study is not operationally ready if nobody knows where the first dataset, interview recording, field note, image, specimen record, or participant identifier will go.
Before relevant data are created or obtained, establish an appropriate system for storage, organization, identifiers, access, backup, documentation, security, and version control.
The sophistication should match the project. A small study may need a straightforward folder structure and data dictionary. A complex collaborative project may require controlled repositories, permissions, audit trails, data-transfer procedures, and formal governance.
The important point is that the system exists before researchers begin improvising one around accumulating files.
You should know enough about analysis to know that the study can answer its question
“We will decide how to analyze everything after we see the data” is rarely a strong readiness signal.
The required level of advance specification varies. Confirmatory research generally requires more prospective analytical decisions than exploratory work. Some qualitative methodologies deliberately integrate data collection and analysis and allow the analytical framework to evolve.
Still, you should understand how the intended evidence can be transformed into an answer.
If the planned analysis requires a comparison variable, time point, contextual measure, or particular form of data that is absent from the collection plan, you have discovered that the study is not ready.
Thinking about analysis before collection is therefore partly a quality-control exercise for the design.
Major responsibilities should have owners
Projects become operational when someone knows who is responsible for doing what.
You do not need a corporate organizational chart for a two-person study. You do need clarity about consequential responsibilities.
Who submits the ethics amendment if one becomes necessary? Who maintains the master participant list? Who has access to identifiable data? Who checks data quality? Who communicates with the research site? Who decides whether a protocol deviation requires escalation?
For a solo project, the answer may repeatedly be the same person. Writing the responsibilities down can still expose work that has not been planned.
Major dependencies should be resolved or actively controlled
A project may be methodologically ready but still unable to proceed because an important dependency remains uncertain.
You might be waiting for access to a dataset, approval from a school, delivery of equipment, confirmation from a collaborator, or availability of a laboratory.
Not every dependency must be completely resolved before any other work begins. The question is whether the unresolved dependency blocks the next activity.
If it does, either resolve it or redirect effort toward work that can legitimately proceed independently.
The principles for planning around ethics approval, recruitment, data access, and other dependencies can help distinguish a real blocker from something that merely remains unfinished elsewhere in the project.
A realistic timeline is part of readiness
You can have a strong research question, an excellent protocol, and an impossible schedule.
If a fixed deadline exists, check whether the remaining stages fit when realistic durations, review periods, dependencies, and contingency are included.
A study requiring six months of follow-up is not ready for a final deadline four months away merely because everything else is well designed.
If the timeline works only when ethics review is instantaneous, recruitment is perfect, no participant cancels, analysis reveals no problems, and the thesis requires no revision, the project is not realistically ready under those assumptions.
Use backward planning from the fixed deadline and protect important uncertainty with appropriate buffer time.
Not every unanswered question is a reason to wait
Research cannot begin only after uncertainty reaches zero. If that were the standard, research would have a rather serious business-model problem.
Some unanswered questions are expected:
- exactly which participants will agree to take part;
- what the data will eventually show;
- which unexpected qualitative themes may emerge;
- whether every scheduled interview will occur as planned;
- which minor operational adjustments will become useful;
- how many rounds of manuscript revision will ultimately be needed; or
- which exploratory analyses may become scientifically interesting.
These uncertainties are not equivalent to being unsure who is eligible, what the main outcome means, whether the data can answer the question, or whether participant activities have required approval.
The goal is not certainty. It is bounded uncertainty.
Classify what remains unresolved
When you are unsure whether to proceed, make a list of everything that is still open and classify each item.
| Remaining uncertainty |
Likely response |
| Affects the research question or intended claim |
Resolve before major downstream commitments. |
| Determines what evidence must be collected |
Resolve before the affected data are generated. |
| Affects participant rights, consent, privacy, or risk |
Resolve according to applicable ethics and institutional requirements before the relevant activity. |
| Controls access to a necessary site, dataset, or resource |
Resolve before the project becomes dependent on unavailable access. |
| Can be tested only through preliminary empirical work |
Consider appropriate piloting, feasibility work, or pretesting. |
| Is methodologically intended to evolve |
Preserve the flexibility and document its boundaries. |
| Concerns low-consequence logistics |
Allow it to remain flexible if it does not block the next stage. |
This classification is often more informative than asking whether the research plan feels finished.
Ask whether another round of planning has a specific expected benefit
Before postponing the next stage, ask:
What exactly will additional planning improve?
A useful additional planning cycle might:
- resolve a methodological inconsistency;
- confirm access to an essential data source;
- reduce participant risk;
- identify a missing variable;
- test whether recruitment is feasible;
- clarify an analysis decision;
- improve an instrument; or
- reveal whether the project fits the deadline.
If you can identify the expected benefit, more planning may be justified.
If the answer is simply “I might think of something else,” the expected return is less clear.
Watch for planning that repeatedly revisits settled decisions without new evidence
Another warning sign is that the project keeps reopening the same questions.
You compare two defensible instruments. Choose one. Reconsider it. Ask another colleague. Return to the first instrument. Search for three more. Repeat.
Reconsideration is appropriate when new evidence or constraints emerge. Reopening a decision without new information can become a form of decision avoidance.
A simple decision log can help. Record the options considered, evidence available, decision, rationale, assumptions, and what would justify revisiting the choice.
This makes it easier to distinguish responsible adaptation from circular planning.
Watch for low-consequence detail displacing high-consequence uncertainty
Researchers can spend considerable time perfecting parts of the project that are already adequate because those tasks feel controllable.
You may be refining citation formatting while access to the research site remains uncertain. Designing a sophisticated project dashboard while the sampling strategy is unresolved. Adjusting the wording of the fifth demographic item while nobody has confirmed whether the main outcome can be measured appropriately.
These tasks create activity without necessarily improving readiness.
When planning time is limited, prioritize decisions by consequence and dependency rather than by how satisfying they are to complete.
Watch for false precision
A plan can look finished because every box contains a number.
Ethics approval: 14 days.
Recruitment: 30 days.
Analysis: 10 days.
Writing: 21 days.
If those numbers are unsupported guesses, the plan has become precise without becoming more credible.
Where duration is uncertain, use ranges, assumptions, milestone conditions, or contingency rather than pretending that uncertainty has been eliminated.
A realistic plan can contain uncertainty and still be ready.
Watch for planning that is no longer changing action
Planning is useful when it changes what you will do.
If the fifth revision of the workflow produces exactly the same study as the fourth, the additional planning may have little practical value. If another literature search identifies no information likely to alter the design, continued searching may have diminishing returns for the current decision.
This does not mean the literature review ends permanently. Researchers continue reading throughout many projects. It means you do not need exhaustive knowledge of everything ever published before taking the next justified step.
Use a readiness gate rather than waiting for a feeling of certainty
For consequential transitions, establish explicit readiness conditions.
Before main data collection, for example, your gate might require:
Scientific readiness The research question, design, evidence requirements, sampling logic, instruments, and analysis-relevant decisions are sufficiently settled.
Ethical readiness Applicable review, consent, participant-protection, privacy, and other requirements are satisfied.
Operational readiness Access, staff, equipment, systems, procedures, and responsibilities are ready.
Data readiness Storage, identifiers, documentation, access control, quality procedures, and backup arrangements are operational.
Schedule readiness The remaining project fits the available time with realistic assumptions and appropriate contingency.
If those conditions are satisfied, continuing to postpone the study because some minor uncertainty remains may not improve the research.
Use stop, revise, or proceed as legitimate outcomes
Readiness assessment does not need to produce only “start” or “do not start.”
Formal pilot and feasibility research often uses progression logic that distinguishes proceeding, proceeding with modifications, and not proceeding. Contemporary guidance recommends setting relevant criteria in advance while considering contextual information rather than treating thresholds as automatic rules.
A similar structure can help ordinary project planning:
Proceed
The consequential requirements for the next stage are satisfied and remaining uncertainty is acceptable.
Proceed after revision
The study is broadly viable, but a specific problem should be corrected before the next consequential activity.
A third possibility is to stop or substantially redesign the project when a foundational requirement cannot be satisfied. That can be the scientifically responsible outcome of planning rather than evidence that planning failed.
Do not lower the readiness threshold because the deadline is close
Deadlines create a dangerous temptation: if the study is not ready on the planned date, redefine “ready.”
An unresolved ethics requirement becomes “probably fine.” An unfinished instrument becomes “good enough.” A missing data-access agreement becomes “we will sort it out later.” An unrealistic recruitment period becomes “we will recruit faster.”
That is not adaptation. It is transferring schedule pressure into scientific or ethical risk.
Watch Out
If the project is not ready for a consequential activity by the date originally planned, revise the timeline, scope, resources, design, or other legitimate assumptions. Do not make the study appear ready by relaxing requirements that exist to protect participants, preserve methodological integrity, or ensure that the evidence can answer the research question.
Once the readiness conditions are met, start
There is a point at which planning has done its job.
The question is coherent. The design is defensible. The required evidence is understood. The study is feasible. Consequential procedures are documented. Required approvals and access are in place. Data-management arrangements exist. Responsibilities and dependencies are clear. The timeline remains plausible.
Some uncertainty remains because research has not yet happened.
That is not a planning defect.
At that point, the next useful information may come only from doing the research.