Prof. Dr. Larry AdamsAcademic, Author & Researcher
DBA 704 — Week 4: Action Research in Practice · 36 slides

Presentation · 36 slides

DBA 704 — Week 4: Action Research in Practice

Doctor of Business Administration · Action Research module

Prof. Dr. Larry Adams

Week 4: Action Research in Practice — 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 4: Action Research in Practice

    DBA WEEK 4

    From systematic inquiry to practical organisational change

    DBA Week 4 • Action Research • 1

    01
  2. Learning Outcomes

    • Define Action Research and distinguish it from conventional organisational research.
    • Why Action Research combines systematic research with action.
    • Style participation, reflection, evidence, learning and iterative development.
    • As a Student you must be able to “Explain the Action Research cycle and what happens at each stage".
    • Compare major approaches and identify when Action Research is appropriate.
    • Develop a defensible DBA Action Research problem, question and intervention.
    • Recognise common methodological weaknesses and improve research quality.
    • DBA Week 4 • Action Research • 2
    02
  3. 4. Why is it called "Action" Research?

    • The defining idea: inquiry and change are deliberately connected.
    • Key distinction
    • A company implementing a new software system is taking action. That alone does NOT make the study Action Research. The research must involve systematic inquiry, evidence, reflection, learning and methodological reasoning.
    • DBA Week 4 • Action Research • 3
    03
  4. What Makes a Study Action Research?

    • Systematic inquiry
    • Action
    • Participation
    • Planned research process with explicit questions, methods and evidence.
    • A deliberate intervention or change is introduced or supported.
    • Relevant participants contribute to diagnosis, action, reflection or learning.
    • Reflection
    • Learning
    • Iteration
    • Findings and experience are critically examined.
    • Knowledge is generated for practice and scholarship.
    • The process develops through repeated cycles.
    • DBA Week 4 • Action Research • 4
    04
  5. Action Research vs Conventional Organisational Research

    • Conventional empirical research
    • Action Research
    • Often observes or explains a phenomenon ( Significance )
    • Researcher may remain relatively separate from the setting
    • Emphasis can be on testing, estimating or explaining
    • Data collection is often organised around a defined study period
    • Change may be a recommendation after the study
    • Investigates while attempting improvement or change
    • Researcher and participants interact with the problem
    • Emphasis on action, reflection and learning
    • Evidence informs subsequent cycles
    • Change is part of the research process, not merely an afterthought
    • DBA Week 4 • Action Research • 5
    05
  6. What Action Research is NOT

    • Not consultancy alone
    • Not change management alone
    • Recommendations without a transparent scholarly research process.
    • Implementing a project does not automatically constitute research.
    • Not a survey with an intervention
    • Not informal problem solving
    • A questionnaire plus an intervention is not automatically Action Research.
    • Good intentions are insufficient without systematic evidence.
    • Not a loose cycle
    • Not researcher-only activity
    • Calling activities 'Plan–Act–Reflect' does not prove rigour.
    • Meaningful engagement with the practice setting is normally central.
    • DBA Week 4 • Action Research • 6
    06
  7. Foundations of Action Research

    • Practical problem orientation: begins with a meaningful issue in a real setting.
    • Systematicity: research questions, evidence, analysis and decisions are documented.
    • Collaboration: participants are contributors to knowledge where appropriate.
    • Reflexivity: the researcher examines assumptions, role, influence and decisions.
    • Change: an intervention or action is designed, implemented and evaluated.
    • Learning: each cycle informs the next cycle and contributes to organisational knowledge.
    • Context: findings are interpreted in relation to the specific organisation and environment.
    • Ethics: consent, confidentiality, power relationships and potential harms are addressed.
    • DBA Week 4 • Action Research • 7
    07
  8. The Action Research Cycle

    • Plan → Act → Observe → Reflect → Revise
    • 1. PLAN
    • 2. ACT
    • 3. OBSERVE
    • 4. REFLECT
    • 5. REVISE
    • Key idea
    • Reflection does not end the research. It feeds the next plan. This creates a spiral of learning and improvement rather than a single linear intervention.
    • DBA Week 4 • Action Research • 8
    08
  9. Stage 1 — PLAN

    • Diagnose the problem and design a defensible intervention.
    • Planning questions
    • Define the organisational problem and why it matters.
    • Review existing evidence, theory and prior research.
    • Identify stakeholders and participants.
    • Specify research questions and objectives.
    • Decide what action/intervention will be introduced.
    • Define what evidence will indicate improvement or learning.
    • Plan ethics, access, consent, confidentiality and data management.
    • Establish a feasible timeline and criteria for reviewing the cycle.
    • What is the problem?
    • For whom is it a problem?
    • What evidence supports the diagnosis?
    • What could realistically change?
    • Who should participate?
    • What will we observe?
    • How will we know whether the action helped?
    • What alternatives could explain the result?
    • DBA Week 4 • Action Research • 9
    09
  10. Stage 2 — ACT

    • Example
    • Implement the intervention while preserving the research logic.
    • Problem: slow customer-response times.
    • Action: redesigned service workflow + staff training.
    • Evidence: response-time metrics + staff interviews + customer feedback + implementation records.
    • The intervention is not automatically the research; the systematic inquiry around it is.
    • Implement a clearly described action or intervention.
    • Record what was actually done—not only what was planned.
    • Monitor participation, context, deviations and unexpected events.
    • Collect evidence relevant to outcomes and process.
    • Maintain a decision log where practical.
    • Protect participants and organisational confidentiality.
    • Do not manipulate evidence simply to demonstrate success.
    • DBA Week 4 • Action Research • 10
    10
  11. Stage 3 — OBSERVE

    • Collect evidence about what happened and why.
    • Outcome evidence: did performance, quality, satisfaction or another indicator change?
    • Process evidence: how was the intervention implemented?
    • Participant perspectives: what did participants experience, learn or recommend?
    • Contextual evidence: what organisational or environmental factors affected results?
    • Four evidence lenses
    • Outcome • Process • Participant perspective • Context
    • Use evidence that directly answers the research question and helps explain the cycle.
    • DBA Week 4 • Action Research • 11
    11
  12. Stage 4 — REFLECT

    • Move from 'what happened?' to 'what does it mean?'
    • Compare intended action with actual implementation.
    • Interpret quantitative and/or qualitative evidence.
    • Examine unexpected outcomes and competing explanations.
    • Ask whose perspective is represented—and whose is missing.
    • Consider researcher influence and positionality.
    • Identify what was learned about the problem, intervention and context.
    • Decide whether to continue, modify, stop or redesign.
    • Reflection is analytical
    • Description: “Staff reported shorter delays.”
    • Reflection: “Shorter delays coincided with the workflow change, but interviews suggest the improvement was strongest where supervisors reinforced the new process.”
    • The second statement informs the next cycle.
    • DBA Week 4 • Action Research • 12
    12
  13. Stage 5 — REVISE / NEXT CYCLE

    • Use learning to design the next, better-informed cycle.
    • Retain elements that appear useful and defensible.
    • Modify elements that produced weak, mixed or unintended results.
    • Refine research questions if justified by evidence.
    • Change measures or data sources where gaps are identified.
    • Re-engage participants in interpreting findings and planning.
    • Document why decisions changed.
    • Begin the next cycle with a clearer problem understanding.
    • Spiral rather than circle
    • Cycle 1 → learning
    • Cycle 2 → deeper learning
    • Cycle 3 → consolidation
    • Each cycle should add knowledge, improve practice, or both.
    • The DBA thesis should explain the logic linking cycles.
    • DBA Week 4 • Action Research • 13
    13
  14. The Action Research Spiral

    • Each cycle should deepen understanding and improve the next decision.
    • What increases over time?
    • Cycle 4
    • Better problem definition
    • Better evidence
    • Better intervention design
    • Better participant understanding
    • Better theoretical interpretation
    • Stronger practical recommendations
    • Cycle 3
    • Cycle 2
    • Cycle 1
    • DBA Week 4 • Action Research • 14
    14
  15. Participation: Who is Involved?

    • Researcher
    • Practitioners / participants
    • Organisation / stakeholders
    • Designs and justifies the research process.
    • Collects/interprets evidence.
    • Maintains reflexivity and methodological transparency.
    • Does not automatically become the sole owner of knowledge.
    • Help identify problems.
    • Contribute experiential knowledge.
    • Participate in action and/or reflection.
    • May help interpret findings and shape subsequent cycles.
    • Provide context and access.
    • May support implementation.
    • Can influence feasibility and sustainability.
    • Must not compromise participant rights or research integrity.
    • DBA Week 4 • Action Research • 15
    15
  16. The DBA Researcher as a Participant-Researcher

    • Action Research can make the researcher part of the organisational situation being studied.
    • This creates access and practical insight—but also risks bias, role conflict and power effects.
    • Reflexivity requires the researcher to make their position and influence visible.
    • Keep an audit trail of major decisions, changes to the intervention and interpretation.
    • Use triangulation where appropriate: different data sources, methods or perspectives.
    • Distinguish participant voice, researcher interpretation and evidence-supported inference.
    • Reflexive questions
    • How might my role influence participants?
    • What assumptions did I bring?
    • Could participants feel pressured?
    • What evidence challenges my interpretation?
    • What changed because of my involvement?
    • How have I documented these effects?
    • DBA Week 4 • Action Research • 16
    16
  17. From Organisational Problem to DBA Research Question

    • Problem
    • Customer complaints are increasing.
    • Diagnosis
    • Evidence suggests inconsistent service processes.
    • Research gap
    • Existing studies do not explain how the intervention works in this context.
    • Action
    • Co-design and implement a standardised workflow.
    • Inquiry
    • How does the intervention influence response quality and employee learning?
    • Reflection
    • What worked, for whom, under what conditions—and why?
    • DBA Week 4 • Action Research • 17
    17
  18. Designing Action Research Questions

    • Descriptive
    • Action-oriented
    • Explanatory / reflective
    • What is happening?
    • What patterns, experiences and contextual conditions characterise the problem?
    • Useful early in diagnosis.
    • How can a specific intervention improve or address the problem?
    • What changes when the intervention is introduced?
    • Connects inquiry to action.
    • Why did the intervention produce particular outcomes?
    • What did participants learn?
    • Under what conditions did change occur?
    • DBA Week 4 • Action Research • 18
    18
  19. Evidence and Data in Action Research

    • Action Research can use quantitative, qualitative or mixed evidence.
    • Quantitative
    • Qualitative
    • KPIs, surveys, transaction data, performance metrics, time measures, pre/post indicators.
    • Interviews, focus groups, observations, reflective journals, meeting records, participant narratives.
    • Documentary
    • Mixed evidence
    • Policies, process maps, reports, complaints, audit records, project documentation.
    • Combines numerical change with participant and contextual explanations.
    • DBA Week 4 • Action Research • 19
    19
  20. Quantitative Evidence: What Can You Demonstrate?

    • Define an outcome indicator before the intervention where possible.
    • Use comparable measures across cycles.
    • Consider baseline or pre-intervention data.
    • Use descriptive statistics to show patterns and change.
    • Where appropriate, use inferential tests suited to the design and sample.
    • Do not claim causality simply because an outcome improved after an intervention.
    • Consider alternative explanations: seasonality, staffing, policy changes, economic conditions and concurrent projects.
    • DBA standard
    • What exactly changed?
    • How was it measured?
    • Compared with what?
    • What other factors could explain the change?
    • How does the evidence connect to the research question and theory?
    • DBA Week 4 • Action Research • 20
    20
  21. Qualitative Evidence: Understanding Experience and Process

    • Capture participant experiences of the intervention.
    • Explore mechanisms: how and why did change occur?
    • Identify barriers, enablers, resistance and unintended effects.
    • Use transparent coding and thematic analysis.
    • Compare perspectives across participant groups.
    • Preserve an audit trail of coding and interpretation.
    • Use quotations selectively as evidence—not as a substitute for analysis.
    • Example coding logic
    • Raw statement → code → category → theme → interpretation
    • “Training made the new process easier.”
    • Code: perceived competence
    • Category: capability
    • Theme: capability as an implementation condition
    • DBA Week 4 • Action Research • 21
    21
  22. Mixed Evidence: Triangulation

    • Triangulation asks
    • Do different sources point in the same direction?
    • Where do they disagree?
    • What does disagreement teach us about context?
    • The aim is not forced agreement; it is stronger interpretation.
    • DBA Week 4 • Action Research • 22
    22
  23. Ethics in Action Research

    • Voluntary participation and informed consent.
    • Clear explanation of research purpose and intervention.
    • Confidentiality and secure handling of organisational and personal data.
    • Careful management of power relationships—especially where the researcher supervises participants.
    • Right to decline participation without penalty.
    • Minimise risks associated with workplace disclosure or reputational harm.
    • Ethical approval should be secured before research activities requiring approval begin.
    • Be transparent about conflicts of interest and dual roles.
    • Important DBA question
    • Can an employee freely refuse if their manager is the researcher?
    • If not, redesign recruitment, consent and role boundaries to reduce undue influence.
    • DBA Week 4 • Action Research • 23
    23
  24. Rigour: How Do We Know the Research Is Credible?

    • Credibility
    • Dependability
    • Confirmability
    • Are interpretations supported by evidence and participant/context knowledge?
    • Is the process documented well enough to understand how conclusions were reached?
    • Can readers see the basis for interpretations rather than only the researcher's opinion?
    • Transferability / applicability
    • Triangulation
    • Reflexivity
    • Are context and boundaries described so others can judge relevance?
    • Are multiple sources, methods or perspectives used where appropriate?
    • Is researcher influence acknowledged and critically examined?
    • DBA Week 4 • Action Research • 24
    24
  25. Common DBA Mistakes in Action Research

    • Calling any organisational intervention 'Action Research'.
    • No clear research question—only a business problem.
    • No baseline or meaningful evidence of change.
    • Reporting activities instead of analysing cycles.
    • Reflection written as personal opinion without evidence.
    • Participants are described as 'involved' but their role is unclear.
    • No explanation of how cycles connect.
    • Claims of success without considering alternative explanations.
    • Theoretical framework disconnected from the action.
    • Ethical risks of dual roles and workplace power are ignored.
    • DBA Week 4 • Action Research • 25
    25
  26. Theory and Action Research

    • Before action
    • During cycles
    • After cycles
    • Use literature and theory to diagnose the problem.
    • Identify constructs and mechanisms that may matter.
    • Build a reasoned conceptual framework.
    • Use theory to interpret what is happening.
    • Ask whether evidence supports, extends or challenges existing explanations.
    • Do not force findings into the theory.
    • Connect learning back to literature.
    • Explain theoretical contribution as well as practical contribution.
    • State boundaries: context, participants and conditions.
    • DBA Week 4 • Action Research • 26
    26
  27. Where Action Research Fits in a DBA Dissertation

    • Chapter 1
    • Problem, context, purpose, research questions and significance.
    • Chapter 2
    • Literature, theory, prior evidence and research gap.
    • Chapter 3
    • Action Research philosophy/approach, participants, cycles, intervention, data, ethics and analysis.
    • Chapter 4
    • Evidence and findings from each cycle; integrate quantitative/qualitative analysis.
    • Chapter 5/6
    • Cross-cycle discussion, conclusions, theoretical and practical contribution.
    • Recommendations
    • Sustainable practice changes, future research and limitations.
    • DBA Week 4 • Action Research • 27
    27
  28. Worked DBA Example: Improving Employee Adoption of an ERP System

    • Problem
    • Cycle 1
    • Cycle 2
    • Contribution
    • Employees use the new ERP inconsistently.
    • Errors and duplicated work increase.
    • Management wants a practical improvement.
    • PLAN: diagnose barriers.
    • ACT: targeted training + workflow guide.
    • OBSERVE: system data + interviews.
    • REFLECT: training helps, but role ambiguity remains.
    • PLAN: clarify roles.
    • ACT: role-based workflow redesign.
    • OBSERVE: error rate + interviews.
    • REFLECT: stronger adoption, but one team needs supervisor support.
    • Practice:
    • Improved adoption.
    • Research:
    • Explains conditions supporting implementation and employee learning.
    • DBA Week 4 • Action Research • 28
    28
  29. Classroom Case: Is This Action Research?

    • Scenario
    • Students must ask
    • A bank notices long customer waiting times. A manager introduces a new queue system. After four weeks, waiting times are lower. The manager reports the improvement to senior leadership.
    • Question: Is this Action Research?
    • 1. Was there a research question?
    • 2. Was evidence systematically collected?
    • 3. Were participants involved?
    • 4. Was there reflection?
    • 5. Was learning documented?
    • 6. Was another cycle considered?
    • 7. Was the intervention studied—not merely implemented?
    • Conclusion: action alone is insufficient.
    • DBA Week 4 • Action Research • 29
    29
  30. In-Class Activity: Build One Action Research Cycle

    • Small groups • 20–30 minutes
    • 1. Choose a real organisational problem
    • 2. Diagnose
    • 3. Plan
    • Keep it specific, feasible and ethically researchable.
    • What evidence shows that the problem exists?
    • What intervention could realistically be introduced?
    • 4. Observe
    • 5. Reflect
    • 6. Revise
    • What quantitative and qualitative evidence will you collect?
    • What would count as success, failure or an unexpected result?
    • What would you change in Cycle 2?
    • DBA Week 4 • Action Research • 30
    30
  31. Questions for Group Presentations

    • What makes your problem a research problem rather than only a management problem?
    • What is your research question?
    • Who are the participants, and why are they relevant?
    • What exactly is the action/intervention?
    • What evidence will demonstrate change?
    • What evidence will explain why change did or did not occur?
    • What will you do if results contradict your expectations?
    • How will you protect participants from workplace pressure or harm?
    • How will you show researcher reflexivity?
    • What theoretical or scholarly contribution could emerge?
    • DBA Week 4 • Action Research • 31
    31
  32. Quick Knowledge Check

    • 1. Action Research requires action alone. True or False?
    • False — systematic inquiry and learning are also essential.
    • 2. Reflection can influence the next research cycle. True or False?
    • True — reflection informs revised planning and action.
    • 3. A software implementation automatically qualifies as Action Research. True or False?
    • False — implementation is action, not necessarily research.
    • 4. Can Action Research use quantitative data?
    • Yes — it can use quantitative, qualitative or mixed evidence.
    • 5. Why is reflexivity important?
    • Because the researcher may influence the setting and interpretation.
    • DBA Week 4 • Action Research • 32
    32
  33. DBA Action Research Checklist

    • □ Clear organisational problem and research gap
    • □ Explicit research question(s) and objectives
    • □ Appropriate theoretical/conceptual framing
    • □ Justified Action Research approach
    • □ Clearly defined participants and roles
    • □ Ethical approval and informed consent where required
    • □ Explicit intervention/action
    • □ Planned evidence and measures
    • □ Transparent analysis procedures
    • □ Documented cycles and decisions
    • □ Reflection supported by evidence
    • □ Researcher reflexivity
    • □ Practical contribution
    • □ Theoretical/scholarly contribution
    • □ Limitations and boundary conditions
    • DBA Week 4 • Action Research • 33
    33
  34. Suggested Teaching Flow for Week 4

    • 0–15 min
    • Concept + why 'action' matters
    • 15–30 min
    • Action Research vs conventional research
    • 30–50 min
    • Cycle: Plan → Act → Observe → Reflect → Revise
    • 50–70 min
    • Evidence, participation, reflexivity and ethics
    • 70–95 min
    • Worked DBA example + group activity
    • 95–110 min
    • Group presentations + critique
    • 110–120 min
    • Quiz + dissertation checklist + take-home task
    • DBA Week 4 • Action Research • 34
    34
  35. Take-Home DBA Task

    • Prepare a one-page Action Research concept note.
    • 1. Organisational problem and context
    • 2. Evidence that the problem exists
    • 3. Research gap
    • 4. Research question(s)
    • 5. Proposed participants/stakeholders
    • 6. Proposed action/intervention
    • 7. Evidence and data sources
    • 8. Planned reflection and next-cycle decision rules
    • 9. Ethical considerations
    • 10. Expected practical and scholarly contribution
    • Bring to next class
    • Be prepared to defend:
    • Why is this Action Research?
    • Why this intervention?
    • Why these participants?
    • How will you know whether it worked?
    • What will you learn if it does not work?
    • How will the research contribute beyond the organisation?
    • DBA Week 4 • Action Research • 35
    35
  36. Week 4 — Key Takeaways

    • Core message
    • Action Research is not simply research about organisations and not simply action in organisations. It is a systematic, ethical and reflective process in which research and action inform one another through iterative cycles of learning and change.
    • DBA Week 4 • Action Research • 36
    36
01 / 36

Slides in this deck

  1. DBA 704 — Week 4: Action Research in Practice
  2. Learning Outcomes
  3. 4. Why is it called "Action" Research?
  4. What Makes a Study Action Research?
  5. Action Research vs Conventional Organisational Research
  6. What Action Research is NOT
  7. Foundations of Action Research
  8. The Action Research Cycle
  9. Stage 1 — PLAN
  10. Stage 2 — ACT
  11. Stage 3 — OBSERVE
  12. Stage 4 — REFLECT
  13. Stage 5 — REVISE / NEXT CYCLE
  14. The Action Research Spiral
  15. Participation: Who is Involved?
  16. The DBA Researcher as a Participant-Researcher
  17. From Organisational Problem to DBA Research Question
  18. Designing Action Research Questions
  19. Evidence and Data in Action Research
  20. Quantitative Evidence: What Can You Demonstrate?
  21. Qualitative Evidence: Understanding Experience and Process
  22. Mixed Evidence: Triangulation
  23. Ethics in Action Research
  24. Rigour: How Do We Know the Research Is Credible?
  25. Common DBA Mistakes in Action Research
  26. Theory and Action Research
  27. Where Action Research Fits in a DBA Dissertation
  28. Worked DBA Example: Improving Employee Adoption of an ERP System
  29. Classroom Case: Is This Action Research?
  30. In-Class Activity: Build One Action Research Cycle
  31. Questions for Group Presentations
  32. Quick Knowledge Check
  33. DBA Action Research Checklist
  34. Suggested Teaching Flow for Week 4
  35. Take-Home DBA Task
  36. Week 4 — Key Takeaways