“there's a recent book no rules rules think it's called”
No Rules Rules
By Reed Hastings and Erin Meyer
1 recommend/use · 2 sourced episodes
Every sourced reference
Short attributed excerpts only. Timestamps are approximate.
“you can read no rules rules from netflix you can see how that's done”
Related frameworks
Additive Hiring
Stop hiring people who fit the box. Hire people who make the team stronger than it is today.
Calendar-Defended Proximity
Connection to the front line won't happen by accident as you rise — you have to fight your calendar for it.
Context Not Control
Your job as a leader is to give people the context to decide well — including the context that isn't flattering.
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
Excellence Is the Outcome, Not the Artefact
Ask what the meeting is actually for, then spend the effort there — not on the last 20% of polish.
Expectation, Gap, Fill
Set the bar explicitly, name the exact gap, then jump in with both feet and close it with them.
Feature Team vs. Empowered Product Team Diagnostic
Tell in minutes whether your squad is handed features to ship or problems to solve
Solution-Weighted Discovery
Spend a little time validating the problem; spend most of it winning on the solution
Talent Density as Prerequisite
Freedom, low process and candour are not policies you adopt — they are dividends of talent density.
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 Diseases of a Devolving Product Company
Four diagnosable diseases that turn a great product company into a feature factory
The Four Product Risks and Their Owners
Valuable, usable, feasible, viable — any one fails and the product fails
The Full-Stack Centralized Insights Org
Keep data, research and engineering in one central team — objectivity is the asset you're protecting.
The Keeper Test
Ask monthly: if this person quit today, would I fight to keep them? If not, have the conversation now.
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 Three Sacred Accesses
Delegate anything off the PM's plate except direct access to customers, engineers, and stakeholders
People in these episodes
Related resources
- A Fine Balance
- Airbnb
- Amazon
- Amazon Prime
- Apple
- Apple Podcasts
- Beef
- Build
- Chaos Monkey
- Continuous Discovery Habits
- eBay
- Empowered
- Explo
- Fellow Pour-Over Coffee Maker
- Flatfile
- Floodgate
- Inspired
- iPhone
- iPod
- Jira
- Lenny's Podcast
- Linear
- Lyft
- Microsoft
- Modern Treasury
- Netflix
- Netflix Cloud Games
- Netscape
- Optimizely
- Peloton Bike
- SAFe
- Scrum
- Sendbird
- Shopify
- Silicon Valley Product Group
- Slack
- Spotify
- Sprint
- Stripe
- Substack
- The Lost Interview
- Triangle of Sadness
- Uber
- Vanta
- What I Talk About When I Talk About Running
- Whimsical
- Working Backwards
- YouTube
Spot an error or want this page removed? Request a correction or removal.