Most leadership-team assessments measure relationships — trust, conflict, cohesion, the conditions for a good team. Leadership Architecture measures something different: the structure of how decisions are made. A team can score well on a relational diagnostic and still stall, because cohesion and decision-system health are not the same thing.
You ran a team assessment. It came back — fine. Trust is solid, the team genuinely likes each other, the facilitator was excellent. And yet six months later the same decisions still stall, the same issues still escalate to you, and execution still lags the plan. When a healthy team assessment and unhealthy execution coexist, the assessment measured the wrong layer.
It almost certainly measured the relationships — and most leadership-team diagnostics do, very well. But relationships are not the only thing that determines whether a team executes. The other half is structural: who actually holds which decisions, when something escalates, how decision load is distributed. That is a different measurement, and most team tools simply don't take it.
The most widely used leadership-team assessments share a focus: how the team relates and functions as a group. They are good instruments, and they measure things that genuinely matter.
The Five Behaviors, built on Patrick Lencioni's work, measures a pyramid of team behaviors — vulnerability-based Trust, then Conflict, Commitment, Accountability, and Results. The 6 Team Conditions and its Team Diagnostic Survey, developed by Ruth Wageman and the late J. Richard Hackman at Harvard, measure the six enabling conditions that research links to team effectiveness — a Real Team, the Right People, a Compelling Purpose, Sound Structure, a Supportive Context, and Team Coaching. Leadership Circle's BRITE assesses team dynamics — how energy flows across a team — and pairs with its individual Leadership Circle Profile.
Put simply, this family answers a relational question: how well does this group function as a team? Trust, conflict norms, shared purpose, cohesion, the conditions for working well together. When those are the problem, these tools find it.
What none of them measures directly is the structure of how decisions are made. Not whether the team trusts each other, but whether it is unambiguous who decides what. Not whether conflict is healthy, but whether there are defined thresholds for what escalates and what is resolved locally. Not whether the team is cohesive, but whether decision load is distributed or quietly concentrated on one person.
The closest any of them comes is the 6 Team Conditions' "Sound Structure" — and it is worth being precise here, because it is a real overlap. But "Sound Structure" in that model is about team design: the team's size, composition, norms of conduct, and task design. It is not a reading of the decision architecture — the configuration of authority, escalation pathways, and governance through which the team coordinates decisions. A team can have sound design conditions and still have a broken decision system.
Here is the gap that surprises people: high trust does not tell you who decides. You can have a leadership team that trusts each other completely and still watch a decision sit for three weeks — not because anyone is avoiding conflict, but because two leaders both believe it is their call and nothing in the structure resolves the overlap.
Relational diagnostics read that as a healthy team, because relationally it is. The stall is structural: undefined authority (Decision Clarity), overlapping ownership (Role Ownership & Accountability), no escalation threshold (Escalation Discipline). Patrick Lencioni's Five Dysfunctions of a Team — trust, conflict, commitment, accountability, results — describes how a team relates and behaves. Wageman, Nadler, and Hackman's research on senior leadership teams shows how much effectiveness depends on design conditions like the right people and a clear, compelling direction. Both are essential, and neither sets out to map who holds authority over which decision. That ambiguity is invisible to a trust-and-cohesion assessment. It is exactly what a structural diagnostic is built to surface.
Three relational/behavioral instruments and one structural one. They answer different questions — which is why they're complementary, not competing.
Built on Lencioni's model. Measures the behavioral foundations of a cohesive team, starting from vulnerability-based trust. Strongest where the problem is interpersonal.
Wageman & Hackman's research-grade survey. Measures Real Team, Right People, Compelling Purpose, Sound Structure, Supportive Context, and Coaching. The most structural of the relational set — at the level of team design, not the decision system.
Assesses the generative and disruptive dynamics that shape how a team works together, and connects to the individual Leadership Circle Profile. A relationship-and-dynamics lens.
Measures decision authority, role accountability, escalation discipline, leadership load balance, and execution alignment — the structure of how decisions are coordinated, against the demand the team actually carries.
When the symptoms are interpersonal: low trust, avoided or unproductive conflict, a newly formed or recently fractured team, unclear shared purpose. If people aren't working well together, a relational diagnostic names why — and it's the right place to start.
When the symptoms are decision-related: choices stall, settled decisions reopen, cross-functional calls escalate to the founder, decision load piles on one or two people. These persist regardless of how much the team likes each other — they trace to the decision structure, which is what Leadership Architecture measures.
Often. Relationships and structure are different layers, and a serious team-effectiveness effort usually touches both. The sequence that works: diagnose which layer your most expensive symptom lives in, fix that first, and don't assume a relational fix will repair a structural fault — or the reverse.
You don't have to guess. Look at your last handful of frustrating moments and ask what kind of problem each one really was:
The CEO Fit Diagnostic gives you that structural read in about five minutes — enough to tell whether your decision system is the bottleneck before you invest in any team program.
No — it measures a different layer. Relational diagnostics like the Five Behaviors, the 6 Team Conditions, and BRITE assess how your team relates and functions: trust, conflict, cohesion, and the conditions for effectiveness. Leadership Architecture measures the decision system: who holds which decisions, how they escalate, and how decision load is distributed. They are complementary, not alternatives.
Because the assessment most likely measured relationships, not the decision system. A team can have high trust and genuine cohesion and still stall, reopen decisions, or route everything to the founder — because decision authority is unclear, escalation has no thresholds, or decision load is concentrated. Those are structural faults a relational diagnostic is not built to detect.
Team effectiveness is about how well people work together — trust, communication, shared purpose, the conditions for a good team. Decision-system health is about how decisions are structured — clarity of authority, role accountability, escalation discipline, leadership load balance, and execution alignment. The first is relational; the second is structural. A team can be strong on one and weak on the other.
Partly. The 6 Team Conditions (Wageman and Hackman) includes "Sound Structure" as one enabling condition — making it the most structural of the relational diagnostics. But that condition is about team design: size, composition, norms, and task. It does not measure the decision architecture specifically — who holds final authority over which decisions, when something escalates, and how decision load is balanced. That is what Leadership Architecture measures.
Match the diagnostic to the symptom. If the pain is interpersonal — low trust, avoided conflict, a new or fractured team — start with a relational diagnostic. If the pain is decision-related — choices stall, decisions reopen, everything escalates to one person — start with a structural one. The CEO Fit gives you a 5-minute structural read to tell which problem you actually have.
Sources: Lencioni, P. (2002). The Five Dysfunctions of a Team. Jossey-Bass. · Wageman, R., Nadler, D. & Hackman, J. R. (2008). Senior Leadership Teams. Harvard Business Review Press.
Five minutes. No account. A structural read on whether your decision system — not your team's relationships — is the bottleneck.