Saying no intentionally: a framework for managing workload and commitments

Executive overview

Most people already say no constantly — they just do it haphazardly, waiting until stress peaks before declining anything. That default approach guarantees you stay stuck at a persistent level of overload.

The fix is intentionality: track what you accept, apply explicit criteria, and deliver a clear no — not a soft maybe.

The hidden cost of passive no

• Everyone is already filtering requests; the question is whether it's by design or by exhaustion
• Waiting until you feel "sufficiently stressed" to say no means you never escape that stress level
• The result is productivity purgatory: enough on your plate to be uncomfortable, never enough to force change
• Implicit, haphazard filtering keeps you reactive rather than deliberate

Four insights from 100 deliberate no's (Nature article)

1. Track everything. Keeping a yes/no list makes no feel like a real option; gamification helps. Tracking also surfaces how much you've already taken on and what you've accomplished — countering imposter syndrome.
2. Target bigger asks. It's easy to rack up nos on small tasks, but the large commitments — leadership roles, grant proposals — cause the most stress and yield the most relief when declined.
3. Saying no is emotional work. Cultural and social conditioning makes declining feel like a personal failure. Making the emotional cost visible — not just the logistical cost — is itself valuable. Acknowledge it rather than pretend the difficulty isn't real.
4. Practice makes it easier. Each successful no lowers the activation energy for the next one.

Five criteria for evaluating a request

• Does it fit my research agenda or professional identity?
• Does it spark genuine interest?
• Do I have time to do it well without sacrificing existing commitments?
• Does it leave space for my personal life?
• Am I uniquely positioned to fill this need?

How to say no clearly

• A soft no ("I'm pretty busy, not sure it'll work out") is a slippery slope — people will keep pushing as long as there's any opening
• Only a firm no actually reduces commitments
• Include the word "no" explicitly: "Because of X, I have to say no to this request"
• Don't cite temporary busyness — you'll get a follow-up for next month
• Saying no without wiggle room is a service to both parties: clarity is kinder than ambiguity

Structural approaches to reduce inbound volume

• Remove a general-purpose contact point; route requests to agents, publicists, or agencies instead
• Make non-response the stated default for certain channels
• Brief close contacts on a standard script so they can deflect on your behalf

Anxiety, scheduling resistance, and motivation

• The brain hasn't evolved to respond to abstract scheduled commitments — resistance to planned events or tasks is a normal neurological mismatch, not a character flaw
• For some people the mismatch triggers physical anxiety (constriction, breathing difficulty) rather than simple inertia
• Treating it as a physiological event — "thank you, brain, this will pass" — and acting anyway is more effective than trying to eliminate the feeling
• Abandoning structure to avoid the anxiety trades one discomfort for a deeper existential one: drift, missed deadlines, reactive scrambling

Career and workload planning

• Lifestyle-centric career planning: define what you want your daily life to look like first, then work backwards to what professional choices support it
• Deep life buckets (craft, constitution, community, contemplation, celebration) prevent false trade-offs between "hobbies" — each activity belongs to a different bucket with its own logic
• "Which hobby should I pursue?" is the wrong frame; the right frame is: what belongs in which bucket, and what's tractable given my current season of life?
• The three disqualifiers for staying in a job (from So Good They Can't Ignore You): no skill-building options, value conflicts, can't stand the people — supplement these with lifestyle fit
• When evaluating a career, study role models and case studies broadly before assuming the only paths are the ones visible from your current employer

On process before tools (project management)

• Project management tools (Wrike, monday.com, Scrum) are often adopted as a totem — as if the tool itself fixes disorganization
• The right sequence: design the workflow that fits your specific team and work first, then select tools to implement it
• Custom, informal, flexible interpersonal plans outperform off-the-shelf methodologies applied without adaptation
• Simple tools (Google Docs, Trello, Dropbox, shared sheets) are usually sufficient once you have a clear process

On values documents and planning systems

• A values document doesn't need to be perfect before it's useful; having something is better than nothing
• Values evolve with life experience, relationships, and exposure to philosophical or theological frameworks
• Quarterly/semester/strategic plans are the same thing under different names — a three-to-five month forward view anchored to your core values
• Daily time-block planning has initial resistance every time you restart it; two weeks in, the brain adapts and the routine becomes self-reinforcing