Prof. Dr. Larry AdamsAcademic, Author & Researcher
DBA 704 — Week 5: The Basic Action Research Cycle · 28 slides

Presentation · 28 slides

DBA 704 — Week 5: The Basic Action Research Cycle

Doctor of Business Administration · Action Research module

Prof. Dr. Larry Adams

Week 5: The Basic Action Research Cycle — part of the DBA 704 Action Research teaching module for doctoral students.

Free to view online and to download for teaching, with acknowledgement of the author. To reproduce or adapt any part of a deck, please request permission through the contact page beforehand.

  1. DBA 704 — Week 5: The Basic Action Research Cycle

    The Basic Action Research Cycle

    From PLAN → ACT → OBSERVE → REFLECT to a DBA-level iterative research framework

    DBA 704 • Action Research in Operations Management

    Teaching deck | concepts • application • evidence • reflection • iteration

    DBA 704 • Week 5 • Action Research in Operations Management • 1

    01
  2. Learning Outcomes

    • By the end of Week 5, students should be able to explain, apply, document, and critique an action research cycle.
    • Explain the logic of the classic PLAN → ACT → OBSERVE → REFLECT cycle.
    • Distinguish action research from a one-shot intervention or conventional observational study.
    • Apply the expanded DBA framework: DIAGNOSE → PLAN → ACT → OBSERVE/COLLECT EVIDENCE → REFLECT → LEARN → REVISE → ACT AGAIN.
    • Identify what counts as evidence at each stage and align evidence with the research question.
    • Use reflection to generate learning rather than merely describe what happened.
    • Recognise iteration, adaptation, participation, and context as central features of action research.
    • Document decisions so the research process is transparent, credible, and auditable.
    • Connect the cycle to an operations-management problem and prepare for the next cycle.
    • DBA 704 • Week 5 • Action Research in Operations Management • 2
    02
  3. Why a Cycle?

    • Action research treats organisational change and knowledge generation as connected, iterative processes.
    • The cycle is not a circular checklist. Each stage informs the next decision.
    • DBA 704 • Week 5 • Action Research in Operations Management • 3
    03
  4. Classic Action Research Cycle

    • The four-stage logic is simple enough to remember and powerful enough to structure a real intervention.
    • 1. PLAN
    • 2. ACT
    • 3. OBSERVE
    • 4. REFLECT
    • Define the problem. Set objectives. Choose an intervention. Decide what evidence is needed. Anticipate risks and constraints.
    • Implement the planned change. Engage participants. Record deviations. Manage the intervention responsibly.
    • Collect evidence systematically. Monitor outcomes and process. Capture participant perspectives. Record unexpected effects.
    • Interpret what happened. Compare evidence with expectations. Ask why outcomes occurred. Generate learning and revise.
    • DBA 704 • Week 5 • Action Research in Operations Management • 4
    04
  5. The DBA Expansion

    • The expanded framework makes diagnosis, evidence, learning, and revision explicit.
    • OBSERVE / COLLECT EVIDENCE
    • Working framework for DBA students
    • DBA 704 • Week 5 • Action Research in Operations Management • 5
    05
  6. Stage 1 — DIAGNOSE

    • Before changing anything, establish what the problem is, for whom, where, and why it matters.
    • What to diagnose
    • Useful evidence
    • DBA question
    • Current-state process • Performance gap • Root causes / contributing conditions • Stakeholder perspectives • Organisational context • Constraints and assumptions
    • Process maps • Baseline KPIs • Interviews / focus groups • Surveys • Documents / logs • Observation • Existing operational data
    • What evidence demonstrates that this is a genuine problem rather than an assumption? What alternative explanations should be considered? Who defines the problem—and who experiences it?
    • DBA 704 • Week 5 • Action Research in Operations Management • 6
    06
  7. Diagnosis: From Symptom to Researchable Problem

    • Symptom: “Customer complaints are increasing.”
    • Operational problem: “Complaint resolution is slower than the service-level target.”
    • Diagnostic question: “Which process conditions contribute to resolution delays?”
    • Action-research problem: “Can a revised complaint-triage process improve resolution speed while maintaining service quality?”
    • Research question should connect the intervention, context, participants/data, and intended learning.
    • Do not begin with the preferred solution. Diagnose before prescribing.
    • Prompt
    • Students: 1. What is the symptom? 2. What is the measurable gap? 3. What evidence establishes the baseline? 4. What might explain the gap? 5. What remains uncertain? 6. What could reasonably be changed?
    • DBA 704 • Week 5 • Action Research in Operations Management • 7
    07
  8. Stage 2 — PLAN

    • Planning converts diagnosis into a deliberate, evidence-informed intervention.
    • Define the intervention and its intended mechanism of change.
    • Specify participants, roles, responsibilities, and decision rights.
    • Establish baseline measures before intervention where feasible.
    • Select data sources and collection points.
    • Decide how qualitative and quantitative evidence will be integrated.
    • Define practical constraints: time, resources, access, operational disruption, ethics.
    • Set criteria for judging progress—but avoid pretending that outcomes are fully predictable.
    • Create a change log: what was planned, what changed, when, why, and who decided.
    • Planning test
    • A strong plan answers: WHAT will change? WHY should it help? WHO participates? WHEN will it occur? WHAT evidence will be collected? HOW will evidence be interpreted? WHAT would trigger revision?
    • DBA 704 • Week 5 • Action Research in Operations Management • 8
    08
  9. Stage 3 — ACT

    • Action research requires action: the intervention is implemented in the real organisational setting.
    • Implementation
    • Do not hide change
    • Researcher role
    • Real organisations are dynamic. A plan may change because of staffing, technology, customer demand, policy, resource constraints, or participant feedback. Document the change rather than pretending it did not happen.
    • Introduce the planned change • Communicate roles and expectations • Support participants • Monitor implementation fidelity • Record deviations • Manage operational risks
    • The researcher is not simply an observer. The researcher must balance: • intervention • participation • evidence collection • ethical responsibility • reflexivity • organisational realities
    • DBA 704 • Week 5 • Action Research in Operations Management • 9
    09
  10. Stage 4 — OBSERVE / COLLECT EVIDENCE

    • Observation is broader than “watching.” It means systematic collection of evidence about process, experience, and outcomes.
    • Outcome evidence: Did the target performance indicator change?
    • Process evidence: What actually happened during implementation?
    • Participant evidence: How did employees/customers/managers experience the change?
    • Context evidence: What organisational or environmental conditions shaped the outcome?
    • Unexpected evidence: What consequences, positive or negative, emerged?
    • Timing matters: collect evidence before, during, and after the intervention when appropriate.
    • Use multiple evidence sources when feasible to strengthen interpretation.
    • Evidence matrix
    • Baseline → Intervention → Immediate outcome → Sustained outcome Example: Cycle time → new triage → average resolution → repeat-cycle performance Add qualitative evidence to explain why the numbers moved—or did not.
    • DBA 704 • Week 5 • Action Research in Operations Management • 10
    10
  11. Evidence: Quantitative + Qualitative

    • DBA action research often benefits from combining measurement with explanation.
    • Quantitative
    • Qualitative
    • Integration
    • KPIs Cycle time Defect/error rate Cost Throughput Satisfaction scores Absence/turnover indicators Before/after comparisons
    • Interviews Focus groups Open-ended survey responses Field notes Meeting records Participant reflections Process observations
    • Numbers show patterns. Qualitative evidence can explain mechanisms, perceptions, implementation barriers, and contextual conditions. Neither automatically “proves” causality.
    • DBA 704 • Week 5 • Action Research in Operations Management • 11
    11
  12. Stage 5 — REFLECT

    • Reflection is disciplined analysis—not simply personal opinion.
    • Compare intended and actual implementation.
    • Compare expected and observed outcomes.
    • Ask what worked, what did not, and under what conditions.
    • Examine participant interpretations and researcher assumptions.
    • Look for contradictions and disconfirming evidence.
    • Consider unintended consequences.
    • Distinguish evidence from interpretation and interpretation from speculation.
    • Record reflective decisions so another reader can follow the reasoning.
    • Reflective questions
    • What surprised us? What did we assume? What evidence supports that conclusion? What evidence challenges it? What changed in context? What should remain unchanged? What should we test next?
    • DBA 704 • Week 5 • Action Research in Operations Management • 12
    12
  13. Stage 6 — LEARN

    • Learning is the intellectual bridge between reflection and the next intervention.
    • Operational learning
    • Research learning
    • DBA contribution
    • What changed in practice? Which process condition mattered? Which barrier was removed? Which behaviour or routine shifted? What capability was developed?
    • What does the evidence suggest? Which explanation is strengthened? Which is weakened? What contextual conditions matter? What new question emerged?
    • Learning should move beyond: “the intervention worked.” Aim toward: “under these conditions, this mechanism/process change appears associated with this outcome, with these limitations.”
    • DBA 704 • Week 5 • Action Research in Operations Management • 13
    13
  14. Stage 7 — REVISE

    • The next cycle should be informed by evidence—not by habit or convenience.
    • Keep: elements supported by evidence and practical experience.
    • Modify: elements that show promise but require adjustment.
    • Remove: elements that create burden or fail to contribute.
    • Add: newly identified components or controls.
    • Change the measurement strategy if the evidence was insufficient.
    • Revisit assumptions, stakeholder roles, timing, and implementation conditions.
    • Document why the next plan differs from the previous plan.
    • Revision rule
    • DO NOT ask: “What should we do next?” Ask first: “What have we learned that justifies doing something differently next?”
    • DBA 704 • Week 5 • Action Research in Operations Management • 14
    14
  15. Stage 8 — ACT AGAIN

    • The end of one cycle is the beginning of the next learning opportunity.
    • Iteration is not repetition. Each cycle should reduce uncertainty, improve practice, or deepen understanding.
    • DBA 704 • Week 5 • Action Research in Operations Management • 15
    15
  16. Worked DBA Example — Operations Management

    • Illustration: reducing customer complaint resolution time in a service organisation.
    • REFLECT → LEARN → REVISE
    • Baseline shows average resolution = 5.2 days. Interviews identify inconsistent triage and unclear ownership.
    • Introduce triage categories, ownership rules, escalation triggers, and a dashboard. Define KPIs + interview questions.
    • Pilot for four weeks. Collect resolution time, backlog, rework, customer feedback, and staff reflections.
    • Resolution improves, but escalations rise. Learning: triage improved speed but exposed an authority bottleneck. Revise escalation rules → next cycle.
    • DBA 704 • Week 5 • Action Research in Operations Management • 16
    16
  17. A Second Cycle: What Changes?

    • The second cycle should be visibly different because the researcher has learned something.
    • Cycle 1 learning: triage categories reduced delays but escalations accumulated.
    • Cycle 2 diagnosis: the escalation decision is itself a bottleneck.
    • Cycle 2 plan: introduce delegated approval thresholds and clearer escalation ownership.
    • Cycle 2 action: implement the revised authority model with monitoring.
    • Cycle 2 observation: compare cycle-time, escalation volume, rework, and participant experience.
    • Cycle 2 reflection: determine whether faster resolution was achieved without unacceptable quality or control problems.
    • Cycle 2 learning: refine the process and develop a more context-sensitive explanation of performance.
    • DBA 704 • Week 5 • Action Research in Operations Management • 17
    17
  18. What Counts as a Strong Cycle?

    • Use these criteria when students document their own action research.
    • 1. Clear problem
    • 2. Traceable intervention
    • 3. Credible learning
    • A defensible diagnosis and baseline. The problem is meaningful to practice and research.
    • A clear link between diagnosis, intervention, intended mechanism, and evidence.
    • Reflection is evidence-based, limitations are acknowledged, and the next cycle follows logically.
    • DBA 704 • Week 5 • Action Research in Operations Management • 18
    18
  19. Common Mistakes to Avoid

    • Calling a one-time implementation an “action research cycle” without iteration or learning.
    • Jumping to a solution before diagnosing the problem.
    • Collecting data that are interesting but not connected to the research question.
    • Treating a positive KPI change as proof of causality without considering context and alternative explanations.
    • Failing to document changes made during implementation.
    • Using reflection as a personal diary rather than systematic critical analysis.
    • Ending after the first cycle when the research question requires deeper learning.
    • Changing the intervention and measures simultaneously without explaining why.
    • Reporting only success and hiding negative or contradictory evidence.
    • DBA 704 • Week 5 • Action Research in Operations Management • 19
    19
  20. The Researcher’s Reflexive Position

    • Because the researcher may influence the setting, reflexivity is part of methodological quality.
    • State your role in the organisation and relationship to participants where relevant.
    • Recognise how your authority, expertise, expectations, or incentives may shape the intervention.
    • Record decisions and turning points during the cycle.
    • Distinguish participant voice from researcher interpretation.
    • Actively seek evidence that challenges your preferred explanation.
    • Explain how ethical responsibilities were managed throughout the cycle.
    • Treat unexpected outcomes as potential learning rather than inconvenient noise.
    • Reflexive memo
    • “What did I expect to happen?” “What actually happened?” “How might my role have influenced this?” “What evidence would make me reconsider my interpretation?”
    • DBA 704 • Week 5 • Action Research in Operations Management • 20
    20
  21. Ethics Across the Entire Cycle

    • Ethics is not a single approval step. It remains relevant during diagnosis, intervention, observation, and subsequent cycles.
    • Protect participants from unnecessary harm, pressure, embarrassment, or professional consequences.
    • Maintain informed participation and respect withdrawal/choice requirements applicable to the approved study.
    • Protect confidentiality and handle organisationally sensitive information appropriately.
    • Do not manipulate data or suppress inconvenient findings.
    • Do not allow operational goals to override research ethics.
    • Record protocol deviations and seek appropriate approval when changes affect the approved research.
    • Be especially careful when the researcher has managerial or evaluative power over participants.
    • DBA 704 • Week 5 • Action Research in Operations Management • 21
    21
  22. Cycle Documentation Template

    • Students should be able to reconstruct the logic of every cycle from their research record.
    • A. Diagnosis
    • B. Plan + Act
    • C. Observe
    • D. Reflect + Learn
    • Problem statement Baseline evidence Stakeholders Context Root causes / assumptions Diagnostic questions
    • Intervention Objectives Participants Timeline Implementation record Deviations / decisions
    • Data sources Measures Collection points Qualitative evidence Unexpected outcomes Data quality
    • Findings Interpretation Contradictions Lessons Limitations Revision decision Next cycle
    • DBA 704 • Week 5 • Action Research in Operations Management • 22
    22
  23. From Cycle to Dissertation Chapter Structure

    • The cycle should be visible in the dissertation—not hidden behind a generic methodology description.
    • Chapter 1: establish the practical/research problem and purpose.
    • Chapter 2: position the problem within relevant literature and theory.
    • Chapter 3: explain philosophy, action research approach, design, participants, ethics, data sources, and procedures.
    • Chapter 4: present evidence/findings from the cycle(s), including implementation and outcomes.
    • Chapter 5: interpret learning, connect findings to literature/theory, discuss implications and limitations, and explain the revised understanding.
    • Across chapters: make the link between diagnosis → intervention → evidence → reflection → learning → revision traceable.
    • DBA 704 • Week 5 • Action Research in Operations Management • 23
    23
  24. Activity 1 — Build Your Own Cycle

    • Individual task: map one real operations-management problem onto the expanded framework.
    • 1. Write a one-sentence problem statement.
    • 2. Identify at least two baseline indicators or evidence sources.
    • 3. State what you would diagnose before intervening.
    • 4. Design a feasible first intervention.
    • 5. Identify quantitative and/or qualitative evidence you would collect.
    • 6. Write three reflection questions.
    • 7. State what learning would cause you to revise the intervention.
    • 8. Describe what Cycle 2 would test or change.
    • Deliverable
    • One-page Action Research Cycle Map Students should show: Problem → evidence → intervention → evidence → reflection → learning → revision → next action
    • DBA 704 • Week 5 • Action Research in Operations Management • 24
    24
  25. Activity 2 — Challenge the Cycle

    • Small-group critical review.
    • Is the diagnosis supported by evidence?
    • Is the intervention logically connected to the diagnosis?
    • Could the same outcome be explained another way?
    • Are the proposed measures sensitive to change?
    • Whose perspective is missing?
    • Where could researcher influence or bias enter?
    • What unexpected outcome should be monitored?
    • Is there a defensible reason to conduct another cycle?
    • Peer-review rule
    • Do not ask only: “Is this a good idea?” Ask: “What evidence would justify this decision?” The objective is methodological challenge, not personal criticism.
    • DBA 704 • Week 5 • Action Research in Operations Management • 25
    25
  26. Class Discussion — What Makes It “Action Research”?

    • Scenario A: A manager changes a process and reports that performance improved.
    • Scenario B: A researcher observes a process for six months but makes no intervention.
    • Scenario C: A researcher and participants diagnose a problem, implement a change, collect evidence, reflect on results, revise the intervention, and repeat.
    • Which scenario best represents action research—and why?
    • What minimum features would you require before calling a study iterative action research?
    • Debate prompt: Is iteration alone enough, or must each cycle generate meaningful learning?
    • DBA 704 • Week 5 • Action Research in Operations Management • 26
    26
  27. Key Takeaways

    • The expanded cycle is the students' working framework.
    • Understand the problem and establish a defensible baseline.
    • Design an evidence-informed intervention.
    • Implement in the real organisational setting.
    • Collect systematic evidence about process and outcomes.
    • Critically interpret what happened.
    • Turn evidence into operational and research knowledge.
    • Change the plan because of what was learned.
    • Begin the next cycle with a sharper question.
    • PLAN → ACT → OBSERVE → REFLECT is the classic logic; DIAGNOSE → PLAN → ACT → OBSERVE/COLLECT EVIDENCE → REFLECT → LEARN → REVISE → ACT AGAIN is the DBA working framework.
    • DBA 704 • Week 5 • Action Research in Operations Management • 27
    27
  28. Closing Teaching Questions

    • Use these to consolidate Week 5 and transition students toward their own research designs.
    • What exactly will you diagnose in your study?
    • What is your baseline, and how will you establish it?
    • What will you change—and why?
    • What evidence will tell you whether the change matters?
    • How will you capture participant experience and contextual conditions?
    • What would count as evidence against your preferred explanation?
    • What will you learn from Cycle 1?
    • What specific change would you make in Cycle 2?
    • How will your dissertation demonstrate the logic of the cycles?
    • Remember: the objective is not simply to make a change. It is to generate credible learning through action, evidence, reflection, and revision.
    • DBA 704 • Week 5 • Action Research in Operations Management • 28
    28
01 / 28

Slides in this deck

  1. DBA 704 — Week 5: The Basic Action Research Cycle
  2. Learning Outcomes
  3. Why a Cycle?
  4. Classic Action Research Cycle
  5. The DBA Expansion
  6. Stage 1 — DIAGNOSE
  7. Diagnosis: From Symptom to Researchable Problem
  8. Stage 2 — PLAN
  9. Stage 3 — ACT
  10. Stage 4 — OBSERVE / COLLECT EVIDENCE
  11. Evidence: Quantitative + Qualitative
  12. Stage 5 — REFLECT
  13. Stage 6 — LEARN
  14. Stage 7 — REVISE
  15. Stage 8 — ACT AGAIN
  16. Worked DBA Example — Operations Management
  17. A Second Cycle: What Changes?
  18. What Counts as a Strong Cycle?
  19. Common Mistakes to Avoid
  20. The Researcher’s Reflexive Position
  21. Ethics Across the Entire Cycle
  22. Cycle Documentation Template
  23. From Cycle to Dissertation Chapter Structure
  24. Activity 1 — Build Your Own Cycle
  25. Activity 2 — Challenge the Cycle
  26. Class Discussion — What Makes It “Action Research”?
  27. Key Takeaways
  28. Closing Teaching Questions