What a summit push taught me about deadlines

                       ^^^^^^^^^  ^^^^^^^^        ^^^^^  ^^^^^   ^      ^^^^^^^^^^        ^^^^^^
                    /\/         \/        \/\/\__/     \/     \_/ \__/\/          \_  ___/      
            _      /                                                                \/          
_______/\__/ \____/                                                                             

We left high camp at 2:40am with headlamps and a rule: if we are not on top by 11:00, we turn around. No discussion, no "just twenty more minutes." The guide said it plainly: the summit is optional, getting down is mandatory.

The summit is halfway

Most accidents on big mountains happen on the descent. People spend everything they have reaching the top and have nothing left for the part that actually brings them home.

Software deadlines have the same shape. Shipping is not the summit; it is the halfway point. After launch comes the monitoring, the bug reports, the migration you promised to clean up, and the on-call week. If a team spends all its energy hitting the date, the descent gets dangerous.

Turnaround times are kindness

A turnaround time feels like pessimism when you set it. At 10:40am, with the summit visible and your legs burning, it feels like the only sane voice on the mountain.

I now try to set turnaround times for projects up front:

• If the prototype does not prove the idea by Friday, we stop and write down what we learned.
• If the migration is not at 50% by the end of the sprint, we roll back and rethink.
• If the scope grows twice, we cut it in half before anyone works late.

Deciding this early, while everyone is rested and calm, is the whole trick.

We made it

We reached the crater rim at 10:20, stayed for eleven minutes, and were back at camp by early afternoon with enough energy to make tea. The best part of the day was not the top. It was how unremarkable the way down felt.