Is the Study Feasible With the Expertise Available to You?

Does Someone on the Project Actually Know How to Do What the Study Requires?

A research design can look entirely feasible until its individual tasks are translated into capabilities.

Who can validate the measurement model? Who understands the clinical procedure? Who can build the computational pipeline, conduct interviews in the required language, manage sensitive linked data, implement the intervention consistently, or diagnose why the planned statistical model is behaving strangely?

You do not need to be personally expert in every component. Modern research is often collaborative precisely because worthwhile questions cross methodological, disciplinary, technical, and contextual boundaries. The relevant question is whether the project has access to the expertise needed to conduct and interpret the work properly.

This is sufficiently consequential that the current NIH Simplified Review Framework evaluates investigator expertise and institutional resources as a distinct factor, asking whether the investigators and environment provide what is necessary to carry out the proposed project.

Expertise Is Feasible When Every Critical Capability Has a Credible Owner

How Do You Determine What Expertise the Study Actually Requires?

Research feasibility frameworks commonly include expertise among the practical conditions of a workable research question. FINER-based guidance, for example, treats technical expertise, available personnel, institutional support, time, and other resources as part of feasibility.

The challenge is that expertise gaps are often invisible during proposal writing. You usually notice what you know. You may not notice the decisions that require knowledge you do not yet possess.

Translate the Protocol Into Capabilities

Instead of asking broadly, “Do I have enough expertise?”, decompose the proposed study.

If you plan to conduct multilingual interviews, someone must understand the substantive topic, qualitative interviewing, the relevant languages, and how translation choices affect interpretation. If you propose a multilevel longitudinal model, someone needs sufficient expertise to specify, diagnose, interpret, and defend that analysis. If the study uses institutional administrative data, expertise may be needed in data governance, linkage, domain-specific coding, and the processes that generated those records.

Every critical methodological choice should eventually correspond to a capability available somewhere on the project.

Substantive Expertise and Methodological Expertise Solve Different Problems

Knowing a research domain extremely well does not automatically make someone proficient in every method used to investigate it. The reverse is equally true.

Strong research often requires both. A sophisticated analysis cannot compensate for misunderstanding the phenomenon, while deep subject expertise does not guarantee that the analytical strategy supports the intended claim.

Technical Expertise May Be Separate Again

Some studies require capabilities that are neither purely substantive nor conventionally methodological.

Examples include laboratory procedures, database engineering, software development, natural language processing, geographic information systems, secure computing, imaging, instrumentation, transcription systems, digital trace extraction, or management of complex research platforms.

Do not assume that familiarity with the conceptual method implies operational ability to implement its technical infrastructure.

Contextual and Population Expertise Can Affect Research Quality

A research team may understand the theory and statistics while lacking knowledge of the population or setting being studied.

This matters when language, institutional structures, professional practice, community norms, accessibility needs, cultural meaning, or lived experience influence recruitment, measurement, intervention delivery, interpretation, or ethics.

Relevant expertise may come from local collaborators, practitioners, community partners, or members of the population rather than conventional academic credentials alone.

Ask Whether Expertise Is Needed for Execution or Only Advice

A one-hour consultation may be enough to clarify a narrow issue. It is not equivalent to having someone capable of supporting a complex method throughout the project.

Suppose a statistician helps select a model during proposal development. Who will assess model diagnostics after data collection? Who will decide what to do if assumptions fail? Who will interpret sensitivity analyses? If the method is central to the study, occasional advice may be insufficient.

Determine when each expertise is needed, for how long, and at what depth.

Do Not Leave Specialist Input Until the End

Some expertise must enter before data collection because it shapes what data should be generated.

Consulting a statistician after collecting the data cannot retroactively repair an inadequate design. Asking a measurement specialist after administering an inappropriate instrument may reveal the problem but cannot recreate the missing evidence. Bringing in a qualitative methodologist after poorly conducted interviews may similarly arrive too late.

Research-question guidance recommends early consultation when specialist methodological input can influence design and resource requirements.

Training Can Close Some Expertise Gaps, but Not Instantly

Learning a new method is a legitimate part of research. Student projects in particular are expected to involve intellectual development.

The question is whether the skill can be developed to the necessary level within the available time and with appropriate supervision. Learning basic use of unfamiliar software may be realistic. Becoming independently competent in a technically demanding laboratory procedure, advanced causal method, or new language shortly before data collection may not be.

Include training in the actual study timeline. “I will learn it” is a plan only after the learning requirements, support, and time have been considered.

Collaboration Can Make a Study Feasible

A gap in your personal expertise does not imply that the research idea should be abandoned. It may indicate that the study requires a collaborator.

The collaborator could contribute statistical, qualitative, clinical, technical, disciplinary, implementation, or contextual expertise. Current NIH review guidance similarly focuses on whether the investigative team collectively has the background, training, and expertise appropriate to the proposed work, rather than expecting one investigator to embody every capability.

The collaboration must nevertheless be real. Naming someone who has not agreed to participate or assuming that specialist help can be found later does not close the feasibility gap.

Expertise Includes the Ability to Interpret the Result

Research capability does not end when an analysis successfully runs.

A team needs enough knowledge to understand what the evidence does and does not support. This can require domain knowledge, statistical reasoning, methodological judgment, awareness of measurement limitations, and familiarity with alternative explanations.

A technically correct output can still be interpreted badly. Expertise should therefore cover the full chain from design through interpretation, not merely operation of instruments or software.

Project Management Expertise Can Matter in Complex Studies

Multi-site studies, large teams, repeated measurements, complex data flows, interventions, and projects with many external dependencies may require substantial coordination.

Someone must manage version control, schedules, site communication, protocol adherence, data transfer, documentation, personnel responsibilities, and emerging problems. NIH reviewer guidance likewise asks whether teams demonstrate appropriate expertise for the proposed project and the capacity for successful project management and execution.

A scientifically brilliant team can still struggle if nobody owns the operational work needed to turn the design into a completed study.

Do Not Confuse Reputation With Relevant Expertise

A famous collaborator does not necessarily fill the capability your project lacks. Neither does being at a prestigious institution.

Current NIH review policy deliberately evaluates expertise and resources in relation to the work proposed, partly to reduce the influence of general reputation on judgments of research merit.

Use the same principle in your own planning. Ask what the study requires and who can do it, rather than who has the longest curriculum vitae.

When the Proposed Method Exceeds the Expertise Currently Available

The expertise audit improves more than feasibility. It can also simplify the study by revealing methods that were impressive on paper but unnecessary for answering the question.

What Can Hide an Expertise Gap Until It Is Too Late?

Create an Expertise Map Before Finalizing the Methods

Break the study into major decisions and operations. For each one, identify the capability required, the person who will provide it, when that person must become involved, and whether their availability is confirmed.

Any critical task with “learn later,” “ask someone,” or “find collaborator” beside it should remain marked as a feasibility risk until the pathway becomes concrete.

Expertise also interacts with resources. A collaborator may require funding, specialized equipment may require trained personnel, and external analytical services may carry substantial costs. Once the capability map is credible, examine whether the resources and budget can realistically support it.

Does the Study Have Access to Every Critical Capability?

Questions About Expertise and Research Feasibility

You Do Not Need Every Skill Yourself, but the Study Needs Every Skill Somewhere

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.