There is a moment in the life of every high-performing organization when the team that built the business is no longer quite the team the business needs.
The instincts that drove early growth, the bias for speed over process, the culture of getting it done: these are genuine assets. But at a certain point in an organization’s trajectory, those same instincts begin to create friction that slows things down, creates execution gaps, and limits what becomes possible next.
That was the honest starting point when Perpetual convened this leadership team in May 2026 at a remote luxury property chosen deliberately for its distance from the operational environment. Our client is a North American regional operation within one of the world’s leading global luxury groups. Over a compressed window, the business had undergone a significant revenue transformation, growing from a strong regional player into an organization of materially greater scale, complexity, and strategic importance to the global parent. The leadership team had driven that growth themselves. They were proud of it. They were also, in some ways, still running the organization with the mindset and operating rhythms of the business they had built, not the business they were now responsible for leading.
The question Perpetual was brought in to help answer was not whether this was a good team. It clearly was. The question was whether it was operating at the right level for what came next.
building on evidence, not assumption
The program did not begin when the group gathered for the residential offsite. It began six weeks earlier, with 14 structured one-on-one leadership interviews conducted by Perpetual’s facilitation team and a full deployment of the t3® Diagnostic Survey across the senior team. Every interview followed the same framework: current team dynamics, individual leadership strengths and development edges, what was working operationally, and what the team needed to build or change to perform at the next level.
By the time the group arrived, Perpetual had a detailed picture of where this team was genuinely strong, where the development gaps were, and what the four days together needed to accomplish. Nothing was introduced in the room that had not been grounded in data from the team’s own experience.
The overall t3® score came in at 8.26, above the high-performing threshold of 8.2 and a genuinely rare result in Perpetual’s global benchmarking data. Fewer than 15% of teams assessed at this size and seniority level reach that threshold in an initial diagnostic. But averages can flatter, and in this case they did. The attribute breakdown told a more instructive story.
Two findings shaped the program design more than any others.
The agile execution score, the lowest of the six attributes, pointed directly to a feedback culture that had settled into polite coexistence. In a team of experienced, high-performing professionals, the path of least resistance was to agree in the room and work around the issue outside it. The interviews had surfaced this pattern repeatedly: people described feeling reluctant to raise challenges directly, unsure whether candor would be received well, and experienced in routing around difficult conversations rather than through them. No one described this as dysfunction. They described it as how things worked.
The strategy cascade gap was equally significant. The leadership team’s own clarity score was 9.08. Across the broader organization, that number dropped to 7.73. That 1.35-point gap sits precisely at the layer where strategy has to be translated into daily priorities and decisions. At this stage of growth, that is not a communication problem. It is an execution risk.
four days away from the noise
The program opened on the first evening with a timed multi-challenge exercise. Groups worked in parallel, making decisions under pressure, managing incomplete information, and coordinating across sub-teams with different mandates.
The after-action review that followed set the tone for the entire program. Participants showed genuine persistence under pressure and strong individual contribution. But communication between sub-teams broke down when it mattered most. Risk assessment was bypassed in the rush to action. The overall mission failed even as individual sub-teams reported success on their specific tasks. The group had optimized for the wrong level.
Most tellingly: when asked to name the most important team in their professional lives, only around 10% of the room named the group of leaders sitting in front of them. The others named their own functional teams, the teams they were accountable to above, or teams from earlier in their careers.
That gap between the team people felt loyal to and the team they were actually sitting in became the central thread of everything that followed. The senior leadership group of any organization is, or should be, the primary team: the one whose collective performance matters more than any individual’s functional results. Reaching that level of genuine collective accountability requires something most high-performing people find difficult: prioritizing the group outcome over personal KPI protection and being willing to challenge each other directly rather than routing around the uncomfortable conversations.
the science of how teams make decisions
A Predictive Index team dynamics session on day two gave the group a language for something most of them had been experiencing without being able to name it. Fourteen leaders. Fourteen different cognitive profiles. The team’s aggregate profile showed high strategic drive, strong analytical depth, and above-average independence. It also showed limited natural patience for process, a low collective tolerance for ambiguity at the implementation stage, and a pattern of dominant voices in open discussion that made it structurally difficult for the team’s quieter contributors to be heard.
The PI data landed with an unusual degree of acceptance. Leaders who had been privately attributing their experience of the team to interpersonal friction or organizational politics found themselves looking at a structural explanation. The issue was not that certain voices were too loud or too quiet. The issue was that the team had no agreed protocol for ensuring all voices contributed, and no cultural expectation that the best idea in the room might come from someone who needed more than thirty seconds to formulate it.
That insight directly shaped the program’s subsequent facilitation design. The exercises that followed were structured to surface the quieter voices by design, requiring structured input before open discussion and using named contribution formats rather than open-floor conversation.
when process determines outcome
A survival scenario exercise on day three made the feedback culture gap visible with hard data, not opinion.
Two teams faced the same challenge. Team 1 moved fast, reached consensus quickly, and scored well by a conventional measure of efficiency. Team 2 was slower, messier, and occasionally uncomfortable. But Team 2 was the better-performing team by every measure that mattered: every individual improved their personal outcome through the collaborative process, while Team 1’s faster approach had actually produced an outcome that was worse than several members’ individual starting positions.
The difference was not effort or intelligence. It was process. Team 2 began by defining roles before engaging with the problem, used a structured input framework that required every voice before reaching any conclusion, and protected quieter contributors from being talked over. Team 1 defaulted to its dominant voices, moved at the pace of the most confident individual, and missed critical information that slower contributors held.
By the time the debrief concluded, the group was not debating whether a feedback and process gap existed. They had watched it cost them in real time. The question had shifted from whether it was real to what they were going to do about it.
the conversation nobody had been having
The afternoon of day three surfaced something that the diagnostic interviews had raised repeatedly but had never been addressed collectively.
This leadership team operates at the intersection of two distinct organizational cultures. The North American regional business brings a direct, action-oriented operating style: lead with the recommendation, move to decision, execute. The global parent organization operates within a European leadership framework that expects a different structure: establish the theoretical and contextual basis first, demonstrate that the full landscape has been mapped, then arrive at the recommendation.
When those two approaches meet across a reporting line without any shared awareness of the gap, the friction that results gets attributed to the wrong things. Relationships are blamed. Personalities are blamed. The cultural misread goes unexamined.
Erin Meyer’s Culture Map framework gave the group a structured and non-personal language for what had previously been experienced as interpersonal friction. The session involved direct application to real scenarios the team had encountered, not generic illustration. Leaders named specific situations in which the communication mismatch had created confusion or eroded trust upward, and the group worked through what a different approach might have produced.
The outcome was not a resolution. Cultural operating differences between a regional team and a global parent are not resolved in a single session. But the team left with a shared framework, a common vocabulary, and for the first time a collective awareness of the dynamic rather than a set of individual and contradictory interpretations of it.
structured feedback at scale
The program closed on the final afternoon with a structured peer feedback process. Every leader in the room gave and received specific, behavioral feedback from every other person, using a situation-behavior-impact format that had been introduced and practiced during the program.
This is one of the most consistently high-stakes moments in any leadership team program. Offering candid feedback to a peer or a functional leader in the room, in a culture where feedback had previously been withheld or routed around, requires a different kind of psychological safety than the team had previously operated with.
The energy in that session was demonstrably different from the first day. The group that had arrived calibrated to professional courtesy was having direct, specific, substantive conversations about each other’s leadership in real time. Feedback was given without softening the behavioral observation. It was received without defensiveness. Several participants described it afterward as the first time they had received feedback in a professional setting that felt genuinely useful rather than diplomatically managed.
Each leader left the program with a named behavioral commitment they had stated publicly and were prepared to be held to. The commitments were specific, observable, and grounded in the feedback they had received. They were not intentions or aspirations. They were agreements.
what the team committed to
Three organizational priorities were framed as non-negotiable in the weeks following the program. Each had a named owner, a defined timeline, and a specific indicator of what successful delivery would look like.
Post-program survey data confirmed the program had landed.
Qualitative responses consistently pointed to three elements: Perpetual’s frameworks as something participants were applying within days of leaving, the exercises as genuine analogies for the real dynamics of their organization rather than abstract simulations, and the structure of the program as well-calibrated throughout: building trust and relational foundation before introducing diagnostic or evaluative material.
the 18-month view
The residential offsite in May was Module 1 of a three-module program arc. It was designed as a foundation, not an event.
Module 2, planned for Q4 2026, will bring the group back together to audit what has held and what has not since May. The design will move from the frameworks introduced in the first module to their application against live organizational decisions. The team will work on real strategic challenges using the process disciplines they have committed to and will build the muscle for productive conflict that the May program identified as the team’s most significant undeveloped capacity.
Module 3, in Q1 2027, will shift to relational depth, executive presence at the next level of organizational complexity, and year-two ambition-setting. It will include a full t3® remeasure against the May baseline, providing the team with a data-driven view of what has genuinely moved and where the next development edge sits.
Running alongside both modules will be a cascade program extending the same diagnostic rigor and behavioral frameworks to functional leaders at the one and two levels below the senior team. The strategy cascade gap identified in the May diagnostic cannot be closed by the leadership team working harder on messaging. It requires investment in the leaders who are responsible for translating that strategy into daily decisions across the organization.
This team built something significant. The work in May was about ensuring the way they lead is commensurate with what they have built, and genuinely ready for what they intend to build next.
Nigel Robinson | nigel@beperpetual.com | beperpetual.com
about perpetual:
Perpetual is a team effectiveness and organizational design consultancy working with leadership teams across consumer goods and beyond. Our t3® framework and diagnostic are trusted by organizations committed to building high-performance cultures that execute.
Perpetual: • Executive Search • Leadership Development • Advisory • beperpetual.com
