Elon Musk sent every Tesla employee a memo that took authority away from their managers and handed it to them.
He never asks for more hours. Every rule moves a decision closer to the person doing the work.
Musk: “Excessive meetings are the blight of big companies and almost always get worse over time.”
Companies have a role for everyone who creates process and no role for anyone who removes it. Meetings and approval chains survive because removing them was never anyone’s job.
Musk: “Walk out of a meeting or drop off a call as soon as it is obvious you aren’t adding value.”
Attendance has always been treated as proof of commitment. He made it worthless, and contribution became the only thing that counts in the room.
Musk: “It is not rude to leave, it is rude to make someone stay and waste their time.”
Ordinary manners protect whoever called the meeting. He moved that protection to everyone else sitting quietly with real work waiting on them.
Musk: “Don’t use acronyms or nonsense words for objects, software, or processes at Tesla. Anything that requires an explanation inhibits communication.”
Internal vocabulary converts knowledge into status and charges every newcomer a fee to participate.
A company that speaks plainly can absorb talent at full speed.
Musk: “Communication should travel via the shortest path necessary to get the job done, not through the chain of command.”
Most good ideas die in transit, three levels below anyone with the power to act on them.
Musk: “Any manager who attempts to enforce chain of command communication will soon find themselves working elsewhere.”
The only threat in the entire memo. A manager who insists on being routed through is buying his own relevance with everyone else’s time. Musk put a price on it.
Musk: “Always pick common sense as your guide. If following a company rule is obviously ridiculous in a particular situation, the rule should change.”
Following a bad rule normally shields you. Exercising judgment exposes you.
He flipped which one carries the risk, and every rule now has to earn its place against the person applying it.
Every institution drifts toward protecting its own comfort. The ones that keep building are held together by people who rewrite the rules back down to something a single person can act on.
Nothing on that list requires a budget, a headcount, or a title.
You can run the entire memo from wherever you are sitting right now. Most people never test it and never learn it was permitted the whole time.
The human system’s default mode is optimized for health. But it’s pushed too far by our choices and it compensates in all kinds of ways until it finally looses that optimization function and purely lives on survival function.
My biggest takeaways from @Netflix's Chief Product and Technology Officer Elizabeth Stone:
1. Elizabeth believes that “systems thinking” is becoming the most important skill in the AI era. In engineering and product, this means people who can see across business domains and build the common capabilities that let many teams move quickly. In design, it means experience designers who create templates and design systems so that non-designers can ship work that stays coherent and on-brand. The underlying driver is velocity: when more people are doing more types of work at higher speed, you need to be good at building common scaffolding.
2. Systems thinking is learnable: zoom out one level from your specific problem. Given a task, step back one click—what bigger problem does this serve the business, will it scale across the product surface areas, should it become a platform capability? The companion habit: do your job in a way that helps your manager do theirs. This will force you to think about how all the pieces fit together.
3. Expect a storming phase before a forming phase. The role confusion people feel right now (“What is my job anymore?”) is the predictable middle of any transformative technology. Elizabeth’s advice: focus on high-quality source-of-truth data, guardrails on what ships, and constant internal reinforcement that humans own what they create.
4. The top AI labs converged on Netflix’s culture. High agency, high talent density, top-of-market pay, bottom-up thinking, fast experiments—the traits Lenny hears constantly from AI labs were in Netflix’s early culture deck. Elizabeth’s explanation: excellence comes from hiring exceptional people, trusting them to do great work, and holding them accountable.
5. Netflix’s culture is centered around building “excellence as an operating system.” High talent density, radical transparency, context not control, and the keeper’s test. These work together to create an environment of trust and accountability, without bureaucracy. But it’s also uncomfortable. It requires tolerating people making decisions you’d make differently, resisting the reflex to add process when things go wrong, and letting people carry the weight of their own choices. Elizabeth describes the hardest part as “being comfortable in that discomfort.”
6. The keeper’s test is as much about recognizing great people as it is about removing the wrong ones. The test—“If this person told me they were leaving, would I fight to keep them?”—is often cited in its difficult form: the moment you realize someone isn’t the right fit. But Elizabeth uses it predominantly as an entry point for honest performance conversations that are deeply positive. Most of the time the answer is “I would fight so hard to keep you,” which creates the opening to articulate strengths, discuss impact, and name what’s working. Good feedback hygiene needs a forcing function; the keeper’s test provides one.
7. Specialization is trending down—adaptable generalists are trending up. We’re shifting away from narrow stack-layer specialists (pure frontend, pure backend) toward people who can navigate fluidly across layers. The same logic applies to business domain knowledge: the mindset of “I’m a payments expert, full stop” is less valuable than “I know payments well enough and I’m willing to imagine what the future version of this looks like.” The meta-skill is learning to learn, not locking into a single lane.
8. Netflix’s approach to AI fluency is a universal principle, not a level-specific expectation. Rather than rewriting career ladders to specify what AI competence looks like at each level, Netflix added a single aspiration across all roles and levels: AI fluency. What fluency means varies by function and seniority, but the non-negotiable minimum is the same everywhere—an open-minded, experimental mindset, genuine curiosity, and comfort with ambiguity.
Forward deployed engg and product is the most effective way to automate finance processes that are poorly documented, have high accuracy bar and have multiple stakeholders many of who are just another reviewer and don’t make sense in the ai + deterministic hybrid world.
The underlying reason why ‘just add another button’ is common in enterprise software is how decisions get made on what is needed. buyer of product sends a requirement by talking to user of product to builder of product and lot gets lost in translation.
.@tobi removed all the Norman doors from Shopify’s offices because he couldn’t have excellent people surrounded by bad design.
Ramp Cofounder @eglyman says he learned the same lesson by studying Breville toasters:
“ If you care about design, you should buy a Breville toaster.”
“ One of the big problems in a lot of B2B software is: it starts out clean and elegant. There's a bunch of businesses who love the product and they start serving more customers and have more requirements and more ideas.”
“Before you know it, you end up with these disasters of B2B softwares which require a PhD to learn how to use.”
“ If you were to go ask people, ‘What do you want in a toaster or in a microwave?’ They might say I like toast but sometimes I want to reheat pizza. I should have a ‘reheat frozen pizza’ mode. Or maybe you're cooking stuff and want it to be more like an oven, or you want to make popcorn and it's a toaster/microwave and all these things.”
“Before you know it, you end up with these toasters filled with buttons and buttons and knobs and dials.”
“That is literally asking customers what they want and building exactly that.”
“ if you watch people toast things, what they actually do falls into two categories: you hit start and either you've undercooked the toast and need to put it back in, or you've overdone it and have to start over.”
“If you look at the [Breville] there are only a few buttons. One of the four buttons is called ‘A Bit More.’”
“ No one would ask you for ‘A Bit More.’ They just want the perfect level of toast and it's hard to know that, so they built that in.”
So much $ lost in corporate travel expenses where a whole team travelling together still expenses hotel room per person for privacy and independence. There must be sweet spot considering people most of the work travel time outside the hotel.
Claude Code eng leader @Nerdi_Yogi on the two profiles she's hiring for now:
1. Creative builders with product sense
2. Deep systems experts (for the hard parts)
Spent 15 min trying to chat with or send a support request to @BiltRewards . The chat in the app doesn’t work and had no luck finding the submit button on their support website :)
We’re now at this point:
Each time I hand draft an email in Gmail or edit a spreadsheet directly in Excel, I wonder jf it’s the last time I do it for the rest of my life.
Top takeaways from @stanine, COO/CPO at @Rippling:
1. Extraordinary results demand extraordinary efforts. “If you ever find yourself in the comfort zone at work, you’ve definitely made a mistake.”
2. Your job as a leader is to preserve intensity, not buffer it. Every layer of management can dilute the founder’s urgency by an order of magnitude. Don’t protect people from high standards. There’s an infinite supply of people who will advocate for relaxation; don’t be one of them.
3. Never be a “chill boss.” Chill doesn’t accomplish anything. Be intense, be respectful, be good, but don’t be chill. Nobody in a position of leadership actually wants to coast. The invigorating message isn’t “Take it easy”; it’s “Let’s go win.”
4. Understaff every project on purpose. When you have too many people, the lower-priority work gets done. It also creates politics and wasted effort. Deliberately keep teams lean. The wisdom is in knowing when you’ve gone too far.
4. Processes exist to reduce volatility—but they they will suppress creativity. Your payroll system should be boring and predictable (low volatility). Your new product experiments should tolerate chaos (high creativity).
5. The “bored and tired zone” is where great teams separate from good teams. Before you hit an inflection point, the work feels endless and unrewarding. You don’t want to write the documentation, you’re sick of the 19th bug. Push through anyway. That’s when competitors lose.
6. Treat escalations and complaints as gifts. Customers don’t want to bother you. Your reports don't want to bother you. That silence hurts you. The only way to improve is to know the problems. Chase them. Every escalation is data on how to make the system better.
7. You learn far more from success than failure. The “failure is the best teacher” line is comforting but misleading. Matt learned more in seven years at Rippling than nine years at his struggling startup. Join winning teams. Watch how it’s done right.
8. If you’re wondering whether you have product-market fit, you don’t. When it arrives, it’s unmistakable. Matt spent nine years at a startup thinking he “maybe” had it. At Rippling, it’s obvious. That’s what PMF feels like.
9. Quitting is sometimes the smartest move. 4-5 years in without clear traction? Maybe it's time to quit. “Never give up” serves VCs, not founders. Time is the one resource you can’t get back.
10. None of this matters—and that’s liberating. We’re on a blue marble drifting through space. Silicon Valley in 2025 is Florence in the Renaissance: a once-in-history moment. Play the sport with everything you’ve got, but never forget it’s just a sport. That perspective is the backstop that makes the intensity sustainable.