Adam Grant: From Time Management to Attention Management

Adam Grant is an organizational psychologist at the Wharton School. He has written six books (most recently Hidden Potential, 2023), runs the WorkLife podcast for TED, and is one of the most-cited voices in business writing on collaboration, motivation, and the design of work.

On Tim Ferriss's podcast in December 2019, he reframed how to think about a packed schedule in a way that has been quoted constantly since:

"I'm bad at time management. I've gotten good at attention management."

Here is the quote in full context, what it means, and why it matters for protecting your lunch hour.

The Quote

From The Tim Ferriss Show, Episode #404: "Adam Grant — The Man Who Does Everything," December 7, 2019, transcript notes:

"I'm bad at time management, but I've gotten good at attention management."

He elaborated: stop optimizing how many hours you spend on things. Start optimizing what you give your attention to in the first place.

"Instead of focusing so hard on time management, focus on the substance of the projects you choose."

And:

"If I'm choosing people and projects that matter to me, it doesn't matter how long they take."

What "Attention Management" Means

Three implications worth unpacking.

1. The unit of analysis is the project, not the calendar slot

Time management asks "how do I fit X into my day?" Attention management asks "is X worth my attention at all?" The two questions sound similar. They are not.

Time management produces calendar Tetris — squeezing more obligations into fewer minutes. Attention management produces a much shorter list of obligations that get all the minutes they need.

Grant's claim is that most productivity advice optimizes the wrong layer. You cannot make a calendar with 30 meetings work, no matter how good your time management is. You can only choose to have fewer meetings about more important things.

2. The cost of yes is the implicit no

Grant's framing dovetails with Tobi Lütke's "subtraction" framing (see our Lütke profile). Lütke says saying yes to a meeting is saying no to whatever else you could have done with that time. Grant says the question is which meetings (or projects) get your attention in the first place.

The two framings stack: Grant covers the project-selection layer; Lütke covers the calendar-execution layer.

3. The decline script changes

Grant has a specific script for declining requests. Instead of "I'm too busy" — which he argues is dishonest because everyone has the same 24 hours — he uses:

"Based on the commitments I have on my plate, this isn't something I can add."

The framing matters. "I'm busy" puts the speaker on the defensive. "This isn't something I can add" treats the listener's request as a legitimate ask that has been compared to existing commitments and lost. The decline is non-pejorative and final.

What Grant Said About Missed Meetings Specifically

In the same Tim Ferriss episode, Grant described his rule for when he has to break a commitment because he is locked into a flow state:

"I'm really sorry. I know you're counting on me to be able to be there, but I'm not going to be able to make it. But what you can count on me for is to always deliver results. You may not always get the face time I promised… but I will NEVER miss a deadline or fail to deliver something I promised to you."

This is a different kind of attention management. The principle: be dependable for outcomes, even if you cannot always be dependable for the meeting. People who care about outcomes will accept the trade. People who care only about face time were never going to be your high-leverage collaborators.

Why This Matters for Lunch

The lunch hour is the single most common casualty of bad attention management.

A workplace meeting culture that books lunch implicitly says: this 60-minute window matters less than whatever ad-hoc need just emerged. That is an attention-allocation choice. Grant's framework forces the question explicitly: if you booked over your lunch every day for a month, what were the projects that gained those hours? Were any of them more important than recovery, lunch, and afternoon decision quality?

In our experience interviewing customers, the honest answer is usually no. The booked-over hours went to status meetings, low-leverage 1:1s, and "quick syncs" that Grant's filtering would have eliminated upstream.

The fix: treat the lunch hour as a project ("midday recovery") whose attention budget is non-negotiable. Apply Grant's filter to every meeting that wants to encroach on it. Most fail the filter.

How Grant Manages Email and Meeting Requests

Grant has been unusually specific in interviews about his email and meeting rules. The relevant ones for calendar protection:

• No meetings with strangers. Cold meeting requests get a polite no with a redirect to written exchange.
• No "I'm too busy" excuses. Replace with "this isn't something I can add."
• A triage team for emails outside his expertise. Specific topics get forwarded to colleagues whose attention is better suited.
• A challenge network for unvarnished feedback. A defined small group whose input gets prioritized over broad outreach.

The pattern: aggressive upstream filtering so the calendar reflects an attention-allocation decision, not a request-acceptance default.

The Limit of Grant's Framework

The attention-management framing works well for academics, authors, and senior executives who have unilateral control over project selection. It works less well for mid-level employees whose project queue is set by managers or skip-levels.

A junior employee saying "this isn't something I can add" to their VP gets a different response than Grant does to a podcast booker. The framing is right; the latitude to apply it varies.

For lunch specifically, the framework still applies regardless of seniority because nobody else gets to decide whether your brain needs a midday break. The recovery is a personal commitment. Grant's filter applies: is this meeting more valuable than the recovery your afternoon depends on?

Most of the time, the answer is no.

How CovertLunch Implements Grant's Idea

CovertLunch is the calendar-execution layer for one specific application of Grant's attention-management principle: the lunch hour gets prioritized, by default, every day.

The product does not require you to re-litigate the decision each time someone wants to book over it. The decision was made once: lunch matters. The implementation is automatic: realistic-looking calendar events in the lunch window, varied daily so the protection holds.

The cognitive load drops. The principle holds. You do not have to consciously defend the block every time the calendar fills up.

Try CovertLunch free for 7 days →

Related Reading

• Tobi Lütke on subtraction — the calendar-side complement
• Cal Newport on deep scheduling — the calendar-execution mechanics
• Naval Ravikant on empty calendar space — the "ideas come from boredom" angle
• Executive Calendar Management — applied playbook

Frequently Asked Questions

Is "attention management" Grant's original term?

He popularized it in this Tim Ferriss interview and his subsequent writing, but the concept appears earlier in cognitive psychology research. Grant's contribution is the practical reframing for working professionals.

Should I tell my team I am attention-managing?

Probably not in those words. The behaviors (saying no with specific reasons, prioritizing outcome over presence) speak for themselves and read as professional rather than self-referential.

How is this different from "saying no"?

Saying no is a single-instance decline. Attention management is the upstream choice about which categories of requests reach the decline step at all. Most attention-managed people get fewer asks because their public commitments are narrower.

Does Grant defend his lunch hour?

He has not commented publicly on the lunch hour specifically. His broader framing — attention is the scarce resource, defend it accordingly — applies directly.

Is the "I'm too busy" replacement script actually better?

In our customer interviews, yes. "I'm too busy" reads as a rebuke. "This isn't something I can add" reads as a status update on capacity. The latter generates fewer follow-up arguments.