“I recommend Build by Tony Fadell.”
Build
By Tony Fadell and Noam Lovinsky's wife
5 recommend/use · 5 sourced episodes
Every sourced reference
Short attributed excerpts only. Timestamps are approximate.
“I love the the new book from Tony Fidel called build It's a Wonderful book”
“First is Build by Tony Fadell.”
“I've really enjoyed Build by Tony Fadell”
“you can read build that talks about how apple did it”
Related frameworks
Advocate Yourself Out of a Job
Argue for the company-optimal allocation of your team even when it defunds you — and read the response.
Alpha Co-Creation Loop
Pick the users who are already pushing the boundary, build with them in a shared channel, ship only when they're thrilled.
Belsky's Founder Bet Checklist
Back mission-driven, pragmatically pessimistic founders building products with a clear object model.
Channel Diversification Before the Drought
A one-channel growth company is always a no-no — turn on the second channel while the first still works.
Designing a Zero-to-One Incubator Inside a Giant
Fix the incentive system and the time horizon first — everything else about internal incubation follows.
Do Half, Then Go on a Killing Spree
Build half the features, then remove things until the one core action runs at 10x velocity.
Empowerment Without Anarchy
Leaders place the bets; teams figure out how to win them. Neither top-down nor bottom-up.
Evaluative User Research (Hunt for Reasons They Won't Use It)
Test prototypes to find every reason people won't use it — and never let the researcher go alone
Feature Team vs. Empowered Product Team Diagnostic
Tell in minutes whether your squad is handed features to ship or problems to solve
Friction Logging
Adopt a specific user's identity, walk your own product end-to-end, and log every point of friction.
Group UX Review and Walking the Store
Taste the soup together — experience the product as a group, log issues live, then debate each one.
Hire for Autonomy: References, Real Work, and Default Trust
You'll be in none of the decisions that matter — so hire people you can hand autonomy to, and verify via references.
Internal Tools as a Product (The Crying Octopus)
Run your dev-productivity team like a product team: monthly surveys, hard metrics, and one-click paper cuts.
Merchandise Progress Through the Messy Middle
Short-circuit the human reward system with agreed micro-goals and a narrated sense of progress.
No Bystanders on Product Strategy
Get the CFO, the head of people and sales fingerprinted on product strategy before growth goes negative.
Optimize for the Problems You Want to Have
Only build features that stop people from reaching the point where they'd ask you for more.
Ship Fast Without Breaking Money
Reject the reliability/velocity trade-off: automated gauntlet, ramped exposure, and remediations ahead of roadmap.
Solution-Weighted Discovery
Spend a little time validating the problem; spend most of it winning on the solution
Stamina as the Kill Signal
Projects die of exhausted stamina long before they die of exhausted money — so watch the team, not the runway.
Stretch With an Anchor
Take the role that will hurt you into growth — but only if one or two things in it are already in your wheelhouse.
The Best-Teams Adoption Heuristic
Adopt a practice only if several of the best teams already use it — then strip the culture from the technique
The Conviction Test for Whether to Quit
Compare your conviction now versus at the start to decide whether to persevere or pivot.
The Diseases of a Devolving Product Company
Four diagnosable diseases that turn a great product company into a feature factory
The Engineer-cation
Leaders clear 3-4 days, join a team as an IC, ship one small feature to production, and log the friction.
The Feature Team vs Empowered Product Team Diagnostic
Diagnose whether your team ships output or owns outcomes — and what that means for the PM role.
The First Mile: Lazy, Vain, and Selfish
Design onboarding for the first 30 seconds, when every new user is lazy, vain, and selfish.
The Founder's First-PM Timing Rule
The founder IS the product manager until scale forces the handoff — around 20 to 25 engineers.
The Four Product Risks and Their Owners
Valuable, usable, feasible, viable — any one fails and the product fails
The Inverted W Planning Process
Teams propose, leaders synthesise, teams adjust, leaders resynthesise, orgs distribute with context.
The Marketplace Priority Stack
Pre-commit an explicit ranking of who you serve first, so thorny trade-offs resolve themselves.
The Negative-Growth Rehearsal
Growth masks all problems — so ask what you'd do if growth went negative, before it does.
The Object Model: Three Questions Every Screen Must Answer
On every screen, a user should know how they got here, what to do now, and what to do next.
The One-Quarter Empowered Team Experiment
Convert a single feature team into an empowered product team in one low-risk quarter
The Product Manager's Four Areas of Homework
The four knowledge domains a PM must own because nobody else on the team can bring them
The Product Operating Model
Three dimensions and four competencies that separate companies that consistently innovate from the rest.
The Three Sacred Accesses
Delegate anything off the PM's plate except direct access to customers, engineers, and stakeholders
The Value and Viability Skill Ladder
Climb from backlog administrator to real product manager by owning the two risks nobody else can.
Think First, Then Challenge with AI
Reverse the default AI workflow: form your own answer, then use the model to attack it.
People in these episodes
Related resources
- Adobe
- Airbnb
- Airtable
- Amazon
- Amazon Prime
- Andrej Karpathy's YouTube channel
- Apple
- Apple Podcasts
- Apple TV+
- Arc
- Atlassian
- AWS
- Behance
- BeReal
- BigQuery
- BMW
- Braintrust
- Burning Man
- ChatGPT
- ChatGPT Plus
- Clubhouse
- Coda
- Confluence
- Continuous Discovery Habits
- Cosmos
- Descript
- Discord
- Duolingo
- eBay
- Empowered
- Eppo
- Facebook Ads
- Fargo
- Figma
- Flatfile
- Flexport
- For All Mankind
- GitHub Copilot
- GitHub Enterprise
- Google Analytics
- Google Docs
- GPT-4
- Grammarly
- High Output Management
- HubSpot
- IBM
- Inspired
- iPhone
- iPod
- Jira
- LaTeX
- Lenny's Newsletter
- Lenny's Podcast
- LennyPodcast.com
- Link
- Meta
- Microsoft
- Microsoft Copilot
- Microsoft Word
- Midjourney
- Modern Treasury
- Nest
- Netflix
- Netscape
- New York Times
- Nike
- No Rules Rules
- Notion
- OpenAI
- Optimizely
- Oracle
- Photoshop
- Queue
- Rivian
- Rows
- Ruby
- SAFe
- Salesforce
- SAP
- Scaling People
- Scrum
- Sequoia Capital
- Shopify
- Silicon Valley Product Group
- Slack
- Snapchat
- Snowflake
- Spotify
- Sprint
- Stack Overflow
- Stripe
- Stripe Atlas
- Stripe Billing
- Stripe Connect
- Stripe Sessions
- Substack
- SVPG.com
- Tesla
- The 48 Laws of Power
- The Lost Interview
- The Messy Middle
- Threads
- Thumbtack
- TikTok
- Tome
- Transformed
- Uber
- Ukraine
- Vanta
- What's Our Problem?
- Whimsical
- Working Backwards
- YouTube
- Zoom
Spot an error or want this page removed? Request a correction or removal.