Concept
Less But Better
Less but better is the principle, borrowed by Greg McKeown from industrial designer Dieter Rams, that real progress comes from concentrating finite energy on a few commitments done with depth rather than spreading it thinly across many.
Rams used "less, but better" to describe products stripped of everything that didn't serve the person using them. In Essentialism, McKeown applies the same test to a working life. The goal isn't minimalism, and doing less isn't the point in itself. The point is arithmetic. Energy, attention and time are finite. Split them across twenty commitments and each one gets a sliver, so none moves far enough to matter. A crowded calendar feels productive because every item gets touched, but touching something is not the same as progress. Fewer commitments let each one cross the threshold where it actually changes something: a project ships, a skill becomes usable, a relationship deepens. The hard part is that every commitment you drop was a genuinely good option. Less but better asks you to give up good things so that a few can become great.
A real-life example
A product manager is running seven initiatives at once: a dashboard redesign, two integrations, a pricing test, onboarding emails, a hiring loop and an internal wiki. After a quarter, all seven are "in progress" and nothing has launched. She ranks them by impact. She keeps two, hands off three and openly parks the last two. Six weeks later the redesign and the pricing test both ship. That is more delivered value than the whole previous quarter of motion produced.
How to use it
- 1List every commitment currently taking your time, then ask of each one: if I weren't already doing this, would I say yes to it today?
- 2Keep the two or three with the highest impact. Explicitly drop, delegate or pause the rest, and tell the people affected.
- 3Block calendar time for the survivors before new requests arrive, and run the same test again whenever something new asks for a yes.