Prof. Dr. Larry AdamsAcademic, Author & Researcher
DBA 704 — Week 1: Introduction to Action Research · 50 slides

Presentation · 50 slides

DBA 704 — Week 1: Introduction to Action Research

Doctor of Business Administration · Action Research module

Prof. Dr. Larry Adams

Week 1: Introduction to Action Research — 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 1: Introduction to Action Research

    DBA 704 — Introduction to Action Research

    Week 1: Introduction to Action Research in Operations Management

    Prof. Dr. Larry Adams.

    01
  2. 1. What We Will Learn Today

    • Nature and purpose of Action Research
    • Origins and development of Action Research
    • Defining characteristics: action, research, participation, reflection and learning
    • Action Research versus traditional research, consulting and problem-solving
    • The practitioner-researcher and researcher positionality
    • Action Research and organizational improvement
    • Relevance to Operations Management
    • The Action Research cycle and doctoral-level rigor
    • Theory–practice relationship, ethics and feasibility
    • Preparing for Assessment 1
    02
  3. 2. The Big Idea of Week 1

    • Week 1 is not simply about memorising a definition.
    • It establishes the intellectual foundation for the entire DBA 704 module.
    • Action Research generates knowledge while addressing a real-world problem.
    • It combines systematic inquiry with action, participation, evidence, reflection and learning.
    • The goal is both organizational improvement and credible scholarly knowledge.
    03
  4. 3. A Simple Way to Understand Action Research

    • ACTION = something is deliberately changed, tested, implemented or improved.
    • RESEARCH = the change is investigated systematically so that knowledge can be generated.
    • Therefore: Action Research = systematic action + observation/evidence + reflection + learning.
    • Important: ordinary management action is not automatically Action Research.
    • The research process must be explicit.
    • The Action Research mindset
    04
  5. 4. The Action Research Mindset

    • Ordinary approach: “Find a problem, fix it, and move on.”
    • Action Research approach:
    • Identify an important operational problem.
    • Investigate it systematically.
    • Work collaboratively with relevant participants.
    • Take informed action and collect evidence.
    • Reflect critically, learn, and use the learning to inform further action.
    • The cycle
    05
  6. 5. The Master Action Research Cycle

    • PROBLEM → DIAGNOSIS → PLANNING → ACTION
    • ↓
    • OBSERVATION / EVIDENCE → REFLECTION → LEARNING
    • ↓
    • REVISED ACTION → NEXT CYCLE
    • The cycle is iterative, not simply a straight line.
    • The end of one cycle becomes the beginning of another.
    06
  7. 6. The Basic Logic — Step by Step

    • 1. Something needs to be understood or improved.
    • 2. Investigate what is happening.
    • 3. Plan an intervention.
    • 4. Take action.
    • 5. Examine what happened using evidence.
    • 6. Reflect critically.
    • 7. Identify what has been learned.
    • 8. Modify the action and begin the next cycle.
    07
  8. 7. Action Research vs. Ordinary Problem Solving

    • Example: customer-service delays.
    • Managerial problem solving might say: “Service is too slow; hire two more employees.”
    • Action Research asks:
    • What exactly is causing the delay?
    • What evidence establishes the problem?
    • How do employees and customers understand it?
    • What intervention should be implemented?
    • What happened after the intervention?
    • What was learned, and what should change next?
    08
  9. 8. Action Research vs. Consulting

    • Consulting primarily focuses on solving a client problem.
    • Action Research focuses on understanding and addressing a problem through research.
    • Consultants may diagnose and recommend; Action Researchers may diagnose and act collaboratively.
    • Consulting may end with recommendations; Action Research commonly continues through cycles.
    • In Action Research, research design, rigor, evidence and scholarly contribution are central.
    • Key message: diagnosing a problem and recommending a solution is not automatically Action Research.
    09
  10. 9. Action Research vs. Traditional Research

    • Traditional research may maintain greater researcher distance; Action Research may involve active participation.
    • Participants may be research subjects; Action Research often treats them as collaborators or co-inquirers.
    • Traditional research may observe an existing situation; Action Research investigates while changing the situation.
    • Traditional designs may be relatively fixed; Action Research can evolve through cycles.
    • Traditional research often emphasises explaining phenomena; Action Research also emphasises understanding and improving practice.
    10
  11. 10. Two Different Kinds of Knowledge

    • Traditional research can produce KNOWLEDGE ABOUT an organization.
    • Example: employees report that an inventory system is difficult to use.
    • Action Research can produce KNOWLEDGE THROUGH changing an organization.
    • Example: employees participate in redesigning the inventory process; evidence shows adoption increases, while reflection reveals the importance of training and managerial support.
    • Doctoral Action Research connects action, participation, evidence, reflection, context and possible theoretical contribution.
    11
  12. 11. What Makes Action Research “Research”?

    • 1. A clear research problem
    • 2. Research questions or objectives
    • 3. Theoretical grounding
    • 4. Methodological design
    • 5. Systematic evidence
    • 6. Critical reflection
    • 7. Transparency and documentation
    • 8. Rigor
    • 9. Ethical conduct
    • 10. Contribution to practice and/or scholarly knowledge
    12
  13. 12. What Does Doctoral Rigor Mean?

    • Action Research is not a less rigorous form of research because the researcher participates.
    • Rigor includes clear research questions and appropriate theoretical grounding.
    • Use transparent methodology and systematic data collection.
    • Use triangulation where appropriate.
    • Document Action Research cycles clearly.
    • Practise critical reflection and reflexivity.
    • Acknowledge limitations and maintain ethical research practice.
    • Participation does not remove rigor; it makes transparency and reflexivity especially important.
    • Practitioner + Researcher
    13
  14. 13. The Practitioner-Researcher

    • In DBA Action Research, the researcher may simultaneously be:
    • PRACTITIONER + RESEARCHER + PARTICIPANT + FACILITATOR OF CHANGE
    • Potential advantages: organizational knowledge, contextual understanding, access, history and practical insight.
    • Potential challenges: bias, role conflict, politics, power relationships, assumptions, confidentiality and competing responsibilities.
    • Your position matters
    14
  15. Four common forms of triangulation At doctoral level, it is useful to distinguish these:

      15
    • 14. Researcher Positionality

      • Ask: “Who am I in relation to the organization I am studying?”
      • The researcher may be a manager, consultant, employee, executive, department head, external researcher or organizational partner.
      • Position can influence access, relationships, participant behaviour, interpretation, intervention, power and ethics.
      • Key message: the researcher’s presence may influence the organization.
      • Therefore, reflexivity is essential.
      • Participants matter
      16
    • 15. Participants: From Subjects to Co-Inquirers

      • Action Research moves attention from research subjects toward participants, collaborators and co-inquirers.
      • Ask who possesses relevant knowledge.
      • Ask who is affected by the problem.
      • Ask who should participate and who has decision-making power.
      • Ask who implements the intervention.
      • Ask whose perspectives may be missing.
      • Participation does not necessarily mean equal authority for everyone; roles must be considered carefully.
      17
    • 16. Why Participation Matters

      • Warehouse example: a manager believes inefficiency is caused by employees not working hard enough.
      • Employees may identify other causes:
      • inefficient warehouse layout
      • malfunctioning scanners
      • inaccurate inventory information
      • constantly changing orders
      • poorly designed staffing schedules
      • Participation can improve the quality of diagnosis and intervention.
      • Operations in action
      18
    • 17. Action Research in Operations Management

      • Operations Management concerns how organizations produce, deliver, coordinate and process work.
      • It includes resource management, quality, supply chains, services, technology and process improvement.
      • Action Research is useful when a real operational problem exists and meaningful change is both necessary and possible.
      • The operational setting becomes a context for systematic inquiry and learning.
      19
    • 18. Operations Example 1 — Production Delays

      • Problem: production orders regularly miss deadlines.
      • Potential Action Research:
      • Diagnosis → identify bottlenecks → redesign workflow → implement → measure delays → reflect → redesign again.
      • Notice the difference: the researcher does not simply recommend a solution; the intervention becomes part of the inquiry.
      20
    • 19. Operations Example 2 — Inventory Inaccuracies

      • Problem: inventory records do not match physical inventory.
      • Potential intervention: redesign the inventory verification process.
      • Possible evidence:
      • inventory accuracy
      • error rates
      • employee feedback
      • process observations
      • Reflection question: Why did some employees adopt the new procedure while others did not?
      21
    • 20. Operations Example 3 — Customer-Service Delays

      • Problem: customers experience long response times.
      • Possible intervention: redesign the customer-service workflow.
      • Evidence could include response time, complaints, employee experience and customer feedback.
      • Reflection: Which organizational factors affected implementation?
      22
    • 21. Operations Example 4 — Digital Transformation

      • Problem: employees resist a new digital system.
      • Possible intervention: collaboratively redesign implementation and training.
      • Evidence: system usage, employee feedback, adoption rates and workflow performance.
      • Doctoral question: Is the issue resistance to technology, or resistance to how the technology was introduced?
      23
    • 22. When Is Action Research Appropriate?

      • The problem is real and organizationally important.
      • Change is possible: the researcher and participants can influence the situation.
      • Relevant stakeholders can participate.
      • The researcher has appropriate access.
      • Evidence of change can be collected.
      • Iteration is realistically possible.
      • Ethical conditions can be satisfied.
      • The project can produce scholarly learning beyond an internal management report.
      24
    • 23. When May Action Research NOT Be Appropriate?

      • The researcher cannot influence the situation.
      • Participants cannot realistically participate.
      • Organizational access is unavailable.
      • Intervention is impossible.
      • Ethical risks are unacceptable.
      • The study only aims to describe a phenomenon.
      • Complete detachment is required.
      • There is no realistic opportunity for iterative action.
      • The project is merely a consultancy exercise.
      • Do not choose Action Research because it sounds practical; choose it because it fits the problem, purpose and context.
      25
    • 24. The Eight Stages of the Cycle

      • 1. PROBLEM — What is happening?
      • 2. DIAGNOSIS — Why is it happening?
      • 3. PLANNING — What could we change?
      • 4. ACTION — What did we actually do?
      • 5. OBSERVATION / EVIDENCE — What evidence do we have?
      • 6. REFLECTION — What happened, and why?
      • 7. LEARNING — What do we now understand?
      • 8. REVISED ACTION — What should we do differently next cycle?
      26
    • 25. Why Does the Cycle Repeat?

      • First cycle: researcher assumes employees need more training.
      • Training is implemented but performance does not improve.
      • Reflection reveals that the software workflow was poorly designed.
      • Second cycle addresses the software.
      • Lesson: learning from action changes the next action.
      • This is the essence of iterative Action Research.
      27
    • 26. What If the Intervention Fails?

      • Failure can become data.
      • Ask: Why did it fail?
      • What assumption was wrong?
      • What did participants experience?
      • What contextual factors interfered?
      • What unintended consequences occurred?
      • What should be changed?
      • An unsuccessful intervention can still produce valuable research knowledge.
      28
    • 27. Action Research and Theory

      • Action Research should not be practice without theory.
      • It should not be theory without practice.
      • Think: THEORY ↔ PRACTICE
      • Theory can help identify problems, understand causes, design interventions and interpret findings.
      • Practice can test assumptions, reveal context, challenge theory, generate insights and identify literature gaps.
      29
    • 28. From Practical Problem to Research Problem

      • Too broad: “Our organization has poor inventory control.”
      • Improved: “The organization has experienced persistent discrepancies between recorded and physical inventory despite existing control procedures.”
      • Research-oriented: “There is insufficient understanding of the organizational and process factors contributing to persistent inventory discrepancies, and existing control practices have not adequately addressed the problem.”
      • A doctoral researcher moves from description toward systematic inquiry.
      30
    • 29. The Operational Problem Selection Test

      • A — Important: Does it matter to the organization?
      • B — Researchable: Can evidence be collected?
      • C — Actionable: Can something realistically be changed?
      • D — Accessible: Can relevant people and information be accessed?
      • E — Ethical: Can participants be protected?
      • F — Iterative: Can learning inform subsequent action?
      • G — Scholarly: Can knowledge be generated beyond fixing the immediate problem?
      • Think like a doctoral researcher
      31
    • 30. Doctoral-Level Questions

      • What makes Action Research research rather than consulting?
      • If the researcher participates in an intervention, can the research still be rigorous?
      • Can an unsuccessful intervention produce valid research knowledge?
      • Who owns knowledge generated through Action Research?
      • What happens when the researcher’s role creates a power imbalance?
      • How can meaningful change be demonstrated?
      • What distinguishes a management problem from a doctoral research problem?
      • What scholarly contribution could emerge from solving a practical problem?
      • Case discussion
      32
    • 31. Case Study — Warehouse Order Processing

      • A company is experiencing increasing delays in fulfilling customer orders.
      • Management believes employee productivity is the problem.
      • Employees identify outdated software, poor layout, inaccurate inventory, unclear priorities and departmental communication problems.
      • Customer complaints are increasing.
      • Management wants immediate improvement.
      • A DBA researcher working inside the organization is asked to investigate.
      33
    • 32. Case Study Discussion

      • 1. What is the operational problem?
      • 2. What evidence would you need?
      • 3. What assumptions has management already made?
      • 4. Who should participate?
      • 5. What could the researcher diagnose?
      • 6. What intervention might be considered?
      • 7. What evidence could demonstrate improvement?
      • 8. What ethical issues could arise?
      • 9. What risks exist because the researcher works inside the organization?
      • 10. How could this become Action Research rather than consulting?
      • Group activity
      34
    • 33. Group Exercise

      • Task: Convert an organizational problem into a potential Action Research problem.
      • A. Operational problem — What is wrong?
      • B. Evidence — How do we know?
      • C. Stakeholders — Who is affected?
      • D. Possible causes — Why might it be happening?
      • E. Intervention — What could potentially be changed?
      • F. Evidence — How will we know whether it made a difference?
      • G. Reflection — What would we need to learn?
      • H. Next cycle — What might we change next?
      • Your own problem
      35
    • 34. Individual Student Activity

      • Identify one significant operational challenge in your professional context.
      • 1. What is the problem?
      • 2. Where does it occur?
      • 3. Who experiences it?
      • 4. What evidence suggests that it exists?
      • 5. Why is it important?
      • 6. What has already been attempted?
      • 7. Could you intervene?
      • 8. Who needs to participate?
      • 9. Why might Action Research be appropriate?
      36
    • 35. Student Worksheet

      • Operational problem: __________________________
      • Organizational context: ________________________
      • Who is affected: ______________________________
      • Evidence that the problem exists: ______________
      • Why the problem matters: ______________________
      • Possible causes: ______________________________
      • Previous attempts: _____________________________
      • Potential intervention: _________________________
      • Potential participants: ________________________
      • Potential evidence: ____________________________
      • Why Action Research may be appropriate: ________
      37
    • 36. Your First Action Research Cycle

      • ↓
      • ↓
      • ↓
      • ↓
      • ↓
      • ↓
      • ↓
      • REVISED ACTION → NEXT CYCLE
      38
    • 37. Assessment 1 — What You Need to Do

      • Identify an operational challenge in your professional context.
      • Explain how the foundational principles of Action Research apply to addressing it.
      • Section 1: Introduction to the operational challenge.
      • Section 2: Organizational context.
      • Section 3: Significance — why does it matter?
      • Section 4: Action Research suitability — why is this methodology appropriate?
      • Section 5: Foundational principles — participation, action, reflection, iteration, collaboration and rigor.
      39
    • 38. How to Move Beyond a Weak Answer

      • Weak: “My organization has customer-service problems. Customers wait too long and employees need training. Action Research would solve it.”
      • Why weak? It describes the problem and jumps to a solution without demonstrating doctoral reasoning.
      • A stronger response establishes evidence, context, access, participation and possible causes.
      • It explains why Action Research fits the problem and how iterative diagnosis, intervention, observation and reflection could generate learning.
      40
    • 39. How DBA-Level Reading Should Work

      • Read the Action Research literature on methodology, Operations Management, dual contribution, rigor, opportunities and weaknesses.
      • Do not simply collect quotations.
      • Ask: What does this author argue?
      • What assumptions underpin the argument?
      • What are the strengths and limitations?
      • How does the argument apply to my operational problem?
      • How does the literature justify my methodological choice?
      41
    • 40. Important Reading Message

      • Do not use the literature simply to define Action Research.
      • Use the literature to justify methodological decisions.
      • At DBA level, literature should support critical reasoning, methodological justification and scholarly contribution.
      • The question is not only “What is Action Research?”
      • The stronger question is “Why is Action Research appropriate for my particular problem, purpose and context?”
      42
    • 41. Week 1 Homework / Deliverable

      • Submit a one-page Action Research Problem Brief.
      • Include:
      • 1. Operational problem
      • 2. Organizational context
      • 3. Evidence of the problem
      • 4. Stakeholders
      • 5. Why the problem matters
      • 6. Possible intervention
      • 7. Why Action Research may be appropriate
      • 8. Preliminary Action Research cycle
      43
    • 42. Week 1 Summary — Where Are We Now?

      • PROBLEM — a potential operational problem has been identified.
      • PHILOSOPHY — begin considering how you understand reality and knowledge.
      • PARTICIPATION — identify who should be involved.
      • RIGOR — distinguish research from ordinary organizational problem solving.
      • THEORY/PRACTICE — consider how scholarly knowledge and practical improvement interact.
      • These foundations support the remaining weeks of DBA 704.
      44
    • 43. The DBA 704 Eight-Week Intellectual Journey

      • Week 1 — What is the problem and why is Action Research appropriate?
      • Week 2 — What philosophical assumptions underpin my inquiry?
      • Week 3 — How will the Action Research cycle operate?
      • Week 4 — How do I diagnose the operational problem?
      • Week 5 — How do I design collaborative and ethical action?
      • Week 6 — How do I evaluate the intervention and demonstrate rigor?
      • Week 7 — What have I learned through critical reflection?
      • Week 8 — What does the Action Research contribute to practice, theory and scholarly knowledge?
      45
    • 44. The Intellectual Journey

      • → UNDERSTANDING
      • → ACTION
      • → EVIDENCE
      • → REFLECTION
      • → LEARNING
      • → IMPROVEMENT
      • → CONTRIBUTION
      46
    • 45. Six Key Messages to Remember

      • 1. Action Research is research through action, not simply action.
      • 2. A management problem is not automatically a research problem.
      • 3. Action Research is iterative: learning from one cycle informs the next.
      • 4. Participants are important sources of organizational knowledge and may actively participate.
      • 5. Participation does not eliminate rigor; it increases the importance of transparency, reflexivity, evidence and methodological justification.
      • 6. The goal is not merely to fix a problem, but to generate credible knowledge about the problem, intervention, change process and implications.
      • Reflect and apply
      47
    • 46. Final Reflection

      • If you were asked to solve an operational problem tomorrow, what would you do differently as an Action Researcher rather than simply as a manager or consultant?
      • Would you investigate before acting?
      • Would you involve participants and examine different perspectives?
      • Would you collect systematic evidence and document what happens?
      • Would you reflect on your assumptions?
      • Would you evaluate the intervention, learn from failure and revise the action?
      • Would you connect the experience with scholarly literature?
      48
    • 47. The Big Picture

      • You are not simply being asked to find something wrong in an organization and fix it.
      • A real organizational problem becomes the context for systematic inquiry.
      • The process combines collaborative action, evidence generation, critical reflection and learning.
      • The objective is to improve practice while producing knowledge that can withstand scholarly examination.
      • This is the foundation of DBA 704.
      49
    • 48. Closing Question

      • “What will you now do differently when you encounter an operational problem?”
      • Think like a manager: What should we do?
      • Think like a consultant: What solution should we recommend?
      • Think like an Action Researcher:
      • What is happening?
      • Why is it happening?
      • Who should participate?
      • What can we change?
      • What evidence will show what happened?
      • What have we learned?
      • What should we do next?
      50
    01 / 50

    Slides in this deck

    1. DBA 704 — Week 1: Introduction to Action Research
    2. 1. What We Will Learn Today
    3. 2. The Big Idea of Week 1
    4. 3. A Simple Way to Understand Action Research
    5. 4. The Action Research Mindset
    6. 5. The Master Action Research Cycle
    7. 6. The Basic Logic — Step by Step
    8. 7. Action Research vs. Ordinary Problem Solving
    9. 8. Action Research vs. Consulting
    10. 9. Action Research vs. Traditional Research
    11. 10. Two Different Kinds of Knowledge
    12. 11. What Makes Action Research “Research”?
    13. 12. What Does Doctoral Rigor Mean?
    14. 13. The Practitioner-Researcher
    15. Four common forms of triangulation At doctoral level, it is useful to distinguish these:
    16. 14. Researcher Positionality
    17. 15. Participants: From Subjects to Co-Inquirers
    18. 16. Why Participation Matters
    19. 17. Action Research in Operations Management
    20. 18. Operations Example 1 — Production Delays
    21. 19. Operations Example 2 — Inventory Inaccuracies
    22. 20. Operations Example 3 — Customer-Service Delays
    23. 21. Operations Example 4 — Digital Transformation
    24. 22. When Is Action Research Appropriate?
    25. 23. When May Action Research NOT Be Appropriate?
    26. 24. The Eight Stages of the Cycle
    27. 25. Why Does the Cycle Repeat?
    28. 26. What If the Intervention Fails?
    29. 27. Action Research and Theory
    30. 28. From Practical Problem to Research Problem
    31. 29. The Operational Problem Selection Test
    32. 30. Doctoral-Level Questions
    33. 31. Case Study — Warehouse Order Processing
    34. 32. Case Study Discussion
    35. 33. Group Exercise
    36. 34. Individual Student Activity
    37. 35. Student Worksheet
    38. 36. Your First Action Research Cycle
    39. 37. Assessment 1 — What You Need to Do
    40. 38. How to Move Beyond a Weak Answer
    41. 39. How DBA-Level Reading Should Work
    42. 40. Important Reading Message
    43. 41. Week 1 Homework / Deliverable
    44. 42. Week 1 Summary — Where Are We Now?
    45. 43. The DBA 704 Eight-Week Intellectual Journey
    46. 44. The Intellectual Journey
    47. 45. Six Key Messages to Remember
    48. 46. Final Reflection
    49. 47. The Big Picture
    50. 48. Closing Question