Pick a Lane and Write the Story
Master one of the five product ambiguities early, then write the paragraph your next employer needs to hear.
- Difficulty
- Easy
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 93%
Singhal's two-goal prescription for early-career and IC product people. Goal one: pick a lane — become world-class at one of a small set of product ambiguities rather than being mediocre across all of them. Goal two: work backwards from the story you'll tell about this role, in the same way Amazon writes the press release before building the product. He argues the story test is the single highest-leverage thing any PM can do for their career, and that the rise of the senior IC track makes a mastered ambiguity more hireable than a thin management résumé.
Origin
Singhal's own framing, borrowing the working-backwards mechanic from Amazon's press-release-first product process.
Core principles
- 01A PM is confronted with all five ambiguities at once; the trap is being average at all of them.
- 02Pick one lane as early as possible and go to world-class in it.
- 03Write the story before you do the work, the way Amazon writes the press release before building the product.
- 04The story must use 'I', not 'we' — 'we' is for doing good things; careers are individual.
- 05A senior IC with a mastered ambiguity beats a mediocre manager story in a hiring loop, because the hiring manager needs the ambiguity cracked, not another team-ambiguity expert.
- 06If the story sucks, that is information — change what you're doing, don't improve the telling.
How to run it
- 1
Learn the ambiguity taxonomy
The lanes Singhal names: craft (being a great crafter); market ambiguity (navigating markets, creating something that doesn't exist); organizational ambiguity (complex teams with complex goals, inside-the-building problems); domain expertise (ML, hardware, a specific vertical); team/people ambiguity (thriving at managing managers, getting the balance right); and growth.
- 2
Pick one lane, early
Choose the ambiguity you will go world-class in and commit. This is goal number one of an early career, and diversity of experience is how you find out which lane fits.
Pro tip Use the diverse-experiences sequence from The Skip to discover the lane, then narrow.
- 3
Write the story before you do the work
Sit down and write the paragraph you will be able to write in 6, 12 and 24 months when this role is finished: here's the problem I solved, here's the skill I built, here's the headwind I faced, here's what I did to overcome it.
Pro tip Use 'I' in every sentence. 'We' is how you do good work; 'I' is how you think about your career.
- 4
Judge the story, and change the work if it sucks
Read the paragraph cold. If the story is weak — you were merely present, things happened around you — that's a career signal. Change what you take on until the story is compelling.
Pro tip Test it against the skip job: is this story meaningful for the job after next, not just the next one?
Watch out In interviews, the tell for someone who never did this is that they can describe that they were there and that things happened, but not what they learned or what they specifically did.
- 5
Only then plan the quarter, the month and the week
With the lane and the story fixed, work backwards into day-to-day, week-to-week, month-to-month execution and the performance review — not the other way around.
In the wild
Candidate A: 'I managed two people, I was nominally in charge of this thing but they did the details, and before that I was early on getting something out the door, and then they picked me to be a manager.' Candidate B: 'I was an IC the whole time; I went from learning something, to demonstrating it, to taking it forward, and I've mastered one of these ambiguities — I'm an expert in this domain / in navigating complex organizations.'
→ Singhal hires B: 'I don't need a team-ambiguity expert — my hard part is cracking the code on this complex market or this very complicated organization. You're the type of person I want.'
Singhal, across hundreds of interviews, keeps hitting candidates who describe early jobs by saying they were there and this happened — and cannot answer 'tell me exactly what you learned and what you did.'
→ The candidate reads as passive; the career story that would have made them promotable was never authored.
Common mistakes
Being average across all five ambiguities
PMs face craft, market, organizational, domain and team ambiguity simultaneously, and default to mediocrity in all of them rather than mastery in one.
Taking a management role for status rather than story
The industry programs people to 'go manage that person, it gets you closer to the top' — but a thin manager story from an untrained manager is weaker in the market than a mastered IC lane, and the learning often isn't there either.
Writing the story in 'we'
'We' obscures what you specifically did. Careers are evaluated individually; the paragraph has to survive the question 'what did YOU do?'
Is it for you?
Best for
Early- and mid-career product managers choosing what to specialise in, and ICs deciding whether the manager track is actually the right move
Not ideal for
Generalist founders and very early startup employees, where mastering one ambiguity is a luxury the company can't afford yet
From the transcript
“picking a lane is kind of goal number one and then maybe goal number two is having a story to tell”
“ensure that the story you will tell about the work you're doing today is Meaningful for your skip job”
“here's a problem I solved here's a skill I built here's the headwind I faced here's what I did to overcome it use I in…”
“it's just like Amazon talks about building the press release before they start”
From the episode
Building a long and meaningful career
Nikhyl Singhal (Meta, Google)