Problem Solving in Health Services: A Practical Team-Based Method
A step-by-step method for health teams to define problems, investigate causes, choose safer solutions, test change and measure whether care improves.
Editorial context
The uploaded file contains learning objectives but no developed lesson. This article expands those objectives using current systems-based quality-improvement and patient-safety methods.
Key points
- Define the gap with evidence before choosing a solution.
- Study the care process and its conditions instead of assuming one person caused the problem.
- Prioritize causes the team can influence and interventions strong enough to change the system.
- Test changes on a manageable scale and watch for unintended harm.
- A problem is not solved until results are measured and the better process is sustained.
Define the problem precisely
A problem is a measurable gap between the present situation and an agreed standard or desired result. State who is affected, where and when the gap occurs, its size and why it matters. Avoid embedding an untested cause or preferred solution in the problem statement.
For example, “many patients wait too long” is vague. A stronger statement gives the service, time period, observed waiting time, target and affected population.
Map the process and collect evidence
Bring together people who perform, manage and receive the service. Map the real sequence from the user's perspective, including hand-offs, decisions, delays, rework and information flow. Direct observation often reveals a different process from the written procedure.
Use a small, relevant dataset to confirm the pattern. Protect personal information and avoid delaying urgent safety action while waiting for perfect data.
Investigate causes without blame
Ask why the gap occurs across people, tasks, equipment, environment, communication, policy and organizational conditions. A cause-and-effect diagram, process map or repeated “why” questions can structure discussion, but the conclusion must be supported by evidence.
Human error is a starting point, not a root cause. Automatically prescribing retraining or discipline often leaves workload, design and communication failures unchanged.
Select and test a solution
Compare options by likely effect, feasibility, equity, cost, safety and sustainability. Prefer changes that simplify the process, improve information at the point of work, standardize critical steps or create effective checks over reminders alone.
Test the change with a Plan–Do–Study–Act cycle: predict what will happen, try it on a limited scale, compare results with the prediction and adapt before wider use.
Measure, learn and sustain
Track an outcome measure, a process measure and, where useful, a balancing measure that could reveal unintended consequences. Share results with the team and service users in a form they can understand.
If the change works, assign ownership, update procedures, orient affected staff and continue periodic monitoring. If it fails, record what was learned and revisit the problem or causal assumptions rather than concealing the result.
Sources and further reading
Use the linked institutions for current definitions, regulations, programmes and statistics.
- AHRQ TeamSTEPPS
Evidence-based tools for communication, teamwork and safer care.
- AHRQ: Workflow mapping
Practical guidance for mapping and redesigning clinical workflows.
- WHO: Quality health services
Quality-of-care strategy and implementation resources.
Related learning note
Quality & Patient SafetyQuality Assurance in Health Care: Standards, Measurement and ImprovementAn evidence-informed guide to healthcare quality assurance and improvement, including standards, indicators, patient experience, PDSA cycles and Nepal context.Educational notice: This article summarizes historical and public-health material. It does not replace current national protocols, clinical judgement or care from a qualified professional.