Constraint-Driven Performance Architecture
Remove expensive freedoms to make the core experience dramatically faster
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 94%
Start by defining the single experience that must feel exceptional, then identify which forms of flexibility make that experience expensive. Romero describes how id Software prioritized fluid, high-speed 3D movement and constrained players to one plane of rotation: no looking up, down, or tilting sideways. That smaller computational problem let the team avoid much of the normal 3D math and draw a visually complex scene quickly on limited hardware. The mechanism is not simply to cut features. It is to remove degrees of freedom that do not serve the chosen experience, then redesign the underlying architecture around the simpler problem. The result can outperform more general systems precisely because it attempts less and spends its resources on what users notice most.
Origin
Extracted from The Tim Ferriss Show, where John Romero explains id Software's early approach to fluid 3D rendering.
Core principles
- 01Optimize for one defining user experience
- 02Treat constraints as design tools rather than deficiencies
- 03Remove computational work users do not need
- 04Use deep system knowledge to spend limited resources deliberately
How to run it
- 1
Choose the defining experience
State the user experience the system must deliver better than alternatives. id Software chose smooth, high-speed movement through a 3D maze.
Pro tip Use an observable experience such as response speed or ease of control, not a vague ambition.
Watch out Multiple competing priorities weaken the constraint decisions that follow.
- 2
Map the expensive freedoms
List the movements, calculations, features, or edge cases that consume resources. Separate those that serve the defining experience from those that do not.
Watch out Do not remove a freedom merely because it is technically difficult.
- 3
Constrain the problem
Deliberately eliminate the nonessential freedoms so the system has a smaller problem to solve. Make the trade-off explicit to the team.
Pro tip Prefer a constraint that users barely notice but the system benefits from substantially.
Watch out A hidden constraint can become a product defect if users expect the removed capability.
- 4
Architect for the reduced space
Build the implementation around the constrained problem rather than carrying the cost of a general-purpose solution. Apply detailed knowledge of the underlying system to the new design.
- 5
Validate the experience
Test whether the constraint produces a dramatic improvement in the chosen experience. Reconsider any restriction that creates more user friction than performance value.
Pro tip Judge the result from the user's perspective, not only through technical benchmarks.
In the wild
For its early 3D work, id Software restricted movement so players could rotate on one plane but could not look up, look down, or tilt sideways. That reduced the calculations needed to render the scene and supported smooth, high-speed movement through the maze.
→ The team produced a fluid 3D experience that Romero says people had not seen before.
Common mistakes
Optimizing everything
A general solution preserves costly freedoms and can prevent the defining experience from becoming exceptional.
Cutting user-critical freedom
A constraint fails when it removes behavior users need rather than behavior peripheral to the product's focus.
Is it for you?
Best for
It is best for products with one clear performance dimension that matters more than full flexibility.
Not ideal for
It is not ideal when users genuinely require the freedoms that would be removed.
From the transcript
“Our focus was on trying to make that happen, the speed was the focus for us, getting 3D moving quickly became — at least at…”
“So by reducing your motion that way, it reduced the kind of computations that we needed to do.”
From the episode
#681: Doom Legend John Romero — The Path to Prolific Innovation and Making 130+ Games, How to Find the Soul of the Work, Audacious Ambition, and Building in Monk Mode
John Romero