How the best product leaders think, decide, and disagree.
Will AI replace team roles or augment existing teams?
There is a Mexican standoff happening in every product org right now. Every engineer thinks AI lets them do the PM's and designer's jobs. Every PM thinks they can code now. Every designer knows they can do both. Meanwhile, the CEO is reading headlines about 10-person companies hitting $100M in revenue and wondering why they have 500 employees.
When should founders stay in 'founder mode' vs. shifting to 'manager mode'?
Brian Chesky gave a talk, Paul Graham wrote an essay, and suddenly every founder in Silicon Valley had a two-word excuse to override their entire leadership team: "founder mode."
Should you ship a scrappy MVP or hold out for a high quality bar?
Reid Hoffman famously said you should be embarrassed by your first release. Rahul Vohra spent years polishing Superhuman before letting anyone touch it. Cameron Adams held off launching Canva despite investors begging him to ship. Gaurav Misra ships a new feature every week at Captions. They are all successful. So who is right — and more importantly, when is each approach the winning bet?
Should you grow through product-led growth or a sales-led motion?
A company doing $5 million in ARR, growing over 100 percent. The founders fire the sales team to go product-led. Eighteen months later, revenue has collapsed to under $1 million.
Should product decisions be driven by data or intuition?
A small code change sat in Bing's backlog for months. It moved the second line of ad text to the first line. Nobody rated it as a priority. An engineer who kept seeing it in the backlog said, "My God, we're spending too much time discussing it. I could just implement it." He spent a couple of days on it and launched the experiment. An alarm fired: something was wrong with the revenue metric. But there was no bug. That trivial change increased revenue by about 12% -- worth $100 million annually. It was the biggest revenue impact in Bing's entire history.
Should you ever throw away your codebase and start over, or is a rewrite always a doomed trap?
In 2000, Joel Spolsky called throwing away a working codebase "the single worst strategic mistake that any software company can make." A quarter century later, the answer turns out to depend on which crime scene you are standing in. Tanguy Crusson is standing in the wreckage of HipChat and Stride, the product Atlassian spent three years rewriting while Slack and Microsoft Teams lapped the field. Will Larson is standing next to a table of untouched sushi and champagne flutes, served at the Digg v4 launch party while the production site refused to come back up. Jay Baxter is inside the post-layoff X offices, where a forced audit of Community Notes discovered that deletion, not rebuilding, was the highest-leverage move the team had ever made. And Dhanji Prasanna, CTO at Block, is typing prompts to an AI agent, deleting the output, and calling this the new baseline.
How do you balance radical candor with psychological safety?
Here is a scene that plays out in every company: a manager notices a team member's work is slipping. They care about the person -- maybe even consider them a friend. So they say nothing, work around the problem, and absorb the extra load themselves. Six months later, they are burned out and the team member is blindsided by a bad performance review they never saw coming.
Is freemium or a free trial the better growth model?
Here is a stat that should end this debate: nearly 90% of successful freemium products also offer a free trial. Only three major freemium products -- Figma, Miro, and Amplitude -- do not pair freemium with a trial tier. The question is not "freemium or free trial?" It is "what combination, and when do you layer each in?"
Should you stay lean or scale headcount aggressively to capture opportunity?
Gamma has 30 employees serving 50 million users and generating $100M in annual recurring revenue. Boris Cherny at Anthropic ships 10 to 30 pull requests daily without writing a single line of code by hand. Cognition's 15 engineers each work alongside five AI agents simultaneously. Nick Turley runs ChatGPT -- with 700 million weekly active users -- modeled on the WhatsApp playbook of a small team running a global-scale product.
Should the design quality bar be enforced by a small group of taste-keepers at the top, or distributed across every PM, designer, and engineer?
At Shopify, nothing ships without Glen Coates personally okay-to'ing it on behalf of Tobi Lütke. At Snap, Evan Spiegel overruled his entire leadership team to declare the company a "camera company" and nobody else at the org could even articulate why the call was right. At Airbnb, Brian Chesky renamed every product manager to "product marketing manager" so there would be no ambiguity about who actually owned the product. And then there is Linear, where one product manager total runs an entire 50-person org, and Karri Saarinen insists craft is held not by him but by every engineer the company has been willing to wait months to hire.
How quickly should you fire someone who is not working out?
Every manager has a story about the person they should have let go six months earlier. The underperformer whose mother had cancer. The loyal early employee who grew past their competence. The nice person who just couldn't cut it. In every case, the manager's empathy -- the very quality that makes them a good leader -- was the thing preventing them from doing the right thing.
Should you specialize deeply or stay a generalist in your career?
The standard career advice has been "go T-shaped" for so long that it has become wallpaper. Deep in one thing, broad across many. Everyone nods. Nobody asks the uncomfortable follow-up: deep in *what*? Broad in *what*? And for *how long*?