Skip to main content

Servant Leadership in High-Reliability Healthcare: How Executives Balance Voice, Standards, and Speed

A bedside nurse leads a hospital team discussion while an executive listens at the same table and takes notes.
Greg Wahlstrom, MBA, HCM
Skip to article

Executive Leadership and Governance

Servant Leadership in High-Reliability HealthcareHow Executives Balance Voice, Standards, and Speed

An evidence-informed operating framework for protecting voice without weakening decision clarity.

Listen at the workDevelop authorityRemove barriers
A bedside nurse leads a hospital team discussion while an executive listens at the same table and takes notes.
Frontline expertise leads. Accountable leadership listens.
Listen with The Healthcare ExecutiveChecking for Michael. Playback never starts automatically.

Abstract

Healthcare leaders often face a false choice: listen broadly or decide quickly, support people or enforce standards, distribute authority or maintain accountability. This narrative evidence review examines a more useful question: how can servant-leadership behaviors strengthen high-reliability work without weakening command clarity? Thirty peer-reviewed sources were selected through an authorized institutional database route, with priority given to healthcare studies, systematic reviews, and recent implementation evidence. The literature suggests that listening, trust, development, psychological safety, and barrier removal can improve the conditions for voice and learning. High-reliability practice adds necessary discipline through risk recognition, standard work, explicit decision rights, deference to relevant expertise, escalation, resilience, and measurement. The evidence is encouraging but heterogeneous and largely observational. It does not show that servant leadership or high-reliability programs guarantee safety. The article introduces VOICE, an evidence-informed operating framework: Verify the operating risk, Open the voice channel, Identify decision rights, Control the response, and Evaluate service and safety together. VOICE is a management synthesis, not a validated instrument or clinical rule.

Keywords: servant leadership; high reliability; healthcare leadership; psychological safety; employee voice; patient safety

The false choice between service and control

Imagine two moments in the same hospital.

In the first, a respiratory therapist notices a recurring equipment problem during routine rounds. No patient is in immediate danger. The therapist has time to describe the pattern, bring in biomedical engineering, and test a durable correction.

In the second, a nurse sees that a medication pump is delivering an unexpected volume. The patient may be at risk now. The right response is not a long listening session or a search for consensus. The nurse needs the authority to stop the process, call for the right expertise, and trigger a defined escalation.

Both moments require voice. Both require leadership. They do not require the same pace, forum, or decision structure.

This distinction matters because servant leadership is often reduced to kindness, accessibility, or consensus. Those qualities can be valuable, but they are not enough for high-risk operations. A leader who listens but does not decide can prolong exposure to harm. A leader who invites concerns but does not assign an owner teaches people that speaking up changes nothing. A leader who removes every source of discomfort may weaken standards that protect patients and staff.

Servant leadership is more useful when it is treated as disciplined stewardship. The leader listens for operational truth, develops other people’s capability, removes barriers to safe work, protects the dignity of staff and patients, and uses authority in service of the mission. High reliability contributes a complementary discipline: remain alert to weak signals, resist oversimplification, understand current operations, prepare to recover, and defer to the person with the most relevant expertise. Recent healthcare literature connects these ideas with psychological safety, voice, engagement, and safety culture, but the evidence remains context-dependent and largely nonexperimental.[1-6]

The executive task is therefore not to choose between service and control. It is to design an operating system in which voice improves control, expertise improves speed, and accountability makes service credible.

An environmental-services professional and a bedside nurse explain a workflow barrier while a hospital executive listens and takes notes.
Servant leadership begins by lowering the cost of telling the truth. Leaders go to the work, listen across roles, and treat weak signals as operating intelligence.

What was reviewed and how the evidence is bounded

This article is an applied narrative evidence review, not a systematic review or meta-analysis. A focused search was completed through the University of Phoenix Library using EBSCOhost Research Databases. Full-text and peer-reviewed filters were applied. Searches combined servant leadership with high reliability, patient safety, safety culture, psychological safety, speaking up, employee voice, leadership, escalation, and decision-making.

Thirty sources were retained. Healthcare-specific research received priority. The final set includes systematic and scoping reviews, qualitative studies, cross-sectional surveys, pre-post quality-improvement evaluations, measurement studies, implementation reports, theory reviews, and executive commentaries. Adjacent nonhealthcare evidence was used only when it clarified a mechanism, such as trust, psychological safety, or knowledge sharing, and its transferability limit was stated.

The evidence must be read cautiously. Reviews of servant leadership in healthcare identify favorable relationships with work climate, engagement, attitudes, behavior, psychological-safety mechanisms, and organizational outcomes.[13,18] Yet much of the underlying literature is cross-sectional, self-reported, geographically concentrated, and inconsistent in how servant leadership is defined and measured. A systematic review focused on nursing included 14 studies and 7,041 participants, but it could not answer its planned question about gender differences because the necessary evidence was absent.[13] A broader healthcare review found 55 relevant studies while also calling for stronger methods and greater attention to underexplored outcomes.[18]

High-reliability evidence has similar limits. A 2026 scoping review screened 3,305 records but found only 11 studies that met its inclusion criteria for implementation and safety outcomes.[4] The included studies reported favorable associations with patient-safety measures, staff perceptions, and psychological safety, but their designs and outcomes varied. Large-scale quality-improvement work in the Veterans Health Administration offers promising evidence across 139 facilities, including changes in selected safety-culture domains and increases in close-call reporting, but the phased pre-post design cannot isolate the program from secular trends or implementation differences.[12]

These limitations do not make the evidence unusable. They define the claims leaders can responsibly make. The literature supports an operating hypothesis worth testing locally. It does not support promises that a leadership label will produce zero harm.

What servant leadership contributes

Listening for operational truth

In a high-risk organization, listening is not ceremonial. It is a method for detecting weak signals before they become visible in lagging outcomes. Frontline clinicians, technicians, schedulers, pharmacists, and support staff often see variation first. They know which workaround has become normal, which alarm is routinely dismissed, and which policy does not match the work.

Servant-leadership behaviors can make that information easier to surface. A 2025 study of employee voice found that servant leadership was positively associated with voice through trust in the leader, although the nonhealthcare sample and nonexperimental design limit transfer.[14] In healthcare, qualitative evidence from three Ethiopian public hospitals connected servant-leader behaviors with learning, empowerment, communication, resource allocation, and policy alignment.[11] A separate healthcare study linked servant leadership, engagement, patient safety culture, and task performance, again through observational evidence rather than a causal trial.[8]

The practical implication is narrow but important: leaders can improve the conditions in which operational knowledge reaches decision-makers. They still need a response system that can distinguish a useful weak signal from noise, assign ownership, and close the loop.

Developing capability instead of dependence

Service-oriented leadership is sometimes mistaken for solving every problem personally. That creates dependence and slows the organization. A stronger approach develops the capability of the person closest to the work.

In complex departments, leadership is already distributed across professions and shifts. A radiology synthesis describes servant and distributive leadership as a way to decentralize problem-solving while maintaining accountability through decision-rights design, meeting architecture, psychological safety, and development pathways.[3] This is not a claim that every decision should be decentralized. It is a claim that expertise should be available where and when the decision is made.

Executives serve the system by clarifying the boundary. They specify which decisions can be made locally, which require consultation, which trigger mandatory escalation, and which remain reserved to a designated accountable leader. Development then becomes operational: people learn not only how to raise a concern, but how to assess risk, use standard work, communicate a recommendation, and act within their authority.

Removing barriers while preserving standards

Barrier removal is one of the clearest ways to translate service into performance. Leaders can resolve missing equipment, conflicting policies, unclear handoffs, poor access to data, or a staffing process that makes safe work unnecessarily difficult.

The caution is that not every barrier should be removed. Independent checks, required documentation, sterile technique, medication safeguards, credentialing controls, and escalation rules may feel inconvenient because they are designed to constrain variation. Servant leadership does not mean making every task easier. It means distinguishing waste from protection and helping people perform necessary controls reliably.

That distinction is central to high-reliability thinking. Theory reviews warn that even well-intended safety practices can create new risks. Redundant checking can diffuse responsibility. Technology can tighten coupling and spread uncommon errors quickly. A reporting program can collect large volumes of data without improving learning.[29,30] The leader’s role is to ask what risk the control manages, whether the control works as designed, what burden it creates, and whether a safer alternative exists.

What high reliability contributes

A disciplined view of risk

A High Reliability Organization (HRO) is not defined by a badge or a destination. High reliability is a way of organizing attention and response in work where the cost of failure is high. Healthcare frameworks consistently emphasize leadership commitment, a functioning safety culture, and effective process improvement.[28] More recent implementation studies add measurement, coaching, local learning, and enterprise support.[10,12,21,23]

The five commonly cited principles are useful when translated into observable behavior:

  1. Preoccupation with failure: Treat near misses, workarounds, repeated defects, and small deviations as information.
  2. Reluctance to simplify: Test more than one explanation and examine system conditions before assigning cause.
  3. Sensitivity to operations: Understand what is happening now, not only what policy or a dashboard says should be happening.
  4. Commitment to resilience: Prepare teams to contain, adapt, recover, and learn when prevention fails.
  5. Deference to expertise: Move technical authority toward the person with the most relevant knowledge for the problem at hand.

These principles can fail when they remain slogans. In one hospital-wide qualitative study, participants could identify preoccupation with failure, reluctance to simplify, and sensitivity to operations more readily than resilience or deference to expertise. Different professional groups understood and enacted the program differently, and an individualized approach hindered collective action.[22] The lesson is direct: a high-reliability vocabulary is not the same as a high-reliability operating system.

First-line managers are especially important translators. Interview evidence from intensive-care units in eight Swedish hospitals shows how they work between formal guidance and operating reality while balancing competing goals in everyday safety work.[27]

Psychological safety with operational boundaries

Psychological safety is the belief that a person can raise a question, concern, mistake, or dissenting view without humiliation or interpersonal punishment. It lowers the social cost of contributing information. It does not lower the clinical standard, remove consequences for reckless conduct, or require a leader to accept every recommendation.

Healthcare evidence consistently links leadership behavior, psychological safety, and voice. A 2025 metasynthesis of 15 qualitative studies found that hierarchy and poor work environments impeded nurses’ speaking up, while professional responsibility and a supportive atmosphere facilitated it.[9] A 2024 systematic review of 45 hospital studies classified determinants at individual, relational, contextual, and organizational levels.[16] Cross-sectional nursing studies found that management support, supervisor support, communication openness, response to error, and inclusive leadership were associated with speaking up, reduced withholding, and error reporting.[24,26]

Operating boundary: Psychological safety protects good-faith voice. It does not suspend clinical standards, delay urgent escalation, or prevent proportionate accountability.

This evidence challenges a common executive shortcut. A communication campaign cannot create voice if staff expect retaliation, indifference, or endless delay. Psychological safety is experienced through repeated transactions: what happens after someone raises a risk, how uncertainty is handled, whether respectful dissent is protected, and whether leaders distinguish human error, at-risk behavior, and reckless behavior.[17,25]

Speed through prepared authority

Under time pressure, broad participation and fast action are not opposites if decision rights are prepared in advance. The organization can listen widely during design, train to defined thresholds, and act quickly when a threshold is crossed.

Deference to expertise does not mean that everyone votes. It means rank does not silence relevant knowledge. In an immediate threat, the person with the best situational expertise may need stop-work authority while an incident leader retains responsibility for coordination and escalation. In a routine improvement, the same issue may move through a scheduled review with broader participation.

An infusion-pump case study shows this distinction in practice. A multisite health system analyzed 112,875 upstream occlusion events among 389,604 infusion starts over six months. The team used the five HRO principles to bring clinical, technical, human-factors, and vendor expertise together. The work led to removal of malfunctioning pumps, a national recall, systemwide training, and mitigation protocols, although the design cannot establish that the framework alone caused the results.[7]

Prepared authority accelerates action because the team does not have to negotiate its governance during the event.

An emerging nurse manager leads a hospital simulation debrief while an executive and senior physician listen from the side.
Servant leaders develop authority at the point of expertise. They prepare people to assess risk, act within clear boundaries, and escalate without waiting for permission.

The VOICE operating framework

VOICE translates the evidence into five management actions. It is an evidence-informed synthesis created for this article. It is not a validated scale, clinical algorithm, or substitute for emergency procedures.

V: Verify the operating risk

Start by classifying the situation, not the person who raised it.

  • A routine improvement has no immediate exposure and can enter a defined review cycle.
  • An emerging risk shows credible potential for harm, recurrence, regulatory failure, or major disruption and needs prompt containment and executive visibility.
  • An immediate threat presents current or imminent danger and activates stop rules, emergency procedures, or incident command.

The classification should be revisable. New information can raise or lower the response level. Reluctance to simplify requires leaders to ask what else could explain the signal. Sensitivity to operations requires them to verify actual conditions with the people doing the work.

This first step protects both voice and speed. Staff do not have to prove a final root cause before raising a concern. Leaders do not have to treat every concern as an emergency.

O: Open the voice channel

Invite the information needed for the decision. Use a channel suited to the risk.

For routine issues, options include leader rounding, a structured improvement board, a staff forum, or an electronic reporting system. For emerging risks, use a rapid huddle with the relevant roles present. For an immediate threat, use a standard callout, stop-work phrase, or escalation channel that is practiced and unmistakable.

Leader rounding can support bidirectional communication when it uses consistent questions, documented ownership, and follow-up.[15] A 12-week safety-huddle intervention in four surgical units found improvement in six of nine measured outcomes and described benefits for learning and speaking up, while also identifying participation challenges.[20] A multifaceted hospital program that combined standards, response guidance, education, and leadership training reported lower perceived barriers to speaking up, more incident reporting, and fewer identified adverse events over time. Because several components changed together and there was no control group, the findings should guide pilots rather than promises.[19]

Opening the channel therefore means more than saying, “My door is open.” It means creating a predictable method, a response time, and a visible path from concern to action or reasoned closure.

I: Identify decision rights

For each class of risk, name five roles:

  1. Who can raise or stop the work?
  2. Who provides the relevant expertise?
  3. Who decides the immediate action?
  4. Who owns execution and communication?
  5. Who reviews the decision and the system afterward?

One person may hold more than one role, but the roles should not be assumed. Ambiguity causes delay, duplicate work, and defensive escalation. It can also create the appearance of participation while the real decision remains hidden.

Decision rights should be explicit enough to support action and flexible enough to defer to expertise. That combination is especially important in tightly coupled clinical work. The accountable executive does not surrender accountability when technical authority moves to a pharmacist, infection-prevention specialist, bedside nurse, engineer, or other expert. The executive creates the conditions for the right expertise to govern the right decision.

C: Control the response

Once the risk and decision rights are clear, apply the controls suited to the situation. These may include standard work, independent verification, equipment quarantine, temporary staffing changes, backup capacity, escalation, incident command, patient disclosure, regulatory notification, or a formal investigation.

Use closed-loop communication:

  • State the concern and risk level.
  • Name the decision and its owner.
  • Confirm the action, deadline, and affected area.
  • Verify that the action occurred.
  • Communicate the outcome to the people who raised or manage the issue.

Control also requires just accountability. Human error calls for consolation and system redesign. At-risk behavior calls for coaching, incentive review, and removal of normalized shortcuts. Reckless behavior or intentional misconduct requires proportionate corrective action. Psychological safety protects good-faith voice. It does not prevent fair accountability.

E: Evaluate service and safety together

Do not evaluate the framework with a single culture score or a raw count of reports. More reporting can mean that safety is getting worse, that trust is getting better, or both. A lower number can indicate improvement, fear, fatigue, or a broken reporting channel.

Use a balanced set of measures:

  • Voice: concerns raised, role and shift distribution, anonymous versus identified reports, and staff perception that concerns are heard.
  • Response: time to acknowledgement, owner assignment, containment, closure, and feedback to the reporter.
  • Reliability: adherence to critical controls, repeated-defect rate, close calls, recovery performance, and variation across sites or units.
  • Speed: decision time by risk class, escalation delays, and time from decision to verified action.
  • Workforce: workload, moral distress, engagement, turnover, and unintended reporting burden.
  • Equity: whether voice, response, and corrective action differ by profession, seniority, shift, location, or demographic group.
  • Safety and quality: relevant harm, process, patient-experience, and regulatory outcomes.

Measurement research suggests that trust in team members and leaders can be associated with local learning and willingness to perform extra-role activities.[23] Enterprise evidence also shows why multiple signals matter: safety-culture domains, close-call reporting, adverse events, and implementation exposure may move differently.[12]

A nurse and biomedical engineer verify an accessible equipment station while a hospital executive records closure.
Service becomes credible when leaders return with ownership, verified action, and closure for the people who raised the concern.

Match the leadership posture to the decision

The following matrix prevents two predictable errors: using consensus during an emergency and using command-and-control for every improvement question.

SituationServant-leader postureVoice windowDecision rightRequired closure
Routine improvement with no immediate exposureListen broadly, develop local capability, remove barriersDefined review cycle, usually five business days or lessProcess owner within approved boundariesDecision, rationale, owner, due date, and feedback
Emerging operational riskConvene a rapid cross-functional huddle; protect dissentUsually within 15 to 30 minutesDesignated operational or clinical leader, informed by relevant expertiseContainment plan, escalation threshold, and next review time
Immediate threat to patient or staffSupport stop-work authority and activate the standard responseSeconds to minutesPerson with defined stop authority, then incident or clinical commandVerified containment, handoff, reporting, and after-action review
Persistent system defect across unitsSponsor system analysis; remove resource and policy barriersInitial containment within 24 hours; full review on a defined scheduleExecutive sponsor with cross-functional governanceSystem action, measurement plan, and communication across sites
Performance or conduct concernListen without prejudging; preserve facts, dignity, and due processPrompt fact-finding appropriate to riskAccountable manager with human-resources, compliance, or legal support as requiredProportionate action and a separate system-learning review

The time ranges are starting points, not universal standards. Each organization should align them with its emergency operations plan, clinical policies, regulatory duties, collective-bargaining obligations, and local risk profile.

A 90-day implementation agenda

VOICE should begin as a bounded operational pilot, not an enterprise slogan.

Days 1 through 30: map risk and authority

Select one service line with executive sponsorship, a stable improvement team, and a real but manageable voice or reliability problem. Map current reporting channels, escalation points, decision delays, and feedback failures. Identify three to five recurring situations and classify them as routine improvement, emerging risk, or immediate threat.

For each situation, document who can stop work, who supplies expertise, who decides, who executes, and who reviews. Compare the map with policy and actual practice. Where they differ, determine whether the problem is policy design, training, access, workload, incentives, or informal hierarchy.

Establish baseline measures for acknowledgement, ownership, containment, closure, feedback, repeated defects, workload, and relevant safety or quality outcomes.

Days 31 through 60: test the operating routines

Train leaders and staff on the three risk classes and the five VOICE actions. Use short scenarios from real operations. Practice a routine concern, an ambiguous emerging risk, and an immediate stop-work event.

Pilot two voice channels, such as daily safety huddles and structured leader rounding. Give each channel a purpose, owner, response standard, and escalation rule. Observe whether seniority still overrides expertise, whether concerns receive owners, and whether staff receive closure.

Review workload weekly. A process that depends on extra unpaid effort or repeated duplicate entry is not reliable.

Days 61 through 90: evaluate and adapt

Compare process measures with baseline, but do not claim causality from a 90-day pilot. Review cases in which VOICE helped, cases in which it delayed action, and cases that never entered the process. Stratify participation and response by role, shift, and location.

Ask five questions:

  1. Did staff raise material information earlier?
  2. Did leaders classify risk consistently?
  3. Were decision rights understood during pressure?
  4. Were actions completed and communicated?
  5. Did the process reduce risk without creating disproportionate burden?

Decide whether to stop, revise, extend, or scale the pilot. Scaling should require evidence that the routines work across more than one leader and one favorable unit.

Failure modes executives should anticipate

Listening without response

Repeated invitations without ownership or feedback create learned silence. Track response reliability, not only the number of listening events.

Consensus as a substitute for accountability

Participation can improve information and commitment. It cannot erase the need for a named decision-maker. Every huddle should end with a decision, an owner, or an explicit statement that more information is required by a defined time.

Kindness used to avoid a difficult standard

Leaders sometimes delay corrective feedback because they want to preserve trust. Ambiguity is not compassionate. Clear expectations, fair process, and timely coaching protect the team and the patient.

Command used when learning is needed

Directive action is appropriate during immediate danger. If it becomes the default for routine improvement, staff may stop contributing local knowledge. The risk class should determine the posture.

Voice measured without equity

A rising total can hide systematic silence among night-shift staff, contractors, environmental services, residents, or other groups with less positional power. Examine who speaks, who receives a response, and who experiences correction.

High reliability treated as branding

Programs can adopt the language of high reliability while leaving decision rights, staffing, incentives, and learning routines unchanged. The 2022 implementation study found uneven understanding across professional groups and limited evidence of resilience and deference to expertise.[22] Observable practice should precede the label.

A framework treated as a clinical rule

VOICE organizes management decisions. It does not replace clinical judgment, emergency procedures, legal duties, or professional standards. Local validation should focus on feasibility, reliability, burden, and unintended effects.

Implications for executives and boards

Executives should ask whether the organization has made good-faith voice operational. Can staff identify the correct channel under pressure? Are stop rules real? Does expertise outrank status when the risk demands it? Is there a named decision-maker? Does the reporter receive closure? Do leaders study the burden created by safety controls as well as the risk those controls manage?

Boards should resist easy assurances. A high culture score, a declining event count, or completion of leadership training does not independently establish reliability. Governance should examine a balanced set of leading and lagging signals, variation across units, repeated defects, response times, workforce burden, and examples of how leaders acted when expertise challenged hierarchy.

The most credible evidence of servant leadership is not a self-description. It is an operating pattern: leaders make it safer to tell the truth, easier to do the right work, clearer who decides, faster to contain risk, and more likely that the organization learns.

Conclusion

Servant leadership and high reliability solve different parts of the same executive problem. Servant leadership focuses attention on people, stewardship, trust, capability, and barriers to performance. High reliability focuses attention on weak signals, complexity, operations, resilience, expertise, and disciplined control.

Neither is sufficient as a label. Listening without decision creates delay. Standards without voice conceal risk. Distributed expertise without accountability creates ambiguity. Accountability without psychological safety creates silence.

VOICE offers a practical synthesis: Verify the operating risk, Open the voice channel, Identify decision rights, Control the response, and Evaluate service and safety together. Its value should be judged through local testing, balanced measures, and transparent limitations. The goal is not softer leadership or tighter control. The goal is a system in which service makes control more intelligent and control makes service dependable.

References

  1. Olszyk MD. Servant leadership and the chief medical officer: ethos made operational. Physician Leadership Journal. 2026;13(3):21-23. doi:10.55834/plj.4112495816.
  2. Roy I, Islam R. Entrepreneurial and servant leadership in knowledge sharing: unveiling the roles of psychological safety and workplace bullying. The Learning Organization. 2026;33(4):657-680. doi:10.1108/TLO-03-2025-0078.
  3. Kamran R, Patlas MN, Cecere M, Doria AS. Building purpose-driven radiology departments: distributive and servant leadership in action. Canadian Association of Radiologists Journal. Published online April 6, 2026. doi:10.1177/08465371261437071.
  4. Morales MJG, Hilton P, Hong O, et al. High reliability organizations and healthcare safety outcomes on patients and staff: scoping review. PLOS Global Public Health. 2026;6(4):e0006181. doi:10.1371/journal.pgph.0006181.
  5. Ippolito PJ, Kay JS, Hurt KJ. The effect of servant leadership and psychological safety on employee commitment and workplace engagement. Journal of Values-Based Leadership. 2026;19(1):Article 11. doi:10.22543/1948-0733.1609.
  6. Campbell Y. The ethical responsibility of psychological safety: leadership at the intersection of safety culture. Healthcare Management Forum. 2026;39(1):66-69. doi:10.1177/08404704251348817.
  7. West AM, Schueler NL, Moody RA, et al. Applying high-reliability principles to infusion pump safety: a case study at a multisite health system. Journal of Patient Safety. 2025;21(8):e185-e189. doi:10.1097/PTS.0000000000001395.
  8. Demeke GW, van Engen ML, Markos S. Linking servant leadership to task performance through work engagement and patient safety culture. Discover Health Systems. 2025;4(1):1-18. doi:10.1007/s44250-025-00325-4.
  9. Lee E, De Gagne JC, Randall PS, Tuttle B, Kwon H. Experiences of nurses speaking up in healthcare settings: a qualitative metasynthesis. Journal of Advanced Nursing. 2025;81(11):7464-7479. doi:10.1111/jan.16592.
  10. Lin K, Karim S, Porsa E, Brass SD. The transformative journey to becoming a high-reliability organization. Physician Leadership Journal. 2025;12(5):35-42. doi:10.55834/plj.5702386779.
  11. Demeke GW, van Engen ML, Markos S. Servant leadership and patient safety culture in Ethiopian public hospitals: a qualitative study. BMC Health Services Research. 2025;25(1):1-14. doi:10.1186/s12913-025-13118-5.
  12. Sawyer AM, Thiyarajan S, Essen K, et al. Implementation of a high-reliability organization framework in a large integrated health care system: a pre-post quasi-experimental quality improvement project. Military Medicine. 2025;190, issues 5 and 6:e1190-e1197. doi:10.1093/milmed/usae511.
  13. Saavedra S, Ruiz-Palomino P, Pérez-Contreras R, Gonzalez-Sanz JD, Leal Costa C. Impact of servant leadership on the work environment and the attitudes and behavior of nursing professionals as a function of gender: a systematic review. Journal of Nursing Management. 2025:1-15. doi:10.1155/jonm/8825138.
  14. Hassan N, Yoon J, Dedahanov AT. Servant leadership style and employee voice: mediation via trust in leaders. Administrative Sciences. 2025;15(3):99. doi:10.3390/admsci15030099.
  15. Murray JS, Clifford J. Assessing the effectiveness of leader rounding for high reliability: a quality improvement initiative. BMJ Open Quality. 2025;14(1). doi:10.1136/bmjoq-2024-003101.
  16. van Dongen D, Guldenmund F, Grossmann I, Groeneweg J. Classification of influencing factors of speaking-up behaviour in hospitals: a systematic review. BMC Health Services Research. 2024;24(1):1657. doi:10.1186/s12913-024-12138-x.
  17. Maddineshat M, Safi-Keykaleh M, Ghaleiha A, Sadeghian E. Speaking up: exploring mental health care workers’ patient safety concerns. Journal of Psychosocial Nursing & Mental Health Services. 2024;62(10):41-49. doi:10.3928/02793695-20240424-02.
  18. Demeke GW, van Engen ML, Markos S. Servant leadership in the healthcare literature: a systematic review. Journal of Healthcare Leadership. 2024;16:1-14. doi:10.2147/JHL.S440160.
  19. Nakatani K, Nakagami-Yamaguchi E, Hagawa N, et al. Evaluation of a new patient safety educational programme to reduce adverse events by encouraging staff to speak up: application of the trigger tool methodology. BMJ Open Quality. 2024;13(1). doi:10.1136/bmjoq-2022-002162.
  20. Lee SE, Dahinten VS, Kim E, et al. A safety huddle intervention in in-patient surgical units: a mixed-methods study. Journal of Nursing Management. 2023:1-8. doi:10.1155/2023/8929993.
  21. Cox GR, Starr LM. VHA’s movement for change: implementing high-reliability principles and practices. Journal of Healthcare Management. 2023;68(3):151-157. doi:10.1097/JHM-D-23-00056.
  22. Rotteau L, Goldman J, Shojania KG, et al. Striving for high reliability in healthcare: a qualitative study of the implementation of a hospital safety programme. BMJ Quality & Safety. 2022;31(12):867-877. doi:10.1136/bmjqs-2021-013938.
  23. Cartland J, Green M, Kamm D, et al. Measuring psychological safety and local learning to enable high reliability organisational change. BMJ Open Quality. 2022;11(4). doi:10.1136/bmjoq-2021-001757.
  24. Seo JK, Lee SE. Hospital management, supervisor support and nurse speaking-up behaviours: the mediating role of safety culture perception. Journal of Nursing Management. 2022;30(7):3160-3167. doi:10.1111/jonm.13737.
  25. Murray JS, Kelly S, Hanover C. Promoting psychological safety in healthcare organizations. Military Medicine. 2022;187, issues 7 and 8:808-810. doi:10.1093/milmed/usac041.
  26. Lee SE, Dahinten VS. Psychological safety as a mediator of the relationship between inclusive leadership and nurse voice behaviors and error reporting. Journal of Nursing Scholarship. 2021;53(6):737-745. doi:10.1111/jnu.12689.
  27. Hedsköld M, Sachs MA, Rosander T, von Knorring M, Pukk Härenstam K. Acting between guidelines and reality: an interview study exploring the strategies of first-line managers in patient safety work. BMC Health Services Research. 2021;21:48. doi:10.1186/s12913-020-06042-3.
  28. Chassin MR, Loeb JM. High-reliability health care: getting there from here. Milbank Quarterly. 2013;91(3):459-490. doi:10.1111/1468-0009.12023.
  29. Tamuz M, Harrison MI. Improving patient safety in hospitals: contributions of high-reliability theory and normal accident theory. Health Services Research. 2006;41, issue 4, part 2:1654-1676. doi:10.1111/j.1475-6773.2006.00570.x.
  30. Ruchlin HS, Dubbs NL, Callahan MA. The role of leadership in instilling a culture of safety: lessons from the literature. Journal of Healthcare Management. 2004;49(1):47-58. doi:10.1097/00115514-200401000-00009.

Declarations

Funding: No external funding was received for this article. Conflicts of interest: The author declares no conflict of interest. Data availability: No new dataset was created. The evidence record consists of published scholarly sources. Framework status: VOICE is an evidence-informed management synthesis. It has not been validated as a scale, clinical decision rule, or causal intervention.

Management Atlas disclaimer

This article is for educational and management-development purposes. It does not provide medical, legal, regulatory, employment, or patient-specific advice. Healthcare organizations should apply qualified clinical, legal, human-resources, compliance, and safety expertise to local decisions and requirements.

Blog Attachment