Same scene in Berlin U-Bahn (metro) this morning.
Train was late and all the people that came to the station in the meantime were trying to get in. Cramming in leads to longer delays. Once the train is delayed, it’s delayed for every station downstream. Thus, sadly, the same behavior accelerates and it gets even worse.
Same thing happens in product development when you start with a big batch and that’s almost always the case. The bigger the batch, the more likely it’s going to be late, which in turn hurts predictability. Once it’s late, cramming in and pressure starts piling up.
If you knew the next train will be coming in two minutes, how likely would you not do this and wait for it? I’d say very likely.
In complex systems you cannot assure predictability by planning and estimates. You can assure predictability by reducing the batch size. This also leads to extracting value sooner and accelerating feedback. When you think the batch size is small enough, halve it, then halve it again.
High demand and low predictability incentivizes the system for cramming in more work.
Original LinkedIn post