Many capstones jump straight from "falls are high" to "we will educate staff", and graders notice the leap.
Education only works when the cause is a knowledge gap. Plenty of clinical problems have other causes: a bed alarm that is hard to reset, a toileting round that slips at shift change, a call light out of reach. A fishbone diagram makes you examine every possible cause first, so the intervention you choose actually fits the problem.
How a Fishbone Diagram Works
A fishbone diagram puts a specific problem at the head and groups possible causes along the bones under four to six categories, such as people, processes, equipment, materials, environment and measurement.
Build it with staff where possible, dig deeper with the 5 Whys, check causes against data, prioritize the ones that matter and that the unit can control, and show how your intervention targets them.
What a Fishbone Diagram Is
The fishbone is also called an Ishikawa diagram, after Kaoru Ishikawa, the Japanese quality expert who popularized it, or a cause-and-effect diagram. It is a standard tool in healthcare quality improvement and appears in toolkits such as those from the Institute for Healthcare Improvement.
- The head is the problem, written as a specific effect, such as "inpatient falls above unit target".
- The spine runs from tail to head.
- The main bones are categories of causes.
- The smaller bones are specific causes within each category, and causes of those causes.
It is a thinking tool rather than a statistical one. It organizes possible causes so a team can discuss them and decide which to test or act on.
Where It Fits in Your Capstone
The fishbone usually sits in the problem analysis or needs assessment section, after you show that a gap exists and before you propose your intervention.
- After a gap analysis shows the size of the problem, the fishbone explains why the gap exists.
- In QI and DNP projects it is often required, alongside process maps or Pareto charts.
- In leadership courses it can be the main tool in a root cause analysis assignment.
Cause Categories for Healthcare
Manufacturing teams use the "6 Ms". Healthcare teams usually rename them to fit clinical work. A practical set looks like this.
| Category | What it covers | Example questions |
|---|---|---|
| People | Staff, patients and families | Knowledge, fatigue, staffing, acuity, health literacy |
| Methods and processes | How work is done | Workflows, handoffs, policies, protocols, timing |
| Equipment and technology | Devices and systems | Alarms, pumps, EHR prompts, availability, maintenance |
| Materials and supplies | Consumables | Non-slip socks, signage, teaching materials, stock levels |
| Environment | Physical setting and culture | Layout, lighting, noise, distance to the bathroom, unit norms |
| Measurement and policy | How performance is tracked and governed | Inconsistent risk tools, data gaps, unclear ownership |
You do not need all six, and you can rename them. Keep to four to six so the figure stays readable.
How to Build One, Step by Step
1. Write a Precise Problem Statement
A vague head produces a vague diagram. "Falls" is too broad; "unassisted falls during toileting on night shift" gives the team something specific to investigate.
2. Gather the Right People
Root cause analysis works best with the people who do the work: staff nurses, nursing assistants, a charge nurse and, where relevant, therapy, pharmacy or a patient representative. In a student project, a short huddle or a few interviews may be all you can arrange. Describe honestly what you did.
3. Brainstorm by Category
For each main bone, ask what in that category could contribute. Capture every idea first and discuss later. Sticky notes on a whiteboard or a shared online template both work.
4. Ask Why to Go Deeper
First answers are often symptoms. Asking "why does that happen?" several times, the 5 Whys technique, takes you to causes you can act on.
5 Whys in practice. Patients get up alone at night. Why? They need the bathroom urgently. Why do they not call? They often wait a long time when they do. Why? Night staffing leaves one assistant for 16 patients. Why is toileting not anticipated? There is no scheduled toileting round on nights.
The last answer is a process cause the unit can change, which makes it a far better target than "patients should call for help".
5. Check Causes Against Evidence
The diagram shows possible causes, not proven ones. Before building an intervention on a cause, look for support in incident report patterns, audit data, staff survey results or the literature.
6. Prioritize
Mark the causes that are both likely to matter and within the unit's control. A simple high, medium or low rating for impact and feasibility works, or a Pareto chart if you have incident data by cause.
Worked Example: Inpatient Falls
Here is a fishbone summary for a fictional 28-bed medical unit with falls above target. In your paper you would include the diagram as a figure and summarize it in a table like this.
| Category | Causes identified |
|---|---|
| People | Many older patients with delirium; night staffing ratios; new graduates unfamiliar with the risk tool |
| Methods and processes | No scheduled toileting rounds on nights; no reassessment after a change in condition; handoff omits fall risk |
| Equipment and technology | Bed alarms switched off and not reset after care; alarm volume too low to hear from the station |
| Materials and supplies | Non-slip socks often out of stock; fall risk signs missing from some doors |
| Environment | Long walk to bathrooms in older rooms; dim night lighting; cluttered rooms |
| Measurement and policy | Post-fall huddles inconsistent, so causes of individual falls go unrecorded |
Incident reports showed most falls happened at night during unassisted toileting. The team therefore prioritized two causes: no scheduled toileting rounds and alarms not reset.
The intervention became purposeful hourly rounding on nights with a toileting prompt, plus an alarm check in the rounding script. Education supported both but was not the whole intervention.
How to Write It Up
- Introduce the tool in one or two sentences and cite a source for it.
- Explain how you built it: who contributed, what data you used and the limitations.
- Include the diagram as a labeled APA figure, readable at page size.
- Summarize the key causes in the text, by category.
- Explain how you prioritized and the evidence behind it.
- Show which causes your intervention targets and why that should close the gap.
Word processors, presentation software and online whiteboards all have free templates. Hand-drawn diagrams are fine in team sessions, but use a clean digital version in the final paper.
How It Works with Other Tools
| Tool | What it adds |
|---|---|
| Gap analysis | Shows that a problem exists and how large it is, before the fishbone explains why |
| Process map | Shows each step of a workflow so you can see where it breaks down |
| Pareto chart | Ranks causes by frequency when you have incident data, helping you prioritize |
| SWOT analysis | Judges whether the setting is ready for the change you choose |
Common Mistakes
- Blaming individuals. "Nurse forgot" is not a root cause. Ask why the system made forgetting likely.
- Stopping at symptoms. Use the 5 Whys to reach causes you can change.
- A vague problem statement. Name the effect, the setting and, where possible, the timing.
- Treating every cause as proven. Support your priorities with data.
- An intervention that ignores the diagram. If the causes are mostly processes and your intervention is only education, graders will see the mismatch.
- An unreadable figure. Group and simplify rather than adding dozens of tiny bones.
How NurseCapstone Helps with Root Cause Analysis
Send your topic, unit details and any incident or audit data you are allowed to share. A writer matched to your level drafts a model problem analysis with a clear fishbone figure, prioritized causes backed by evidence, and an intervention that targets them.
Use it as a reference for your own work. Your writer will not invent unit data. Free revisions within the scope of your original request are included.
Want the Problem Analysis Done Properly?
Send your topic, setting and any unit data. You get a model problem analysis with a readable fishbone figure, prioritized causes and a matched intervention.
Start My Problem AnalysisFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
It identifies and organizes the possible causes of a clinical or operational problem, such as falls or medication errors, so a team can choose interventions that target root causes rather than symptoms.
Common categories are people, methods and processes, equipment and technology, materials and supplies, environment, and measurement or policy. Adapt them to your problem and keep to four to six.
It is one tool within root cause analysis. A full analysis may also use timelines, process maps, the 5 Whys and data review.
Yes, but name it as a limitation. Strengthen it with staff interviews, incident data, observation and literature, and explain how you would confirm the causes with the unit.
Usually in the problem analysis or needs assessment section, after the gap analysis and before the intervention, as a labeled figure.
Enough to cover each category fairly, but not so many that the figure becomes unreadable. Group similar causes together.