Summit fever is the dangerous urge to keep pursuing a nearly reached goal after time, energy, or safety says stop. Everest’s completed 2026 spring season made the pattern vivid: Nepal recorded 1,008 successful summits, while 274 people reached the top from the Nepal side in one day—both records.

Most came home. But two Indian climbers reached the summit and died during the descent. That does not prove summit fever caused either death. It does underline the detail almost everyone skips: reaching the top does not end the exposure. Climbers have a name for the tunnel-visioned pull toward a goal that is right there, even when every signal says turn around: summit fever.

This piece is about why the version that runs your team is so costly. We’ll look at why the descent—not the summit—is where Everest’s danger concentrates, the rule experienced climbers use to overrule compromised judgment, and how to install that rule before the next launch becomes a death-zone scramble. The short version: the top is not the finish line. It is the halfway point you are most likely to mistake for the end.

What climbers mean by summit fever

Summit fever is tunnel vision under extreme pressure: a climber becomes so attached to reaching the top that time, weather, oxygen, and physical decline stop carrying their proper weight. Near Everest’s summit, the effect arrives exactly when hypoxia and exhaustion make clear judgment hardest and the cost of a late decision highest.

Above 8,000 meters—about 26,000 feet—climbers enter what mountaineers call the death zone. Atmospheric pressure there leaves roughly a third of the oxygen available at sea level. The body cannot meaningfully recover, thinking deteriorates, and every additional hour spends a physiological budget that cannot be refilled until descent. Summit fever is what happens when that impaired brain locks onto the one thing it came for and stops weighing everything else properly.

Now the counter-intuitive part. A 2026 Journal of Physiology study, Updates to Mortality on Mount Everest: 1921–2024, examined outcomes for more than 30,000 mountaineers who climbed above base camp. It found that more than three-quarters of climber deaths from 1921 onward occurred during descent from extreme altitude. Not on the way up, chasing the summit. On the way down, after getting it.

The published study also reported that, from 2007 through 2024, climbers were eight times more likely than Sherpas to die during a spring summit descent: 0.8% versus 0.1%. Overall mortality above base camp halved from 1.4% in 1921–2006 to 0.7% in 2007–2024, but the shape of the danger persisted. As the researchers put it, most deaths still occur when climbers are severely impaired and rescue is difficult or impossible. The summit feels like the achievement. Physiologically, it is the moment you may have spent the resources needed to survive what comes next.

The turnaround time: a rule built to overrule you

A turnaround time is a deadline set before the climb that requires everyone to descend, even if the summit is close. It exists to replace the exhausted, oxygen-deprived judgment of the person on the mountain with the clear-headed judgment of the person who planned the climb safely at base camp.

On the 1996 Everest expedition made famous by Into Thin Air, guide Rob Hall had such a rule. According to the account on Wikipedia, Hall established a 2:00 p.m. turnaround time—although some sources report 1:00 p.m.—when everyone still climbing was required to begin returning to Camp IV. The logic was sound: a late summit left too little daylight, oxygen, and energy for the descent.

Then the rule met the mountain. Many climbers summited after 2:00 p.m., leaving insufficient time to reach the South Col before darkness at roughly 6:45 p.m. A blizzard struck, and eight people died on Everest while attempting to descend. Hall was among them. The disaster had multiple causes—delays, weather, crowding, exhaustion, oxygen problems, and late decisions—but the missed turnaround became its clearest warning.

The lesson is not merely to have a rule. Hall had one. The lesson is why it must bind: the person standing below the summit late in the day, oxygen-deprived and agonizingly close, is the worst possible person to reopen the decision. A turnaround time is a choice made by your clear-headed self, built to overrule your compromised self. It only works as a hard line—not as one more factor to “take into account” when the moment comes.

Summit fever at work—and why the descent is invisible

Summit fever at work is the late-project fixation that makes a launch, deadline, demo, or quarter-end target feel non-negotiable even as evidence says to cut scope, delay, or stop. The organizational danger is not only the final push; it is the recovery, rework, support load, and attrition hidden after the apparent win.

Watch what the fever does. The closer the goal, the more the resources already spent begin steering the decision. This is the sunk cost fallacy at work: continuing because of what you have already invested, even when expected future costs outweigh expected benefits. Its uglier cousin, escalation of commitment, arrives when stopping feels like admitting that you failed—so you pour in more.

Asana uses Concorde as the famous example. Before its first commercial flight in 1976, the British and French governments had invested $2.8 billion in the aircraft, which ultimately gave the bias another name: the Concorde fallacy. The useful lesson is not that every later year of service was irrational. It is that money already spent cannot make the next dollar wise. Teams run the smaller version every quarter.

The project data has moved since this article’s original benchmark. PMI’s 2018 Pulse of the Profession reported that 9.9% of every invested dollar was wasted through poor project performance and that 52% of projects experienced scope creep. Those remain historical findings, not current rates. In PMI’s 2026 Pulse research, 81% of project professionals said projects had become more complex, and teams rated highly effective at navigating complexity reported an 88% project success rate versus 14% among teams rated only slightly effective or ineffective.

That is not a burnout statistic, but it describes the terrain in which burnout grows: fragmented alignment, decision friction, rework, and strain. The bill comes due on the descent—the post-launch firefighting, bugs shipped to hit a date, support load nobody staffed, and exhausted owner who carried the final push. Post-launch burnout is the team’s version of failing on the way down: you got the win, and it consumed what you needed to survive the next month.

The case for pushing through (and the exact condition where it breaks)

Pushing through is rational when the cost to finish is bounded and the finish really ends the risky work; it becomes summit fever when costs keep compounding and the milestone merely begins another demanding phase. Persistence and stopping rules are not opposites: a clear boundary is what separates disciplined grit from open-ended escalation.

Now the honest objection, because it is a strong one. Isn’t a turnaround time just a license to quit? Persistence is real. Grit is real. Most teams that ship anything difficult do it by pushing through the moment it stops being fun, and a team that bails at the first obstacle ships nothing. “We’re almost there” is often true. Turning around close to the summit can be the cowardly call, not the wise one. A rule that forces premature retreat every time is its own failure mode.

The hidden condition is whether the remaining cost is bounded and whether finishing genuinely ends the exposure. On Everest, neither is true after a missed turnaround: every late minute compounds risk, and the summit merely begins the descent. At work, “we’re almost there” stops being useful information when it has been true for three weeks straight. Bounded cost, real finish: persevere, and good for you. Unbounded cost, false finish: you do not have grit; you have summit fever—and grit is precisely the story it tells you so you will keep climbing.

The professionals do not try to resolve this distinction in the moment, because the moment is when judgment is worst. They resolve it in advance.

How to set a turnaround time and beat summit fever

Teams beat summit fever by defining a measurable stopping condition before work begins, making it binding, assigning someone to call it, and budgeting the post-launch descent. The rule must be visible while everyone is calm; if it can be renegotiated by the same exhausted people it is meant to constrain, it is not a rule.

None of this is about quitting easily. It is the opposite. A turnaround-time rule earns the team the right to push hard because it pre-commits everyone to the signal that distinguishes hard from destructive. Knowing when to stop a project is not weakness; it is the operational skill that preserves the people, attention, and credibility needed for the next climb.

Why distributed teams miss the turn

Distributed teams miss turnaround points because overload is harder to observe across distance: leaders see completed work but not always the late-night push, degraded judgment, or recovery debt behind it. A shared stopping rule and a visible, current project state are therefore more important in remote and asynchronous work, not less.

On a co-located team, someone may see the fever. They notice the engineer who has not slept, the room that has lost perspective, or energy curdling from focused to frantic—and someone with standing can say stop. Spread the team across time zones and those signals fade. The 2 a.m. push happens silently. The decision to blow past the stopping point lands in a Slack thread no one with authority reads in time. What travels is the shipped artifact—the summit photo—not the cost of getting there.

This is the same blind spot from a different angle. The crux of a project is its single hardest move; summit fever is the judgment failure near the top—a different danger on the same climb. It is why busy teams mistake motion for progress, why the recovery skipped after crunch is a decompression stop they cannot afford to miss, and why distributed teams systematically underprice the descent: post-launch risk that looks remote until it floods them.

The fix is to make the turnaround time visible and shared. The rule, the honest state of the climb, and the authority to turn around must live somewhere the whole team can see—not in scattered DMs where inertia wins by default. That is the gap a tool like Coommit is built to close: by keeping the conversation, a live shared canvas, and contextual AI in one place, a distributed team can set the line together, see when it has crossed it, and plan the descent instead of discovering it the hard way.

The bottom line

The bottom line is simple: the summit is not the finish, and judgment is often weakest when the goal looks closest. Teams should set a hard turnaround point before the push, reserve capacity for post-launch work and recovery, and let the pre-agreed rule—not exhaustion, proximity, or sunk cost—decide when to stop.

Remember the finding: more than three-quarters of Everest climber deaths since 1921 occurred during descent from extreme altitude. Your team’s launch is not literally Everest, but the planning error rhymes. Set the turnaround time before climbing, hand the decision to the rule instead of the moment, and plan the descent as part of the project. The teams that come back are not the ones that never feel summit fever. They are the ones that decided, in advance, not to obey it.

Sources and further reading