Assess the structural conditions of your team — not your leadership style. Get a scored architecture and concrete structural interventions.
Every other framework (Edmondson, Google's Project Aristotle) ends at behavioral recommendations for leaders. This tool starts where they stop: the structural conditions that make safety possible regardless of who is in the room.
This assessment evaluates six architectural dimensions — meeting design, decision rights, failure protocols, dissent channels, information access, and accountability structure. For each weak dimension it returns a specific structural intervention, not a behavioral coaching tip.
How meetings are structured determines what can be said in them. Agenda sequence, who speaks first, and whether silence is treated as agreement are architectural decisions — not cultural ones.
When your team discusses a risky or uncertain project, who typically speaks first in the meeting?
Research consistently shows that whoever speaks first anchors the group's position — making it structurally harder for dissent to follow.
Does your team have a formal agenda slot — before accomplishments are reviewed — specifically for surfacing what is not working?
When a team member raises a concern and there is no immediate response, how is that silence treated?
Ambiguous decision authority is one of the most reliable predictors of silence. When people do not know who can say yes or no, they default to saying nothing — because speaking up carries risk without corresponding influence.
Does every team member know, for their area of work, which decisions they can make independently versus which require escalation?
When a team member raises a concern that falls outside their formal decision authority, is there a defined channel for that concern to be heard and acted on?
When a decision is reversed after being delegated, how is that reversal communicated?
What actually happens when something fails determines whether people will ever tell the truth about risk. Leaders who say "failure is okay" but respond to it with blame, urgent escalation, or public post-mortems that feel like trials have built a system where failure is penalized regardless of their stated intent.
Does your team have a defined process for reviewing failures that separates learning from accountability?
A learning process asks: what in the system produced this outcome? An accountability process asks: who is responsible? Both are legitimate, but conflating them prevents honest learning.
When a team member makes a significant error, what is the default first response from the leader?
Does leadership publicly model failure acknowledgment — sharing their own mistakes with the team as learning moments?
Dissent requires a structural home. Teams with high psychological safety do not have leaders who are personally easy to challenge — they have structures that make challenge the expected, normal, low-risk thing to do.
Does your team have a mechanism — other than speaking up in a meeting — through which a team member can formally register disagreement with a decision?
When dissent is raised and ultimately overruled, how is the outcome communicated to the person who raised it?
Are there people on your team who have never expressed a concern, asked a challenging question, or disagreed with a direction in a group setting?
People cannot speak meaningfully about things they have no information about. Selective information flow creates structural silence — not because people are unwilling to speak, but because they lack the context to know what to say or whether it is already known.
Does every team member have access to the strategic rationale behind the decisions that directly affect their work?
When your team is performing poorly on a key metric, how quickly does the team (not just the leader) have access to that information?
Does your team know what decisions are currently being made above them that will affect their work in the next 90 days?
Accountability without psychological safety produces compliance theater. Psychological safety without accountability produces learned helplessness. The architecture question is: how is accountability applied, and does the way it is applied make future honesty more or less likely?
When a team member underperforms, is the accountability conversation focused on the behavior and its impact, or on the person's competence or character?
Is the standard of performance applied consistently across the team, or does it vary based on seniority, relationships, or perceived status?
Does the team have a shared, documented definition of what "good performance" looks like — against which all members are evaluated?
Book a free 30-minute Capability Readiness Review. No prep required.