Mapping Where Human-Centred Design Meets Implementation Science in Public Health
Public health research is increasingly being asked to do two difficult things at once: produce interventions that people will actually use and deliver them in systems that can sustain them. The BMJ Open protocol for a scoping review addresses that overlap directly by examining the combined use of human-centred design and implementation science across public health research. The focus is not on a single disease area or one intervention class. It is on how two complementary frameworks are being joined, where they converge, and where the field still lacks a common operating language.
The need for that map is straightforward. Human-centred design begins with the lived experience of users, patients, providers, and communities, then shapes solutions around real-world needs, preferences, and constraints. Implementation science asks a different but equally practical question: once an intervention exists, how does it move into routine practice, what helps it spread, and what blocks it from taking hold? When these approaches are separated, one can produce elegant but unusable interventions, while the other can optimize delivery of tools that never fit the people expected to use them.
This protocol treats that tension as a research problem rather than a philosophical one.
Why the Combined Framework Matters for Public Health Delivery
The protocol is built around the reality that public health challenges rarely fail because of biology alone. They fail because programs do not fit clinic workflows, community settings, staffing patterns, cultural expectations, or the practical pressures of everyday life. A design process centered on end users can surface barriers early, while implementation science can test whether those design choices actually help a program survive contact with real systems. In theory, combining the two should improve both acceptability and adoption. In practice, the literature appears to be fragmented enough that researchers need a structured review simply to understand how the combination has been used.
The review is designed as a scoping exercise, which is the right tool for a field still trying to define its boundaries. Rather than answering a narrow efficacy question, it will chart the range of study types, health contexts, and conceptual approaches used when the two frameworks appear together. That kind of synthesis is especially useful in public health, where the same design principles may be applied to vaccination delivery, chronic disease prevention, digital health tools, maternal health programs, or community-based services, yet described with different terminology from one paper to the next.
One sentence captures the practical stakes: interventions that ignore users rarely survive implementation.
Search Breadth, Study Diversity, and the Limits of a Scoping Approach
The protocol emphasizes a comprehensive search strategy spanning multiple databases and supplementary sources, which should improve capture across diverse health contexts. Broad inclusion of study types is equally important here. A field combining human-centred design and implementation science is unlikely to be represented by one clean study format alone. Qualitative projects, mixed-methods studies, pilot interventions, design studies, and implementation-focused evaluations may all contribute pieces of the same conceptual puzzle.
The data charting form draws on established constructs and definitions, a method intended to keep extraction consistent across reviewers and reduce ambiguity over what qualifies as relevant evidence. In a space where terminology can shift from article to article, that operational clarity matters. Human-centred design can appear under related labels such as participatory design, co-design, or user-centered design, while implementation science may be embedded in frameworks of adoption, feasibility, fidelity, reach, or sustainment. Without disciplined charting rules, a review can become a loose anthology instead of a usable evidence map.
Still, the protocol acknowledges two clear constraints. English-language restriction can exclude relevant work and introduce language bias, and limiting the review to peer-reviewed articles may leave out meaningful practice-based or grey literature contributions. Those limits are especially relevant in public health, where community innovation often emerges outside traditional journals and where local implementation experience may be published unevenly across regions and languages.
What the Review Can and Cannot Tell Us
Because this is a scoping review protocol, it does not assess the quality of the eventual included studies. That choice is methodologically appropriate for an early-stage evidence map, but it also means the final review will describe how the combined approach is being used more than it will judge how well the underlying studies were executed. Readers will learn where the field is active, which health problems are most often addressed, and what kinds of design and implementation concepts are paired together. They will not get a formal estimate of comparative effectiveness or a risk-of-bias ranking for each study.
The absence of quality appraisal is not a flaw so much as a statement about the review’s purpose. Scoping reviews are meant to clarify scope, identify patterns, and expose gaps. In this case, the gap may be conceptual as much as empirical. If human-centred design is often used to shape intervention development, but implementation science is not always integrated from the start, then the literature may be revealing a sequence problem: programs are designed first and implemented later, instead of being built with delivery constraints in mind from the outset.
In public health systems, that sequencing can determine whether an intervention scales or stalls.
A Field Searching for Shared Vocabulary
The most useful contribution of this protocol may be its attempt to organize a literature that is probably more dispersed than it first appears. Researchers working in implementation science may describe a process through constructs like adoption, feasibility, acceptability, or maintenance. Design-oriented teams may frame the same work around empathy, co-creation, iteration, and user needs. Both traditions aim to reduce the gap between an idea and its real-world use, but they do so with different methods and different vocabularies. A scoping review that tracks those overlaps can make the field easier to navigate for investigators, funders, and practitioners who need to know not just whether work exists, but how it has been conceptualized.
The broader implication is clinical and operational rather than abstract. Public health programs that are designed without real users in mind often struggle during rollout, while implementation strategies that ignore design can optimize a process nobody wants to engage with. Bringing the two together may help close that gap, but only if the field can describe the combination consistently enough to study it well. This protocol is a step toward that clarity, although the final review will still inherit the limits of the literature it can access, the English-only search boundary, and the absence of formal study-quality appraisal.