"After project fails, we typically would investigate. And suddenly we all knew, oh, we raised that concern, but we said the schedule was unrealistic... Where was all that knowledge before the failure?"

Welcome to Part 3 of our deep dive into S2.E10 of the CI3 Fireside Chat: Speak-Up Cultures: Courageous Conversations That Change Projects with Roula Eid, Sara ElFeky and Adejisola B H Atib. In Part 1, we shattered the illusion of the "open door" policy, and in Part 2, we broke down the mechanics of delivering hard truths. Today, we confront what happens when organizations treat culture like a corporate checklist rather than a living, breathing ecosystem.

We are tackling the "Iceberg of Ignorance," examining why everyone suddenly becomes a prophet after a project fails, defining the fine line between dissent and disruption, and learning how to rebuild a team's trust after it has been broken.

1. The Meaningless Checkbox

Psychological safety has become the ultimate corporate buzzword. Companies proudly declare they have it, weaving the phrase into mission statements and HR onboarding materials. But as Roula Eid pointed out, declaring you have psychological safety is entirely different from actually testing it. For many organizations, it is simply a box to be checked off by management.

True psychological safety is not a gift that a leader bestows upon a team; it is a shared, two-way accountability matrix. It requires the leader's ego to leave the room, forcing them to humbly admit when they do not have the answers. Simultaneously, it requires the team to hold the space, supporting the leader's vulnerability rather than exploiting it. If psychological safety is only expected from the bottom up, the culture is fundamentally broken.

"Psychological safety is not something an organization can declare or a leader can simply tick off a checklist. It has to be experienced in practice. And it works both ways. For leaders, that means putting ego aside, accepting that we may be wrong, and having the humility to say, ‘I don’t know." - Roula Eid

Insights 🔎:

  • Corporate declarations of "psychological safety" are often performative checkboxes that mask an underlying culture of fear and compliance.
  • Safety cannot exist if a leader is incapable of publicly admitting fault or demonstrating vulnerability.
  • Building trust is not a one-time event; it is a daily nutritional requirement for team communication that must be continuously maintained.

Actions 🛠️:

  • In your next team meeting, intentionally highlight a recent misstep or knowledge gap of your own to model that it is safe to be wrong.
  • Co-create a "Communication Protocol" with your team, establishing specific, agreed-upon behaviors for how disagreements will be handled moving forward.

Quick Win ✅:

  • Stop using the phrase "psychological safety" in your team meetings; replace it with the phrase "open debate without fear" to force clear behavioral expectations.

2. Disagreeing vs. Being Disagreeable

When leaders finally attempt to open the floor and invite dissenting opinions, they often encounter a new problem: professionals who weaponize the new freedom.  Adejisola B H Atiba astutely observed that creating a safe space for dialogue does not mean abandoning organizational standards or accountability.

Some individuals will take the opportunity to disagree purely for the sake of disagreeing, creating disruption rather than value. True psychological safety means creating room for productive, outcome-driven debate, not establishing a free-for-all where every standard operating procedure is endlessly and needlessly debated.

"Psychological safety does not mean lowering standards or removing accountability. It means creating the conditions where people can challenge what we think we know, speak openly about what they see, and still hold one another accountable." - Adejisola Atiba

Insights 🔎:

  • Psychological safety is not an excuse to lower performance standards or bypass organizational accountability.
  • Chronic contrarians who disagree simply to hear their own voices actively degrade the safety and efficiency of the broader team.
  • Healthy dissent is rooted in a desire to improve the collective outcome, whereas toxic dissent is rooted in ego and the desire to be "right".

Actions 🛠️️:

  • Establish a "Solution Requirement" for your meetings: if a team member raises a critical objection to a plan, they must concurrently propose at least one alternative path.
  • Pull aside a team member who frequently plays the "devil's advocate" unproductively, and privately coach them on how to frame their objections collaboratively.

Quick Win ✅:

  • When someone challenges an idea in a meeting today, immediately follow up by asking, "That is a great catch, how would you recommend we solve it?"

3. The Iceberg of Ignorance

There is a deeply frustrating phenomenon in complex project management. When a massive initiative inevitably crashes and burns, the subsequent post-mortem investigation usually reveals a startling truth: almost everyone on the ground floor knew it was going to fail months ago.

During the panel, I highlighted this exact reality. You will hear engineers, analysts, and project managers suddenly say, "I've been mentioning this for months". If the knowledge was there, why did it never reach the steering committee? Because bad news gets filtered, massaged, and weakened as it travels up the hierarchy toward executive power. Middle management often smooths out the rough edges to protect their own image, creating an "Iceberg of Ignorance" where the C-Suite only sees the safe, sanitized tip of the project's actual risk profile.

"After a project fails, suddenly everyone remembers the warnings. ‘We raised that concern.’ ‘We said the schedule was unrealistic.’ ‘I’ve been saying this for months.’ Somehow, everybody knew after the failure. The real question is: where was all that knowledge before the failure? - Dr. Charles Igwe

Insights 🔎:

  • Frontline employees almost always possess the critical risk data required to save a failing project, but lack the safe channels to escalate it.
  • Middle management frequently sanitizes critical warnings before passing them to executives to artificially inflate their own perceived competence.
  • If executive leadership is constantly surprised by project failures, they have structurally isolated themselves from the operational truth.

Actions 🛠️:

  • Implement a "Skip-Level" risk assessment on your largest project, pulling data directly from the execution team rather than relying solely on summarized manager reports.
  • Audit your project dashboards: look for vague, emotionally comforting language (e.g., "moderately delayed") that might be masking a critical failure.

Quick Win ✅:

  • Ask your frontline team today: "What is the one risk on this project we are all privately worried about but haven't formally documented?"

4. Rebuilding the Broken Trust

What happens when the damage has already been done? Suppose your organization promised an open culture, an employee bravely spoke up, and they were subsequently punished or marginalized for their honesty. The trust across the entire team instantly evaporates.

Sara ElFeky, leaning on her agile delivery background, offered a masterclass in fire brigade response. You cannot rebuild trust by ignoring the elephant in the room. You must conduct a ruthless, fact-based retrospective focusing entirely on the reality and impact of what happened. Most importantly, leadership must possess the maturity to publicly admit fault. If a leader wrongly punished a dissenting voice, they must openly acknowledge the mistake, explain why it happened, and detail exactly what steps are being taken to ensure the environment actually becomes safe again.

We have to confront the reality of what happened and understand its impact. If we got something wrong, we have to be willing to say, ‘We were wrong.’ Only then can we decide what needs to change and how we move forward." - Sara ElFeky

Insights 🔎:

  • Sweeping a leadership failure under the rug permanently destroys team trust; trust can only be rebuilt through radical transparency.
  • Agile retrospective frameworks (what went well, what went wrong, how we fix it) are incredibly effective tools for repairing emotional and cultural damage.
  • A leader who publicly apologizes for a misstep actively builds more organizational credibility than a leader who pretends the misstep never occurred.

Actions 🛠️:

  • If you recently shut down a team member's idea too harshly, publicly revisit the idea in your next meeting and apologize for your initial defensive reaction.
  • Schedule a dedicated "Culture Retrospective" for your team, entirely separate from project delivery, to explicitly discuss what communication habits need fixing.

Quick Win ✅:

  • Adopt a strict "blame the process, not the person" mindset for the rest of the week, verbally reinforcing this rule every time an error occurs.

5. Closing

We spend millions of dollars trying to build corporate cultures, but the true test of your culture isn't on a poster, it is the unspoken reality of what your team decides to hide from you today. If your team is chronically silent, the failure belongs to the room you have built. You must actively dismantle the iceberg of ignorance before it sinks your next major initiative.

👇 Is your team hiding the truth to survive your leadership? Stop relying on superficial engagement surveys. Run your current professional strategy through the Competence Trap Wheel to expose your executive blind spots and discover if you are the bottleneck to honesty: https://competencetrapwheel.ci3pro.ca/

Next up in Part 4: We will conclude this series by turning the mirror entirely on ourselves, discussing the responsibility of the "middle manager," and answering the ultimate question: if we take away all the metrics, how do you actually measure trust?