Festina lente: the ancient case for slow, relentless work

Executive overview

Busyness feels like progress, but frenetic activity pulls you away from the work that actually matters. The Roman principle festina lente — make haste slowly — offers a durable correction: don't act rashly, but don't stop either.

Cal Newport's interpretive translation: work slowly, but relentlessly, on what matters. Slow down to avoid reactive, low-quality decisions. Stay relentless to keep making progress. Keep aimed at what actually matters.

The episode then applies this philosophy to practical questions: managing team workload, scoping open-ended tasks, and building personal capture systems.

Festina lente: origins and meaning

• Phrase originates in ancient Greece, adopted and popularised by Rome
• Caesar Augustus minted it on coins (aureus): butterfly for speed, crab for deliberateness
• Renaissance humanists rediscovered it — Aldus Manutius used a dolphin-and-anchor as his publishing imprint; Cosimo de' Medici commissioned artwork around it
• Enduring cross-cultural adoption suggests the idea fits something deep in human nature
• Literal translation ("make haste slowly") is oxymoronic; the interpretive version resolves the tension

The three-part framework

• Slowly: don't be reactive or rash; resist the pull of frenetic activity that feels productive but isn't
• Relentlessly: once you know the right move, do it — don't overanalyse or procrastinate; keep making progress without stopping
• On what matters: stay aimed at the right goal; all the careful, persistent work must point somewhere

Why slow ≠ less output

• Everything on your plate carries overhead — cognitive load plus actual coordination (emails, Slack, meetings)
• More simultaneous work = more overhead = less time and mental capacity for the actual work
• Doing things sequentially with full focus often takes less total time than running them in parallel
• Quality is also higher when attention is undivided

Applying this to a scrum team (Trent's question)

• Scrum with a Kanban board is already structurally compatible with slow productivity — the problem is the pace, not the system
• Fix: pull fewer cards into the "working on" column at a time; give each item more time before pulling the next
• Concern 1 — will output drop? Almost certainly not, for the overhead reasons above
• Concern 2 — will the client push back? Address with transparency: give clients visibility into the board so they can see where their feature sits and that it's moving
• Clients demand urgency when they don't trust the system; transparency buys grace

Scoping open-ended tasks (Ben's question)

• For tasks with no clear endpoint (e.g. customer discovery research), fix a reasonable time block and treat scarcity as a focusing constraint
• Don't proactively inflate the estimate — let negative feedback be the trigger to change
• When results are poor, diagnose process before adding time: what specifically should have been done differently in those hours?
• Evidence-based process improvement resolves the issue 80% of the time; more time is rarely the first answer
• Same principle applies to student study habits: restricting time forces better process; open-ended cramming rarely improves outcomes

Working memory systems (Steve's question)

• working memory.txt — plain text file on the computer desktop; used as a live scratchpad while at the computer; fast to type, easy to scroll, holds large volumes of notes
• Remarkable quick sheet — substitute working memory when away from the computer; useful in class, on walks, in meetings
• Key discipline: review all working memory sources during the daily shutdown; this turns ad hoc capture into a reliable inbox
• Weekend capture: new time block planner has dedicated weekend pages; captures Saturday/Sunday notes so they're visible when building the Monday weekly plan

Care work and deep work (Joni's case study)

• Common assumption: care work (children, aging parents) competes with deep work on a zero-sum time basis
• Joni's experience: unplanned pregnancy at 21 forced time-constrained deep work blocks; she graduated with a 3.96 GPA, earned a full PhD scholarship, completed her doctorate at 30
• Care work can enforce focus rather than destroy it
• Multiple identities — researcher and parent — can add depth of perspective and durability to the work itself
• Deep work alone, without engagement with the rest of life, risks becoming narrow and out of touch

Books read in July 2023

• Shadow Divers (Robert Kurson) — narrative nonfiction about wreck divers who find an unidentified Nazi U-boat off New Jersey; reads like a thriller, multiple deaths, multiple near-disasters
• Power and Progress (Daron Acemoglu & Simon Johnson) — MIT Press; argues that the economic impact of technologies is shaped by social and political choices, not technological determinism; highly relevant to the current AI moment
• River of the Gods (Candice Millard) — narrative history of the 19th-century European quest to find the source of the Nile; vivid account of brutal conditions; the Sudd swamp blocked the obvious river route north-to-south, forcing explorers to enter from East Africa
• The Last Action Heroes (Nick de Semlyen) — history of the 1980s action movie era (Schwarzenegger, Stallone, Van Damme, Seagal); thesis: these stars were the spectacle before CGI made that possible; Jurassic Park ended the era by replacing human spectacle with digital spectacle
• The Island (Adrian McKinty) — thriller set in Australia; a family trapped on an island with violent locals and shark-infested waters surrounding them; structured as one continuous third-act climax