Ladder vs Map
Choose career moves by what makes an interesting life, not by what climbs the next rung
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 5
- Confidence
- 95%
Two competing operating systems for a career. The Ladder optimises for upward movement: title, power, scope, comp. The Map optimises for interesting terrain: go where the experience is novel, accept discomfort as the price of growth. Shah's claim is that most people are highly intentional in the micro (next job, next title, next equity grant) and completely unintentional in the macro (what kind of life am I building), and that inverting this makes 'risky' moves look inevitable.
Origin
Jason Shah's own framing, developed across a self-funded startup, Yammer/Microsoft, do.com, Amazon, Airbnb and Alchemy. He explicitly analogises it to travel — Greece, India, Australia — and to the deathbed test ('nobody's really gonna be looking at my linkedin at my funeral'). The 'ladder can fall over' extension is Lenny Rachitsky's addition in the same conversation.
Core principles
- 01The ladder is a fragile bet: it assumes the rung you're standing on stays attached to something worth climbing.
- 02False precision is the enemy — most career decisions are made on roughly ten cumulative hours of signal, yet people act as if the outcome is known.
- 03Discomfort is not a cost to be minimised; it is where the growth and the stories come from.
- 04Map does not mean job-hopping. Long tenures at few companies still form a map if the macro is chosen deliberately.
- 05A 30-50 year career is a lot of chips — you can play five ten-year runs, so single moves are rarely fatal.
- 06Use the long-horizon question (what will I care about decades from now) as the tiebreaker on all life decisions, not just work.
How to run it
- 1
Diagnose which mode you're currently in
Look at your last two career decisions and ask what actually drove them: title, compensation, and reporting line (Ladder) or curiosity, novelty, and the nature of the problem (Map). Most people discover they have been unconsciously on the Ladder because that is what the surrounding culture rewards.
Pro tip Read the reasons you gave other people at the time. Ladder reasoning tends to be defensive and comparative; Map reasoning tends to be specific about the work itself.
- 2
Define the macro before the micro
Write down what you actually want your life to be about — where you get energy, what you want to have built, who you want to be around — before you evaluate any specific role. Shah notes there are almost no classes or blog posts on this 'touchy-feely' side, so nobody does it by default.
Pro tip Run the deathbed test: at your funeral nobody reads your LinkedIn. What products, people and experiences would actually matter?
Watch out Skipping this step means every subsequent role gets evaluated against the only scoreboard available — the ladder's.
- 3
Strip out the false precision from the option in front of you
Name explicitly what you actually know about a prospective move versus what you are assuming. You have spoken to the team for maybe ten hours. The projected outcome — the equity value, the promotion path, the mentorship — is largely invented. Downgrade it to the guess it is.
Pro tip Ask: if the company's trajectory flatlines and no promotion arrives, would this still have been worth doing? If yes, it's a Map move that survives failure.
Watch out False precision feels like rigour. It is the main thing that talks people out of the bolder, better decision.
- 4
Pick the interesting terrain, then commit to it seriously
Choose the move that is most interesting on the macro map — then stay long enough to actually learn it and build institutional depth. Shah's own map is a small number of long chapters (seven years running his first company, years at Yammer, four at do.com, Alchemy 'for a very long time'), not a tour of 180 companies.
Pro tip The rare people who stay four to seven years accumulate institutional knowledge and cultural gravity nobody else has. Map-thinking and long tenure are not in conflict.
Watch out A map read as permission to bounce every few months produces no depth, no track record, and no network — the failure mode on the opposite end of the spectrum from the ladder.
- 5
Front-load one credibility chapter early
Early roles are disproportionately formative — they teach you the craft, seed your network, and become the signal others read. Shah recommends sitting in the middle of the spectrum early on: not the pure prestige stamp (Goldman), not pure unaffiliated wandering, but a hyper-growth company with strong people to learn from and real scope for you.
Pro tip Shah still, a decade later, meets ex-Yammer colleagues weekly — they taught him product, funded his next company, and became his hiring pipeline. That compounding is the actual return on an early chapter.
In the wild
After a small acquisition of the education company he'd run for seven years since age 15, Shah moved to San Francisco with no job while his college peers took prestigious roles at places like Google. He worked from his dining table on savings, built five or six products, got substantially better at programming, and once pitched Ron Conway on the street while dishevelled.
→ The micro-level learning was thin and it was often boring, but the period made him a materially better builder and led into his first formal PM role at Yammer. On the Ladder scoreboard it was a wasted year; on the Map it was foundational.
Post-Microsoft acquisition, Shah's equity was finally valuable and there was a large-company structure to learn from. He left anyway to start do.com, backed by a couple of angels. The four years that followed included an M&A offer collapsing the day before his wedding and a featured App Store app that crashed 90% of the time over Memorial Day weekend with no BD contact reachable.
→ Financially and structurally a worse decision than staying. Shah treats it as a Map move — the equivalent of getting lost in a foreign city or bitten by a dog in Thailand — that built character and taught him things the Microsoft ladder never would have.
Common mistakes
Pinning everything on a ladder that falls over
You assume the rung leads somewhere — the company keeps growing, the promotion comes, the equity vests into something. When any of that fails, the entire rationale for the move evaporates, because there was no second reason for being there. That is a fragile career decision.
Treating it as a binary between ladder and map
Shah is explicit that you can often have both: go to the most interesting place in the world and still get progression and success. People assume it's either/or because false precision has convinced them they already know the outcome of each branch.
Using 'map' as cover for job-hopping
Shortening tenure from years to months creates no institutional knowledge, no cultural contribution, and no track record. The map is about the shape of the whole journey, not the frequency of moves.
Is it for you?
Best for
Mid-career operators (PM, engineer, founder) staring at a fork where the safe, high-title move and the interesting, unproven move diverge — and who default to the safe one for reasons they haven't examined.
Not ideal for
People with hard near-term financial or visa constraints where optionality is genuinely unaffordable, or those very early in a first job who haven't yet built any credibility chapter to trade on.
From the transcript
“so the framework i like is ladder versus map”
“moving up more influence more power a higher title things like this whereas map is i just want to go wherever's interesting”
“privilege thing to say but i care more about living in a really interesting life than let's say a good or comfortable life”
“think about their next job their next title how much salary and equity there is and in good ways too they think about the team…”
“what we think a given career move is going to lead to or what it's going to be like and we forget that you know…”
From the episode
Building a meaningful career
Jason Shah (Airbnb, Amazon, Microsoft, Alchemy)