Essentialism: Greg McKeown's Disciplined Pursuit of Less

Essentialism: Greg McKeown's Disciplined Pursuit of Less
Greg McKeown's Disciplined Pursuit of Less

Greg McKeown's Essentialism (Crown Business, 2014) argues that the undisciplined pursuit of more (more commitments, more projects, more meetings) produces less actual output than the disciplined pursuit of less. The essentialist asks 'Is this the very most important thing I could be doing right now?' and accepts the trade-off of doing fewer things in order to do the right things well.

2026-02-19 6 min read

The Essentialist Framework

Greg McKeown published Essentialism: The Disciplined Pursuit of Less (Crown Business, 2014), drawing on research into high-performing executives and his consulting work with companies including Apple, Google, and LinkedIn. The book’s core argument: the non-essentialist mindset (responding to whatever is most urgent, saying yes to avoid disappointment, treating all opportunities as roughly equal) systematically produces less impact than the essentialist mindset, which asks “Is this the very most important thing I could be doing right now?” before every commitment.

McKeown identifies three realities that the essentialist accepts and the non-essentialist ignores. First: individual choice is real. Even in constrained environments, we always have a choice about where our energy goes, and failing to make that choice explicitly is itself a choice, usually in favor of whatever is most urgent rather than most important. Second: almost everything is noise. Only a tiny fraction of all possible activities, commitments, and projects will produce disproportionate results; most will produce trivial results or net negative results when their opportunity cost is counted. Third: trade-offs are real. Choosing to do one thing is always a choice not to do something else, and the non-essentialist’s pretense that everything can be done simultaneously results in doing everything inadequately.

Less but better

McKeown's core formula: the essentialist does less (takes on fewer commitments, attends fewer meetings, pursues fewer projects) but executes what they do take on with more depth, focus, and quality. The output is greater contribution from fewer inputs, not less contribution from fewer inputs.

McKeown, G. (2014). Essentialism: The Disciplined Pursuit of Less. Crown Business.

Explore, Eliminate, Execute

McKeown structures the essentialist practice across three phases:

Explore. Before committing, the essentialist creates space to explore options broadly rather than reacting to whatever arrives first. This requires protecting time for reflection, research, and judgment. The non-essentialist defaults to the first reasonable option; the essentialist asks whether there is a better option, including the option of doing nothing. McKeown argues that the more successful a person becomes, the more options they face, and the more critical it becomes to invest time in evaluating them before committing.
Eliminate. Identifying what is essential requires actively removing what is not. McKeown proposes a test: “If I wasn’t already doing this, how hard would I work to start?” Work that doesn’t clear a high bar for active re-adoption should be eliminated. Practically, this means learning to say no to good opportunities, not just bad ones. The essentialist’s difficulty is not resisting obviously bad requests; it is declining good requests to protect time and energy for excellent ones.
Execute. Once the essential few things have been identified, the essentialist removes obstacles to executing them: building routines, creating systems, and clearing the path so that doing the important work requires less energy than navigating friction. McKeown argues that most execution problems are design problems: the environment wasn’t set up to make the essential work easy, so the non-essential work wins by default.

The 90 Percent Rule

McKeown proposes a practical decision tool called the 90 percent rule: when evaluating any opportunity, score it on the single most important criterion for that type of decision. If it does not score at least 90 out of 100 on that criterion, decline it. The rule is designed to force explicit evaluation and prevent the accumulation of 70-percent opportunities: options that are good enough to justify acceptance but not good enough to justify the time and attention they consume.

The practical difficulty is that the rule requires defining the criterion in advance, which requires knowing what matters most, which requires the exploration phase. The 90 percent rule is not a substitute for judgment; it is a structure that forces judgment to be made explicitly and documented rather than defaulted into “yes” under social pressure or in the absence of a clear reason to decline.

Frequently Asked Questions

How does essentialism differ from simply having priorities?

Having priorities and practicing essentialism are related but not the same. Most knowledge workers have a nominal priority list, the things they are 'supposed to' focus on. Essentialism requires that the priority list actually govern behavior: that lower-priority activities are actively declined rather than added to the list of things being worked on simultaneously. The difference is in how decisions are made when new requests arrive. The person with priorities may still say yes to requests that seem reasonable even if they don't serve those priorities, because the priorities are beliefs, not constraints. The essentialist makes the priority list a constraint: new commitments that don't serve the essential must be declined, regardless of their apparent reasonableness. This requires being willing to disappoint people, which is where most priority lists fail in practice.

Is essentialism compatible with collaborative, team-based work environments?

Essentialism creates tension in team environments where the expectation is broad availability and responsiveness to all team needs. McKeown acknowledges this tension and argues that the solution is clarity: making your essential priorities explicit so that colleagues understand what you are working on and why, rather than being opaque about declining requests. An essentialist's 'no' should come with an explanation of what is being protected. 'I can't take that on right now because I'm committed to X for the next two weeks' is more functional than a bare refusal. McKeown also argues that teams benefit from essentialist members because clear priorities enable better delegation and coordination. The failure mode of non-essentialist teams is everyone trying to do everything, resulting in no one doing anything excellently.

How does essentialism apply to daily scheduling, not just long-term commitments?

McKeown's framework applies at every time horizon. At the daily level, essentialism means identifying the one or two things that would make today successful and protecting time for those before the day is consumed by reactive tasks, meetings, and requests. The non-essentialist's day is structured by what arrives first and loudest; the essentialist's day is structured by what matters most. The practical implementation is what McKeown calls 'protecting the asset': scheduling the most important work first, when cognitive resources are highest, rather than letting it be crowded out by administrative tasks. This connects to the broader time management literature on morning routines, peak performance windows, and energy management: the essentialist's scheduling principle is 'the most important things get the best time, not the leftover time.'