YOU DON’T GET TO IGNORE THE WARNING. & THEN BLAME THE ALARM.

I keep running into a problem when I try to write about a professional experience that still makes me angry: the more neatly I summarize it, the less accurately I describe it.

A disagreement about leadership styles. A difficult relationship with a boss. A stressful job that eventually came to an end. Those descriptions are tidy enough to make everyone comfortable. They also leave out the part that matters.

I repeatedly raised concerns about staff training, staffing, client appropriateness, and whether the operational resources matched the care we were agreeing to provide. In some situations, I recommended against admitting or continuing to serve clients whose needs I believed exceeded the program’s available support. Those recommendations were overruled.

Later, I intervened in an active suicide attempt and helped save a woman’s life. I was fired afterward. I had already intended to leave because of ethical concerns, but planning to leave and being fired are different events. The account of my departure presented to others blurred a distinction that was very real to me.

The sequence alone does not establish why I was fired or what caused the emergency. It does explain why a generic story about workplace frustration feels inadequate. I was raising questions about the organization’s capacity to care for people, working within decisions I could not fully control, and eventually responding when someone’s life was at risk.

My anger has a person attached to it. There is something satisfying about giving frustration a name and a place to land. But I do not want the safety questions to disappear into a familiar story about a former employee and a former boss.

What I want to understand is what happened to the information I brought forward. Who examined it? What decisions followed? And why can it become easier to discuss the person raising a concern than the conditions that made them raise it?

What happens after someone speaks up

We talk a lot about encouraging employees to speak up. We train people to communicate clearly, escalate concerns, and advocate for safety. All of that matters. But it leaves a rather large question sitting on the other side of the conversation: what is leadership prepared to do once somebody actually speaks?

A 2014 review by Ayako Okuyama and colleagues examined 26 studies of speaking up among hospital professionals. It identified both fear of personal consequences and doubt that speaking up would accomplish anything as barriers. Someone might stay quiet because they expect conflict or retaliation. They might also stay quiet because previous experience suggests their concern will change nothing. [1]

That second possibility stays with me. There is a particular frustration in doing what an organization says it wants—identifying a problem, explaining the risk, proposing a response—and then discovering that the process seems to end at your willingness to say it out loud.

In my experience, finding the courage to raise concerns was not the whole challenge. I had already raised them. The difficult part was deciding what to do when the conditions remained unresolved and the final decisions belonged to someone else.

A 2024 systematic review by Dimmy van Dongen and colleagues, covering 45 articles, placed speaking-up influences across individual, relational, contextual, and organizational levels. Leaders’ responses and perceived inaction appeared alongside employees’ confidence and communication skills. That broader picture matters: improving how people communicate cannot, by itself, resolve how an organization receives and acts on their information. [2]

I did not expect every recommendation to be accepted. I expected the concern to be examined. If I had misunderstood the client’s needs, I wanted that explained. If support existed that I did not know about, I wanted to understand how it would work. If my proposed solution was impractical, I wanted us to work toward an alternative.

Those are ordinary parts of making a responsible decision. They also give disagreement somewhere to go. Without them, an employee can be asked to collaborate while having no clear route from the concern they identified to a decision they can understand.

At some point, asking the person to be more constructive becomes a peculiar response when they have already described the problem and suggested a way forward. What additional construction are we looking for? A PowerPoint? A better font?

The question still needs an answer. Repetition can become irritating, but irritation does not tell us whether the issue has been resolved. Sometimes a concern keeps returning because the conditions keep returning with it.

Survival does not settle the preparation question

That distinction becomes especially important after an emergency. In the immediate moment, the priority is the person who needs help. When someone survives, that outcome matters enormously. Having been involved in that response, I do not take it lightly.

But relief cannot answer every question about what happened before the crisis. A successful intervention does not tell us whether a placement was appropriate, whether staffing matched the needs involved, or whether the team had the preparation it should have had. Those questions deserve attention even when the outcome is the one we hoped for.

Research on outcome bias helps explain why this distinction can be difficult. In a preregistered 2023 experiment with 692 participants, Aiyer and colleagues found that people evaluated the same underlying medical decision more favorably when it produced a successful outcome. These were hypothetical scenarios, but they demonstrate how knowing the result can influence our judgment of a decision’s quality. [3]

For me, that research raises a useful question: are we examining whether a decision was sound when it was made, or letting the eventual outcome do the judging? A good outcome can follow a decision that deserved more scrutiny. A terrible outcome can occur despite reasonable preparation. Either way, we need to examine what was known, what support was available, and why the decision was made.

James Reason’s work gives that examination a wider frame. In his 2000 BMJ paper, he described how organizational decisions can create latent conditions—weaknesses such as understaffing, time pressure, or inadequate equipment—that exist before an incident. His systems approach asks what made an error possible and what defenses were available, rather than stopping at the actions of the person closest to it. [4]

That is why I want the timeline of a review to begin before the emergency. What did the client need? What could the program actually provide? What concerns were raised about that fit, and who decided to proceed? If our first question concerns what someone did during the crisis, we may have already skipped decisions that shaped their options.

Preparation belongs in that timeline too. Signing a policy tells us someone signed a policy. It does not tell us what they can recognize, what they can do, or how quickly they can reach qualified help.

A 2011 meta-analysis by William McGaghie and colleagues included 14 studies and 633 medical learners. Simulation with deliberate practice—structured repetition, feedback, and assessment—favored clinical skill acquisition over comparison conditions. The evidence primarily concerned procedural skills, so it does not establish that any particular training package prepares behavioral health staff for every aspect of an emergency. [5]

The question it prompts is practical: if we expect staff to perform a skill, where do they practice it, who gives them feedback, and how do we know they are ready? A behavioral health program needs answers suited to its own risks, staff roles, and access to clinical support.

That takes time and money. It also takes leaders willing to discover that the current approach is insufficient. You cannot demand crisis-level competence and offer wishful thinking as the training budget. The person approving the resources is part of the preparation story, even if they never enter the room when something goes wrong.

Responsibility needs authority behind it

This is where the experience becomes harder to describe as an ordinary workplace disagreement. I was trying to help an operation function while questioning whether the resources and decisions supporting it were adequate. I could identify a gap. I could recommend a change. I could not approve every expense or reverse every decision.

There is a difference between being responsible for coordinating work and having the authority to change the conditions under which that work happens. When those are treated as the same thing, an organization can expect someone to answer for a problem while leaving the decisions needed to address it elsewhere.

Research on moral distress offers language for part of that tension. Trine-Lise Jansen and colleagues interviewed 16 acute psychiatric nurses who described conflicts between their care ideals and what circumstances allowed them to provide. Inadequate resources and concern about vulnerable patients being followed by untrained personnel were among the themes. These interviews illuminate experiences rather than establish how common they are. [6]

A 2024 systematic review by Sara Lamoureux and colleagues brought together 10 studies of moral distress among acute mental health nurses. It reported associations with emotional exhaustion, cynicism, and poorer job satisfaction, alongside themes involving insufficient resources and care conflicts. None of the included studies tested an intervention specifically targeting moral distress in that setting. [7]

My role was operations leadership, so I am not treating research about nurses as a direct study of my own job. What I recognize is the conflict: caring about what people need while feeling constrained by decisions that make meeting those needs harder.

It is possible to understand a budget and still question what it can support. It is possible to care about keeping a program open and still believe that accepting a particular client exceeds its capacity. Financial realities deserve honest discussion precisely because they affect what care can be delivered.

If a program cannot provide the support a client needs, someone has to face the implications. Can that support be added? Is a different placement needed? What happens while the decision is being made? These are consequential questions. The answer cannot simply depend on staff becoming more resourceful with whatever they happen to have.

That is a more accurate description of my anger than saying I wanted my ideas adopted. I was concerned about what the decisions asked staff to manage, what they meant for clients, and what continuing to work under them required me to accept. Encouraging me to feel differently would not have changed those conditions.

A person to blame does not complete the review

The same need to examine the surrounding decisions applies to concerns about client relationships. In another situation, I raised a concern about an older client being sexually involved with a younger client. I was told one client was the problem, and I did not see meaningful action to address the situation itself.

An age difference alone does not establish coercion or misconduct. Taking a concern seriously means making room to establish the facts, including facts that might change the initial impression. I wanted to understand what was happening and whether a response was needed.

In a treatment environment, that means asking about relevant boundaries, vulnerability, possible pressure, and the expectations communicated to the people involved. It also means examining the program’s response. What information was gathered? What responsibilities did staff have? Were any protections needed, and who would decide?

Clients can be accountable for their conduct. A program can be accountable for how it assesses and responds to that conduct. Naming one person as the problem does not answer the second set of questions.

What unsettled me was how quickly an explanation about someone’s behavior could appear to close a concern about the situation around them. Once blame has a destination, the conversation can feel finished. But the work of understanding what happened may barely have begun.

That connects this concern to the others I raised. Whether the subject was training, admission decisions, or client boundaries, I wanted a fair examination that led to a clear response. I kept coming back to the same question: what had actually been assessed, and what would happen next?

What a meaningful response would have looked like

I think about that question now because it gives me a more useful standard for leadership than whether a difficult conversation felt pleasant. A meaningful response should leave people with a clearer understanding of the concern and a clearer account of the decision.

In a study of 23 neonatal intensive care units, Ingrid Nembhard and Amy Edmondson examined leaders who invited and appreciated contributions. That inclusiveness was associated with psychological safety—the belief that taking interpersonal risks, such as asking difficult questions, is safe within a team—and helped counter the inhibiting effects of professional status differences. Psychological safety was also associated with engagement in improvement work, although the observational study cannot establish causation. [8]

That matters because an invitation to speak is most useful when information from someone with less authority can influence a decision. A leader may ultimately disagree. But there should be a visible connection between the concern raised, the assessment made, and the next step.

For a concern about client appropriateness, I would want the relevant clinical assessment connected to the operational reality. What support does this person require, and can the program provide it across the times and circumstances when it will be needed? If the answer depends on adding staff, training, or access to qualified help, those commitments need an owner and a feasible plan.

If leadership decides to proceed despite a recommendation against it, I want to understand the reasoning. That includes what information changed the assessment, what protections are in place, and what would trigger reconsideration. A decision can be confident and still be open to review.

If the answer is that resources cannot be added immediately, then we need to discuss the gap in the meantime. What can staff safely be expected to manage under the current conditions? Who can they contact when those conditions are exceeded? What changes, if anything, about the plan for the client?

And once an action is agreed upon, someone needs to check whether it happened. Was the training completed in a way that established the needed skills? Was support available when staff needed it? Did the revised arrangement address the concern, or do we need to reconsider?

None of that requires leaders to predict every emergency. It requires them to stay involved in the consequences of their decisions. A reassuring sentence is easy to produce. Following through takes more attention and may require changing a choice someone important already made.

I would rather hear a reasoned disagreement than be left wondering whether a concern had been examined. I would rather understand the limits of a plan than be asked to take comfort in another statement about how seriously the organization takes safety. Mission statements have excellent attendance. They are less helpful when you need another trained person on shift.

The warning still deserves an answer

An honest review would include my actions during the emergency. It would also include the concerns raised beforehand, the support available to staff, and the decisions about which clients the program could safely serve. Accountability becomes less convincing when its questions stop before reaching the people who held the final authority.

My firing is part of this experience too. So is the difference between what happened and how my departure was described. I do not want the research to supply a verdict about someone’s motive. I want the account to be accurate enough that the safety questions remain visible.

The studies I have discussed largely come from hospitals, medical education, and acute mental health nursing. They cannot establish what happened in my workplace. They can help us ask better questions about how warnings are received, how preparation is evaluated, and how responsibility connects to the power to make changes.

Those questions matter beyond one employer or one departure. When the person raising a concern leaves the room, the conditions they were describing may still be there. A quieter workplace is not necessarily one that has addressed its risks. It may simply have fewer people continuing to ask about them.

So I want to know what happened to the warning. Was it examined? Did it change a decision? Was someone responsible for following through? When the concern remained unresolved, who carried the consequences?

I am still angry. I do not need to turn that anger into a tidy lesson about everything happening for a reason. I do want it to sharpen the kind of leadership I practice: explain my decisions, make room for information that challenges them, and stay accountable for what I have the authority to change.

You do not have to like the person raising a concern to take the concern seriously. You do not have to enjoy the conversation to be responsible for having it. And you do not get to put care at the center of your mission while treating the work required to deliver it as a fucking inconvenience.

Care is also what happens after someone tells you that the current approach may not be enough. It is the examination you are willing to undertake, the resources you are willing to provide, and the decision you are willing to change—even when the warning comes from someone you would rather stop hearing.

Research references

[1] Okuyama, A., Wagner, C., & Bijnen, B. (2014). Speaking up for patient safety by hospital-based health care professionals: a literature review. BMC Health Services Research, 14, 61. https://doi.org/10.1186/1472-6963-14-61

[2] van Dongen, D., Guldenmund, F., Grossmann, I., & Groeneweg, J. (2024). Classification of influencing factors of speaking-up behaviour in hospitals: a systematic review. BMC Health Services Research, 24, 1657. https://doi.org/10.1186/s12913-024-12138-x

[3] Aiyer, S., Kam, H. C., Ng, K. Y., Young, N. A., Shi, J., & Feldman, G. (2023). Outcomes affect evaluations of decision quality: Replication and extensions of Baron and Hershey’s (1988) outcome bias experiment 1. International Review of Social Psychology, 36(1), 12. https://doi.org/10.5334/irsp.751

[4] Reason, J. (2000). Human error: models and management. BMJ, 320, 768–770. https://doi.org/10.1136/bmj.320.7237.768

[5] McGaghie, W. C., Issenberg, S. B., Cohen, E. R., Barsuk, J. H., & Wayne, D. B. (2011). Does simulation-based medical education with deliberate practice yield better results than traditional clinical education? A meta-analytic comparative review of the evidence. Academic Medicine, 86(6), 706–711. https://doi.org/10.1097/ACM.0b013e318217e119

[6] Jansen, T.-L., Hem, M. H., Dambolt, L. J., & Hanssen, I. (2020; first published online 2019). Moral distress in acute psychiatric nursing: multifaceted dilemmas and demands. Nursing Ethics, 27(5). https://doi.org/10.1177/0969733019877526

[7] Lamoureux, S., Mitchell, A. E., & Forster, E. M. (2024). Moral distress among acute mental health nurses: a systematic review. Nursing Ethics, 31(7). https://doi.org/10.1177/09697330241238337

[8] Nembhard, I. M., & Edmondson, A. C. (2006). Making it safe: the effects of leader inclusiveness and professional status on psychological safety and improvement efforts in health care teams. Journal of Organizational Behavior, 27, 941–966. https://doi.org/10.1002/job.413