Skip to main content
The Incentives Lab
Mental Models · Strategy

Projects Not People

Organize around outcomes and projects rather than fixed org-chart roles.

"Reorgs are theater. Project assignments are reality."

Quick answer

What is Projects Not People? Organize around outcomes and projects rather than fixed org-chart roles. Talent fluidity in fast-changing markets.

In the wild

Lean and agile teams formed around bets, dissolved on completion.

Why it matters in the room

Talent fluidity in fast-changing markets.

Counter-move

Refresh project portfolios quarterly; let roles follow work, not the other way around.

Visual · Pattern
Projects Not People — a recurring shape in how people decide.
Live example · Apply Projects Not People

Use the model. Pick the move.

Organize around outcomes and projects rather than fixed org-chart roles. You've just seen this: Lean and agile teams formed around bets, dissolved on completion. Which lever does the model recommend?

● Live

Pick a lever. There are no neutral ones — every incentive funds a behavior somewhere.

How does this land?

Pick a reaction to Projects Not People

One tap. We'll point you at the most useful next surface based on how this hits.

Human Behavior Element™ · HBE Spec

The full taxonomy entry

Every concept in the Atlas uses the same structure — so Projects Not People can be compared, recombined, and cited like an element on a periodic table.

About the standard →
M
PN
HBT-M4556
Official name
Projects Not People
Mental Models · Strategy
Identity
HBT ID
HBT-M4556
Symbol
PN
Official name
Projects Not People
Synonyms
Strategy
Keywords
Mental Models, Strategy, human behavior, incentive design
Version
v1.0
Last updated
Maintained by The Incentives Lab
Classification
Kingdom
Cognition
Domain
Frameworks
Family
Mental Model
Class
Strategy
Element
Projects Not People
Definition
Scientific
Organize around outcomes and projects rather than fixed org-chart roles.
Plain-English
Organize around outcomes and projects rather than fixed org-chart roles.
Feynman
Reorgs are theater. Project assignments are reality.
Core principle
Organize around outcomes and projects rather than fixed org-chart roles.
One-sentence summary
Talent fluidity in fast-changing markets.
Mechanisms
Psychological
Organize around outcomes and projects rather than fixed org-chart roles.
Behavioral econ.
Talent fluidity in fast-changing markets.
Neurological
Reward, threat, and salience circuits bias attention toward the cue.
Evolutionary
Heuristics that paid off in ancestral environments now misfire in modern systems.
Sociological
Group norms and status incentives reinforce the pattern across a team.
Computational
Models trained on biased human signals will replicate and amplify the pattern.
Systems thinking
Feedback loops between metrics, incentives, and behavior lock the pattern in place.
Signals & signature
Inputs (activators)
Lean and agile teams formed around bets, dissolved on completion.
Outputs (observable)
Talent fluidity in fast-changing markets.
Behavioral signature
You see Projects Not People when the explanation for a decision sounds reasonable but the outcome keeps repeating.
Behavioral molecules
Often combines with related Atlas entries — see the rail below.
Pathways · before
A goal, metric, or contract clause makes the behavior rational locally.
Pathways · after
Locally rational choices accumulate into a systemic distortion.
Domains where it shows up
  • Business
  • Leadership
  • Government
  • Healthcare
  • Education
  • Sales
  • Marketing
  • AI
  • Negotiation
  • Media
  • Public Policy
  • Relationships
Examples
Everyday
Lean and agile teams formed around bets, dissolved on completion.
Modern
Talent fluidity in fast-changing markets.
Historical
A pattern repeatedly documented since the foundational behavioral science literature on mental model.
Famous experiments
See the References block — primary papers in the Atlas link out to the original studies.
Design principles
How to leverage
Talent fluidity in fast-changing markets.
How to reduce
Refresh project portfolios quarterly; let roles follow work, not the other way around.
How to redesign
Refresh project portfolios quarterly; let roles follow work, not the other way around.
The Perverse Incentive Lens™
How it's exploited
Organizations weaponize projects not people — sometimes deliberately, often by accident — when metrics reward the symptom rather than the outcome.
Common perverse incentives
Volume metrics, short review windows, bonus cliffs, and contracts that pay on activity rather than impact.
Failure modes
When Projects Not People dominates, teams optimize for the dashboard while the real outcome quietly degrades.
Incentive redesign
Refresh project portfolios quarterly; let roles follow work, not the other way around.
Ethical considerations
Don't engineer projects not people into customers, employees, or citizens as a manipulation tactic — design for informed choice instead.
Diagnostic questions
  • Where in our org would Projects Not People most often show up unnoticed?
  • Which metric, ritual, or contract clause quietly rewards Projects Not People?
  • If we removed every payoff for Projects Not People, what behavior would replace it?
  • Who benefits when Projects Not People persists — and who pays the cost?
Organizational warning signs
Metrics
A KPI is hit while the underlying outcome stalls or worsens.
Behaviors
People route around the rule rather than challenge it.
Language
'That's just how we do it here.' / 'The system requires it.'
Culture
Naming the pattern is treated as disloyalty.
Red flags
  • People defend the status quo using the language of projects not people.
  • Decisions cluster around the easiest narrative rather than the strongest evidence.
  • New data changes the slide deck but not the decision.
  • Anyone naming the pattern is treated as the problem.
Intervention playbook
Immediate
Make the perverse payoff visible to the people creating it.
30-day
Run a small pilot that pays for the outcome, not the proxy.
Long-term
Rewrite the comp plan, contract, or ritual so the right behavior becomes the easy behavior.
AI considerations
Detect
Audit training data and reward signals for the same pattern this element describes.
Avoid amplifying
Don't optimize models on metrics that already encode the perverse incentive.
Counteract
Use the model to surface where the pattern is most active, then redesign the incentive — not the model.
Measurement
Metrics
Outcome-to-proxy ratio over time.
Assessment
The Incentives Lab III Diagnostic.
Survey
Calibrated pulse questions on rules vs. outcomes.
Behavioral signals
Where people work around the system.
Observational
Where the dashboard and the lived experience disagree.
Scientific evidence
Evidence grade
Synthesized from the behavioral science literature; see Atlas references.
Replication
Tracked in the Atlas as primary, replicated, or contested.
Intervention confidence
Moderate — patterns generalize, mechanisms vary by context.
Research consensus
Broad agreement on the pattern; ongoing debate on boundary conditions.
Known limitations
Local context, culture, and incentive structure all change the strength of the effect.
Open questions
How does Projects Not People interact with AI-mediated decisions at scale?
References
Meta-analyses
Tracked in the Atlas registry.
Seminal authors
Kahneman, Tversky, Thaler, Ariely, Cialdini, Ostrom, Simon — and the field they built.
Cross references

Every Atlas entry is a node in a knowledge graph. See the related rail below to follow the connections.

Disciplinary layers

See Projects Not People through 2 lenses

Each layer of the Incentives OS reframes this concept with its own thinkers, vocabulary, and diagnostic question.

Test yourself · 60 seconds

Do you actually know Projects Not People?

Three quick questions. Result is saved into your review streak — come back when the term is due to lock it in.

Question 1 of 3Score: 0/3

Which best describes Projects Not People?

Go deeper

Worked example, counter-example & concept map

On-demand AI analysis grounded in the Lab's research. Cached on your device after first run.

How this lands in you

Your nervous system has a region for this.

Primary region
Prefrontal Cortex

When you encounter Projects Not People, your prefrontal cortex has to do extra work to override the automatic response — and that override budget is finite.

Executive control, planning, impulse override, working memory, System 2. First thing to go offline under stress, fatigue, or low blood sugar. Why your 4pm decisions are worse than your 9am ones.

See Prefrontal in the Brain Atlas →
You may also like

Picked for you, from the Atlas

Ranked by shared learning paths, overlapping chips, and what you've saved.

Share this rabbit-hole

Send the card, not just the link

A pre-rendered social card with the title, eyebrow, and URL. Copy the link, post it anywhere, or download the SVG for slides.

Keep pulling the thread

More definitions to follow

Every term in the Atlas connects to a dozen others. Pick any of these and see where it takes you.

Keep exploring the Atlas
← Browse the full Atlas