AAcquired
← All frameworks
Leadership

People, Processes, and Priorities Model

Diagnose a business by how its talent, routines, and priorities reinforce outcomes

Difficulty
Moderate
Time to result
~weeks to results
Steps
5
Confidence
96%

The People, Processes, and Priorities Model treats a business as an interacting operating system rather than a collection of assets. People contribute judgment and skill, processes turn that skill into repeatable work, and priorities decide which outcomes receive attention, resources, and protection. Pixar illustrates the mechanism: talented filmmakers operated within rigorous review, director-development, and quality-control routines, while the organization prioritized releasing only work it considered excellent. Disney therefore gained more than animators or rendering technology. By preserving Pixar as a separate business line while extending John Lasseter and Ed Catmull's leadership across animation, it could learn from the system without immediately dismantling the conditions that made it effective.

Origin

The hosts invoked a business-school model while explaining why Pixar's repeatable creative performance depended on more than its individual employees.

Core principles

  • 01Talent succeeds through supporting systems
  • 02Processes make quality repeatable
  • 03Priorities determine what receives resources and protection
  • 04Acquirers must preserve the interactions among all three
  • 05Leadership transfer can spread a system without merging teams

How to run it

  1. 1

    Map the people

    Identify the individuals and teams whose judgment, expertise, and relationships materially affect outcomes. Record what each contributes that is difficult to replace.

    Pro tip Include emerging talent and developmental pipelines, not only famous leaders.

    Watch out Do not assume star employees operate independently of their environment.

  2. 2

    Map the processes

    Document recurring reviews, milestones, feedback loops, training paths, and decision routines. Connect each process to the quality or reliability it creates.

    Pro tip Study what happens to weak work before customers ever see it.

    Watch out A process map that captures formal procedure but misses real behavior will be misleading.

  3. 3

    Surface the priorities

    Infer priorities from resource allocation and repeated trade-offs rather than slogans. Determine what the organization refuses to sacrifice under pressure.

    Pro tip Look for projects that were delayed, reworked, or stopped to protect quality.

    Watch out Published values may differ from operational priorities.

  4. 4

    Test reinforcement

    Examine whether people, processes, and priorities strengthen one another or create friction. Locate dependencies where changing one element would weaken the whole system.

    Pro tip Ask how a strong performer would fare if moved into the buyer's existing routines.

    Watch out Treating the elements as independent assets can destroy the performance being acquired.

  5. 5

    Preserve and transfer selectively

    Protect the target's functioning system while transferring selected leadership practices or lessons elsewhere. Measure whether both autonomy and organizational learning survive.

    Pro tip Leadership overlap can spread principles while production teams remain separate.

    Watch out Forced cross-pollination can erase the distinctive system before its lessons are understood.

In the wild

Pixar's creative operating system

Pixar developed directors through short films, reviewed work through an internal brain trust, replaced directors when projects failed to meet its standards, and prioritized releasing strong films. Disney kept Pixar's studios and teams separate while Lasseter and Catmull assumed broader animation leadership.

→ Pixar retained its distinctive business while Disney animation gained access to its leadership philosophy and quality discipline.

Hypothetical design-studio acquisition

A buyer discovers that an acquired studio's success comes from senior critique sessions, apprenticeship, and a refusal to accept rushed client work. Rather than scattering the designers across departments, it preserves the studio and selectively adopts its review routines elsewhere. This is a plausible application of the model.

→ The buyer retains the studio's performance while improving quality across adjacent teams.

Common mistakes

Buying talent without its environment

Moving strong people into incompatible routines and incentives can eliminate the conditions that supported their performance.

Copying visible rituals only

A review meeting will not reproduce results if leaders lack the judgment or authority to enforce its decisions.

Confusing slogans with priorities

Real priorities appear in staffing, budgets, deadlines, and the work an organization is willing to reject.

Is it for you?

Best for

It is best for leaders evaluating organizational performance, acquisitions, integrations, or culture-dependent operating systems.

Not ideal for

It is not ideal for problems driven almost entirely by a discrete technical defect or external shock.

From the transcript

“what a business really is is people, processes and um priorities.”

Ben Gilbert · 22:00

“the processes and the priorities had had just as much to do with the the acquisition as the people did in this this case.”

Ben Gilbert · 22:30

“With the exception of leadership.”

Ben Gilbert · 20:00

From the episode

Pixar

→