Culture-Preserving Creative Integration
Protect a studio's distinctive culture while adding only the support it needs
- Difficulty
- Expert
- Time to result
- ~ongoing to results
- Steps
- 6
- Confidence
- 97%
Treat the acquired team's culture as a productive asset rather than an obstacle to standardization. First observe how people collaborate, make decisions, arrange their environment, and express their values through the product. Distinguish practices that must integrate—such as access to platform infrastructure—from parent-company conventions that merely feel normal. Preserve the latter differences whenever possible. Bungie rejected Microsoft's status-oriented private offices because its programmers and artists depended on open, immediate collaboration. Fries later concluded that preserving company culture was generally preferable, even though selective co-location helped unite Bungie's Chicago and California teams. The mechanism is contextual integration: add scale and support around the studio while protecting the identity, working relationships, and creative signals that made it valuable.
Origin
Ed Fries derived the model from integrating Bungie and comparing its culture with Ensemble Studios, two successful teams whose values were almost opposites.
Core principles
- 01Strong cultures can succeed even when their values differ
- 02A creative team's working environment shapes its products
- 03Preserve uniqueness instead of imposing the parent company's defaults
- 04Integrate selectively where coordination creates genuine value
How to run it
- 1
Observe the Existing Culture
Study how the team communicates, arranges its workspace, resolves disagreements, and produces work before changing anything.
Pro tip Ask which practices employees believe directly affect product quality.
Watch out Corporate norms can look universally correct when they are only locally familiar.
- 2
Identify Product-Culture Links
Connect specific cultural practices to collaboration speed, talent fit, creative decisions, and the resulting customer experience.
Pro tip Look for practices that persist across offices or company eras.
Watch out Do not protect every habit merely because it is traditional.
- 3
Define Essential Integration
List the systems and relationships that must connect to the parent organization for the acquisition to succeed.
Pro tip Keep the list narrow and tied to concrete outcomes.
Watch out Labeling preferences as requirements leads to unnecessary assimilation.
- 4
Preserve Distinctive Practices
Retain the team's effective workspace, values, communication patterns, and identity wherever they do not block essential integration.
Pro tip Let the acquired team redesign imposed environments that interfere with its workflow.
Watch out Symbolic changes can communicate cultural domination even when leaders intend no harm.
- 5
Integrate Selectively
Co-locate or connect teams only where shared work creates a clear benefit, as Microsoft did when bringing Bungie's two development groups together.
Pro tip Explain the product-specific reason for each integration decision.
Watch out Relocation can destroy relationships and increase attrition if the benefit is speculative.
- 6
Monitor Cultural Health
Track retention, collaboration quality, conflict patterns, and product coherence after integration. Reverse changes that weaken the creative system.
Pro tip Include acquired-team leaders in every review of integration effects.
Watch out Financial performance may lag behind cultural damage and should not be the only signal.
In the wild
Microsoft prepared a new wing filled with private offices, which represented status and a desirable working environment inside Microsoft. Bungie's team rejected it and requested low-walled cubicles in an open bay so programmers and artists could communicate across the room. Microsoft removed the walls and accommodated Bungie's preferred workflow.
→ Bungie retained a collaborative spatial pattern that remained part of its culture in later offices.
Fries compared Bungie's hardcore identity with Ensemble Studios' family-oriented culture. Their value systems were nearly opposite, yet both teams produced successful games. The comparison showed that cultural strength and internal fit mattered more than adherence to one supposedly correct set of values.
→ Fries rejected the idea that every successful creative team must share the same culture.
Common mistakes
Standardizing Before Observing
Immediate adoption of parent-company practices can dismantle the collaboration system that created the acquisition's value.
Confusing Difference With Dysfunction
An unfamiliar workspace or set of values may be highly effective for the acquired team's creative process.
Preserving Culture Without Coordination
Autonomy still requires deliberate interfaces with teams responsible for shared products, platforms, and market delivery.
Is it for you?
Best for
Leaders integrating studios, design teams, research groups, or other creativity-dependent acquisitions.
Not ideal for
Turnarounds where the acquired culture is demonstrably dysfunctional or incompatible with essential legal and safety controls.
From the transcript
“I think I think the more you can do to to preserve the culture of the company uh the better, uh, because I think that's…”
“It's it's like having a culture is what matters. It's not which culture you have that matters”
“that culture ends up just expressing itself in the product.”
From the episode
Bungie (with Xbox Co-Founder Ed Fries)
Ed Fries