Skip to content
Back to search results

Action Research

Introduced by
Kurt Lewin; expanded by Kemmis, McTaggart, Reason & Bradbury
Year
1946
Type
Method
Family
change-oriented-collaborative
Font size

What does it do?

Action research is a collaborative research methodology in which researchers work with practitioners and community members to investigate a problem, implement change, and evaluate outcomes, cycling through reflection, action, and learning.

Developed by Kurt Lewin (1946), action research bridges research and practice, aiming simultaneously to produce knowledge and practical improvement.

The intuition behind the method

Action research rejects the notion that research must be detached from the world being studied. Instead, researchers collaborate with people experiencing a problem to understand it, develop solutions, test them, and refine approaches based on what is learned. The process is iterative: Plan—Act—Observe—Reflect—Re-plan. Each cycle generates both practical improvements (better processes, solutions) and research knowledge. Key features are: collaboration (practitioners are co-researchers, not merely subjects), cyclical inquiry (multiple iterative cycles of testing and refining), reflexivity (continuous examination of what works and why), and democratization (those affected by the problem participate in investigating it and deciding solutions). Action research is powerful for addressing real-world problems, building capacity, and generating evidence about what works in specific contexts.

History

Kurt Lewin (1946) introduced action research as a way to address social problems through collaborative inquiry and democratic participation. It gained prominence in education (Stenhouse 1975, Kemmis & McTaggart) and became central to participatory approaches in development work and community health. Reason and Bradbury (2006) expanded action research to include diverse participatory and collaborative traditions. Contemporary action research often incorporates critical perspectives, examining power and social structures. AR has become central in implementation science, quality improvement (Plan-Do-Study-Act cycles), and organizational development.

When to use it

Use action research when seeking to address a real-world problem or improve a practice through systematic inquiry and collaborative testing. Ideal for quality improvement in healthcare, organizational change initiatives, educational innovation, or community development. AR is particularly valuable when you want to generate evidence about what works in your specific context (rather than generalizable knowledge alone), when you need to build stakeholder engagement and ownership, or when you want to democratize research by including those affected in the investigation. AR is less suited for research seeking to generalize findings across contexts or for sensitive investigations where researcher neutrality is essential.

Limitations and considerations

  • Limited generalizability; solutions tested in one context may not work elsewhere due to different conditions, cultures, or constraints.
  • Collaborative process can be slow and politically complex; balancing researcher and practitioner priorities, managing group dynamics, and building consensus take time.
  • Potential for bias and conflicts of interest; when researchers work closely with organizations, maintaining objectivity and independence can be challenging.
  • Difficulty isolating the effect of the intervention; in real-world settings, many factors change simultaneously, making it hard to determine what caused improvement.

Source conditions do not replace independent scientific review or validation by an analysis engine.

Strengths

  • Generates contextually relevant, actionable knowledge; solutions developed in specific settings are more likely to be feasible and sustainable.
  • Builds practitioner and community engagement; co-researchers develop ownership of findings and are invested in implementing change.
  • Produces both knowledge and practical improvement; AR is efficient, advancing understanding while simultaneously solving problems.
  • Cyclical design enables learning and refinement; multiple iterations allow solutions to evolve based on evidence.

Applications

  • Healthcare quality improvement: action research cycles testing and refining new patient communication protocols, hand-hygiene practices, or care coordination processes.
  • Educational innovation: teachers collaboratively investigating student engagement or literacy challenges, testing classroom interventions, and refining approaches.
  • Community health: participatory action research engaging community members in investigating health disparities and co-designing culturally relevant health promotion strategies.
  • Organizational change: action research supporting organizational restructuring, culture change, or new system implementation, with staff engaged as co-researchers.
  • Workforce development: action research in training programs examining what instructional approaches work, with educators and learners engaged in inquiry cycles.

How it works

How it works

1

Identify a problem or opportunity for improvement in partnership with those experiencing it (e.g., a healthcare unit seeking to improve patient communication, a school addressing bullying). Form a collaborative research team including researchers, practitioners, and ideally community members affected by the issue. Clarify the research question and desired change together. Conduct initial exploration: interviews, focus groups, review existing data, and environmental analysis to understand the problem in context. Document the baseline situation (current practices, outcomes, challenges). Establish measurable goals for change. Set up regular meeting structures for the collaborative team to maintain partnership.

2

Plan the first action cycle: identify what will be tested, who will do it, when, and how. Implement the action or intervention, documenting what happens (field notes, observations, data collection). Observe and collect data on processes and preliminary outcomes: How did the change go? What worked? What barriers arose? What unintended consequences? Conduct systematic data collection alongside action: interviews with those involved, quantitative metrics (if relevant), document review, observations. Reflect: the team meets to examine what happened, why, and what was learned. Use structured reflection: What was intended? What actually happened? Why the difference? What did we learn? Analyze data collected during the cycle. Refine understanding and decide what to adjust for the next cycle. Re-plan: modifications to the action based on learning, then another cycle begins. Repeat cycles until the change is adequately refined or embedded; typically 3–5 cycles over months or years.

3

Synthesize learning across cycles: what was discovered about the problem and what solutions work? Present findings showing the evolution of understanding and action across cycles. Document both successes and setbacks, analyzing what contributed to each. Present outcome data: Did the change improve the situation as measured by agreed-upon indicators? Describe the change process: how did the problem and solution evolve? What conditions enabled success? What barriers persisted? Discuss implications for scaling or sustaining the change. Reflect on the research process itself: How did collaboration affect the research? What did researchers learn about working with practitioners? Present recommendations for ongoing practice and future improvement cycles.

Common pitfalls

  • Insufficient reflection; cycles that include action without structured reflection miss the learning opportunity.
  • Unequal collaboration; if researchers dominate or practitioners are token participants, it is not truly collaborative and may reproduce power imbalances.
  • Focusing only on action without generating research knowledge; action research should contribute both practical and theoretical learning.
  • Lack of systematic data collection; anecdotal observations are not enough; systematic data (quantitative and qualitative) strengthen action research.

Frequently asked questions

What is the difference between action research and quality improvement (QI)?

Action research and quality improvement (e.g., Plan-Do-Study-Act cycles) are closely related and share cyclical approaches. QI is more narrowly focused on improving specific metrics or processes; AR is broader, aiming to understand a problem and generate knowledge alongside practical improvement. AR emphasizes collaboration and democratization more explicitly; QI may be more top-down. Both involve cycles of action and learning. Some consider QI a form of action research; others view them as related but distinct. Distinctions matter less than ensuring your project is rigorous: has clear aims, involves relevant stakeholders, collects data systematically, reflects regularly, and documents learning.

How many cycles of action should I conduct?

There is no fixed number. Typically, 3–5 cycles over 6–18 months allow sufficient learning and refinement. Early cycles test initial ideas and generate unexpected insights; later cycles refine based on learning. The process is complete when the solution is adequately refined, outcomes are stable or improving, and insights are sufficient to answer research questions or guide ongoing practice. Document when and why cycles end.

How do I ensure genuine collaboration in action research?

True collaboration means: (1) Shared decision-making—practitioners and researchers jointly set research questions and decisions about action and change; (2) Equal voice—mechanisms for practitioners' perspectives to influence research direction; (3) Capacity building—researchers support practitioners' research skills; (4) Transparent process—clear communication about research aims, methods, findings; (5) Benefit sharing—findings and learning belong to all parties, not just researchers. Build in regular reflection on collaboration itself: Is it genuine? Who is driving decisions? Are power imbalances present? Adjust as needed.

What data should I collect in action research cycles?

Collect data addressing your research questions and improvement goals. Typically this includes: (1) Process data—documentation of what was implemented, how, when (field notes, logs); (2) Outcome data—metrics related to your improvement goals (e.g., communication quality, patient satisfaction, error rates); (3) Stakeholder perspectives—interviews or surveys with those involved about what worked, barriers, unintended effects; (4) Implementation fidelity—was the intervention implemented as planned? Be intentional about measurement; use mixed methods (quantitative and qualitative) when possible.

Can action research be conducted individually by one researcher, or must it be collaborative?

Ideally, action research involves multiple stakeholders collaborating. A single researcher can conduct action research if they are investigating their own practice (e.g., a teacher testing new instructional methods in their own classroom) and are in genuine dialogue with colleagues or peers for reflection and input. However, true collaboration—with practitioners outside the researcher's immediate role—is preferable because it broadens perspective and strengthens implementation of findings. If alone, build in external advisory or peer debrief structures.

Related methods

Sources

  1. Lewin, K. (1946). Action research and minority problems. Journal of Social Issues, 2(4), 34–46.

    Open DOI reference
    Copied.
  2. Kemmis, S., & McTaggart, R. (2005). Participatory action research: Communicative action and the public sphere. In N. K. Denzin & Y. S. Lincoln (Eds.), The Sage handbook of qualitative research (3rd ed., pp. 559–603). Sage Publications.

    Open publication reference
    Copied.
  3. Reason, P., & Bradbury, H. (Eds.). (2006). Handbook of action research: Participative inquiry and practice. Sage Publications.

    Open publication reference
    Copied.