Essentialism
Leaders & Managers
DropRegion · Lessons from Essentialism · Greg McKeown

What Leaders and Managers Can Learn from Essentialism

Taking on every reasonable-sounding request from other teams is the specific trap Essentialism names, and it's an especially common one for leaders who feel obligated to be maximally helpful.

01 · The Book in One Minute

The whole book, compressed

01Distinguishing The Vital Few Team
02Saying No Gracefully To Protect
03Eliminating Nonessential Commitments Already
04Building Routines That Make Executing

This edition works through 4 core lessons — take them one at a time, not all at once.

02 · Where Are You Now?

What's different for your conditions

Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.

You face a constant stream of individually reasonable requests from other teams and stakeholders that collectively dilute your team's focus from the few priorities that actually matter.
Saying no to a plausible request can feel like poor collaboration, even when accepting it would cost more in diluted team focus than the request itself is worth.
Your team looks to you to model what actually deserves protected attention, which makes your own choices about what to say yes to unusually visible.

0 of 3 selected

03 · Core Lessons

The core lessons, applied to you

Distinguishing The Vital Few Team

Distinguishing the vital few team priorities from the trivial many

The idea

Most requests a team receives are not actually vital to its core mandate, even though each one looks individually reasonable coming from a legitimate stakeholder.

What it looks like

A leader accepts several plausible but non-core requests simultaneously, and the team's actual core priority suffers from the diluted attention.

Try this

List your team's current active commitments, and identify which one or two are actually vital to its core mandate this quarter.

Saying No Gracefully To Protect

Saying no gracefully to protect the vital few

The idea

Using a high bar, a clear yes or otherwise a no, for new requests protects the attention your team's vital few priorities actually need, and declining gracefully preserves the relationship for a future request that might actually be a clear yes.

What it looks like

A leader accepts a stakeholder's request mainly to avoid an awkward conversation, and the request consumes team capacity that the team's actual priority needed.

Try this

The next time a request arrives that isn't a clear yes for your team's priorities, practice declining it gracefully rather than accepting to avoid friction.

Eliminating Nonessential Commitments Already

Eliminating nonessential commitments already on the team's plate

The idea

Commitments made in the past that no longer serve the team's current vital few need to be actively removed, not just deprioritized, since they continue to compete for the same limited team capacity.

Try this

Identify one existing team commitment that no longer serves current priorities, and take the concrete step to end it this month.

Building Routines That Make Executing

Building routines that make executing the essential nearly effortless

The idea

Relying on willpower to choose the vital few over the merely urgent each week is unsustainable; building a routine (a weekly priority review with your team) makes the choice close to automatic.

When the clusters compete

Being a good organizational citizen and protecting your team's focus on the vital few aren't opposites — a team that's excellent at its actual core mandate is usually a better organizational citizen than one spread thin across many requests.

04 · Choose Your Priority

Name one thing, honestly

Name one current team commitment that isn't a clear yes for its actual vital few. What would it take to end it this quarter?


Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.

05 · Put It Into Practice

The practices from this edition

List your team's current active commitments, and identify which one or two are actually vital to its core mandate this quarter.
The next time a request arrives that isn't a clear yes for your team's priorities, practice declining it gracefully rather than accepting to avoid friction.
Identify one existing team commitment that no longer serves current priorities, and take the concrete step to end it this month.

0 of 3 selected

06 · Small Experiment

Run this for seven days

Identify one existing team commitment that no longer serves current priorities, and take the concrete step to end it this month.

07 · Remember This
If you remember only 4 things
01Distinguishing The Vital Few Team. Most requests a team receives are not actually vital to its core mandate, even though each one looks individually reasonable coming from a legitimate stakeholder.
02Saying No Gracefully To Protect. Using a high bar, a clear yes or otherwise a no, for new requests protects the attention your team's vital few priorities actually need, and declining gracefully preserves the relationship for a future request that might actually be a clear yes.
03Eliminating Nonessential Commitments Already. Commitments made in the past that no longer serve the team's current vital few need to be actively removed, not just deprioritized, since they continue to compete for the same limited team capacity.
04Building Routines That Make Executing. Relying on willpower to choose the vital few over the merely urgent each week is unsustainable; building a routine (a weekly priority review with your team) makes the choice close to automatic.
08 · Your Next Step

What will you do differently because you read this?

Read McKeown's book directly for the fuller framework and additional exercises.