Parkinson's Law: It’s real, so use it

Original Article ↗ Hacker News Discussion ↗

Parkinson’s Law — the idea that work expands to fill the time available — is used here to argue for tighter, well-chosen deadlines as a way to focus effort and curb scope creep. Many engineers and managers counter that arbitrary or chronically aggressive deadlines backfire, driving burnout, poor quality, and fake urgency, especially in low-trust or highly bureaucratic environments. Commenters emphasize that motivation, time perception (e.g., ADHD), team culture, and project type all shape whether deadlines help or harm, with some advocating incremental delivery, slack time, and intrinsic motivation as more reliable levers for productivity.

Parkinson’s Law and Individual Differences

  • Many agree that tasks tend to expand to fill available time, but emphasize this is not universal.
  • Neurodivergent people (e.g., ADHD, “time blindness”) often report that self‑imposed deadlines don’t work at all; medication and external structures matter more than “productivity philosophy.”
  • Some say they can only honor deadlines with medication; others find even external deadlines mostly produce stress rather than focus.

Deadlines as Motivation vs Harm

  • Supporters see deadlines as helpful forcing functions: curb perfectionism, cut over‑engineering, and encourage “good enough” iterative shipping.
  • Several note personal success with timeboxing, rough estimates, and “ship when it’s better than what’s live now.”
  • Critics report fake or arbitrary deadlines (especially in defense, big tech, and large enterprises) that waste time, incentivize workarounds, and erode trust.
  • Concerns: burnout, chronic crunch, attrition, and “deathmarches” when deadlines systematically ignore task complexity and Hofstadter’s Law.

Culture, Trust, and Autonomy

  • A strong theme: deadlines only “work” in a healthy, high‑trust environment where:
    • Mistakes aren’t punished.
    • People have autonomy and contact with customers.
    • There is slack afterward to fix rushed decisions and reduce technical debt.
  • Small, high‑agency teams report high productivity without deadlines, relying on intrinsic motivation, customer empathy, and iterative delivery.

Scope, Risk, and Technical Debt

  • Tight timelines can limit scope creep and force prioritization, but also encourage corner‑cutting and future rewrites that never happen.
  • Some argue tech debt is often over‑feared relative to business value; others say always doing “just good enough” yields a barely acceptable product.
  • Several complain that PMs and managers rarely model risk explicitly, so engineers end up silently managing it under deadline pressure.

Scale, Bureaucracy, and Large Organizations

  • Large orgs often show “Parkinson’s” slowness: ample money, long timelines, heavy process, and cross‑team dependencies.
  • Bureaucracy creates opportunities for smaller, nimble competitors, but also coordination advantages for incumbents.
  • Some say trust‑and‑freedom models don’t scale well; others argue the real issue is increasing coordination cost and distance from customers.

Alternatives and Nuances

  • Suggestions: small increments instead of big project deadlines; weekly progress updates; developer‑driven estimates; slack time for improvement.
  • One view: Parkinson’s Law applies well to small tasks (surveys, short chores), but not reliably to complex, multi‑month software projects.
  • A 4‑day workweek is cited as a “macro‑deadline” that can drive efficiency, though others warn about sustainability and hidden costs.