Time Doesn't Wait For You

There are two clocks running on every team. One is the project clock - deadlines, milestones, the things people remember to track. The other is the latency clock - every wait, every block, every “I’ll get to it tomorrow,” spending real money and time without anyone’s name attached to the spend. The second clock is the one most people forget. It’s also the one with the bigger bill.

Period costs are always running

Engineering leaders carry a budget whether they think about it or not. An org costing $20k, $50k, or more a day is burning that whether the team shipped today or didn’t. That changes the math on most decisions.

• A clever optimization that saves $500 against $50k/day of period cost is noise.
• A one-week delay on a four-engineer team isn’t a scheduling slip - it’s a meaningful chunk of org spend with nothing to show for it.
• A blocked engineer who blocks two others compounds fast. The domino effect is the most expensive kind of latency, and the easiest to underestimate.

This isn’t an argument to obsess over budget. It’s an argument to keep period cost in mind as an incidental concern that’s always present. The essential thing isn’t dollars - it’s latency of feedback (Spiral Iteration). Early discovery, fast loops, short blocks. Period cost is the reminder that those things have a real bill attached.

But don’t confuse urgency with flailing

The opposite failure is just as expensive.

Time pressure can make people rush, skip thinking, and bounce between approaches - what ground rules calls flailing. That spends time without buying discovery. You feel busy. You ship nothing useful.

Think in Goldilocks terms:

• It’s okay to slow down. A 30-minute pause to check assumptions usually costs less than a half-day rebuild.
• Use the pressure to prioritize, not to panic. Period cost should push you toward “what’s the smallest thing that gets me real feedback?” - not “ship anything that looks productive.”
• Defer aggressively. If something can wait without blocking others or worsening downstream cost, it should.

Time doesn’t wait. Cost doesn’t either. The job isn’t to move fast - it’s to move with intent, knowing the meter is running.