Some Victim Support staff 'horrified' by CEO's response to workplace culture concerns - RNZ

When news broke that Some Victim Support staff 'horrified' by CEO's response to workplace culture concerns - RNZ, the reaction from the tech community was immediate and visceral. We've all seen this movie before-a leader, confronted with uncomfortable truths about their organization's culture, responds not with humility but with deflection, minimisation. Or outright denial. It's a pattern as predictable as a segmentation fault in a null-pointer dereference, and just as destructive. But if you're an engineering leader reading this, the lesson isn't just about empathy; it's about systemic failure modes that plague teams from startups to Fortune 500s.

The RNZ article describes how staff at Victim Support felt shocked and further marginalised after the CEO's response to concerns about workplace bullying, lack of transparency. And retraumatisation of employees. What makes this story resonate beyond the nonprofit sector is the textbook breakdown of feedback handling-a skill that separates high-performing engineering organisations from those that slowly hemorrhage talent. In production systems, we instrument every endpoint; in leadership, we too often go blind to the same signals.

Let's deconstruct this incident through an engineering lens. What went wrong, why it matters for every tech leader. And how you can build a culture that doesn't just tolerate feedback but actively seeks it-before it becomes the next headline.

The RNZ Report: A Case Study in Leadership Failure

According to the original RNZ investigation, Victim Support staff described a culture where their own trauma was dismissed, where raising concerns led to retaliation. And where the CEO's written response to a formal review was perceived as defensive and invalidating. The report quoted staff saying they were "horrified" and felt "gaslit. " For engineers, this language mirrors the experience of filing a critical bug report only to have it closed as "works as intended" without discussion.

The CEO's alleged response-questioning the methodology of the review, focusing on achievements rather than failures. And implying staff misinterpreted events-is a classic defensive pattern. In software, we call this a denial-of-service attack on the feedback loop. When leadership refuses to acknowledge the severity of a problem, the system can't recover,

This isn't a niche HR issueMcKinsey research shows that toxic workplace culture is the single biggest predictor of employee turnover, costing companies billions annually. And in tech, where talent is scarce and retention is king, ignoring culture is a direct threat to product velocity and innovation.

Why Workplace Culture Is a Technical Debt Problem

Think of culture as the runtime environment of your engineering organisation. You can have the cleanest code, the best architecture, and the fastest CI/CD pipeline. But if the runtime is poisoned-if people can't speak up without fear-your system will eventually crash. This is the cultural technical debt that compounds silently, much like hardcoded credentials or missing error handling.

In production, we pay down technical debt with refactors. In culture, we pay it down with psychological safety investments. Google's Project Aristotle famously found that psychological safety was the top predictor of high-performing teams. Teams where members felt safe to take risks and admit mistakes outperformed those that didn't-even when the latter had superior individual talent.

The Victim Support story illustrates what happens when debt accumulates without repayment. Staff became "horrified" not just by the initial problems but by the leader's inability to even acknowledge the debt existed. For CTOs and VP Engineering, this is a cautionary tale: your team's silence might not mean agreement; it might mean they've given up on being heard.

The Feedback Loop: Ignoring Signals Like Ignoring Logs

Every engineer knows the nightmare of ignoring a warning log because it's "noisy. " Then, one day, the cluster goes down. And the same principle applies to organisational signalsEmployee engagement surveys, exit interviews, Slack complaints. And even body language in meetings are runtime logs of your culture's health.

In the RNZ case, multiple staff raised concerns through formal channels. Those channels returned a review that corroborated their experiences. Yet the CEO's response effectively ignored the logged warnings by casting doubt on the data. Imagine a DevOps engineer seeing a critical alert and responding, "Well, that monitoring tool has been unreliable before. " That response would get the engineer fired. But in leadership, such dismissal is often rewarded as "decisive. "

The fix is straightforward: treat every culture complaint as a P1 incident until proven otherwise. That means acknowledging receipt, investigating with an open mind, communicating what you learned. And showing concrete changes. Anything less is a bug in your leadership platform.

Psychological Safety: The Missing Unit Test for Team Health

One of the most devastating outcomes of the Victim Support situation is the erosion of psychological safety. staff who were already vulnerable because of their work-supporting victims of crime-felt further endangered by their own employer. In a tech context, that's akin to having a test suite that randomly fails because of flaky assertions: you lose trust in the entire process.

Building psychological safety requires deliberate architecture. Amy Edmondson's research defines it as "a shared belief that the team is safe for interpersonal risk taking. " For engineering leaders, that means: (1) modeling vulnerability by admitting your own mistakes, (2) inviting dissenting opinions during design reviews. And (3) rewarding people who escalate issues early-even if the issue turns out to be minor.

If your team is afraid to bring up a bad block of code, they're also afraid to bring up a bad manager. The same muscle is used. When a CEO invalidates staff concerns, they're not just being insensitive; they're actively breaking the unit test that would catch the next failure.

The CEO's Response: A Classic Bug in Executive Decision-Making

Let's analyse the CEO's reported behaviour using the Cynefin framework-a popular decision-making model in Agile and DevOps communities. The CEO treated a complex problem (systemic cultural issues) as if it were simple (a misunderstanding to be corrected). The appropriate response in the complex domain is to probe, sense. And respond. Instead, the CEO reacted by asserting pre-existing solutions and dismissing the probes.

This is a classic cognitive bias bug: the Dunning-Kruger effect applied to leadership. The CEO may have genuinely believed they understood the culture because they saw only the surface metrics-happy hours, open-door policies-while missing the deeper alienation. In engineering, this is equivalent to a lead dev insisting the code is clean because they haven't looked at the production logs.

The fix requires humility tools: regular skip-level meetings, anonymous feedback systems (like Officevibe or Culture Amp). And external audits. But more fundamentally, it requires a mindset shift from "I need to have the answers" to "I need to create the conditions for the right answers to emerge. "

Engineering Teams Can Learn from Victim Support's Cultural Breakdown

You might ask: what does a victim support organisation have to do with shipping software? Everything. The dynamics of power, fear, and silence are universal. Here are three concrete lessons for engineering leaders:

• Treat culture complaints like security vulnerabilities. When a staff member raises a concern, treat it with the same urgency as a reported CVE. Assign an owner, set a timeline, and require a before/after comparison.
• Use blameless postmortems for cultural incidents. Just as we learn from outages without blaming individuals, apply the same methodology to team health. Ask: "What systemic factors allowed this toxic dynamic to persist? " rather than "Who messed up? "
• Instrument your culture with regular, anonymised telemetry, Use pulse surveys (eg., 15Five, Lattice) that measure psychological safety, trust in leadership, and workload. Track trends quarterly, just as you track deployment frequency and change failure rate.

These practices aren't soft skills; they're hard engineering of human systems. And they require the same rigor as building a distributed database.

How to Audit Your Own Organization's Culture for Warning Signs

Don't wait for a news article about your company. Perform a culture audit now. Here's a checklist inspired by the RNZ situation:

• Exit interview patterns: Are leavers citing the same reasons? If you see phrases like "leadership doesn't listen," that's a red alert.
• Silence in meetings: Do only the same three voices dominate,? And that might indicate fear, not agreement
• Responses to reviews: When an external or internal review is published, how does leadership react? Does the response acknowledge gaps or attack the methodology?
• Retention of mid-level managers: they're the canaries. If they're leaving in droves, the culture is likely toxic.

Each of these signals is a monitoring metric for organisational health. If your CTO dashboard doesn't include these, you're flying blind.

The Cost of Toxic Culture: Metrics That Matter

Research by the Society for Human Resource Management (SHRM) estimates that a toxic workplace culture can cost an organisation 34% of an employee's annual salary in turnover costs. For a tech company with an average salary of $150,000, that's $51,000 per departure. If you lose 10 engineers a year due to culture, that's over half a million dollars-not counting lost productivity, institutional knowledge, and hiring costs.

Further, a 2023 study by MIT Sloan found that a toxic culture was 10. 4 times more predictive of turnover than compensation. This aligns with what we see in engineering: people don't leave because of the paycheck; they leave because of broken trust.

The RNZ story is a reminder that even mission-driven organisations with noble purposes can develop toxic cultures. In tech, we often assume our "smart" culture protects us, and it doesn'tEvery organisation needs deliberate maintenance.

Conclusion: Building a Culture That Handles Feedback Without Defensiveness

The most important takeaway from the Victim Support fiasco is that feedback is a feature, not a bug. When your users report a crash, you don't argue with them; you fix the crash. When your employees report a cultural crash, the same logic applies.

Some Victim Support staff 'horrified' by CEO's response to workplace culture concerns - RNZ should be required reading for every tech leader. It shows the cost of ignoring early warnings, the pain of invalidated experiences. And the fragility of trust. If your organisation's CEO would react similarly, you have a leadership bug that needs patching before it escalates into a full outage.

Start today: schedule a skip-level meeting, send an anonymous survey,? Or simply ask your team, "What's one thing I do that makes it harder for you to speak up? " Then listen-not to defend, but to learn, and your runtime depends on it

Frequently Asked Questions

• Q: How can I tell if my company has a toxic culture before it's too late?
  A: Look for patterns: high turnover in specific teams, consistent negative feedback in anonymous surveys. And a tendency for leadership to blame external factors. Also check if incidents (like the RNZ case) are discussed openly or swept under the rug.
• Q: What should a CEO say when confronted with a negative culture review?
  A: Acknowledge the findings, thank participants for their courage, commit to a transparent action plan, and set measurable goals. Avoid disputing methodology or attacking motives. Apologise genuinely if the review reveals harm.
• Q: Can engineering metrics like DORA four keys predict cultural health.
  A: IndirectlyTeams with high deployment frequency and low change failure rate often have good collaboration. But correlation isn't causation. Culture metrics (engagement, psychological safety) are more direct predictors.
• Q: How do I handle a leader who reacts defensively to feedback?
  A: Use data-share anonymous quotes or aggregated survey results. Frame it as a system problem rather than personal criticism. If that fails, consider escalation to HR or board. Or even leaving if the environment is harming your well-being.
• Q: What are the best tools for measuring workplace culture?
  A: Tools like Culture Amp, Peakon, Lattice, and Qualtrics offer robust surveys and analytics. For real-time sentiment, use Officevibe or 15Five. Pair quantitative data with qualitative exit interviews and stay interviews,

What do you think

Have you ever watched a leader dismiss valid concerns only to see the best engineers leave within six months? What specific incident in your career made you realise workplace culture was just as critical as architecture?

If you were on the board of an organisation like Victim Support, what concrete changes would you demand from the CEO to rebuild trust?

Can a defensive leadership response ever be justified,? Or is acknowledging failure always the better path-regardless of the perceived risk to reputation?