1001: Managing Deadlines + Stress

Hosts Scott Tolinski and Wes Bos address a listener's question on handling deadline stress when behind on work and new tickets pile up. Drawing from agency experience, rapid projects like their Mad CSS tournament, and industry examples, they outline steps to manage crunch time, execute effectively, and prevent recurrence through planning and communication.

Slow Down to Assess and Plan

The first counterintuitive step amid deadline panic is to pause and inventory progress. Stress often stems from a vague "looming cloud of unknowns"—what exactly needs doing across files, sections, or integrations. Hosts recommend getting "out of your head into your system": list completed tasks, remaining work, and blockers in a tool like Linear, a Trello board, or a simple document.

This surfaces hidden issues, such as unclear specs, deployment ownership, API access, or external approvals (e.g., legal sign-off for libraries at Ford, or shifting domain nameservers for their CSS platform). Writing it out clarifies dependencies—mark blocked items explicitly, creating a linear sequence to tackle. Scott likens it to outlining code logic in comments before filling in, or an author's outline; it turns chaos into a checkable sequence. Psychologically, this reduces anxiety by making the abstract concrete, countering optimistic biases where one assumes "it'll get done" without realism.