Miranda’s Rescue, Humboldt County, and the Conflict the Legal Process Can’t Heal

Eight dogs. That's the number that broke Humboldt County's heart a month ago, when a sheriff's affidavit first alleged Shannon Miranda had killed and buried them on his rescue's property.

As of June 23, eight is not the number anymore.

That day, investigators brought heavy excavation equipment onto the 50-acre Miranda's Rescue property in Fortuna and started digging. The FBI and the USDA were there alongside the Humboldt County Sheriff's Office, executing a second search warrant. By the end of the first day, they'd recovered the remains of two more animals, a horse and a smaller animal whose identity hadn't yet been confirmed.

The numbers behind that excavation are what turn this from one property under suspicion into something much bigger. From the start of 2025 through May 1, 2026, investigators say Miranda's Rescue received more than 900 dogs from shelters across California and beyond. Investigators have confirmed 116 adoptions, and 71 dogs were still on the property when the first warrant was served in May. That leaves 731 animals unaccounted for.

No arrests have been made, and authorities have described the case as an active animal cruelty, fraud, and theft investigation. Sheriff Honsal has said investigators will turn the facts over to the Humboldt County District Attorney, the California Attorney General, and the U.S. Attorney's Office for potential charging decisions. Shannon Miranda has not been convicted of anything and is legally entitled to the presumption of innocence while that process plays out.

But long before any courtroom resolves what happened on that property, something else already has: this community has split in half.

Rose and her friends surrendered a dog named Marco to Miranda's Rescue in March. They'd spent two weeks caring for him, a stray Great Pyrenees, enormous and untrained but eager to please, after one of them found him in Eureka. One of them slept on the floor while he slept on top of her. They fell in love, but their apartments were not appropriate homes for Marco. They started a GoFundMe to cover the $500 surrender fee because they believed Miranda's 50-acre property would give Marco a real chance.

She was later told he'd been adopted by a woman in Oregon who wouldn't share her exact location and stopped sending photos.

When the Humboldt County Sheriff's Office executed the first search warrant at Miranda's Rescue in May, based on an affidavit in which a sheriff's detective alleged that owner Shannon Miranda had killed and buried at least eight dogs on his property, Rose found out. She still doesn't know if Marco is alive.

"I think I'm still kind of in denial," she said at a June 3 vigil outside the courthouse. "The idea that Marco's laying somewhere with a hole in his head, surrounded by dirt, is something that I haven't fully processed yet, but it’s definitely something I’m having a hard time handling."

That sentence describes where this community is right now. Processing something that hasn't fully landed. Holding grief and rage and uncertainty all at once. With nowhere to take any of it.

A community divided, predictably

Three weeks before federal investigators arrived with excavators, residents lined up at the June 2 Humboldt County Board of Supervisors meeting to speak during public comment. The split was visible almost immediately. Some residents described horror, urgency, and a demand for accountability. Others defended Miranda's character and warned against rushing to judgment.

It's easy to look at those responses and hear one side telling the truth and one side in denial. But that's not entirely what's happening here.

When a trusted community figure is accused of serious harm, communities don't just react. They fracture along relational lines. People who have known someone for years, who held bake sales for him, surrendered their most beloved animals to his care, trusted him with their money and their grief, aren't being naive when they defend him. They're being human. The mind protects what it has deeply invested in. That's not a character flaw. It's a feature of how trust works.

And the people demanding accountability aren't being a mob. They're also being human, responding to what the evidence in front of them is telling them, and to the pain of what they've lost.

Both responses are completely predictable. They will happen in every community that faces this kind of rupture. And no one is building a process for any of it.

The legal process will not heal this

Shannon Miranda has said, "A legal process is now underway to sort the facts from the lies, and I'm asking you to please hold fire until that process works its way through." That's a reasonable request for the legal question. Law enforcement, prosecutors, and, if charges are filed, the courts will determine what can be proven and what accountability looks like under the law.

But the legal process cannot heal a community.

Joe and Maurine spent years fundraising for Miranda's Rescue after adopting a dog from him. Their daughter and her friends held bake sales, donated everything they made. They don't know what happened to those dogs or that money. Even if the legal process eventually produces charges, findings, or a verdict, it won't give them that back.

Since the first stories broke, the circle of people carrying unanswered questions has widened. Shelters from Del Norte County to Napa to Palm Springs sent animals to Miranda's Rescue, believing they were giving them a better chance; Napa County alone sent 105 dogs. Many of those shelters are now trying to figure out how many of their own transfers are among the 731 animals investigators can't account for. That is not just evidence in a case. It is another layer of institutional trust that now has to be reckoned with.

Some shelters have begun trying to account for and retrieve the dogs they transferred. That matters. But it still leaves the larger community question unanswered: what happens to the people who trusted, donated, defended, suspected, reported, and now feel betrayed?

Speakers have described more than two decades of reports, missing animals, questioned practices, and unanswered concerns. That is not just an allegation against one person. It is a question a community has to sit with about itself: who raised concerns, who didn't listen, and what that means.

The legal process won't answer that question either.

Public comment is not conflict resolution

Here's what a community in crisis currently has access to: two minutes at a podium, in front of supervisors who cannot respond, on a topic that isn't even on the agenda.

Public comment is a release valve. It gives people somewhere to direct their voices when they feel unheard. That's not nothing. But it is not a process. There is no acknowledgment, no dialogue, no structured path toward any kind of shared understanding. People speak into a void.

Since then, the issue has also surfaced at the Planning Commission, where residents have questioned the county's decision to let Miranda's Rescue continue operating under a compliance agreement instead of suspending its permit outright. The rescue's permits were approved in 2003 and have been out of compliance with their original conditions for more than two decades. In early June, the county gave Miranda 14 days to sign and notarize a new compliance agreement tied to floodplain violations rather than pulling the permit. That, too, is not the same thing as a community process. It is a regulatory process, filtered through public comment, with residents trying to squeeze grief, anger, evidence, and institutional distrust into the margins of an agenda.

A woman at the vigil bought handcuffs specifically for Shannon Miranda and said she swallowed the key. Dan Martinez, who runs the San Jose-based rescue Adopt My Block, drove up after hearing that a dog named Oliver was back at Miranda's, and found him emaciated, with patches of missing fur and his spine visible through his coat. These are people in acute pain, responding to an absence of process with whatever they have available to them. That's what communities do when the formal structures fail to hold the weight of what's happening.

What could exist instead

I'm not suggesting the legal investigation, now involving the FBI and USDA on top of county and state authorities, should be interrupted or that conclusions should be drawn before evidence is heard. That's not what this is about.

What I'm saying is that the community fracture, the grief, the betrayal, the divided loyalties, the twenty years of unheard concerns, is its own wound. And it needs its own process.

Community dialogue circles. Restorative conversations facilitated by a neutral third party. A formal space, distinct from the courtroom, where people can bring what they're carrying and have it witnessed. Not to determine guilt. The legal process is for that. But to begin the slower, harder work of understanding how this happened, who was affected, and what accountability and healing might look like for a community that trusted deeply and is now in pieces.

Dan Martinez put it simply: "Crises precipitate change, and this is the crisis."

He's right. The question is whether this community will use it.

Sources

Humboldt County Sheriff's Office / County of Humboldt, "Miranda's Rescue Investigation," June 23, 2026

https://humboldtgov.org/m/newsflash/Home/Detail/6256

Lost Coast Outpost, "More Than 700 Dogs From Miranda's Rescue Remain Unaccounted For, Sheriff Honsal Says; Excavation of Grounds to Continue for Several Days," June 23, 2026

https://lostcoastoutpost.com/2026/jun/23/video-more-700-dogs-mirandas-rescue-remain-unaccou/

Lost Coast Outpost, "At Miranda's Rescue, Multiple Agencies, Including the FBI, Execute Search Warrant Authorizing Excavation," June 23, 2026

https://lostcoastoutpost.com/2026/jun/23/mirandas-rescue-investigation-update/

KRCR, "731 animals unaccounted for as investigators uncover remains at Miranda's Rescue," June 23, 2026

https://krcrtv.com/north-coast-news/eureka-local-news/search-warrant-served-at-mirandas-rescue-as-animal-cruelty-investigation-unfolds

Lost Coast Outpost, "Miranda's Rescue Search Warrant Reveals Eight Dead Dogs Have Been Recovered; Sheriff's Investigator Believes Miranda Killed Them for Financial Gain," May 20, 2026

https://lostcoastoutpost.com/2026/may/20/mirandas-rescue-neighbor-says-she-caught-him-camer/

Lost Coast Outpost, "Protestors, Revulsed by Miranda's Rescue Allegations, Gathered En Masse Yesterday," June 3, 2026

https://lostcoastoutpost.com/2026/jun/3/protestors-revulsed-mirandas-rescue-allegations-ga/

Times-Standard, "Shelters in Napa, Berkeley retrieve dogs from Miranda's Rescue," June 4, 2026

https://www.times-standard.com/2026/06/04/shelters-in-napa-berkeley-retrieve-dogs-from-mirandas-rescue/

Humboldt County Board of Supervisors meeting archive, June 2, 2026

https://humboldt.legistar.com/Calendar.aspx

The LEGO Conflict Is Not Just About LEGO

On its face, a dispute over a missing, mishandled, or poorly documented collection should not become a national conflict story. But the Bricks & Minifigs situation has many of the ingredients that cause conflict to expand beyond its original facts: a family who says they were harmed, a business defending itself, disputed records, a franchise structure, a valuable collection, public statements, lawsuits, creator coverage, threats, and thousands of people online trying to decide who to believe.

That is why the story has traveled so far.

Not because everyone suddenly cares about the resale value of LEGO Star Wars sets. Because the conflict is now carrying something larger: trust, accountability, process, power, and the question of what happens when people do not believe the available system is capable of resolving the harm.

I am not writing this to decide who is legally responsible. That belongs to the people directly involved, the evidence, and the courts. Public reporting and party statements still describe disputed facts: the value of the collection, the records available, who had authority, what was sold or paid, and who is responsible for repair. This article is not a verdict. It is a conflict analysis.

Because as a conflict story, this situation is worth paying attention to. It shows something that happens in many organizations, workplaces, communities, and public disputes:

The thing people are fighting about at the beginning is often not the only thing they are fighting about by the end.

The surface conflict is about property, records, and responsibility

At the center of the story is a valuable LEGO Star Wars collection that a family says was consigned to a Bricks & Minifigs store in the Salem/Keizer area of Oregon.

From there, the public story gets complicated quickly.

There are questions about the terms of the consignment, what inventory existed, what was sold, what was paid, what remained, and what records can prove it. There are questions about a change in store ownership, the role of former franchise operators, the role of corporate, and the responsibilities of later store owners.

Since the first wave of reporting, the legal and process layers have continued to evolve. Bricks & Minifigs has announced the permanent closure of the Salem, Oregon location, stated that it has parted ways with later franchise owners Brandon Best and Joshua Johnson, and said its investigation found significant evidence of negligence connected to the store transition and documentation.

Bricks & Minifigs has also filed suit against multiple people connected to the public campaign, while stating that it is prepared to discuss dropping claims against Bryan Mansell as part of a resolution. Those are party statements and reported developments, not neutral findings. But they matter because they show the dispute has moved from a missing-property question into a broader franchise, documentation, litigation, and accountability problem.

Reporting from Salem Business Journal describes conflicting sales records, disputed value estimates, point-of-sale data, lawsuits, and unresolved questions about what the family is actually owed and who is legally responsible for paying it. Bricks & Minifigs corporate has stated that the consignment arrangement was unauthorized and local to a former franchisee, and later valued the collection at roughly $95,000 to $100,000. While other creator and reporting analysis has suggested a different mix of missing inventory, unpaid proceeds, and disputed valuation. The exact number remains part of the conflict: people are not only arguing over what happened to the collection, but over what the loss is worth, what records should count, and who gets to define the harm.

Those questions matter. They are not small details.

In conflicts involving money, property, business ownership, or records, the facts are part of the harm. People need to know what happened, what can be proven, and who is credibly accountable for it.

But the public intensity around this story suggests that people are not only responding to the factual dispute.

They are responding to what they think the dispute means.

Once trust breaks, the conflict changes shape

When trust is intact, unclear information can sometimes be tolerated for a while. People may wait for clarification. They may give one another some benefit of the doubt. They may accept that a process takes time.

When trust breaks, the same uncertainty lands very differently.

A missing record does not feel like a missing record. It feels like concealment.

A delayed response does not feel like caution. It feels like avoidance.

A legal statement does not feel like risk management. It feels like a refusal to answer.

A disputed number does not feel like a normal accounting problem. It feels like someone is trying to shrink the harm.

This is one of the most important things to understand about conflict escalation. People do not only react to what happened. They react to what they believe the response reveals: Does this organization care? Is anyone taking responsibility? Are we being told the whole truth?

Those are not accounting questions. They are trust questions. And once a conflict moves into trust, the original issue becomes much harder to resolve on its own.

Even a correct spreadsheet may not repair what a poor process has broken.

The human layer: people are not abstractions in a public conflict

Public conflict flattens people quickly.

A family becomes a symbol of harm. A company becomes a symbol of greed or defensiveness. A franchise owner becomes either a villain or a scapegoat. A YouTuber becomes either a hero or an opportunist. Employees become representatives of a brand, even when they had no meaningful role in the original dispute.

That flattening is dangerous because it makes the conflict feel simpler than it is.

On the human level, this story includes people who may feel betrayed, accused, threatened, exposed, dismissed, or unsafe. It includes a family trying to understand what happened to something valuable. It includes local business owners whose reputations and livelihoods may be affected. It includes employees at unrelated locations who may suddenly be treated as responsible for a dispute they did not create. It includes people online who feel morally activated and want accountability.

Those responses are not all the same. They do not carry the same responsibility. But they are all part of the human field of the conflict now.

That is what happens when a dispute becomes public before people believe there has been a credible process for resolution. The conflict recruits more people. More emotion. More meaning. More harm.

The circle gets wider. And in a fast-moving public conflict, it may keep widening as new people, claims, and symbols attach themselves to the story.

The system layer: unclear process creates space for escalation

The system questions in this story are just as important as the human ones.

What documentation existed for the consignment? How was inventory tracked, and who had access to the records? What happens when a franchise location changes hands, and what does corporate need to know about local agreements? What is the escalation process when a customer, consignor, franchisee, or store owner says something has gone wrong?

These are not glamorous questions. They are operational questions. But operational gaps often become conflict accelerants.

Documentation can feel bureaucratic until trust breaks. Then everyone wishes the record had been clearer.

A signed agreement, an inventory process, a transaction log, a change-of-ownership checklist, and a clear escalation pathway are not just administrative safeguards. They are conflict prevention tools. They help people avoid having to reconstruct reality after the relationship has already deteriorated.

In this story, the public appears to be watching multiple versions of reality compete at once. Different parties point to different facts, timelines, records, and responsibilities. That does not automatically tell us who is right. But it does tell us something about process.

When the process is not trusted, people look for another one, litigation, media attention, social media, public pressure, or all of them at once.

The meaning layer: people are fighting over what the story proves

The deepest conflicts are rarely only about what happened. They are about what the event seems to prove.

In difficult conversations, people are rarely having only one conversation. They are talking about what happened, yes, but also about respect, identity, safety, fairness, and whether the other side can be trusted. The Harvard Negotiation Project’s Difficult Conversations framework is useful here because it treats hard conversations as layered: there is the “what happened” conversation, the feelings conversation, and the identity conversation.

Public conflicts work similarly, except the layers become visible to everyone.

To some observers, this story seems to prove that a family was ignored until the internet paid attention. To others, it seems to prove that online audiences can destroy reputations before facts are fully known. To some, it is a story about corporate accountability; to others, about local franchise failures. To some, it is about consumer protection; to others, about harassment and the monetization of conflict.

That is why the conversation becomes so charged. People are not only debating a collection. They are debating which larger story this belongs to. And the answer may not be only one of those things. That is exactly why the conflict is so difficult to hold.

High-conflict public stories often become battlegrounds for bigger questions people already care about: power, fairness, trust, exploitation, responsibility, safety, and whose version of events gets believed. Once those questions enter the room, the original dispute is no longer carrying only its own weight.

Public pressure can reveal harm. It can also create new harm.

One of the hardest things about this story is that two things can be true at the same time.

Public pressure can surface a concern that people believe was ignored. And public pressure can create new harm when it stops distinguishing between responsibility, proximity, and association.

That distinction matters. Accountability requires precision. It asks: Who had authority? Who had knowledge? Who had responsibility? Who benefited? Who failed to act? Who can repair what happened?

Escalation often loses that precision. It asks: Who is connected to this? Who can be pressured? Who can be made visible? Who can be punished quickly enough to satisfy the public demand for action?

Those are very different questions.

Public attention is not inherently wrong. In some cases, it is the only reason an ignored concern becomes visible. But when attention becomes pressure, and pressure becomes targeting, people can be harmed based on proximity rather than responsibility.

Recent reporting has also described disputes over fundraising, speech restrictions, and online creator activity, including Bricks & Minifigs denying that it attempted to seize the Mansell family GoFundMe. Whether or not each claim proves accurate, the pattern is familiar: once the conflict moves online, the process itself becomes another thing people fight over.

When a conflict is moving fast online, the difference between accountability and punishment can collapse. People may start with a legitimate demand for answers and end up targeting people who cannot answer them. They may seek accountability and create fear. They may demand repair while making repair harder.

None of that means the underlying grievance should be dismissed. It means accountability needs structure. A credible process, not just public pressure. Otherwise, the conflict can grow so large that even the original harmed party is no longer fully at the center of it.

Legal resolution and trust repair are not the same thing

The legal process may eventually clarify some of the factual and financial questions in this case. It may determine responsibility, assign liability, validate some claims, and reject others. That matters.

But legal resolution and trust repair are not the same thing.

A court can decide a claim. It cannot automatically restore public trust. A settlement can resolve a financial obligation. It cannot automatically answer why people felt they had to go public to be heard. A corporate statement can correct a narrative. It cannot automatically make people feel that the process was trustworthy from the beginning.

This is where many organizations misunderstand conflict. They assume that if the legal question is being handled, the conflict is being handled. But the legal question is only one layer. The trust question, the process question, and the meaning question still have to be addressed — and if they are ignored, people may experience the formal resolution as incomplete, even if it is technically accurate.

The broader lesson for leaders and organizations

Most organizations will never face a viral LEGO controversy. But many will face some version of this pattern: a concern is raised, the documentation is messier than it should be, the person raising it does not feel heard, and the organization responds cautiously, defensively, or too slowly. People begin filling in the gaps with their own interpretations. The conflict moves from the original issue into trust, identity, fairness, and accountability.

By the time leaders realize the conflict has changed shape, they are no longer only trying to solve the first problem. They are trying to repair the damage created by how the first problem was handled. This is not only a communications problem. It is a process problem. It is a leadership problem. It is a trust problem.

Research on workplace conflict points in a similar direction: conflict is not handled well by good intentions alone. It requires early attention, manager capability, sensitive process, and enough psychological safety for people to raise concerns before they explode. CIPD’s research on managing workplace conflict is a useful reminder that people managers can either help resolve conflict or unintentionally make it worse.

Before a conflict becomes public, leaders can ask:

•        What do we know, what do we not know, and what are we still verifying?

•        Who has authority to respond, and who has been harmed, affected, or pulled into the conflict?

•        What documentation would a reasonable outsider expect us to have?

•        What can we communicate now without pretending to know more than we do?

•        What process exists for appeal, review, escalation, or repair?

•        Who needs protection from retaliation, harassment, or misdirected blame?

Those questions do not guarantee a perfect outcome. But they create a better container for the conflict before the public creates one for you.

That is the lesson worth carrying from this story. Not that every public accusation is true. Not that every corporate defense is false. Not that every viral campaign is justice. Not that every legal response is avoidance.

The lesson is that conflicts expand when people do not trust the process available to them. If leaders want to prevent that expansion, they need more than good intentions. They need clear records, credible escalation pathways, timely communication, and enough humility to recognize when a conflict is no longer just about the thing that started it.

Because by then, people may be fighting about something much larger: whether they were heard, whether the process was fair, whether the organization can be trusted, what the event proves. And once that happens, resolving the original issue is necessary. But it is no longer enough.

A question worth asking earlier

When a conflict escalates, it is tempting to keep asking, “What happened?” That question matters. It should not be skipped. But it is not the only question.

At some point, especially when the conflict has grown, it is also worth asking: What are people fighting about now that they were not fighting about at the beginning?

That question does not replace accountability. It makes accountability more precise. It helps separate the event from the response, the facts from the meaning, the original harm from the additional harm created by escalation. And sometimes, it reveals the real work ahead.

Because the LEGO conflict is not just about LEGO. It is about what happens when trust breaks, the process is not enough, and everyone starts building their own version of the story.

Why “Just Talk to Them” Is Incomplete Conflict Advice

Hard conversations do not only require courage. They require structure, timing, neutrality, and enough safety for people to actually tell the truth.

An employee tells a manager that a teammate keeps dismissing their input in meetings. A board member says a conversation with the chair no longer feels safe. A volunteer admits they are avoiding someone because the last attempt to talk only made things worse.

In each situation, someone nearby may offer the same advice:

“Just talk to them.”

It is one of the most common pieces of advice people receive when they are dealing with conflict at work, in a community group, in a family system, or inside an organization.

On the surface, it sounds reasonable. Direct communication is often better than avoidance. Many misunderstandings do need a conversation. And yes, sometimes people do need to stop venting and speak to the person involved.

But “just talk to them” is also incomplete advice.

Sometimes it is even bad advice.

Because conflict is rarely solved by conversation alone. It is solved by the right kind of conversation, at the right time, with the right structure, and with enough safety for people to participate honestly.

This matters especially for people in leadership or support roles, because the advice they give can either create a path toward repair or quietly send someone back into a situation they do not have the power to change.

Why “Just Talk to Them” Can Make Conflict Worse

Without those conditions, “just talk to them” can make things worse.

When someone is struggling with conflict, they are often not avoiding the conversation because they do not know talking is an option.

They are avoiding it because something about the conversation feels risky.

They may not trust the other person to listen. They may have tried before and been dismissed. They may be dealing with someone who interrupts, denies, blames, or redirects. They may worry that honesty will damage the relationship permanently. 

In those situations, telling someone to “just talk to them” can sound practical, but it actually skips over the most important question:

What would make that conversation safe enough, clear enough, and useful enough to be worth having?

A person can be willing to talk and still not be ready. A team can schedule a meeting and still not have the structure to use it well. But recognizing that gap is the advisor’s job, not the conflict participant’s. When someone comes to you with a conflict, the question is not just “have they talked to each other yet?” It is: what conditions would make that conversation worth having?

Conflict Conversations Need a Container

This is why so many conflict conversations fail. Not because people never talk, but because they talk without a container.

They talk too soon, or when one person is overwhelmed or defensive. They talk without agreeing on what the conversation is for. They talk when one person has much more power and the other knows there may be consequences. They talk after months of buildup and expect one meeting to repair everything.

Conversation matters. But conversation without structure often becomes another round of the same conflict.

Before encouraging someone to “just talk to them,” it is worth asking what kind of support the situation requires.

Most conflict conversations need at least four things: structure, neutrality, timing, and psychological safety.

Structure

Structure means the conversation has a purpose, boundaries, and a process.

Without structure, people often default to their usual conflict patterns. One person over-explains. Another shuts down. The conversation becomes circular, emotional, or vague.

A structured conversation answers questions like: What are we here to discuss, and what are we not trying to solve today? Are we trying to understand, make a decision, repair harm, or create a plan? What happens after the conversation?

A simple structure might look like this: each person shares what happened from their perspective, names the impact, and identifies what they need going forward. Together, they clarify agreements, next steps, or unresolved issues.

That is very different from “just talk.”

Neutrality

Some conflicts need a neutral third party, especially when trust is low, power is uneven, or the same conversation keeps happening without progress.

Neutrality does not mean the third party has no values or never intervenes. It means they are not there to win the argument for either side. Their role is to protect the process, slow down reactivity, and help people stay engaged long enough to understand each other.

In workplaces, this might be a mediator, ombuds, trained facilitator, or outside consultant. In community or family conflict, it might be a restorative practitioner, counselor, or someone both parties genuinely trust.

Neutral support roles, such as organizational ombuds, are grounded in principles like independence, impartiality, confidentiality, and informality, all of which protect the process rather than choose a side.

Timing

Timing can make or break a conflict conversation.

People are often encouraged to address conflict quickly, and that can be helpful. But “quickly” is not the same as “immediately.” A conversation is unlikely to go well when someone is overstimulated, cornered, exhausted, or still actively trying to understand what happened.

Good timing asks: Has each person had enough time to regulate? Is this the right setting? Are we catching someone off guard before a deadline, performance review, or public meeting?

Sometimes the most responsible move is not to talk immediately. It is to pause, prepare, and choose the right moment.

That pause is not avoidance. It can be conflict wisdom.

Psychological Safety

Psychological safety means people believe they can speak honestly without being punished, humiliated, dismissed, or retaliated against.

Google’s Project Aristotle research describes psychological safety as people’s perception of the consequences of taking an interpersonal risk, whether they can speak up, ask a question, or offer a different view without being embarrassed or punished.

A manager may say, “I want honest feedback,” but an employee may know that honesty has not gone well for others. A board chair may welcome all perspectives while members have learned that disagreement leads to exclusion. When safety is missing, people may attend the conversation and appear cooperative. But they will not say what needs to be said.

They will edit themselves. They will perform agreement. And leaders may mistakenly conclude the conflict has been resolved, when really it has gone underground.

Another problem with this advice is that it places responsibility on the person already experiencing harm, and lets the organization or leader off the hook. When someone brings a concern forward and is told “just talk to them,” the message they often receive is: you manage this.

That may be unfair if the person has less power, less protection, or less emotional bandwidth. Before recommending direct conversation, leaders should ask:

Is this person being asked to carry a conflict the system should be addressing?

Has the other person shown capacity to engage respectfully?

Is there a power imbalance? Has this already been tried?

What support would make the conversation fairer?

If those questions are skipped, “just talk to them” can become a form of abandonment disguised as empowerment.

CIPD’s research on workplace conflict notes that people managers can be just as likely to exacerbate a conflict situation as resolve it, which is why early support, process, and structure matter.

When Direct Conversation Is Not the Right Next Step

It is also worth naming what direct conversation cannot do. If the situation involves harassment, discrimination, retaliation, abuse, threats, or formal policy violations, the responsible path may include documentation, HR, legal guidance, or safeguarding procedures. As an advisor or leader, recommending direct conversation in those situations can inadvertently bypass accountability structures that exist for good reason.

Many conflicts can be addressed through ordinary conversation, especially when trust is intact and the stakes are low. But even informal conversations benefit from a better container.

Better Questions to Ask Instead

Instead of saying, “Just talk to them,” try:

“Would it help to plan what you want to say first?”

“What outcome are you hoping for?”

“Do you feel safe having that conversation directly?”

“Is now the right time, or do you need to prepare?”

“What would make the conversation productive instead of circular?”

These questions change the advice from simplistic to supportive. They recognize that conflict is not just about getting people in the same room. It is about creating conditions where something different can happen in that room.

The better response is often not to solve the conflict immediately. It is to help assess what kind of conversation the situation requires.

“Let’s think about what kind of conversation this requires.”

“Do you want to be heard, make a request, set a boundary, repair the relationship, or document a concern?”

“Is this a conversation you can have directly, or does it need support?”

“What has happened in past conversations with this person?”

“Would it be useful to have someone facilitate?”

These responses do not discourage direct communication. They make direct communication more responsible.

The goal of a conflict conversation is not to check the box that communication happened.

The goal is movement: toward clarity, toward accountability, toward repair, toward a decision, toward a safer or more functional working relationship.

If a conversation does not create movement, it may simply repeat the harm in a new setting.

That is why “just talk to them” is not enough.

People do need conversation. But they also need preparation, process, and support. They need to know whether the conversation is safe, whether the purpose is clear, and whether there is a path forward afterward.

Conflict is not resolved by words alone.

It is resolved when the conversation is held in a way that makes honesty, accountability, and change possible.

If the people in your organization, your board, your team, or your community keep having the same conversations without real movement, the problem may not be willingness. It may be that the conversation needs a better container.

A facilitated conflict process can help people move beyond venting, avoidance, and circular discussion toward clearer agreements, better understanding, and more durable repair.

Sources

International Ombuds Association, Standards of Practice & Code of Ethics

Google re:Work, Understand team effectiveness

CIPD, Managing conflict in the modern workplace

U.S. Equal Employment Opportunity Commission, Harassment

The AI Output Was Approved. The Trust Wasn't.

A few weeks ago, reporting from TechCrunch and 404 Media said arXiv would begin banning researchers for a year if they submitted papers where it was obvious no human had looked at what the AI produced. Things like hallucinated citations, notes the LLM left in the text, placeholders where real data was supposed to go but never did.

arXiv's own moderation policy is clear about this. If you put your name on it, you own it, no matter how it was generated. According to the reporting, get caught submitting something with obvious signs of that and you are out for a year, and after that your work may have to pass through a reputable peer-reviewed venue before arXiv will look at it again.

These are the easy failures to spot. The harder problem is what happens when the output looks fine. arXiv is talking about research integrity, yes. But the problem is bigger than research. AI-generated work is moving into official channels, going out under the organization's name, and too often no one has clearly owned the work of verifying it. When it fails, the accountability question gets passed around like something no one wants to hold.

That pattern is not going to resolve itself at the technical level.

You deployed the tool. The team was excited. The vendor demo was clean, the use case was obvious, the productivity gains were real. Six months in, you can see the hours saved on the dashboard. But you can also see something you were not expecting. Complaints have ticked up. The people doing the work seem more guarded than before. Customers, patients, employees, donors, community members. They are quietly losing trust in processes that on paper are working better than ever.

Nobody quite knows how to explain it. The AI is doing what it was asked to do. The output is technically correct. The recommendation, message, or decision is defensible. And yet somewhere downstream, a person reads what the system produced or sits with what it decided, and something in them goes still.

The email is correct and lands wrong. The denial is technically defensible and breaks something. The summary captures what was said and misses what was meant.

The system performed the task. It did not understand what the task meant.

Meaning is not the same as accuracy. Meaning is what the action communicates to the person on the other end of it. What context it lands in. What power it activates. Whether the person feels seen or just processed. The patient does not appeal. They just stop trusting the portal. The employee does not file a complaint. They stop being candid in the next survey. The customer does not explain what broke. They just stop believing the organization understands them.

Most leaders reach for the wrong diagnosis when this happens. We assume the AI needs a better prompt, a larger training set, a more sophisticated model. We treat the gap as a capability problem.

It is not. Or at least, it is not only that. The deeper problem is not just whether the tool can complete the task. It is whether the organization has decided who is responsible for the human consequences of that task once it reaches another person.

The arXiv case makes something visible that has been building quietly everywhere else. When a researcher submits a paper with fabricated citations they never checked, the issue is not only whether they intended to deceive. The issue is that they put the organization's credibility behind work they had not verified. Who is responsible? arXiv's answer is clear: the researcher. Full stop.

That clarity is notable because most organizations do not have it. When an AI system produces an output that breaks trust, the accountability question tends to float. Was it the tool? The prompt? The person who approved deployment? The vendor? The leader who set the efficiency target? In the absence of that clarity, organizations default to the path that protects everyone in the room, which usually means the person on the receiving end absorbs the cost quietly.

This is the structural problem. The AI missed what the action meant, and no human had been clearly assigned to check that part.

Technical problems have owners: vendors, IT teams, implementation leads. Accountability for how a message lands is harder to assign because it implicates leadership, culture, incentives, and the promises an organization has made to the people it serves.

In a recent essay on the next phase of AI, Nate B. Jones calls this access without meaning. His argument is that AI tools are getting impressively good at doing tasks. They open browsers, draft emails, schedule meetings, process claims, complete workflows. But they still do not understand what the task means inside a relationship, an institution, or a person's life. The action is performed. The significance is missed.

His central line is the cleanest articulation of this I have found: Computer use gives agents reach. Semantic control gives them judgment.

Giving a system access to act is not the same as giving it the judgment to understand what its action will mean.

Reach is what the demos sell. Judgment is what organizations actually need. Reach lets a system act. Judgment lets it know whether the action is wise, whether the timing is right, whether what is technically defensible is also relationally sound.

arXiv researchers are not the only ones submitting outputs they never fully read. They are just the ones who now have a formal policy naming what that costs.

Most leaders reach for one of two responses. The first is technical optimism. Better prompts, better models, better data. The second is avoidance. Pull back, wait, let someone else figure out the ethics. Both miss the point. Stop treating this gap as a bug. It is part of the work now, and it belongs to the organization to govern.

There is a third response, and it is the one almost no one is set up to take seriously yet.

Treat the gap as territory, not as a defect.

This is not a missing feature in the software. It is where dignity lives. Where trust is built or quietly broken. Where institutions earn the right to operate, or slowly stop earning it. None of that is a software category. None of it can be retrofitted in a future release. It belongs to the part of organizational life that has always required human attention.

This is the territory conflict practitioners have always worked in.

The work itself does not look like much, which is part of why it is so easy to underestimate. It looks like sitting with the manager whose team has stopped speaking honestly in meetings and asking the question no one else has asked. It looks like noticing that a denial letter, however legally sound, communicated something the organization did not intend. It looks like helping a leader see that what the dashboard calls efficiency may also be wearing down the trust their staff used to offer without thinking.

It looks like the quiet, often unmeasured work of restoring a connection between a system and the people who must continue to live and work inside it.

This is not a soft skill set, and it is not a temporary one. It is the practice of paying attention to what an action communicates after it has been completed. To the second-order effects automation cannot yet see. To the moment a customer, patient, or employee silently decides to stop fully engaging. Some of this eventually shows up in metrics: complaints, appeals, churn, disengagement. But by the time it does, the trust loss has often already begun.

Nate B. Jones frames this as an engineering frontier. I understand why. But for conflict practitioners, this is not new terrain. It is the work we have always been doing. Paying attention to what a decision communicates after the decision has technically been made.

Before deploying AI into any consequential workflow, leaders should be able to answer three questions: Who is responsible for verifying the output before it goes out under the organization's name? Who is responsible for noticing how the output lands with the person receiving it? And what happens when the technically correct answer violates the relationship the organization is trying to protect?

arXiv drew a line because someone eventually has to. Their version is simple. You are responsible for what you put your name on, full stop. That rule will not scale to every sector on its own. But the underlying principle will have to.

The leaders who do well in the next phase will not be the ones who deploy the most tools the fastest. They will be the ones who notice what their tools cannot see, name who is accountable for what those tools produce, and make sure real people are still responsible for the parts of the work that affect trust.

That is the work. Not engineering meaning into machines, but tending the meaning that was always going to remain human.

Sources

• TechCrunch: "Research repository arXiv will ban authors for a year if they let AI do all the work" (Anthony Ha, May 16, 2026)

• 404 Media: "arXiv to Ban Researchers for a Year if They Submit AI Slop" (Samantha Cole, May 15, 2026)

• arXiv: "Content Moderation: Policy for authors' use of generative AI language tools"

• Nate B. Jones: "AI Work Primitives: Why Access Without Meaning Fails for Agents" (Substack)

What the Humboldt Ruling Actually Reveals About Conflict at Work

A California appellate court just held that three Humboldt County HR employees can be sued personally for negligence. The headline reads like an HR liability story. It isn't. It's a conflict avoidance story wearing a court record.

The decision came down on May 13, 2026 (Gibbs v. County of Humboldt et al., No. A173637, Cal. Ct. App., First Dist., Div. 1). The Court of Appeal for the First Appellate District revived a lawsuit by Kay Marie Gibbs, a court reporter who started with the Humboldt County Superior Court in 1982. She became eligible for the California Public Employees' Retirement System (CalPERS) in December 1983. The county did not enroll her until November 1989. The six-year gap went undiscovered until 2019, when she was preparing to retire.

When CalPERS asked the county to certify her full employment history so the missing years could be credited, the county could not. Records were missing for four separate stretches between 1982 and 1989. The trial court had dismissed her case entirely. The appellate court reversed, ruling she had stated viable claims that can proceed. The court held that two duties were mandatory, not discretionary: record retention and pension enrollment. In the unpublished portion of the opinion, the court held that the three named HR employees can be sued personally for negligence, with the county vicariously liable for their conduct. In California, unpublished means the ruling does not set binding precedent for other courts, cannot be cited as precedent by parties in other cases, though it is fully operative for these parties. Both rulings turn on the same core principle: these were not judgment calls. Vicarious liability means the county, as their employer, is legally responsible for what those employees did in the course of their jobs. It cannot distance itself from the actions of its own staff. That the court allowed these claims to proceed at all, over the defendants' immunity arguments, is itself significant. The case now returns to the Humboldt County Superior Court; no determination of liability has been made yet. Gibbs says she has been forced to delay her retirement and is losing hundreds of thousands of dollars in retirement benefits.

The court's own word for what she faced was "Kafkaesque," a reference to the novelist Franz Kafka, whose characters are typically trapped in bureaucratic systems so opaque and self-perpetuating that no door leads anywhere except to another closed door. It is an unusual word to find in a legal opinion. Judges reach for it when the situation earns it.

Those three employees are named in the public record. I am choosing not to name them here. The systems failure is what matters, and personalizing it lets organizations off the hook in a way I do not want to participate in. A forty-year gap, four separate missing-record stretches, multiple administrations of HR. These are not the fingerprints of three individuals. They are the fingerprints of an organization with no way for hard truths to travel upward. Whose names you remember from this story should be a choice, not a default.

What actually went wrong in Humboldt County is operating on three levels at once.

On the human level, multiple staff across multiple administrations encountered, or could have encountered, the same gap. None of them escalated it in a way that closed the loop. People rarely sit on a problem out of malice. They sit on it because the cost of raising it is unclear, the path for raising it is unclear, and silence feels safer in the moment. That is a human pattern, not a personal failing. Most of us would do the same inside a system that does not make the alternative obvious.

On the system level, the duty was mandatory by statute. But the system around the duty was treated as discretionary in practice. That includes workflow, escalation paths, retention practice, and the question of who actually owns a file once it has been quiet for fifteen years. It is worth noting that systemic record loss and human avoidance are not competing explanations. Software migrations, paper-to-digital conversions, and leadership transitions can destroy institutional memory just as surely as silence does, and in most organizations the two operate together. That is the gap statutes cannot close. A law tells you what is required. It does not tell you how the requirement actually moves through a real organization with turnover, software migrations, leadership transitions, and tired people doing their best on a Tuesday afternoon.

On the meaning level, forty years of small avoidances compounded into one woman's lost retirement. That is not administrative housekeeping. That is the slow cost of an organization that never built a way for inconvenient truths to find a path forward. Organizations like this one often communicate, without saying so out loud, that raising old, complicated questions is not a winning move. So the questions do not get raised. And the bill keeps growing.

This is the part most organizations miss. Workplace conflict is not only the loud version: the complaint, the grievance, the lawsuit. The quieter version is the file no one opens, the question no one asks, the escalation no one routes. Avoidance is a form of conflict. It is just conflict that has not yet been spoken aloud. And when an organization has no designed architecture for surfacing difficult information, avoidance becomes the path of least resistance. By the time the bill comes due, it almost always lands on whoever is closest to the gap when it is discovered, not whoever created it.

What organizations actually need is not more compliance reminders. They need conflict systems thinking applied to operational drift. A real way for staff to surface compliance gaps without career risk. A defined path for "I think we missed something years ago" that does not feel like a confession. Leadership accountability for the systems that produce these outcomes, not only for the people standing nearest when the outcomes are found. Conflict systems design is not just about disagreements between people. It is about how organizations make room for hard truths to travel before they become legal events.

Humboldt County is where I live. This ruling is news here. But the underlying pattern is not local. Every organization has its own version of this case quietly building somewhere. The question is whether anyone is set up to see it.

Sources

• Gibbs v. County of Humboldt et al., No. A173637, Court of Appeal of the State of California, First Appellate District, Division One (filed May 13, 2026). Full opinion (PDF)

• Bongat, C. (May 17, 2026). HR staff personally on the hook after California county loses.Human Resources Director.

Why the Same Conflict Keeps Happening at Your Organization

Most organizations have a conflict they can't stop having. Different cast, different details, same shape underneath. It produces a particular kind of exhaustion. A kind that won’t show up in any report.

It lives in the hallway conversations after the meeting. In the manager who has stopped bringing certain topics to certain people. In the team that functions, technically, but hasn't had a real conversation in months. Nobody files a complaint about it. Nobody quite knows how to name it. But everyone feels it, and everyone has quietly decided it's just how this place is.

And then someone gets labeled the difficult person.

Sometimes that's true. Sometimes there is a difficult person, and something needs to change. But often, the difficult person is simply the most visible symptom of something the organization built without meaning to.

I've watched this play out from a few different sides: as an employee, as a board member, as a small business owner, and more recently as someone designing conflict resolution programs for organizations trying to understand their own patterns. From each of those vantage points, the same thing keeps becoming clear. The difficult person is rarely the cause. They're the visible end of a chain that runs much deeper into the system.

Don Norman would call it a design failure. I call it the most expensive misdiagnosis in organizational life.

Norman spent decades studying why intelligent, capable people consistently fail when placed inside poorly designed systems. His central argument, developed most fully in The Design of Everyday Things, is deceptively simple. When something goes wrong, the instinct is to blame the person. But more often than not, the system made the wrong action easy and the right action hard. The feedback was missing. The signals were unclear. The environment was set up for failure, and then a human being stepped into it and did exactly what the environment taught them to do.

Norman named two specific gaps that matter here. The first, the Gulf of Execution, is the gap between what you're trying to do and what the system will let you do. Imagine pushing a door that needs to be pulled, or hunting for a button that isn't there. The second, the Gulf of Evaluation, is the gap between what the system is doing and what you can tell about it. Did your action work? What state are things in now? What just happened? Both gaps are where well-meaning people end up struggling inside environments that don't tell them what's true.

Most organizations have never mapped those gulfs in relation to their conflict. They've mapped them for their technology, their workflows, their customer experience. But the human systems get treated differently. How people communicate. How decisions get made. How disagreement is handled or avoided. Those are usually left to chance, personality, and whoever happens to be in the room.

That gap is where chronic conflict lives.

Toyota understood something similar from a completely different direction. Among the principles that built one of the most studied organizational cultures in the world is genchi genbutsu: go and see for yourself. Don't manage a problem from a distance. Don't rely on the report, the secondhand account, or the assumption about what's happening and why. Go see for yourself. Stand where the work actually happens and look at what the environment is asking people to do.

When Toyota applied that principle to production failures, they found that most errors weren't caused by careless workers. They were caused by systems that made errors nearly inevitable. The fix was rarely the person. It was the process that surrounded them.

The same principle applies when a team keeps having the same argument, when a department can't seem to resolve anything without it escalating, when a leader keeps losing good people and can't quite explain why. Go to the source and see for yourself. Not to assign blame. To understand what this environment is teaching people to do.

That question changes everything about where you look.

Here is what I find in organizations with chronic, recurring conflict. Often, something in the design is generating it.

Roles without clear boundaries create spaces where people spend energy protecting turf that was never actually in dispute, because no one defined where one person's authority ends and another's begins.

Feedback channels exist on paper but have never produced a visible result, so people stop using them and start having the real conversations in parking lots and group texts instead.

Accountability applies differently depending on who you are or how long you've been there, so newer people learn fast that the stated standards and the real standards are not the same thing.

Expectations shift without explanation, so people stop making independent decisions and start waiting to be told. Not because they lack judgment, but because the environment has taught them their judgment doesn't stick.

Organizations hire for competence, then build processes that ignore it. Skilled people end up adapting to the system instead of contributing what they were brought in to do.

None of this requires bad intentions. It doesn't even require bad leadership. But it is worth saying plainly. Many of these design failures persist because they benefit someone. Ambiguous roles protect whoever holds informal power. Feedback channels that produce no visible result protect the people who would have to act on what came back. Accountability that applies unevenly is rarely a bug. It's a feature for whoever the system was quietly built to favor. Looking honestly at what an organization has built means being willing to see who it serves.

Which is why this kind of work is harder than it sounds. The people who would need to redesign the system are often the people whose decisions built it. Saying "go and see for yourself" is easy. Asking leadership to look at the source is where the real friction begins, because it requires considering that the source might be them, or the structures they protect.

Norman would recognize the pattern immediately. So would any Toyota engineer who has ever stood on a production floor and watched a process work against the people inside it.

The difficult person, in most cases, is doing something the environment made easy. Avoiding, escalating, withholding, competing. These are rational responses to environments that reward, or at least fail to discourage, them. The solution is not to train that behavior out of individuals while leaving the environment intact. The solution is to look honestly at what the organization has built and ask what it is quietly teaching everyone inside it.

This is harder than sending someone to a communication workshop. It requires a different kind of courage from leadership. The willingness to look at the system rather than the symptom. The willingness to ask what we built here instead of who is causing this.

But it is also more honest. And in my experience, it is the only approach that actually changes the pattern rather than just managing it until it surfaces again.

Norman designed his life's work around the belief that when human beings fail inside systems, the system owes them an honest accounting. That when the design makes failure predictable, redesign is not optional. It is a responsibility.

Organizations that take conflict seriously enough to ask what they built, and what it is teaching people, are the ones that stop having the same conversation over and over again.

That is the work. Not managing people better. Designing systems worthy of them.

Why Hard Conversations Go Wrong Even When You Do Everything Right

You've had the conversation. Maybe more than once.

You stayed calm. You chose your words carefully. You did everything right, and it still went sideways. The relationship is worse now than before you tried to fix it. And somewhere underneath the frustration is a question you haven't quite let yourself ask: what if the way I'm showing up is part of the problem?

Not your intentions. Your intentions are fine. Something subtler than that.

Jung called it the Shadow. It's the part of us we can't see precisely because we're too busy watching the other person.

Here's what the Shadow does in conflict. It takes the qualities we haven't made peace with in ourselves and finds them, with startling accuracy, in the person across from us. The colleague who never takes responsibility. The leader who always has to be right. The teammate who goes quiet when things get hard. We see them clearly. We can articulate exactly what they're doing and why it's a problem.

What's harder to see is what their behavior is activating in us. Not just frustration. Something older than frustration. A wound, a pattern, a part of ourselves we've been managing so long we've stopped noticing it's there.

This is not an accusation. It's an observation about how human beings work in moments of stress and perceived threat. The nervous system narrows. Perception narrows with it. And in that narrowing, the other person stops being a full human being with their own fears and history. They become, in our minds, the problem.

That's the moment most conflict interventions try to address. How do you communicate better from that state? How do you stay regulated? How do you find common ground?

These are useful questions. But they're downstream of a more important one.

What I keep coming back to, in this work and in my own life, is that the question that actually shifts outcomes isn't tactical. It doesn't live in a script or a framework. It surfaces before any of that, if you stop long enough to ask it.

Who am I willing to become in this moment, regardless of what they do?

Not: how do I get them to change? Not: how do I win this? Not even: how do I stay calm?

Who am I willing to become?

That question does something the tactical questions can't. It pulls the focus back to the one variable you actually control. Not the other person's behavior. Not the history between you. Not whether they'll ever see it your way. Just this: what kind of person do you want to be when this is over?

Jung believed that individuation, the lifelong process of becoming more fully yourself, runs directly through the things that disturb us most. Not around them. Through them. The conflicts that cost us the most sleep are often the ones carrying the most information about where we're still unfinished.

That's not a comfortable idea. It's not supposed to be.

What changes when you hold that question seriously is not that conflict becomes easier. It doesn't. What changes is where you locate the work. Instead of spending all your energy trying to manage or change the other person, you start asking what this situation is asking of you.

That shift is quiet. It doesn't announce itself. But it changes everything about how you enter the room, how you listen, and what becomes possible once you're there.

Most people never get there because the pull toward focusing outward is powerful and understandable. It is genuinely easier to analyze what the other person is doing wrong than to sit with what the situation is reflecting back at us.

But easier rarely gets us where we're trying to go.

The conversations that actually repair something, the ones that move a team or a relationship from stuck to forward, almost always have this quality: someone decided to be a little more honest about their own part. Not perform accountability. Actually get curious about it.

That decision is available before you ever say a word. It lives in the question you ask yourself on the way in.

Who am I willing to become, regardless of what they do?

Everything else follows from there.

If this is showing up in your organization

Hard conversations often go wrong long before anyone says the wrong thing. The problem may be unclear expectations, missing structure, avoidance patterns, or a team that has never been given shared language for conflict.

I help organizations build practical conflict literacy, de-escalation skills, and clearer pathways for difficult conversations before tension turns into damage.

Start the conversation