Designing for the Bottom
Designing systems for the lowest-capability user produces resilience for everyone.
"If your system requires geniuses, it will fail with mortals."
What is Designing for the Bottom? Designing systems for the lowest-capability user produces resilience for everyone. Robust org systems work with average performers, not just stars.
Curb cuts: built for wheelchairs, used by parents, delivery workers, travelers.
Robust org systems work with average performers, not just stars.
Stress-test processes against the median user, not the ideal one.
Use the model. Pick the move.
Designing systems for the lowest-capability user produces resilience for everyone. You've just seen this: Curb cuts: built for wheelchairs, used by parents, delivery workers, travelers. Which lever does the model recommend?
Pick a lever. There are no neutral ones — every incentive funds a behavior somewhere.
Pick a reaction to Designing for the Bottom
One tap. We'll point you at the most useful next surface based on how this hits.
The full taxonomy entry
Every concept in the Atlas uses the same structure — so Designing for the Bottom can be compared, recombined, and cited like an element on a periodic table.
- Business
- Leadership
- Government
- Healthcare
- Education
- Sales
- Marketing
- AI
- Negotiation
- Media
- Public Policy
- Relationships
- Where in our org would Designing for the Bottom most often show up unnoticed?
- Which metric, ritual, or contract clause quietly rewards Designing for the Bottom?
- If we removed every payoff for Designing for the Bottom, what behavior would replace it?
- Who benefits when Designing for the Bottom persists — and who pays the cost?
- People defend the status quo using the language of designing for the bottom.
- 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.
Every Atlas entry is a node in a knowledge graph. See the related rail below to follow the connections.
See Designing for the Bottom through 2 lenses
Each layer of the Incentives OS reframes this concept with its own thinkers, vocabulary, and diagnostic question.
Do you actually know Designing for the Bottom?
Three quick questions. Result is saved into your review streak — come back when the term is due to lock it in.
Which best describes Designing for the Bottom?
Worked example, counter-example & concept map
On-demand AI analysis grounded in the Lab's research. Cached on your device after first run.
When you encounter Designing for the Bottom, 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 →Picked for you, from the Atlas
Ranked by shared learning paths, overlapping chips, and what you've saved.
The minimum energy needed to start a reaction; same idea for starting habits or initiatives.
Combining substances to create a new material stronger than its parts.
A single constraint limits the throughput of an entire system.
A system's throughput is constrained by its single slowest step.
Small visible disorders signal that bigger ones will be tolerated.
Adding manpower to a late software project makes it later.
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.
More definitions to follow
Every term in the Atlas connects to a dozen others. Pick any of these and see where it takes you.
Negative behavior of outgroup members is attributed to character; positive behavior to situational factors.
Designing processes from scratch around AI capability.
Evaluating an argument's logic based on whether you agree with the conclusion.
Working memory has limits.
Reducing cognitive biases through training, structure, and process.
Two things may be equivalent in effect but not in form.
Their failure: character. Our failure: situation.
Without active design, incentives decay toward gameable proxies.
Hospital group-purchasing and opaque contracting inflate device costs far above marginal cost.
Work expands to fill the time available for it.
Assume the opposite of what you want to prove. Derive a contradiction. The opposite must be false.
Preferences that depend on others' outcomes — fairness, reciprocity, altruism, inequity aversion.