Case Study Two · Confidential Client Application · Concentration
The Balance That Concealed a Dependency
A senior leadership team that appeared evenly matched at the aggregate level.
- Organization
- Independent organizational change consultancy
- Participants
- Three-member senior leadership team
- Context
- Established leadership group with significant experience working together
- Engagement
- Faria-Lequay Shift Pattern Index™ followed by facilitated Team Shift Analysis
Identifying characteristics have been generalized to protect client confidentiality.
Presenting situation
The team had a strong track record and no obvious performance problem. When difficult situations arose, the group tended to move through the issue rather than spend extended time unpacking how each leader was experiencing the change. That approach supported productivity. It also meant difficult conversations could be postponed, concerns could be absorbed rather than raised, and differences in response could be interpreted as personality rather than as different change needs.
Aggregate balance did not equal distributed resilience
At the team level, planning capability represented 50.4 percent of combined change energy and execution represented 49.6 percent. On the surface, the profile was unusually balanced.
Planning capability
Execution capability
Finding 1: New-direction capacity was concentrated
The three executives brought genuinely different profiles. One led with Activator, one held Analyzer and Regulator at equal strength, and one led with Envisioner with Explorer close behind. The aggregate view therefore looked well covered. The distribution underneath that average told a different story. Envisioner and Explorer capacity was disproportionately concentrated in one executive. When that leader was not available, the team retained its capacity to analyze, move, and stabilize, but its range for generating new direction dropped substantially. The team therefore carried a dependency that the balanced average did not show.
Finding 2: Interpersonal steadiness was stronger than internal processing
Harmonizer was the team’s highest-scoring pattern, while Processor was among the lowest. That composition was consistent with the leaders’ reported tendency to maintain steadiness while leaving some difficult experiences unarticulated.
A balanced team average can conceal concentration risk when one capability depends too heavily on one person.
Turning a habit into a decision
The facilitated debrief translated the combined profile into practical team decisions. The group introduced a more deliberate pause at the beginning of change work, before momentum made re-examination more difficult. Ownership of vision-setting work was made more explicit so that the leader with the strongest Envisioner and Explorer capacity could be deployed intentionally rather than relied on implicitly. The team also made the naming of what was not working a recurring leadership practice rather than something that depended on an individual choosing to raise a difficult issue. Particular attention was placed on the handoff between planning and execution, where a team with near-equal aggregate strength can still lose continuity.
Observed value
Participants reported that the analysis was consistent with experiences they had recognized informally but had not previously named as a team-composition issue. The organization subsequently discussed broader application of the instrument within its leadership work. The case illustrates why aggregate balance should not be treated as sufficient evidence of team resilience. A capability can be present in the average and still remain operationally vulnerable if it is concentrated in one person.
Key insightBalance describes the total. Resilience depends on how that total is distributed across people.
Next Case
Overconcentration
When the Strengths That Built the Company Became the Constraint
Every founder led with vision or exploration, the strengths that built the company. Regulation and sequencing were thin as the organization scaled. The response was to build structure around the founders rather than ask them to become different people.
Read the Full Case →Reactive teams absorb change. Intentional teams move through it.
See what your team carries, and what it may need to hold deliberately.