"How does a project get to be a year late? One day at a time"
About this Quote
The line lands like a punchline because it refuses the comforting myth of the catastrophic screw-up. Brooks, writing from inside the trenches of large software efforts, frames lateness not as an explosion but as erosion. “One day at a time” is comic in its inevitability, then chilling in its accusation: schedule disasters are usually the arithmetic sum of tiny indulgences, tiny denials, tiny “we’ll make it up later” decisions.
Brooks’s specific intent is diagnostic. He’s puncturing the managerial fantasy that delay comes from a single villain event: the key engineer quits, the vendor fails, the requirements change. Those things happen, but the real mechanism is more banal. A meeting that doesn’t end with a decision. A feature slipped in because it “won’t take long.” Testing pushed to the right. Documentation treated as optional. Each choice feels locally rational; the calendar is where their collective irrationality becomes visible.
The subtext is about accountability without melodrama. “One day at a time” implies everyone participates: leadership that won’t cut scope, engineers who underestimate, organizations that reward optimism over accuracy. It also hints at how humans experience time on projects: late is not a state you enter; it’s a drift you notice only when the shoreline is gone.
Context matters: Brooks is the author of The Mythical Man-Month, the book that made software delay a serious subject rather than a personal failing. The wit functions as a management tool: it’s memorable enough to circulate in teams, a small verbal tripwire meant to catch the next “just one more day” before it compounds into a year.
Brooks’s specific intent is diagnostic. He’s puncturing the managerial fantasy that delay comes from a single villain event: the key engineer quits, the vendor fails, the requirements change. Those things happen, but the real mechanism is more banal. A meeting that doesn’t end with a decision. A feature slipped in because it “won’t take long.” Testing pushed to the right. Documentation treated as optional. Each choice feels locally rational; the calendar is where their collective irrationality becomes visible.
The subtext is about accountability without melodrama. “One day at a time” implies everyone participates: leadership that won’t cut scope, engineers who underestimate, organizations that reward optimism over accuracy. It also hints at how humans experience time on projects: late is not a state you enter; it’s a drift you notice only when the shoreline is gone.
Context matters: Brooks is the author of The Mythical Man-Month, the book that made software delay a serious subject rather than a personal failing. The wit functions as a management tool: it’s memorable enough to circulate in teams, a small verbal tripwire meant to catch the next “just one more day” before it compounds into a year.
Quote Details
| Topic | Management |
|---|---|
| Source | The Mythical Man-Month: Essays on Software Engineering — Frederick P. Brooks, Jr., 1975 (contains the aphorism "How does a project get to be a year late? One day at a time.") |
More Quotes by Frederick
Add to List




