Pixar Brain Trust
Build collective understanding through candid peer review of work in progress.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 97%
The Pixar Brain Trust is a peer-review system for turning lessons from individual projects into shared organizational intelligence. A small group of senior practitioners examines work in progress and discusses recurring problems, successful choices, and the reasons behind both. The group does not act as an executive approval committee, so the project owner retains creative responsibility. Its output is a collective understanding that travels across teams and projects, preventing each new effort from beginning with no memory of prior work. The mechanism is reusable beyond filmmaking: bring experienced peers together early, examine incomplete work candidly, capture causal lessons, and make those lessons available to everyone facing similar decisions.
Origin
The episode attributes the method to Pixar president Ed Catmull, who created a Brain Trust after directors repeatedly encountered the same story and character problems across different films. It was later transferred to Disney Animation.
Core principles
- 01Review work to improve it, not to exercise authority.
- 02Share lessons across projects instead of repeatedly starting from zero.
- 03Discuss why something works or fails, not merely whether it is good.
- 04Preserve ownership with the person responsible for the work.
How to run it
- 1
Form the peer group
Select a small group of experienced practitioners who can recognize recurring problems and explain their reasoning.
Pro tip Include people with experience across several projects rather than only the current one.
Watch out Do not turn the group into another layer of management approval.
- 2
Review unfinished work
Screen or demonstrate work while there is still time to change its direction. Give reviewers enough context to understand the intended outcome.
Pro tip Review at comparable milestones across projects so patterns become visible.
Watch out Waiting until completion reduces the review to criticism rather than useful intervention.
- 3
Diagnose causes
Identify what works, what does not, and why. Look for structural patterns that have appeared in previous projects.
Pro tip Distinguish symptoms from the underlying narrative, strategic, or execution problem.
Watch out A list of preferences without causal reasoning does not build collective knowledge.
- 4
Share learning across projects
Carry the resulting understanding into every relevant team rather than leaving it with the reviewed project.
Pro tip Record recurring lessons in a concise shared context resource.
Watch out If insights remain inside one meeting, another team will solve the same problem again.
- 5
Preserve owner autonomy
Let the responsible creator decide how to address the feedback. The Brain Trust informs judgment rather than replacing it.
Pro tip Frame feedback as problems and observations before prescribing solutions.
Watch out Top-down mandates can suppress candor and weaken ownership.
In the wild
Senior creatives screen work in progress together and share an understanding of recurring story-structure and character-motivation problems. Lessons discovered on one film become available to teams working on later films rather than disappearing when production ends.
→ Creative knowledge compounds across films instead of every production starting from zero.
A company convenes senior designers, researchers, and product leads every two weeks to review unfinished onboarding flows. The group identifies recurring sources of user confusion and records the underlying principles, while each product owner chooses the final implementation.
→ Teams stop recreating the same onboarding mistakes and improve designs earlier.
Common mistakes
Turning review into approval
If senior participants approve or reject the work, the system becomes a hierarchy rather than a shared-learning mechanism.
Giving notes without reasons
Surface-level preferences do not explain the mechanism behind success or failure and therefore cannot transfer reliably.
Keeping lessons inside one project
The value disappears when insights are not shared with other teams confronting similar problems.
Is it for you?
Best for
It is best for organizations running multiple creative or product projects whose lessons should compound across teams.
Not ideal for
It is not ideal for situations requiring formal compliance approval or a single accountable expert decision.
From the transcript
“It was really to share context to build collective understanding of what worked, what didn't, and why across every film simultaneously.”
“It wasn't to get notes from the top. It wasn't to approve or reject anything.”
“And so what Ed Catmull decided was they needed something called a brain trust.”
From the episode
The Real Reason Your AI Content Is Average (It's Not Your Prompts)