Question the Requirements
Strip inherited rules down to the few outcomes that must remain true
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 97%
Start with a process that feels more complicated than its outcome warrants. Map each requirement, then ask whether it is truly legal, regulatory, technical, or simply an artifact added over time. Translate the genuine requirements into a tiny set of plain-language outcomes and rebuild the process around them. Tesla applied this reasoning to car financing: dozens of loan pages became four essential commitments about price, interest, payment, and duration. The redesigned flow reduced a 64-click purchase to 10 clicks. The mechanism is not indiscriminate deletion; it is disciplined separation of necessary constraints from inherited protection and habit, followed by a simpler delivery system that preserves what must be true.
Origin
McNeill describes applying first-principles simplification at Tesla in 2015, when the company needed to sell cars online without the costly store footprint of larger automakers.
Core principles
- 01Inherited requirements are not automatically real constraints
- 02The few essential outcomes should define the process
- 03Removing friction can create a structural cost advantage
- 04Simplicity requires difficult work up front
How to run it
- 1
Map the friction
Trace the customer or operating process and quantify its avoidable burden, such as clicks, pages, delays, or handoffs.
Pro tip Use the customer's full journey rather than an internal department's slice.
- 2
Interrogate every requirement
Ask who imposed each requirement and whether it is legally, regulatorily, or technically necessary.
Pro tip Require evidence for a constraint instead of accepting institutional memory.
Watch out Do not remove regulated or safety-critical controls on assumption alone.
- 3
Define what must be true
Express the irreducible customer agreement or product outcome in a few clear statements.
Pro tip If the definition needs a long explanation, simplify it again.
- 4
Rebuild around the core
Design the shortest process that delivers the essential outcomes while preserving validated constraints.
Watch out Do not merely digitize the old process and call it simpler.
- 5
Find an enabling partner
When incumbents reject the redesign, keep searching for a partner willing to validate and implement it.
Pro tip A series of rejections may reflect convention rather than impossibility.
- 6
Measure the reduction
Compare the new process with the baseline and confirm that customer friction and cost actually fell.
In the wild
Tesla examined the loan paperwork that drove much of a 64-click car purchase. The team found that many paragraphs protected banks rather than satisfying legal or regulatory requirements. It reduced the agreement to four essentials—price, interest rate, payment, and term—then found US Bank willing to support the new structure.
→ The online car-purchase flow fell from 64 clicks to 10.
Common mistakes
Treating every old rule as mandatory
Requirements often accumulate through habit and defensive drafting. Verify their source before designing around them.
Deleting without preserving the outcome
Simplification still has to retain the few commitments, controls, or results that genuinely matter.
Is it for you?
Best for
Leaders redesigning an established process burdened by inherited rules and handoffs.
Not ideal for
Situations where verified safety or regulatory controls cannot be changed without specialist approval.
From the transcript
“Like, are all of these paragraphs legally required?”
“What are you really agreeing to in an auto loan?”
“all of a sudden we had taken a 64-click process to buy a car down to 10.”
From the episode
Episode 541: Jon McNeill: Why "Less" and "Simple" are the Smartest Growth Strategies
Jon McNeill