For decades, the dominant model of organizational strategy has worked like this: hire external experts, give them access to data and senior interviews, wait for a deliverable. The logic seems reasonable — specialists should produce better analysis than generalists. But the research on strategy execution has quietly dismantled this model, finding that the primary predictor of whether a strategy gets implemented is not the quality of the analysis. It is whether the people responsible for implementation were in the room when the decisions were made.
The Ownership Problem with Expert-Delivered Strategy
When an external team delivers a completed strategy, implementers encounter it as a document. They understand it intellectually. But they did not participate in the trade-off decisions, the failures of competing options, or the moment the group committed to a direction. That absence matters. Psychological ownership research — confirmed across hundreds of thousands of subjects in multiple countries — shows that the mechanism connecting involvement to execution is not motivation in the generic sense. It is the binding of professional identity to the outcome. Strategies co-created by implementers are defended, adapted, and sustained. Strategies delivered to implementers are archived.
This dynamic operates independently of sector. It appears in pharmaceutical brand teams navigating market access, in federal agency leadership managing modernization programmes, in not-for-profit boards designing service model transitions. The mechanism is the same: people who build the strategy own it.
Cognitive Diversity and the Speed Advantage
The ownership argument for co-creation is reinforced by a separate body of research on cognitive diversity — the variance in how individuals perceive, process, and act on new, uncertain information. Reynolds and Lewis's analysis of over 100 executive teams across twelve years, published in Harvard Business Review in 2017, produced a striking result: cognitively diverse teams solved complex problems up to three times faster than homogeneous groups of domain experts.
The mechanism is not that diverse teams are smarter in any aggregate sense. It is that when a homogeneous group encounters a roadblock in a complex environment, every member applies the same failed analytical tools. A cognitively diverse group reframes the problem and applies different heuristics. The variety in the room is the resource.
This has a direct implication for how organizations approach high-stakes strategy sessions. Convening only the internal team — or only the senior leadership tier — is not a neutral design choice. It is a decision to reduce the cognitive resources available to solve the problem, while simultaneously producing a strategy that the wider organization will need to be convinced to execute.
The Safety Prerequisite
There is an important caveat in the diversity research: the benefits of cognitive diversity are not automatic. The same studies that document the speed and quality advantage of diverse teams also identify a failure mode — unmanaged cognitive diversity produces coordination failure, interpersonal conflict, and communication breakdown. The relationship between diversity and performance is an inverted U-shape. More diversity helps, until the conditions for integration break down.
Google's Project Aristotle — a landmark longitudinal study of internal team performance — identified the moderating condition: psychological safety. Teams where members felt safe to take interpersonal risks, surface dissenting views, and admit uncertainty without fear of penalty accounted for 43% of the variance in team performance. Those teams completed projects 19% faster and demonstrated 31% more innovation than teams with lower safety scores.
Psychological safety is not the goal of a well-designed strategic session. It is the prerequisite. Without it, cognitive diversity produces noise. With it, diversity produces strategy. At Mind Meeting Group, building that condition — through deliberate session design, facilitation architecture, and structured participation mechanisms — is not incidental to the process. It is the process.
Convening the Village
Merck's launch of Keytruda, the oncology therapy that became one of the most commercially successful drugs in history, illustrates what happens when an organization correctly identifies the human infrastructure required for a complex challenge. Keytruda's success depended on the widespread adoption of a novel PD-L1 biomarker test — a workflow that pathologists, medical societies, and payers had never used before. Rather than treating this as an analytical problem to be solved by internal teams, Merck convened those actors before launch. They co-created testing workflows and reimbursement pathways. The strategy was built in the room with the people who would have to execute it.
AstraZeneca's launch of Farxiga for heart failure illustrates what happens when the contrast is made visible. Rather than treating payer and physician adoption as a downstream execution problem, AstraZeneca convened cardiology societies, heart failure specialists, and payer medical directors before the launch strategy was finalized. The indication was novel — SGLT2 inhibitors had not previously been associated with heart failure outcomes — which meant the entire prescribing and coverage infrastructure needed to be built simultaneously. By bringing those actors into the strategic process early, AstraZeneca achieved reimbursement and formulary positioning that significantly outpaced comparable launches in the same class.
The difference between these two outcomes is not analytical capability. It is the architecture of who was in the room, and when.