Acclimatization is a team sport

                                ^                              ^^^^^       ^^^^^     ^   ^^^    
                               / \____                ___    _/     \__  _/     \___/ \_/   \___
      __        __    ___  ___/       \     /\_      /   \/\/          \/                       
_____/  \__/\/\/  \__/   \/            \/\_/   \____/                                           

Every high-altitude itinerary has the same rhythm: climb high, sleep low. You hike up a few hundred meters, spend an hour there, then come back down to sleep. Your body learns the altitude in doses. Skip that rhythm and the mountain teaches you with a headache, or worse.

Onboarding has altitude too

New engineers face their own thin air: a codebase they do not know, a domain full of acronyms, and a team with years of shared context. Throwing someone straight at a big feature is like flying them to 4,000 meters and asking for a summit by Thursday.

What worked on my teams looks a lot like an acclimatization schedule:

• Day trips first. Small, real tasks that touch many parts of the system and end the same day.
• Climb high with a partner. Pair on one gnarly area early, then step back.
• Sleep low. Give time to read, wander, and ask questions without a deadline attached.

Watch for symptoms

Altitude sickness is sneaky because the person feeling it is the worst judge of it. Teams are the same. A new hire who goes quiet in standups, or says "almost done" three days in a row, is showing symptoms. The answer is the same as on the mountain: go down a little, rest, then try again.

Rope teams

On glaciers we travel roped together. Nobody minds the slowest person setting the pace, because the rope only works if everyone arrives. Good teams treat onboarding the same way: the pace is set by the newest person on the rope, and that is fine.