Builder vs. Information Mover
Diagnose which half of your role AI kills and which half it supercharges.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 4
- Confidence
- 90%
Singhal splits product people (and knowledge workers broadly) into two archetypes: 'information movers' who reframe and route information up and across an org, and 'builders' who directly make, test, and ship. AI is obsoleting the information-mover work while paying builders record comp. The framework is a self-diagnosis: honestly classify which archetype you are, because roughly half the industry sits on the wrong side.
Origin
Nikhyl Singhal's own model, built from running the Skip community of ~125 heads of product and CPOs and his 30 years at Meta, Google, and Credit Karma. Extends the 'PM archetypes' framing from his earlier Lenny's Podcast appearance.
Core principles
- 01Information-moving work (status reports, reframing docs up the chain, managing stand-ups) is what AI attacks first because it is mechanical.
- 02Judgment and hands-on building are what remain valuable and scarce.
- 03Archetype is about what energizes you, not your title — engineers, designers, and marketers can all be builders.
- 04Comp and optionality are flowing to builders; information movers face 'roadkill' risk.
How to run it
- 1
Audit where your hours actually go
Categorize your typical week into information-moving activities (reframing information between people, status reports, backlog and stand-up management, alignment theatrics) versus building activities (making, prototyping, testing, shipping, writing software/agents).
Pro tip The tell for information-moving: work whose main output is a differently-framed version of information someone else already produced.
- 2
Classify your archetype honestly
Ask whether you got into the work because you love building or because you were good at communication and moving information. Singhal estimates about half of product people are primarily information movers.
Watch out Do not flatter yourself. Being paid well for the old skill does not mean the market will keep paying for it.
- 3
If you are a builder, go all-in on judgment plus hands-on building
Lean into the renaissance: use AI to obsolete the mechanical parts you never liked, and reposition around judgment (deciding what to build, whether a change is good, whether it fits the system).
Pro tip Builders now have a broader range: founder, CEO, or even cross-functional C-level roles like CHRO are opening up to builder-PMs.
- 4
If you are an information mover, decide your pivot deliberately
Recognize the industry is moving away from you and choose: cross into building, move to a function/industry where the skill still commands value, or use AI tools to start something outside tech.
Watch out Denial is the expensive option. Many know they need to change and do nothing — that is the group that gets shed in the coming layoff-and-rehire wave.
In the wild
Singhal predicts that in the next 12-24 months companies will do massive shedding then massive rehiring — a company might let go 30,000 and hire 8,000, where all 8,000 new hires are 'AI-first' builders and the 30,000 released were people the company 'didn't get as much for.'
→ A bifurcated labor market: builders see all-time-high comp and more offers, while non-builders are disproportionately cut.
Lenny notes his job-market report shows the most open PM roles globally in over three years, which seems to contradict AI fears. Singhal resolves it: hiring is booming specifically for the builder archetype while information-mover PMs struggle to find roles.
→ Confirms the split is real — 'PM demand is up' and 'half of PMs are in trouble' are both true because they describe different archetypes.
Common mistakes
Assuming 'PM demand is up' means your kind of PM is safe
Aggregate hiring numbers hide the archetype split. The role is growing for builders while contracting for information movers; reading the headline number as reassurance is how information movers miss the warning.
Treating archetype as fixed by job title
Builder vs. mover is about what you actually do and love, not your résumé. Engineers, designers, and marketers can be builders; a titled 'senior PM' can be a pure information mover. Misclassifying yourself leads to the wrong pivot.
Is it for you?
Best for
Mid-career and senior product managers (and adjacent knowledge workers) trying to read whether AI threatens or elevates their specific role.
Not ideal for
People in genuinely non-tech roles, or anyone who already builds daily and just needs execution tactics rather than a diagnosis.
From the transcript
“the the the information mover is essentially going to become a dinosaur”
“if you don't love building stuff, you're in trouble”
“And I mentioned about half the people are in that camp”
“you might see a company shed 30,000 and hire 8,000, but the 8,000 people are going to all be AI-first”
“we have the most open PM roles globally in 3 plus years”
“And I think builders wanted is going to be the big tagline for the next couple of years”
From the episode
Why half of product managers are in trouble
Nikhyl Singhal (Meta, Google)