One-Page Simplification
Edit complexity down until the essential idea fits on one page.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 96%
One-Page Simplification is Nick Jones's practice of reducing complicated work to its essential meaning. He says dyslexia makes complexity confusing for him, so he asks for material on one sheet rather than four and spends time editing down work from designers, chefs, and technology teams. The mechanism is selective compression: identify the decision or idea, remove information that does not alter it, translate specialist language, and test whether another person can readily understand the result. The one-page constraint is a forcing function rather than an absolute rule. It exposes unclear thinking and makes the remaining message easier to discuss. The method should preserve material facts; simplicity becomes counterproductive when it hides qualifications, risks, or necessary operating detail.
Origin
Jones says his dyslexia requires him to look at things differently and simplify them. He developed a preference for one-page explanations and applies the same editing instinct across Soho House functions.
Core principles
- 01Complexity can conceal the essential point.
- 02A shorter explanation is easier for people to understand and use.
- 03Simplification requires editing, not merely summarising.
- 04The method can be applied across functions, from design to technology.
How to run it
- 1
Name the essential point
Write the central idea, decision, or desired outcome in one sentence. If that is impossible, the material is not yet clear enough to compress.
Pro tip Use a verb that shows what the reader should understand or decide.
Watch out Do not choose a neat headline that changes the underlying claim.
- 2
Separate signal from detail
Keep facts that affect the decision and move supporting detail out of the main explanation. Remove repetition and decorative complexity.
Pro tip Ask whether deleting each item would alter the reader's decision.
Watch out Retain important constraints, uncertainty, and risk.
- 3
Translate specialist language
Replace jargon and long constructions with words that the intended reader will understand. Preserve the original meaning while shortening the route to it.
Pro tip Prefer one concrete example over several abstract descriptions.
Watch out Plain language must not imply certainty that the source does not support.
- 4
Apply the one-page constraint
Arrange the essential point, evidence, and requested action on one page. Use the space limit to force another editing pass.
Pro tip Make the requested decision visually easy to locate.
Watch out Treat one page as a review surface, not a substitute for required documentation.
- 5
Test for understanding
Give the page to someone close to the intended audience and ask what it means and what happens next. Edit any part they cannot explain back accurately.
Pro tip Test comprehension rather than asking whether they like it.
In the wild
Jones says designers, chefs, and technology teams can all overcomplicate their work. He responds by editing the material down and simplifying it until people can understand it, rather than accepting complexity as an unavoidable feature of specialist work.
→ The resulting idea is easier for colleagues and members to understand.
A team condenses a long venue proposal into one page containing the member problem, proposed experience, key cost, main risk, and decision required. Detailed forecasts remain attached, but the decision surface no longer requires readers to decode four competing narratives.
→ Decision-makers can discuss the same essential trade-offs without losing access to the evidence.
Common mistakes
Deleting necessary qualifications
A short explanation is not useful if it hides uncertainty, risk, or facts that would change the decision.
Compressing before finding the point
Cutting words without first identifying the essential idea can produce a shorter but equally confused document.
Keeping jargon for status
Specialist language that the audience cannot decode works against the understanding Jones is trying to create.
Is it for you?
Best for
Leaders and teams reviewing dense plans, designs, or technical material that must support a clear decision.
Not ideal for
Safety-critical, legal, or technical records where removing required detail would make the material misleading or incomplete.
From the transcript
“i have to simplify everything all the time”
“i want something on one sheet of paper”
“when you do simplify things people understand it”
From the episode
Soho House Founder: How I Built The World’s Most Exclusive Club: Nick Jones