[andrekandre]

  > It is hard to predict disaster, but you can prepare for it.

yes, you need slack to deal with inevitable surprises and delays that will occur so that you can actually make it 'in time'

  > But if you always predict to be on schedule you're more likely to fall behind because there's more ways to fall behind than get ahead.

this is counterintuitive for a lot of people and especially for managers under pressure from above

running without slack means every bump in the road adds a delay which makes the manager's troubles even worse when they have to report the inevitable delay (which leads to a negative spiral of rush-and-delay)

[godelski]

  > running without slack means every bump in the road

I think you ran into maybe a good analogy here (spitballing). To go fast on a bumpy road you need slack, in your shocks. You have to absorb those bumps. But if you have no shocks you just rattle apart.

Sure, a rally car isn't as fast as nascar, but which environment are you in? Super smooth road with only left turns and is built to allow you to go as fast as possible? Or literally anything else.

[andrekandre]

> You have to absorb those bumps. But if you have no shocks you just rattle apart.

yes, and the real issue is, there are no smooth roads (ime anyways)

> Super smooth road with only left turns and is built to allow you to go as fast as possible?

whats interesting is, from a high-level perspective, riding with shocks (slack) can feel more like nascar than rally even if the day-to-day has bumps.

and of course, aside from slack, there are other things that help get to "nascar" such as good specs, good/easy architecture, low-interruption/async communication, and good management, but even then its just reducing the likelihood of bumps...