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

Presentation · 41 slides

DBA 704 — Week 3: The Action Research Cycle

Doctor of Business Administration · Action Research module

Prof. Dr. Larry Adams

Week 3: The 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 3: The Action Research Cycle

    WEEK 3 — CONDUCTING ACTION RESEARCH

    Doctor of Business Administration (DBA)

    Central question: How do we actually conduct Action Research?

    From identifying a real organisational problem to action, evidence, reflection and the next cycle

    01
  2. Learning Outcomes

    • By the end of this session, students should be able to:
    • Explain the Action Research cycle and why it is cyclical.
    • Distinguish Action Research from conventional research.
    • Diagnose a practical organisational problem before acting.
    • Formulate an actionable research question and intervention.
    • Plan action, collect credible evidence and evaluate consequences.
    • Conduct structured reflection and convert learning into the next cycle.
    • Connect each cycle to DBA-level rigour, theory, ethics and contribution.
    02
  3. The Central Question

    • HOW DO WE ACTUALLY CONDUCT ACTION RESEARCH?
    • Action Research is not simply 'doing something and writing about it'.
    • It is a systematic inquiry in which action and research occur together.
    • The researcher investigates a meaningful problem while participants are involved in understanding the problem, implementing change, examining evidence and learning from the process.
    • Core principle: ACTION + EVIDENCE + REFLECTION + LEARNING.
    03
  4. What Is an Action Research Cycle?

    • An Action Research cycle is a structured process through which researchers and participants investigate a problem, plan an intervention, take action, examine the consequences, reflect on what has been learned, and use that learning to inform the next cycle.
    • Key idea: IT IS A CYCLE, and NOT A STRAIGHT LINE.
    • Traditional logic: Problem → Research → Findings → Conclusion
    • Action Research logic: Problem → Diagnosis → Action → Evidence → Reflection → Learning → Revised Action → New Cycle
    04
  5. Why a Cycle?

    • Organisational problems rarely disappear after one intervention.
    • First diagnosis may be incomplete.
    • Participants may respond differently than expected.
    • Context may change during implementation.
    • Unintended consequences may emerge.
    • New evidence may change the researcher's understanding.
    • Therefore, the end of one cycle becomes the starting point for another.
    • Each cycle should produce learning—not merely activity.
    05
  6. The Action Research Logic

    • 1. Identify a problem or opportunity for improvement.
    • 2. Diagnose the current situation and its causes.
    • 3. Review relevant theory, evidence and organisational context.
    • 4. Develop a plan for action.
    • 5. Implement the intervention collaboratively.
    • 6. Collect evidence before, during and after action.
    • 7. Analyse what happened and compare it with expectations.
    • 8. Reflect critically with participants.
    • 9. Decide what should be retained, modified, abandoned or tested next.
    • 10. Begin the next cycle where appropriate.
    06
  7. Cycle 1 — Identify the Problem

    • Start with a genuine (practical) practice problem, not an abstract topic.
    • A strong problem is:
    • Significant to the organisation or stakeholders.
    • Observable and capable of generating evidence.
    • Within the researcher's reasonable influence.
    • Complex enough to require investigation.
    • Ethically researchable.
    • Connected to a knowledge gap, practice gap or both.
    • Ask: What is happening? Who experiences it? Why does it matter? What evidence shows that it is a problem?
    07
  8. Problem vs Symptom vs Cause

    • Symptom: What we can see happening.
    • Problem: The undesirable condition requiring investigation.
    • Possible cause: A factor contributing to the condition.
    • Example:
    • Symptom — employee turnover is increasing.
    • Problem — retention of experienced employees has deteriorated in a critical business unit.
    • Possible causes — workload, management practices, career progression, psychological safety or compensation.
    • Do not jump directly from symptom to intervention. Diagnose first.
    08
  9. Problem Diagnosis

    • Diagnosis asks: WHY is the problem occurring?
    • Possible evidence sources:
    • Interviews and focus groups
    • Observation and field notes
    • Organisational records and KPIs
    • Surveys and questionnaires
    • Process maps and workflow analysis
    • Customer/employee feedback
    • Policy and document analysis
    • Existing research and theory
    • Triangulate where possible. A single anecdote is not a sufficient diagnosis.
    09
  10. The Research Question

    • An Action Research question should connect KNOWLEDGE and ACTION.
    • Useful structure:
    • How can [intervention/change] improve [practice/outcome] in [context]?
    • Examples:
    • How can a revised onboarding process improve early-stage employee integration?
    • How can participatory scheduling reduce workflow bottlenecks in a service team?
    • How can a digital dashboard improve evidence-based managerial decision-making?
    • Avoid questions that only ask whether two variables are correlated if the purpose is genuinely Action Research.
    10
  11. From Problem to Research Question

    • Weak: 'Employee motivation in Company X.'
    • Better: 'Why are motivation levels declining among frontline employees?'
    • Action Research-oriented: 'How can a participatory recognition intervention improve frontline employee motivation in Company X?'
    • DBA-level refinement requires:
    • Context and boundaries
    • Participants/stakeholders
    • Intended change
    • Evidence of change
    • Relevant theoretical lens
    • Feasibility within the research period
    11
  12. The Role of Participants

    • Action Research is usually participatory.
    • Participants are not merely 'subjects' from whom data are extracted.
    • They may contribute to:
    • Defining the problem
    • Interpreting the situation
    • Designing the intervention
    • Implementing the change
    • Generating and interpreting evidence
    • Reflecting on outcomes
    • Participation must still be structured. The researcher must define roles, responsibilities, boundaries and ethical protections.
    12
  13. Researcher as Practitioner and Researcher

    • The DBA Action Researcher may occupy a dual role:
    • Practitioner — concerned with improving practice.
    • Researcher — concerned with systematic, transparent and defensible knowledge generation.
    • The challenge is to avoid:
    • Acting without inquiry.
    • Treating personal opinion as evidence.
    • Selectively reporting favourable outcomes.
    • Allowing organisational authority to silence participants.
    • Reflexivity is therefore essential.
    13
  14. Cycle 1 — Planning the Action

    • Planning translates diagnosis into a testable intervention.
    • Specify:
    • What will change?
    • Why should it change?
    • Who will participate?
    • What resources are required?
    • What is the implementation period?
    • What risks may occur?
    • What evidence will indicate progress?
    • What alternative explanations should be considered?
    • Plan the smallest meaningful intervention that can generate useful learning.
    14
  15. Designing the Intervention

    • A good intervention should be:
    • Relevant to the diagnosed problem.
    • Grounded in evidence/theory.
    • Feasible in the organisational context.
    • Clear enough to implement consistently.
    • Flexible enough to learn from experience.
    • Example: Introduce a weekly cross-functional problem-solving meeting for eight weeks, with a standard agenda, action log and process KPI tracking.
    • Do not confuse an intervention with an entire organisational transformation programme.
    15
  16. Action — Implementing the Intervention

    • Implementation is itself part of the research.
    • Document:
    • What was planned.
    • What was actually implemented.
    • Who participated.
    • When and where it occurred.
    • Deviations from the plan.
    • Resistance or unexpected events.
    • Adaptations made during implementation.
    • An intervention that was not implemented as planned cannot be evaluated as though it was.
    16
  17. Evidence During Action

    • Collect evidence systematically rather than relying on memory.
    • Possible evidence:
    • Quantitative: KPI data, cycle time, error rate, productivity, attendance, survey scores.
    • Qualitative: interviews, reflective journals, observations, meeting records, participant narratives.
    • Process evidence: participation rates, implementation fidelity, adoption records.
    • Use multiple evidence sources when appropriate.
    • Record dates, sources, instruments, decisions and changes to preserve an audit trail.
    17
  18. Baseline and Post-Action Evidence

    • Whenever feasible, establish a baseline before intervention.
    • Baseline → Intervention → Monitoring → Post-action evidence
    • Example:
    • Baseline: average customer response time before intervention.
    • Action: new triage workflow introduced.
    • Monitoring: weekly response-time data + staff reflections.
    • Post-action: compare performance and investigate why changes occurred.
    • Important: change after an intervention does not automatically prove that the intervention caused the change.
    18
  19. Analysing the Consequences

    • Ask three questions:
    • 1. WHAT changed?
    • 2. HOW did it change?
    • 3. WHY might it have changed?
    • Look for:
    • Intended outcomes
    • Unintended outcomes
    • Positive and negative effects
    • Participant experiences
    • Contextual influences
    • Evidence that contradicts expectations
    • Action Research values learning from unexpected results.
    19
  20. Qualitative Analysis in Action Research

    • Possible approaches include:
    • Thematic analysis
    • Coding interview/observation data
    • Content analysis of reflective records
    • Pattern identification across participants and events
    • Typical sequence:
    • Familiarise → Code → Group codes → Develop themes → Compare across evidence → Interpret in context.
    • Maintain a transparent coding process. Preserve quotations or examples where appropriate, while protecting confidentiality.
    20
  21. Quantitative Analysis in Action Research

    • Use analysis appropriate to the design and sample.
    • Possible techniques:
    • Descriptive statistics
    • Pre/post comparisons
    • Trend analysis
    • Effect sizes where appropriate
    • Repeated observations over time
    • Relevant inferential tests where justified
    • Do not use sophisticated statistics simply to appear rigorous.
    • Rigor comes from alignment among the problem, intervention, evidence, design and research question.
    21
  22. Reflection — The Heart of the Cycle

    • Reflection is more than saying 'the intervention worked'.
    • Ask:
    • What did we expect?
    • What actually happened?
    • What evidence supports that conclusion?
    • What surprised us?
    • What assumptions were wrong?
    • What did participants learn?
    • What did the researcher learn?
    • What contextual factors influenced the outcome?
    • What should change in the next cycle?
    22
  23. Critical Reflection

    • Descriptive reflection: What happened?
    • Analytical reflection: Why did it happen?
    • Critical reflection: What assumptions, power relations, structures or contextual conditions shaped what happened?
    • DBA-level reflection should challenge the researcher's own interpretation.
    • Example: A new process improved productivity, but only because managers increased monitoring. The researcher must consider whether the intervention created sustainable improvement or short-term compliance.
    23
  24. The Next Cycle

    • Cycle 2 should NOT simply repeat Cycle 1.
    • It should be informed by learning.
    • Cycle 1 learning may lead to:
    • Continue the intervention.
    • Modify the intervention.
    • Add a new component.
    • Remove an ineffective component.
    • Investigate an unexpected issue.
    • Reframe the problem.
    • Test the intervention in another context.
    • The cycle therefore creates cumulative organisational and scholarly learning.
    24
  25. A Worked DBA Example

    • Problem: Customer complaints about slow service resolution.
    • Diagnosis: Interviews + process data reveal handoff delays between departments.
    • Plan: Introduce a cross-functional digital escalation workflow.
    • Action: Implement workflow for 8 weeks.
    • Evidence: Resolution time, complaint volume, staff interviews and workflow logs.
    • Reflection: Resolution time improved, but staff report increased workload at peak periods.
    • Learning: Workflow reduces handoff delay but creates capacity pressure.
    • Next cycle: redesign workload allocation and test a revised workflow.
    25
  26. Worked Example — Evidence Matrix

    • Research question: How can the escalation workflow improve service resolution?
    • Evidence 1 — KPI: average resolution time.
    • Evidence 2 — Process data: time spent at each handoff.
    • Evidence 3 — Participant interviews: usability and workload.
    • Evidence 4 — Observation: actual workflow adoption.
    • Triangulation: Compare whether different evidence sources tell a consistent story.
    • Contradictions are findings to investigate, not problems to hide.
    26
  27. Action Research and Theory

    • Action Research is practical, but it is not atheoretical.
    • Theory can help explain:
    • Why the problem exists.
    • Why the intervention should work.
    • How participants may respond.
    • Why outcomes differ across contexts.
    • Use theory as a lens—not as decoration.
    • Move between theory and practice: theory informs action; action generates learning; learning may refine or challenge theory.
    27
  28. Action Research and the Literature Review

    • The literature review should establish:
    • What is already known.
    • What is uncertain or contested.
    • Which theories explain the issue.
    • What prior interventions have achieved.
    • Where the practice/knowledge gap exists.
    • Then show how the Action Research project addresses that gap.
    • Do not write a generic literature review disconnected from the intervention and research questions.
    28
  29. Ethics in Action Research

    • Ethical issues may be heightened because the researcher can have organisational influence.
    • Consider:
    • Informed consent
    • Voluntary participation
    • Confidentiality/anonymity
    • Power relationships
    • Employer–employee pressure
    • Data access and ownership
    • Potential harm from interventions
    • Withdrawal rights
    • Conflicts of interest
    • Secure data management
    • Ethics must apply throughout the cycle, not only at the beginning.
    29
  30. Reflexivity and Researcher Bias

    • Because the researcher may be involved in the setting, bias must be actively managed.
    • Strategies:
    • Reflexive journal
    • Explicit positionality statement
    • Transparent decision log
    • Participant validation where appropriate
    • Triangulation
    • Negative-case analysis
    • Peer/supervisory review
    • Reporting evidence that challenges the researcher's preferred interpretation
    30
  31. Validity, Quality and Trustworthiness

    • Ask whether conclusions are credible and defensible.
    • Useful quality strategies:
    • Triangulation
    • Member/participant checking where appropriate
    • Prolonged engagement
    • Audit trail
    • Clear documentation of cycles
    • Reflexivity
    • Evidence of change over time
    • Alternative explanations
    • Transparent limitations
    • Do not claim causality beyond what the design can support.
    31
  32. The Action Research Audit Trail

    • A DBA dissertation should allow another researcher to understand what happened.
    • Maintain records of:
    • Problem diagnosis
    • Research questions
    • Intervention design
    • Participant roles
    • Dates and stages
    • Data collection instruments
    • Changes to the plan
    • Analytical decisions
    • Reflection records
    • Cycle decisions
    • Ethical decisions
    • Evidence supporting conclusions
    32
  33. Common Mistakes — 1

    • Mistake: Calling any workplace improvement project 'Action Research'.
    • Correction: Demonstrate systematic inquiry, evidence collection, reflection and learning.
    • Mistake: Acting before diagnosing.
    • Correction: Establish the current situation and plausible causes first.
    • Mistake: Treating participants as data sources only.
    • Correction: Build meaningful participation into the research design.
    • Mistake: Reporting only successful outcomes.
    • Correction: Report negative, unexpected and unintended outcomes.
    33
  34. Common Mistakes — 2

    • Mistake: No baseline.
    • Correction: Establish pre-action evidence where feasible.
    • Mistake: No clear intervention.
    • Correction: Specify exactly what action was introduced.
    • Mistake: No distinction between planned and actual action.
    • Correction: Maintain implementation records.
    • Mistake: Reflection becomes personal opinion.
    • Correction: Anchor reflection in evidence and participant perspectives.
    • Mistake: One cycle is presented as a complete solution.
    • Correction: Explain what the cycle taught and why another cycle was or was not required.
    34
  35. From Cycle to Dissertation Chapter

    • Chapter 1: Problem, context, purpose, research questions and significance.
    • Chapter 2: Literature, theory and identified gap.
    • Chapter 3: Action Research methodology, participants, cycles, intervention, data and ethics.
    • Chapter 4: Evidence, analysis and outcomes of each cycle.
    • Chapter 5: Reflection, learning, theoretical/practical contribution, limitations and recommendations.
    • Exact chapter structure depends on the DBA programme and approved proposal. Maintain alignment across all chapters.
    35
  36. Student Activity — Diagnose Before You Act

    • Choose a real organisational problem.
    • Write:
    • 1. The visible symptom.
    • 2. The underlying problem as currently understood.
    • 3. Evidence that the problem exists.
    • 4. Who is affected.
    • 5. Three plausible causes.
    • 6. What additional evidence is needed before intervention.
    • 7. A preliminary Action Research question.
    • Rule: Do NOT design the intervention yet. Diagnose first.
    36
  37. Student Activity — Build Cycle 1

    • Now develop a preliminary cycle:
    • Problem → Diagnosis → Research question → Intervention → Participants → Evidence → Analysis → Reflection → Learning → Next action.
    • For each arrow, explain the connection.
    • Then ask: If the intervention succeeds, what will we learn? If it fails, what will we learn?
    • This question helps move students from 'project management' toward genuine Action Research.
    37
  38. Class Discussion Questions

    • 1. What makes Action Research different from an ordinary change-management project?
    • 2. Can Action Research be rigorous if the researcher is also a practitioner?
    • 3. What counts as convincing evidence of change?
    • 4. What should happen when quantitative and qualitative evidence disagree?
    • 5. How much participant involvement is enough?
    • 6. When should a researcher start a second cycle?
    • 7. Can a failed intervention make a successful doctoral study?
    • 8. How can Action Research generate knowledge beyond one organisation?
    38
  39. DBA-Level Test of a Cycle

    • Before accepting a cycle, ask:
    • ✓ Is the problem clearly evidenced?
    • ✓ Is the diagnosis defensible?
    • ✓ Is the intervention logically connected to the diagnosis?
    • ✓ Are participants appropriately involved?
    • ✓ Is evidence collected systematically?
    • ✓ Are intended and unintended consequences examined?
    • ✓ Is reflection evidence-based?
    • ✓ Are alternative explanations considered?
    • ✓ Does the learning inform the next decision?
    • ✓ Is the scholarly contribution visible?
    • If several answers are 'no', the cycle needs redesign or stronger documentation.
    39
  40. Key Takeaways

    • ACTION RESEARCH IS A LEARNING SYSTEM.
    • Do not think: Problem → Action → Success.
    • Think:
    • Problem → Diagnosis → Plan → Action → Evidence → Reflection → Learning → Revised Action → New Cycle.
    • The quality of an Action Research doctorate is not measured by whether the intervention 'worked'.
    • It is measured by the quality of inquiry, evidence, reflection, learning and contribution generated through the cycle.
    40
  41. Week 3 — Closing Question

    • If your intervention does NOT produce the expected result, what will you do?
    • Do you:
    • Hide the failure?
    • Blame the participants?
    • Change the data?
    • Conclude that the research failed?
    • Examine the evidence?
    • Reflect critically?
    • Reconsider your assumptions?
    • Learn from the outcome?
    • Redesign the next cycle?
    • Action Research treats unexpected outcomes as opportunities for deeper inquiry.
    41
01 / 41

Slides in this deck

  1. DBA 704 — Week 3: The Action Research Cycle
  2. Learning Outcomes
  3. The Central Question
  4. What Is an Action Research Cycle?
  5. Why a Cycle?
  6. The Action Research Logic
  7. Cycle 1 — Identify the Problem
  8. Problem vs Symptom vs Cause
  9. Problem Diagnosis
  10. The Research Question
  11. From Problem to Research Question
  12. The Role of Participants
  13. Researcher as Practitioner and Researcher
  14. Cycle 1 — Planning the Action
  15. Designing the Intervention
  16. Action — Implementing the Intervention
  17. Evidence During Action
  18. Baseline and Post-Action Evidence
  19. Analysing the Consequences
  20. Qualitative Analysis in Action Research
  21. Quantitative Analysis in Action Research
  22. Reflection — The Heart of the Cycle
  23. Critical Reflection
  24. The Next Cycle
  25. A Worked DBA Example
  26. Worked Example — Evidence Matrix
  27. Action Research and Theory
  28. Action Research and the Literature Review
  29. Ethics in Action Research
  30. Reflexivity and Researcher Bias
  31. Validity, Quality and Trustworthiness
  32. The Action Research Audit Trail
  33. Common Mistakes — 1
  34. Common Mistakes — 2
  35. From Cycle to Dissertation Chapter
  36. Student Activity — Diagnose Before You Act
  37. Student Activity — Build Cycle 1
  38. Class Discussion Questions
  39. DBA-Level Test of a Cycle
  40. Key Takeaways
  41. Week 3 — Closing Question