Prof. Dr. Larry AdamsAcademic, Author & Researcher
DBA 704 — Week 6: Identifying the Problem · 28 slides

Presentation · 28 slides

DBA 704 — Week 6: Identifying the Problem

Doctor of Business Administration · Action Research module

Prof. Dr. Larry Adams

Week 6: Identifying the Problem — 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 6: Identifying the Problem

    Stage 1 — Identifying the Problem

    From an operational problem to a focused, researchable DBA problem

    Prof. Dr. Larry Adams

    DBA 704 • Action Research in Operations Management

    Diagnose the situation • define the gap • establish evidence • formulate the research problem

    DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 1

    01
  2. Week 6 Learning Outcomes

    • Students should leave the session able to move from a vague operational concern to a defensible research problem.
    • Identify common operational problems suitable for action research.
    • Distinguish an operational problem from a research problem.
    • Recognise the difference between a symptom, problem, cause, and researchable problem.
    • Narrow a broad organisational issue into a specific and evidence-supported problem statement.
    • Establish why the problem matters to the organisation and to research.
    • Identify the affected process, population/stakeholders, location/context, time frame, and performance gap.
    • Use baseline evidence to avoid relying only on assumptions or anecdotal complaints.
    • Develop a preliminary problem statement that can guide diagnosis, planning, intervention, observation, and reflection in later cycles.
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 2
    02
  3. Where Stage 1 Fits in the Action Research Cycle

    • →
    • →
    • →
    • →
    • →
    • →
    • The quality of every later stage depends on the quality of the initial diagnosis.
    • STAGE 1
    • Starting point
    • Research task
    • Action-research task
    • An operational problem exists or is suspected.
    • Turn the concern into a focused problem that can be investigated.
    • Understand the situation before deciding what to change.
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 3
    03
  4. What Is an Operational Problem?

    • An operational problem is a condition in a process or organisational system that creates an undesirable performance, experience, risk, cost, delay, or outcome.
    • Customer service
    • Supply chain
    • Inventory
    • Quality
    • Long waiting times, complaints, inconsistent service delivery
    • Supplier delays, stockouts, transport disruptions, poor coordination
    • Excess inventory, stock discrepancies, obsolete items, inaccurate records
    • Defects, rework, process variation, failed inspections
    • People
    • Procurement
    • Warehouse
    • Production
    • Employee turnover, absenteeism, skill gaps, poor workflow allocation
    • Slow purchasing, approval bottlenecks, poor supplier performance
    • Picking errors, receiving errors, mislocation, inefficient layout
    • Bottlenecks, downtime, capacity constraints, scheduling problems
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 4
    04
  5. The Central Distinction

    • A problem is not yet a research problem.
    • Operational statement — too broad
    • Researchable problem — more focused
    • “Our warehouse is inefficient.” This may be true, but it does not tell the researcher: • What is inefficient? • Where does it occur? • How is inefficiency measured? • Who is affected? • What evidence supports the claim? • What process condition might be contributing?
    • “The warehouse is experiencing persistent inventory discrepancies associated with inconsistent inventory recording practices.” Now the researcher can investigate: • discrepancy frequency/magnitude • recording practices • process stages • employee experience • system/process controls • contextual factors
    • Broad concern → evidence → defined gap → researchable problem
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 5
    05
  6. Four Concepts Students Must Not Confuse

    • What is visible? Example: customers wait too long. A symptom signals that something requires attention, but does not explain the system.
    • What undesirable condition exists? Example: average waiting time exceeds the service target. This is more measurable.
    • What may contribute? Example: uneven workload allocation or inadequate staffing at peak periods. A suspected cause still needs evidence.
    • What can the researcher investigate and potentially improve? Example: inconsistent workload allocation contributes to excessive waiting time.
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 6
    06
  7. Problem Identification: The Funnel

    • 1. Organisation
    • 3. Performance gap
    • 5. Evidence
    • 7. Research problem
    • “Something is not working as expected.”
    • What measurable difference exists?
    • What data demonstrate the problem?
    • What specific problem can the study investigate and address?
    • 2. Process
    • 4. Context
    • 6. Explanation
    • Which process contains the issue?
    • Where, when, and for whom does it occur?
    • What possible contributing conditions require investigation?
    • Narrowing is not “making the problem smaller” for its own sake; it is making the problem sufficiently specific to investigate rigorously.
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 7
    07
  8. Step 1 — Start With the Process

    • Map the process in which the problem occurs.
    • Identify inputs, activities, decision points, handoffs, outputs, and customers.
    • Ask where delays, errors, duplication, waiting, rework, or failure enter the process.
    • Do not assume the problem belongs to the department that first reports it.
    • Look across functions: procurement → receiving → storage → production → distribution → customer.
    • Identify interfaces between people, technology, policy, suppliers, and workflow.
    • Use process maps, SIPOC, flowcharts, value-stream maps, or other appropriate operational tools.
    • Teaching example
    • Warehouse receiving: Supplier delivery → unloading → inspection → system entry → labelling → put-away Ask: At which step can inventory information become inaccurate? Do not jump directly to “employees make mistakes.”
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 8
    08
  9. Step 2 — Define the Performance Gap

    • Current state
    • Desired state
    • Gap
    • What is happening now? Example: Average customer waiting time = 42 minutes. Use actual evidence where possible.
    • What should happen? Example: Service target = 20 minutes. The target may come from policy, SLA, benchmark, regulation, strategy, or management expectation.
    • Current − desired = 22 minutes. The gap creates a basis for investigation. Then ask: Why does the gap persist, and what conditions sustain it?
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 9
    09
  10. Baseline Evidence: Do Not Build a Problem From Opinion Alone

    • Baseline evidence establishes that the problem exists and provides a reference point for later comparison.
    • Possible baseline measures include cycle time, waiting time, error rate, defect rate, stock accuracy, cost, throughput, service level, complaints, rework, or employee turnover.
    • Qualitative baseline evidence can include interviews, observations, open-ended responses, process narratives, meeting records, or document analysis.
    • Triangulate where practical: compare operational records with participant accounts and direct observation.
    • Be transparent about missing, incomplete, or biased baseline data.
    • Baseline does not have to be perfect; it must be sufficiently credible and appropriate for the research purpose.
    • Baseline checklist
    • What is measured? How often? By whom? Using what definition? Over what period? What is the data quality? What alternative explanations exist?
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 10
    10
  11. Example — Inventory Discrepancies

    • Observation
    • Evidence
    • Focused problem
    • Research direction
    • “The warehouse is inefficient.” Too broad. It combines multiple possible problems: layout, staffing, technology, inventory accuracy, picking, receiving, or scheduling.
    • Inventory records show repeated differences between system quantities and physical counts. Interviews indicate inconsistent recording practices at receiving and put-away.
    • “The warehouse is experiencing persistent inventory discrepancies associated with inconsistent inventory recording practices.”
    • Investigate: • recording workflow • causes • staff practices • system use • controls • feasible intervention
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 11
    11
  12. Problem Statement Formula

    • A useful working structure—not a rigid formula.
    • The [process/organisation] is experiencing [specific undesirable condition] in [context/population] as evidenced by [baseline evidence], with [possible contributing condition] requiring investigation.
    • Process/context
    • Condition
    • Evidence
    • Contributing condition
    • warehouse receiving customer service procurement production line
    • inventory discrepancies waiting time errors rework
    • KPI data records observations interviews
    • inconsistent recording unclear ownership workflow bottleneck technology gap
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 12
    12
  13. Bad → Better → Stronger Problem Statements

    • “Our company has poor supply-chain management.” Problems: • no process • no population • no measurable condition • no context
    • “The company experiences frequent supplier delays.” Improved, but still needs: • evidence • scope • affected process • context • possible mechanism
    • “Persistent supplier delivery delays in the inbound procurement process are contributing to production scheduling disruptions at the organisation’s main manufacturing facility.” Now the problem can be investigated.
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 13
    13
  14. Problem vs Research Question vs Purpose

    • These elements connect, but they are not interchangeable.
    • What undesirable condition exists? “Persistent inventory discrepancies associated with inconsistent recording practices.”
    • What does the researcher need to understand or examine? “How do inventory recording practices contribute to discrepancies, and how might the process be improved?”
    • What will the study do? “To investigate the recording process and collaboratively develop and evaluate an improved inventory-recording practice.”
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 14
    14
  15. Problem Identification Questions for DBA Researchers

    • WHAT exactly is wrong?
    • WHERE in the process does it occur?
    • WHEN does it occur—continuously, periodically, or under particular conditions?
    • WHO is affected or involved?
    • HOW large or important is the gap?
    • HOW long has the condition existed?
    • WHAT evidence demonstrates persistence?
    • WHAT processes, technologies, policies, behaviours, or contextual conditions may contribute?
    • WHY does the problem matter to organisational performance?
    • WHAT is already known—and what remains uncertain?
    • CAN the problem realistically be investigated and addressed within the study?
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 15
    15
  16. Root Cause Thinking — Use Carefully

    • Root-cause analysis can support diagnosis, but a suspected cause is not automatically an established cause.
    • 5 Whys
    • Fishbone / Ishikawa
    • DBA caution
    • Ask successive “why?” questions to move beyond the visible symptom. Useful for generating hypotheses about contributing conditions. Avoid forcing a single linear cause.
    • Explore categories such as: People • Process • Technology • Materials • Measurement • Environment Useful for broad diagnostic exploration.
    • Organisational problems are often multi-causal. Use evidence to test competing explanations. Do not label correlation, perception, or sequence as causation without adequate support.
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 16
    16
  17. Stakeholders: Who Defines the Problem?

    • Managers may define the problem in terms of cost, targets, risk, productivity, or strategy.
    • Employees may experience the problem as workload, ambiguity, poor tools, duplicated work, or unrealistic expectations.
    • Customers may experience the same process as waiting, errors, inconvenience, or inconsistent service.
    • Suppliers may experience poor coordination, late information, or unpredictable demand.
    • Different stakeholders can describe the same problem differently.
    • Action research benefits from participation because those affected by the process can reveal practical conditions that performance data alone may not show.
    • Students should document whose perspective shaped the diagnosis and whose perspective may be missing.
    • Teaching question
    • If management says “employees are inefficient,” what questions should the researcher ask before accepting that diagnosis? Consider: process design technology training workload incentives measurement leadership resource constraints
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 17
    17
  18. Context Matters

    • A research problem is situated in a real organisational environment.
    • Internal context
    • Operational context
    • External context
    • Research context
    • Structure Leadership Culture Technology Resources Skills Policies Workflow
    • Volume Demand variability Capacity Suppliers Customers Seasonality Process interdependence
    • Regulation Market conditions Economic pressures Technology changes Industry expectations
    • Participants Access Ethics Data availability Time Researcher role Study boundaries
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 18
    18
  19. Scoping the Problem

    • A DBA problem must be meaningful but also manageable.
    • Scope by PROCESS: Which part of the workflow?
    • Scope by LOCATION: Which facility, branch, unit, or operational setting?
    • Scope by POPULATION: Which employees, customers, managers, suppliers, or cases?
    • Scope by TIME: What period demonstrates the problem?
    • Scope by OUTCOME: Which specific performance condition?
    • Scope by INTERVENTION: What part of the process could realistically be changed?
    • Scope by EVIDENCE: What data can the researcher realistically access?
    • Scope by RESEARCH RESOURCES: What can be completed within the DBA timeframe?
    • Scope test
    • Too broad: “Improve organisational performance.” Potentially workable: “Investigate persistent inventory discrepancies in the receiving and put-away process at one warehouse and collaboratively test revised recording practices.”
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 19
    19
  20. Feasibility Test

    • A good problem is not only important—it must be researchable.
    • Can you reach the process, participants, records, or operational data needed?
    • Can diagnosis, intervention, observation, reflection, and revision occur within the available period?
    • Can the problem be measured or documented with credible evidence?
    • Can the research be conducted ethically, with appropriate permissions and without unacceptable participant or organisational risk?
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 20
    20
  21. From Problem to Action Research Question

    • Problem: persistent inventory discrepancies.
    • Diagnostic question: Where and under what conditions do discrepancies enter the process?
    • Explanatory question: How do current recording practices and workflow conditions contribute to discrepancies?
    • Action question: What changes to the recording process could improve inventory accuracy?
    • Evaluation question: What evidence indicates whether the revised process improves accuracy and remains workable for participants?
    • Learning question: What does the intervention reveal about the relationship between process design, recording behaviour, and inventory accuracy in this context?
    • The question evolves as the researcher learns. The cycle is iterative.
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 21
    21
  22. Common Problem-Identification Mistakes

    • Starting with a favourite solution instead of diagnosing the problem.
    • Using a vague statement such as “poor performance,” “inefficiency,” or “lack of effectiveness.”
    • Confusing a symptom with a cause.
    • Assuming management’s explanation is automatically correct.
    • Defining a problem without baseline evidence.
    • Choosing a problem because data are convenient rather than because the problem matters.
    • Making the scope so broad that meaningful action is impossible.
    • Making the scope so narrow that the study has little practical or scholarly value.
    • Claiming causality before investigation.
    • Failing to consider context, stakeholders, ethics, and researcher influence.
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 22
    22
  23. Mini Case — Procurement Bottleneck

    • Initial complaint
    • Diagnosis evidence
    • Focused problem
    • Next stage
    • “Procurement is too slow.” Ask: Slow compared with what? Which purchases? Which stage? Who experiences the delay?
    • Purchase-request records show long approval times for routine purchases. Interviews indicate repeated approval routing and unclear spending authority.
    • “Routine procurement requests experience persistent approval delays associated with duplicated approval routing and unclear spending authority.”
    • Plan an intervention: • clarify thresholds • redesign routing • pilot revised workflow • collect evidence
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 23
    23
  24. Class Activity 1 — Problem-Finding Workshop

    • Students work with one operational problem from their own DBA context.
    • Step 1: Write the problem exactly as stakeholders currently describe it.
    • Step 2: Identify the process in which the problem occurs.
    • Step 3: Write the current performance condition and desired condition.
    • Step 4: Identify at least two baseline evidence sources.
    • Step 5: Identify three possible contributing conditions.
    • Step 6: Identify affected stakeholders.
    • Step 7: Narrow the scope by process, setting, population, and outcome.
    • Step 8: Rewrite the problem as a researchable problem statement.
    • Student deliverable
    • One paragraph containing: Context + process + undesirable condition + evidence + scope + possible contributing condition + why the problem matters. Then prepare to defend each phrase.
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 24
    24
  25. Class Activity 2 — Problem Statement Clinic

    • Give students a vague statement:
    • Possible stronger version
    • “Our customer service department is inefficient.”
    • “The customer service department is experiencing persistent delays in resolving standard customer requests, with average resolution time exceeding the internal service target, particularly during high-volume periods.” Then ask: What evidence would we need before accepting this statement?
    • Ask the class to challenge it:
    • What does “inefficient” mean?
    • Which service process?
    • Which customers?
    • What evidence?
    • What target?
    • Where does the problem occur?
    • What is the time period?
    • What possible contributors?
    • What can actually be changed?
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 25
    25
  26. Student Self-Assessment Checklist

    • ☐ I can state the operational problem in one sentence.
    • ☐ I can identify the specific process affected.
    • ☐ I can describe the performance gap.
    • ☐ I have evidence that the problem exists.
    • ☐ I have identified relevant stakeholders.
    • ☐ I have separated symptoms from suspected causes.
    • ☐ I have defined a realistic scope.
    • ☐ I can explain why the problem matters.
    • ☐ I can formulate a researchable problem rather than a general complaint.
    • ☐ I can explain what remains unknown and therefore requires investigation.
    • ☐ The problem can lead logically into the next stage: planning an intervention.
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 26
    26
  27. Linking Week 6 to the DBA Dissertation

    • Chapter 1
    • Chapter 2
    • Chapter 3
    • Establish the practical problem, context, significance, gap, purpose, and research questions. The problem statement should be precise enough to support the study's direction.
    • Show what literature and theory already say about the problem. Do not use the literature to manufacture a problem that does not exist in practice.
    • Explain how the problem will be investigated through the action-research approach, including participants, data, ethics, procedures, and cycles.
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 27
    27
  28. Week 6 — Key Takeaways

    • Students should remember these principles.
    • An operational problem is not automatically a research problem.
    • Start with diagnosis—not your preferred solution.
    • Define the performance gap using evidence where possible.
    • Distinguish symptom, problem, cause, and research problem.
    • Scope the problem by process, context, population, outcome, and time.
    • Consider multiple stakeholder perspectives.
    • A good problem is important, researchable, ethical, and feasible.
    • A precise problem statement creates the foundation for the next action-research stage.
    • NEXT: From identifying and diagnosing the problem → PLANNING the action/intervention.
    • DBA 704 • Week 6 • Stage 1 — Identifying the Problem • 28
    28
01 / 28

Slides in this deck

  1. DBA 704 — Week 6: Identifying the Problem
  2. Week 6 Learning Outcomes
  3. Where Stage 1 Fits in the Action Research Cycle
  4. What Is an Operational Problem?
  5. The Central Distinction
  6. Four Concepts Students Must Not Confuse
  7. Problem Identification: The Funnel
  8. Step 1 — Start With the Process
  9. Step 2 — Define the Performance Gap
  10. Baseline Evidence: Do Not Build a Problem From Opinion Alone
  11. Example — Inventory Discrepancies
  12. Problem Statement Formula
  13. Bad → Better → Stronger Problem Statements
  14. Problem vs Research Question vs Purpose
  15. Problem Identification Questions for DBA Researchers
  16. Root Cause Thinking — Use Carefully
  17. Stakeholders: Who Defines the Problem?
  18. Context Matters
  19. Scoping the Problem
  20. Feasibility Test
  21. From Problem to Action Research Question
  22. Common Problem-Identification Mistakes
  23. Mini Case — Procurement Bottleneck
  24. Class Activity 1 — Problem-Finding Workshop
  25. Class Activity 2 — Problem Statement Clinic
  26. Student Self-Assessment Checklist
  27. Linking Week 6 to the DBA Dissertation
  28. Week 6 — Key Takeaways