Why be productive: defining intention over output

Executive overview

Productivity is not synonymous with working more. It is the practice of being intentional about time, energy, and attention to get more of what you actually care about. Without first answering what you want from life, productivity defaults to overwork.

Productivity without a destination is just driving aimlessly — define your buckets first, then optimise.

Setting up a deep work session

• Separate information-gathering from the session itself — do it in a prior shallow-work block
• Limit context-switching during the session; brief lookups within scope are fine, full context shifts are not
• Define a concrete artifact before you start: a draft section, a proof sketch, a written summary — not "make progress"
• Ambiguity is the most consistent killer of deep work sessions

Managing multiple roles without losing track

• Treat each role (legal, IT, operations, etc.) as a separate part-time job with its own system
• Use role-specific Trello boards (or equivalent): one board per role, not one shared inbox
• Process incoming email by moving items to the relevant role board — out of the inbox, into the right context
• Any one role-board becomes tractable; a single inbox with 100 mixed items is not
• Weekly planning is essential: view the week like a chessboard, theme days by role, consolidate meetings
• Without deliberate weekly structure, the complexity of multiple roles produces constant reactive scramble

Time blocking with unpredictable schedules

• Time blocking requires a clock — "blocking without a clock" is a different (valid) method, but loses the core benefit
• Use rougher-granularity blocks when interruptions are frequent; broad blocks absorb small disruptions without requiring a full rebuild
• Use conditional blocks: "work on X, fall back to Y if time is cut"
• With a partner at home, define clear shifts — during your "off-call" time, be aggressive and specific; during "on-call", use looser blocks
• Rebuilding a schedule mid-day takes four to five minutes; the return in intentional work far exceeds that overhead
• The goal is not to stick to the original schedule — it is to maintain intention about whatever time remains

Tackling procrastination as a graduate student

• Graduate school is a job; treat it as one — plan assignments and build milestones onto the calendar from the start
• For large projects: set calendar dates for research start, research completion, first draft — then execute as if assigned by a supervisor
• Automate all recurring weekly work (readings, problem sets) as recurring calendar appointments so no decision is needed each week
• Time-block your working hours; do a proper shutdown; stop when done
• The alternative — waiting until urgency forces action — produces stress, late nights, and lower-quality output

Deep work with a toddler at home

• Acknowledge the reality: watching a young child is a full-time job; pretending otherwise sets up failure
• Negotiate formal shifts with your partner; your "off-call" hours are for focused, aggressively scheduled work
• Use a dedicated physical space (a garage, a separate room) for all work, not just hobbies
• Invest modestly in making that space functional — the psychological effect of a well-designed workspace is real
• Couples working from home need shared calendars and joint weekly planning; pre-pandemic scheduling independence no longer applies

Async classes and student scheduling

• For asynchronous lectures: schedule them on your calendar as if they were live — watch only at those times
• Treating "watch later" as flexible collapses into "watch when desperate", which collapses into poor academic performance
• The fix is artificial structure: pretend the class is synchronous

Plain-text productivity and Markdown

• Markdown is a human-readable markup language — formatting tags (asterisks for bullets, pound signs for headings) remain legible in raw form
• Created by John Gruber and Aaron Swartz; renders to HTML but readable without rendering
• The classic lifehacker finding (Danny O'Brien, 2004): highly productive programmers all use loosely structured text files as their productivity hub
• Plain text offers maximum flexibility — no app-imposed structure, no constraints on nesting or format
• The right productivity system is personality- and idiom-specific: programmers gravitate to text files, graphic designers to bullet journals, office workers to structured to-do apps
• There is no universally superior system — the wand finds the wizard

Storing materials for future use

• The system matters less than the rule: review your reference repository once a month, no exceptions
• Without a monthly review, no system works — items cause anxiety and get forgotten
• With a monthly review, any system works — files, Evernote notebooks, Trello, long text files, tickler files
• A tickler file (43 folders: 31 days + 12 months) is useful when you know approximately when something will be relevant
• Evernote notebooks stacked by category (books, ideas, business) is an efficient digital equivalent
• On review: scan titles quickly, don't read in depth — the best ideas surface repeatedly across reviews; signal emerges from noise

Social media and self-doubt

• Social media is an extreme amplifier of self-doubt and fear of others' judgement
• For people who already tend toward those insecurities, social media functions as poison — the harm outweighs the benefit
• Practical alternatives: text threads with friends and family, scheduled calls, holding "office hours" for people to reach you
• If you must use it for work: remove it from your phone, access only on a computer, on a schedule, with plugins that bypass the news feed
• Quitting social media is not a full cure — if self-doubt remains incapacitating, seek professional support; validated psychotherapeutic tools exist

Sports and leisure without time sprawl

• Following a sport casually is fine; consuming it as an all-day background activity erodes meaningful time
• Strategy: one scheduled game per week (your team's game), radio or audio as a backdrop during chores or child care
• Occasionally make an event out of it — but deliberately, in advance
• Leisure activities that resemble your work (programming games as a programmer) are not automatically a burnout risk

Burnout: when it happens and when it doesn't

• Burnout has two causes: physical overload (too much, too long) or psychological loss of autonomy (hard work you didn't choose)
• Enjoying a leisure activity that resembles your work does not trigger either cause
• Risk emerges only if you impose rigid goals on leisure and it begins to feel obligatory
• Diversity of activity is not required to avoid burnout — motivation and felt autonomy are the relevant variables

The ultimate why of productivity

• Productivity is not a standalone goal — it is a strategy for getting more of whatever you actually value
• Asking "why be productive?" is like asking "why drive?" — the answer is that you have places you need to go
• The common failure mode: not defining what you want, defaulting to "work more" as the only legible target
• Defining your "buckets" — areas of life that matter — gives productivity a destination
• Example bucket framework: craft (work/creation), constitution (health), community (relationships), contemplation (philosophical/ethical foundations), celebration (appreciating quality and richness)
• Assign a keystone habit to each bucket — a regular, trackable practice that signals you take it seriously
• Rotate focus across buckets over months, overhauling one area at a time
• Without this prior step, optimising productivity is optimising nothing