Embedded Creative Functions
Embed support specialists with creators to maintain one shared product vision
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 96%
Embed the people responsible for marketing and other product-shaping functions directly with the creative team, even when formal reporting lines remain separate. Continuous proximity lets specialists absorb the product's emotional intent, vocabulary, audience, and non-obvious differentiators before they make expensive external commitments. Fries saw the opposite when Xbox centralized marketers in another building: the relationship became “us and them,” and an agency produced Halo advertising focused on a man shooting rather than the vistas, music, anticipation, and scale Bungie considered essential. The correction required backing up and reworking the campaign. The model replaces late functional handoffs with sustained shared context, recurring joint reviews, and a common mission, reducing misalignment while allowing specialists to retain their professional expertise.
Origin
Ed Fries developed the approach while running Microsoft's PC game teams and later saw the consequences when Xbox marketing was centralized away from its game developers.
Core principles
- 01Physical and organizational proximity builds shared context
- 02Support functions need continuous exposure to the product vision
- 03A unified mission matters more than reporting-line symmetry
- 04Late handoffs create avoidable creative rework
How to run it
- 1
Find Product-Shaping Functions
Identify specialists whose decisions materially affect how customers understand or experience the product, including marketing, testing, design, and community teams.
Pro tip Prioritize functions that make irreversible or expensive commitments early.
Watch out Embedding every administrative function can create unnecessary coordination overhead.
- 2
Create Daily Proximity
Place representatives with the creative team physically or through persistent working rituals. Formal reporting lines do not need to change.
Pro tip Give embedded specialists access to builds, reviews, and informal discussions.
Watch out Occasional status meetings do not create the same depth of context.
- 3
Define the Shared Vision
Express what the product should make customers feel and which elements communicate that experience.
Pro tip Use concrete scenes, sounds, and customer reactions rather than abstract brand adjectives.
Watch out A superficial genre description can produce technically accurate but emotionally wrong work.
- 4
Review Work Early
Show concepts and drafts to creators before agencies or support teams commit major production resources.
Pro tip Review rough concepts when changes are still inexpensive.
Watch out Waiting for polished deliverables turns alignment into costly rework.
- 5
Correct Organizational Separation
Monitor for adversarial language, delayed communication, and function-specific goals that displace the shared product mission.
Pro tip Use joint outcome metrics rather than isolated functional outputs.
Watch out Centralized reporting structures can silently recreate separation even after teams agree to collaborate.
- 6
Preserve Functional Craft
Keep specialists connected to peers and professional standards while embedding them in the product team.
Pro tip Combine local product ownership with communities of practice across the wider company.
Watch out Embedding should not isolate specialists from developments in their own discipline.
In the wild
After Xbox marketing staff were pulled away from the game teams, an agency returned Halo advertisements centered on a character running and shooting. Bungie's developers believed Halo was about elements such as the quiet before the storm, distant vistas, and its music. Microsoft had to back up and fix the campaign.
→ The costly rework demonstrated why marketing needed continuous exposure to the developers' product vision.
Common mistakes
Treating Marketing as a Final Handoff
A detached team will interpret the product from surface features rather than the creative intent developed over months of work.
Equating Reporting Lines With Collaboration
A specialist can report to a functional leader while still sitting and working closely with a product team.
Describing Vision Too Abstractly
Generic positioning language leaves agencies and support teams to invent their own interpretation of the experience.
Is it for you?
Best for
Creative products whose positioning, presentation, and launch materials must embody a distinctive emotional vision.
Not ideal for
Highly standardized support work that requires little product-specific context or daily creative judgment.
From the transcript
“they they really got separated from the from the teams and um all of a sudden it was sort of an us and them kind…”
“that's the kind of stuff that happened when you know when there isn't this integrated team working together all the way through so that they…”
From the episode
Bungie (with Xbox Co-Founder Ed Fries)
Ed Fries