Principle · Chief of Staff

Essentialism.

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

The Principle

Essentialism is the disciplined pursuit of less, but better. The non-essentialist says yes to everything, tries to do it all, and ends up doing everything poorly. The essentialist says no to almost everything so they can say yes to what matters most, and do that thing excellently.

The trap most founders fall into is mistaking activity for progress. A full calendar, a long to-do list, many open tabs feel like productivity but often produce less forward motion than ruthless focus would. Essentialism is the discipline of refusing optionality. Of cutting commitments, projects, features, clients, and channels that are not directly producing the outcome the business exists to produce. It is a practice, not a preference. It has to be renewed every week because the pressure to add is constant and the pressure to cut is rarely present.

Why It Matters Here

Chief of Staff is the department that protects the founder's focus. Without the Essentialism lens, every incoming request, idea, opportunity, or obligation looks "worth considering." With it, most inputs are correctly filtered as distractions from the one or two things that will actually move the business.

Signals (When to Apply)

A new task, project, or opportunity is being considered mid-week
The weekly priorities list has grown past 3
The founder is feeling overwhelmed or saying "there's too much to do"
A decision meeting is producing "let's do both" conclusions
The team is busier than ever but revenue is flat

How to Apply

Before any yes, run the Essentialist filter: "If I say yes to this, what am I saying no to?" Every yes has an implicit cost. Name those things out loud.
When deciding between options, ask "is this the absolute best use of my time right now, given everything?" If the answer is not a clear yes, it is a no. Probably-yes is a slower no.
Remove as many decisions from the week as possible. Commitments made once do not need to be re-decided daily. Ritualize the repeating decisions (weekly plan, daily briefing, quarterly refresh) so they are not re-made each time.
Protect the single most-important thing with aggressive calendar defense. Do not let meetings, interruptions, or "quick asks" eat the time allocated to the essential work.
When cutting is hard, make it easier by reframing: you are not abandoning the good options. You are choosing the best option. The good options remain available for a future quarter where they might become the best.

Examples

Applied well A founder's Monday weekly plan has three priorities: (1) ship V1 of the new product, (2) respond to a partnership inquiry, (3) post daily on LinkedIn. Mid-week, a coach suggests adding a podcast guest appearance. The founder applies the filter: if yes to podcast, what no? The answer is "less focus on V1 and one fewer LinkedIn post." V1 is revenue-critical. The podcast is not. The answer: "add to parking lot for a future week, not this one." Essential decisions protect the lever.

Misapplied The same founder says yes to the podcast, yes to a mid-week coffee with a potential partner, yes to reviewing a friend's pitch deck, yes to writing an article. By Friday, no progress has been made on V1, the partnership inquiry has not been called back, and LinkedIn has one post for the week. Each yes was reasonable in isolation. The cumulative effect is a lost week.

When to Break It

When the week's essential work is in a waiting state (blocked on external input, pending review) and additional optionality can be pursued without stealing from the essential. Use the gap deliberately.
When a non-essential item has a time-sensitive component that will expire (a specific opportunity window, an event with a fixed date). Evaluate the expiration cost explicitly. Sometimes the non-essential is actually essential because of timing.
During pre-committed periods (retreats, intentional exploration phases) where breadth is the goal rather than depth. Name the period explicitly so the framework adapts.