What a 2 a.m. summit push taught me about scope cuts

On Deo Tibba we left high camp at two in the morning. Not because anyone enjoys climbing in the dark, but because the summit window closes by noon — after that, the snow softens and the descent becomes the dangerous part. The deadline wasn’t negotiable. The weather doesn’t do stakeholder alignment.

Halfway up, our pace dropped below plan. We faced the choice every rope team knows: push the original route and risk the window, or cut to the direct line — steeper, less scenic, but faster. We cut. We summited at 9:40 with margin to spare.

Enterprise software has the same physics. At Mercedes-Benz, release dates on series vehicle programmes are weather windows — you don’t move them. When a quarter tightened, the answer was never “push the deadline”; it was “cut the load.” Drop the nice-to-have variant, ship the core workflow, return for the rest next PI. The teams that struggle are the ones that treat every feature as summit-or-nothing.

The lesson I keep relearning: scope cuts feel like failure at the moment of decision and like wisdom at the summit. So decide the cut lines at base camp — in planning, well-rested — not at 5,600 metres when you’re tired and emotionally invested in the scenic route.