Big Mountains, Big Teams
Treat difficulty as a signal to add support, not shrink the goal
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 95%
Big Mountains, Big Teams reframes rising difficulty as a support-design problem before treating it as evidence that the goal is too large. Define the mountain, break it into major loads, and map the people already helping at home, at work, or in the field. When a load becomes frustrating, unsafe, or unsustainable, ask who could carry part of it, simplify it, or help the group move faster. Add the missing capability with clear ownership rather than relying on vague encouragement. The framework does not guarantee every goal should continue; conditions can still require retreat. Its value is preventing an ambitious target from being prematurely negotiated downward merely because one person assumed they had to reach it alone.
Origin
Drummond credited her home team, her children's school, and multiple mountain teams with making Everest possible and allowing her to participate fully in the climb.
Core principles
- 01Large goals require support systems
- 02Difficulty can reveal a missing role
- 03Ask who can carry part of the load
- 04A team should make participation safer and more enjoyable
How to run it
- 1
Define the mountain
Describe the goal and the major loads required to reach it. Include logistics and care work, not only the visible performance.
Pro tip Name the work that usually stays invisible.
- 2
Map the current team
List everyone already contributing and what they make possible. Look across home, work, community, and specialist support.
Watch out Do not label people as support without their agreement.
- 3
Find the overloaded edge
Identify where progress is becoming hard, unsafe, or needlessly slow. Specify the load rather than concluding that the whole goal is unrealistic.
Pro tip Use repeated bottlenecks as evidence of a missing role.
- 4
Ask who can help
Find a person, group, or specialist who can carry, simplify, or accelerate that load. Agree on a concrete contribution and coordination point.
Pro tip Seek complementary capability, not just more hands.
- 5
Reassess the route
Review whether the new support makes the goal viable and sustainable. Retreat or redesign if the objective remains unsafe despite the team.
Watch out Team support is not a reason to ignore objective stop conditions.
In the wild
Drummond had people caring for her children at home, a school that turned her expedition into a shared goal, and specialist teams on the mountain. Together they handled responsibilities and created accountability that one climber could not supply alone.
→ She could undertake and enjoy the climb while her children remained supported.
Common mistakes
Shrinking the goal too early
Reducing ambition before checking for a missing support role mistakes a team-design flaw for an impossible objective.
Building a vague support crowd
A large number of supporters does not replace clear responsibility for specific loads.
Is it for you?
Best for
Ambitious goals with multiple logistical, technical, emotional, or operational loads.
Not ideal for
Small tasks where coordination would cost more than doing the work directly.
From the transcript
“one of the biggest lessons for me was big mountains take big teams”
“can help me carry this load or make this easier or get to the top quicker because I think the goal came to you not…”
From the episode
Episode 315: Jenn Drummond: Lessons Learned From Climbing Mountain Everest While Raising 7 Kids
Jenn Drummond