UPI Study › Courses › Healthcare Organization and Management › Free lessons › Lesson 9.3 Free with a free account
PESTLE Analysis and Root Cause Analysis
Healthcare Organization and Management · Chapter 9: Goal Setting, Analysis Tools, and Strategic Alignment in HealthcareSection 9.3 · lesson 56 of 10512 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Healthcare Organization and Management.
Lesson complete
Earn the 3 college credits for Healthcare Organization and Management
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Goal Setting, Evaluation, and Performance Monitoring →← SWOT and Force Field AnalysisNext lesson: Goal Setting, Evaluation, and Performance Monitoring →
In this lesson
Scanning the outside environment and finding system causes of failures.
- Apply PESTLE by judging each factor's materiality, direction, and timing
- Set up environmental scanning with named owners, sources, and intervals
- Distinguish proximate causes, contributing factors, and root causes
- Rank corrective actions using the action hierarchy
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (1,541 words). Read along, or search it.
Opening Case
A Late Antibiotic Dose Under Review
A report reaches Farah Siddiqui, Larkfield's director of quality and patient safety. On 4 North, a patient's scheduled antibiotic dose was given four hours late. The patient recovered without harm. The unit's own review is already attached. It says a float nurse didn't follow the pathway, and it recommends retraining and a reminder email. It's tidy, and it's fast. Farah's question is whether it found the cause, or only the person closest to the event.
Two Tools
Looking Outward and Looking Backward
Root cause analysis is one of two tools in this lesson. It looks backward at a failure. The other, PESTLE, looks outward at the environment the organization doesn't control. Both are done routinely, and both produce almost nothing when they're done as a template. Start outward, with Tom Brennan's team running Larkfield's annual scan.
PESTLE Categories
Six Categories of Outside Factors
Colleen Lawson, the marketing director, explains the method. PESTLE grew from scanning categories Francis Aguilar proposed in 1967. It forces attention onto factors outside the usual field of view, in six categories. Political: the direction of government policy, public program funding, and what regulators are prioritizing. Economic: local jobs and incomes, cost inflation in pay and supplies, and payers' finances. Social: the population's age, deprivation, language, and rising expectations of access. Technological: new ways of delivering care and remote monitoring, plus the staff and capital each one needs. Legal: statute, regulation, employment law, and liability. Environmental: climate effects on demand, fragile supply chains, emissions rules, and how resilient the buildings are.
Assessing Factors
Materiality, Direction, and Timing
But a PESTLE that lists six categories of factors hasn't done anything yet. Three judgments turn it into analysis. Materiality: how much would this factor change what Larkfield must do? Most listed factors are real and immaterial, and separating the two is the point. Direction: does it push demand, cost, or constraint up or down, and is that good or bad for us? A factor whose direction no one can state hasn't been thought about. Timing: when does it start to bind? Eight years out, it's a watching item. Next quarter, it's a planning input. The output is a short list, with direction and timing attached, and it feeds straight into a SWOT's opportunities and threats. Too often the two never meet.
Environmental Scanning
Named Watchers, Sources, and Intervals
And an annual workshop describes an environment that moves continuously. Environmental scanning is the standing arrangement for watching it between planning rounds. It needs three things a workshop doesn't supply. A named person for each material factor, because a factor watched by everyone is watched by nobody. A named source for each: the payer's policy notices, published workforce data, the regulator's program. And an interval matched to how fast that factor moves, not to the meeting calendar. Most of what a plan assumes about the outside world is a PESTLE factor. Scanning is what makes someone notice when an assumption fails.
Quick Check
Planning Input or Watching Item
Quick check. Here are three items from Larkfield's scan. Which one is a planning input for this year, rather than a watching item? Pause, and decide. The payer's notice. It's material, its direction is clear, and it binds in four months. That makes it a planning input now. The drone forecast is tempting, because it sounds big. But it's ten years out, so it's watched, not planned for. And the apps have no stated direction yet.
Root Cause Analysis
System Conditions, Not the Closest Person
Now backward. Root cause analysis is a structured method for finding why a failure happened. It aims at the system conditions that allowed it, not at the individual closest to it. That purpose is often abandoned. An analysis hunting for who was responsible gets a different answer from one asking what allowed it. People won't tell a blame hunt what really happened. For a sentinel event, one causing death, permanent harm, or severe temporary harm, the Joint Commission requires this kind of comprehensive analysis and an action plan. A 2015 framework from the National Patient Safety Foundation, called RCA squared, root cause analysis and action, stressed that the actions matter as much as the analysis.
RCA Steps
Building the Timeline First
Farah starts on 4 North with Ellen Murphy, the charge nurse. Step one: describe what happened, factually, agreed by everyone before any explanation. Step two: the timeline, which does the most work. The order went in at 7:10 PM. The pharmacy's once-a-day cabinet restock had run at six. The dose was due at nine. Nobody had pictured that order. Then step three: contributing factors, across every category, not just the first plausible one. Step four: ask why, again and again. Step five: state the system cause as a condition, never as a person.
Five Whys
One Chain of Questions
The five whys technique, from Toyota's production system, asks why until it reaches a system-level answer. Victor Huang, the pharmacy manager, starts: why was the dose late? It wasn't in the cabinet. Why not? The order came after the restock. Why? Restock times follow pharmacy staffing, not when doses fall due. It's cheap, and good for simple problems. Its weakness is structural: it follows one causal chain. Real failures in hospitals almost never have one chain, so it misses the other factors that also had to be present. And each why picks one of several answers, so two competent people can reach different endpoints. Use it for a first hypothesis, never as the only method for a serious failure.
Fishbone Diagram
Six Branches of Contributing Causes
A cause and effect diagram, often credited to Kaoru Ishikawa and called a fishbone, fixes that by forcing several branches. The effect sits at the head. Causes hang along the bones. Hospitals usually use six branches. People: a float nurse unfamiliar with the cabinet. Process: one restock a day. Information: the pharmacy and unit systems don't share a dose-due status. Equipment: no spare stock on the unit. Environment: the order landed during shift change. Policy: overnight, a second pharmacist signature was required, with one pharmacist on duty. The branches are prompts, not a taxonomy. A diagram with one branch filled and five empty isn't finished. It's the first hunch, drawn more elaborately.
Cause Levels
Proximate, Contributing, and Root Causes
Three terms get used loosely. The proximate cause is the event just before the failure: the dose wasn't in the cabinet at nine. It's what gets reported, because someone saw it. A contributing factor made the failure more likely, without being enough alone: one daily restock, systems that don't share a status, shift change, the overnight signature rule. The root cause is the condition letting those factors persist. Here, no one owns the handoff of first doses between pharmacy and the units. Each factor was visible to someone, for years. The test: fix the proximate cause, and the failure returns next week by another route. Fix a contributing factor, and it gets rarer. Fix the root cause, and the class of failure changes.
Action Hierarchy
Weaker, Intermediate, and Stronger Actions
Then the actions. RCA squared uses an action hierarchy from the Veterans Affairs National Center for Patient Safety, ranked by how much each relies on people behaving differently under pressure. Weaker actions are reminders, warnings, new policies, and training. They fade within weeks. Intermediate actions are checklists, standard processes, and a named contact. They help, but can be dropped in a bad week. Stronger actions change the system: a forcing function that makes the failure hard, or a structural change, like an accountable owner with real authority. The unit's draft, retraining and an email, sits at the bottom. Reviews drift there because weak actions are fast, cheap, and within the authority of whoever did the analysis.
Matching Levels
Escalating Organizational Causes
A ward manager can send an email and book training. She can't change an information system or create an owner for a cross-department handoff. So a unit-level review produces unit-level actions. Three corrections. Match the level of the analysis to the level of the cause, so an organizational cause gets escalated, not settled locally. Require at least one intermediate or stronger action for any serious failure, which forces that escalation. And review months later with one question: has the class of failure changed? A repeat by a different route means the analysis stopped too early.
Quick Check
Blocking an IV Pump Overdose
Quick check. A different review finds that a nurse programmed an IV pump to ten times the intended dose. The error was caught in time. Which corrective action is strongest? Pause, and decide. Setting the pumps to block doses over safe limits. That's a forcing function: the error becomes hard to make, whoever is tired or interrupted. The double-check is tempting, because two people feel safer than one. But it still depends on attention under pressure, and retraining depends on it even more.
Case Resolved
Joint Ownership of First Doses
Back to Farah. She sends the review back with the level corrected, not the conclusion. The cause is organizational, so a group with pharmacy, informatics, and authority over the signature rule takes it. Their actions climb the hierarchy. The systems now flag any due dose that isn't stocked on the unit. And Victor and Ellen jointly own first-dose timing. Farah sets the review question now, for six months out. Not whether the actions were completed, but whether late first doses, by any route, have stopped.
Key Takeaways
Scan Outward, Analyze Backward
To recap. PESTLE scans six categories of outside factors. Judge each factor's materiality, direction, and timing, and feed the short list into a SWOT. For a serious failure, use a fishbone, not five whys alone. Proximate causes get reported. Contributing factors make failure likely. Root causes let them persist. And choose stronger actions, then check whether the class of failure changed.
About Healthcare Organization and Management at UPI Study
Healthcare Organization and Management (Health 302) is a self-paced online course of 105 video lessons in 18 chapters, from health systems and the law to ethics, leadership, teams, strategy, informatics, finance, quality, human resources, marketing and evidence-based practice. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Health courses Every course with PRO →
Why take it here
Why students take Healthcare Organization and Management with UPI Study
Where the credit goes
Universities that work with NCCRS
Healthcare Organization and Management carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About PESTLE Analysis and Root Cause Analysis
What does PESTLE stand for in healthcare strategic planning?
What is the difference between a root cause and a proximate cause?
What are the limits of the five whys technique?
What is the action hierarchy in root cause analysis?
About the Healthcare Organization and Management course
How many college credits is Healthcare Organization and Management?
How much does Healthcare Organization and Management cost and what is included?
Which universities accept UPI Study credits?
How long does Healthcare Organization and Management take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Healthcare Organization and Management.
105 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →