Design-Based Research — Educational Design Experiment
Design-Based Research · Also known as: DBR, design research, design experiment, educational design research
Design-based research (DBR) is an iterative, interventionist methodology that simultaneously designs educational interventions and builds theory about how and why those interventions work in authentic, complex settings. Originating in Ann Brown's 1992 classroom experiments and Allan Collins's parallel work, DBR treats the learning environment as both the object of study and the site of theory generation, cycling through design, enactment, analysis, and redesign until both practical improvement and theoretical insight are achieved.
Read the full method
Sign in with a free account to read this section.
Method map
The neighbourhood of related methods — select a node to explore.
+10 more
When to use it
Use DBR when you want both to improve an educational or social intervention and to build theory about why the intervention works. It is most appropriate when existing theory is insufficient to specify a solution in advance and when the complexity of the learning environment must be preserved rather than controlled away. DBR is well-suited to technology-enhanced learning, curriculum development, professional development programs, and community-based educational initiatives. Do NOT use DBR when you need a clean causal estimate of intervention effects under controlled conditions (use a randomized controlled trial instead), when you have a very short timeline (each iteration takes months), when practitioner collaboration is not feasible, or when the research question is purely descriptive or theoretical rather than design-oriented.
Strengths & limitations
- Produces both practical improvements to real educational settings and transferable theoretical principles simultaneously.
- Preserves the complexity and authenticity of real learning environments that laboratory experiments strip away.
- Iterative design cycles allow the researcher to respond to unexpected findings rather than being locked into a pre-specified protocol.
- Practitioner involvement in design and enactment increases the relevance and uptake of findings.
- Generates design principles that travel across contexts, making findings applicable beyond the original setting.
- Findings are context-sensitive; the extent to which design principles generalize to very different settings requires additional studies.
- Multiple iterations across one or more school years make DBR extremely time- and resource-intensive.
- The absence of a control group makes it difficult to attribute outcomes solely to the intervention rather than to other contextual factors.
- The dual role of the researcher as both designer and evaluator introduces potential bias that must be actively managed.
Frequently asked
How is DBR different from action research?
Both methods are interventionist and iterative, but they differ in emphasis. Action research is primarily practitioner-led and focuses on solving a local problem for a specific community; its primary audience is the practitioners themselves. DBR is researcher-led and aims to generate theoretical principles that extend beyond the local setting; its primary audience includes the broader research community. DBR also places more emphasis on explicit theory-building through conjecture maps and design principles.
How many iterations are required?
There is no fixed number, but two to five iterations are common in published DBR studies. The criterion is theoretical saturation rather than a count: iterations continue until the design has stabilised, the mechanisms are understood well enough to articulate transferable principles, and new iterations are no longer revealing new theoretical insights.
Can DBR produce causal claims?
DBR can produce strong explanatory claims about mechanisms — how and why an intervention produces its effects — but without a randomized control group it cannot produce unconfounded causal estimates in the statistical sense. If the goal is to establish effect sizes or pass a regulatory threshold, a randomized controlled trial should follow a DBR phase that has identified and refined the intervention.
What is a conjecture map and is it mandatory?
A conjecture map (Sandoval, 2014) is a visual or written representation of the theoretical assumptions linking design features to learning outcomes through mediating processes. It makes the theory-to-design connection explicit so it can be tested and refined. While not all DBR publications use this exact term, making the theoretical conjectures explicit in some form is considered essential to distinguishing DBR from mere iterative development.
Is DBR only for educational research?
DBR originated in educational research and the large majority of published studies are in that field. However, the core logic — design an intervention grounded in theory, enact it in an authentic setting, analyze outcomes and mechanisms, refine the design and the theory iteratively — has been applied in health promotion, library science, and organizational development contexts under various labels including design science research and intervention research.
Sources
- Brown, A. L. (1992). Design experiments: Theoretical and methodological challenges in creating complex interventions in classroom settings. Journal of the Learning Sciences, 2(2), 141–178. DOI: 10.1207/s15327809jls0202_2 ↗
- Design-Based Research Collective. (2003). Design-based research: An emerging paradigm for educational inquiry. Educational Researcher, 32(1), 5–8. DOI: 10.3102/0013189X032001005 ↗
How to cite this page
ScholarGate. (2026, June 3). Design-Based Research. ScholarGate. https://scholargate.app/en/field-methods/design-based-research
Which method?
Set this method beside its closest kin and read them side by side — the library lays the books on the table; the choice is yours.
- Action ResearchQualitative Research↔ compare
- Case StudyQualitative↔ compare
- Educational Action ResearchField Methods↔ compare
- Lesson StudyField Methods↔ compare
- Participatory Action ResearchQualitative↔ compare
- Program EvaluationField Methods↔ compare