冷私信请来马斯克，晚宴式社区，以及为什么 Jobs to Be Done 不靠谱

Sriram explains that the Elon Musk invitation started with a cold DM years earlier, when Musk wrote to him while he was at Twitter and asked for something from the company. Sriram offered to help, Musk sent his phone number, and the two had a conversation that grew into a relationship. When Clubhouse launched, Sriram texted Musk to invite him on the show, and Musk said he was game and tweeted about it. That tweet melted Sriram's phone, and Aarthi recalls Clubhouse rooms filling with people trying to collect questions and help them prepare.

Aarthi frames Clubhouse's early growth as a top-of-funnel and status play: Marc Andreessen and Naval Ravikant were invited to speak, and live social audio gave impressive people a new place to pontificate. She defends Clubhouse against the pandemic-fad criticism by noting it was a three-year-old startup whose founders, Paul and Rohan, had been building social products for a decade and still needed time to find product-market fit. The episode also showed how a single high-profile guest can create a growth spike, but retention remains the real test.

Sriram points to Eugene Wei's 'status as a service' essay and its idea that new networks should attract high-status people who are underserved by existing platforms. He contrasts Instagram stars moving to TikTok with TikTok's homegrown creators like Charli D'Amelio, and repeats the Musical.ly founder's analogy of Europe versus America: the people who come may not be kings in Europe, but they can become kings in the new world. Aarthi adds that homegrown talent—people like them, and Lenny on Substack—matters as much as imported celebrities.

Aarthi traces her techno-optimism to a middle-class upbringing in an Indian city that most listeners would not know, where she and Sriram wanted computers before they could afford them. Both sets of parents saved money to buy their first computers, and the two eventually met on Yahoo Messenger while working on a nerdy coding project. Their first jobs were at Microsoft building developer tools and platforms, and Aarthi says technology has given them everything—careers, friends, and the ability to build companies.

Sriram divides the debate into two schools: one believes technology is making things worse and we should build less, while the other believes technology is uneven but responsible for most good things over the last 100 to 200 years. He points to his father, who held essentially the same job from age 25 until retirement and had no easy path out. A laptop, an internet connection, and GitHub would have opened opportunities that were impossible even 30 or 40 years ago.

Sriram's leveling argument is concrete: a king and a peasant once used radically different hardware, but he and Elon Musk probably use the same phone. He notes that many people in India have high-end Android devices and the same internet, and that Google or ChatGPT does not know your net worth when you use them. That shared access is the heart of his optimism.

Aarthi says she spent most of her career believing the standard advice: put your head down, ship good products, and let the work speak for itself. She now rejects that advice for big-company employees in particular, because being one of thousands makes it too easy to disappear. She argues that people must build their own brand, define what they stand for, and put themselves out there—not as self-promotion, but as a way to distinguish themselves from everyone else.

Sriram defines a network as authentic, genuine relationships with human beings, with no expectation of return. He advises meeting every peer, your manager, and your manager's peers for coffee with no agenda, and at Facebook he became known for cold-emailing every leader. Two coffees a week is only two hours, but it compounds over years as people move around and your network becomes a resource for hiring, job searches, and advice.

Sriram warns against the common failure of a great first meeting with no follow-up; he tries to check in every six months or once a year. He also rejects transactional networking, because people can tell when you only want a job or a favor. Lenny cites Naval's advice to create amazing things instead of networking, but Sriram pushes back: inside a large organization it is hard to do great work and get recognized for it, so putting yourself out there matters.

Aarthi says Sriram is genuinely curious about people—their stories, their work, what they care about—and that curiosity is why his network is real rather than performative. Sriram describes himself as a party host who has built more than 100 online communities, curating mixes of thoughtful, controversial, funny, famous, and early-career people. He says he is antisocial in person but loves creating digital spaces where a famous CEO can become best friends with someone in their early 20s.

Aarthi's first rule for community builders is to start small and find a niche instead of launching the world's largest community on day one. She recommends non-scalable work with an oddball set of passionate people, then scaling from there. Her second rule is to think through monetization early, because communities that hit scale without a business model often become less sticky than the price tag they eventually need to charge.

Sriram dislikes the abstract word 'community' and prefers concrete metaphors like a dinner party or a church. A host must tell people what kind of party it is—elite rave or formal seated dinner—because if you do not set the tone, people invent their own. The host must also curate a mix of energies, sense when someone is dominating or silent, and create rituals like a weekly Zoom during Covid.

Sriram notes that a four-person dinner, an eight-person dinner, a 20-person gathering, and a 100,000-person Slack all have different intimacy and different risks of judgment. He is always trying to create smaller, more intimate spaces alongside larger ones. Lenny's Slack is a large-scale example, but the same hosting principles apply.

Sriram strongly disagrees with the idea that people need a certain level of accomplishment before they post, and he does not accept that most content is cringey. He says the fear of judgment stops many accomplished people from starting, and his main advice is to do something every single day so the medium becomes muscle. He also says you do not have to talk about accomplishments; you can talk about your journey, what you are learning, and what it is like to be you, as Charli D'Amelio does on TikTok.

Aarthi pushes back with a call for self-awareness: there is such a thing as bad content, and people should notice when they are not getting traction and improve. She agrees with Lenny that people should not spend too much time sharing wisdom before they have done the thing, and she calls out online LARPers who project a career persona they have not earned. Still, she respects people who keep showing up and iterating in Rocky style.

Sriram's most popular tweet ever was a how-to for writing a cold email, which felt too obvious to him and potentially cringey to his peers. He learned that what is obvious to you can be valuable to many others, and that censoring yourself to sound smart often backfires. He tells a story about a four- or five-year PM who wrote a LinkedIn post on product strategy, then redirected him to a niche topic he had actually researched deeply; the niche post performed better because he was a legitimate expert.

Both say imposter syndrome is real and daily, even for people who seem confident; Aarthi had severe imposter syndrome through school and even at Microsoft, and Sriram felt it at every new job, including when he was told his accent or Seattle background meant he could not cut it in Silicon Valley. Sriram's technique is to retreat to an area of real mastery—at Microsoft it was online developer communities and open source—and build from that base of confidence. Aarthi's founder example was fundraising, where she emailed 250 founders, took 85 meetings, got 50-plus second meetings, and raised 30 checks over eight months while feeling bad at it; she leaned into customer acquisition instead. Lenny adds an executive-coach lesson about accomplishing goals through strengths, and Sriram says performance feedback should focus on superpowers while keeping weaknesses from becoming liabilities. Hunter Walk's trick also helps: you are probably not a good enough actor to be a real imposter, and most people are too busy thinking about themselves to judge you.

Sriram describes the shift from presenting work to reviewing it as jarring because you suddenly have power, implicit feedback, and the ability to upset people by who you invite or overrule. He learned from Zuckerberg's executive reviews that a leader should state the rules of engagement up front: a spectrum from 'I don't care' to 'I'm the founder, just do this.' Zuckerberg also explained why he believed something and said he would let the team overrule him if they could disprove the legs of his logic; Sriram also points to Andrew Bosworth's writing on reviews.

Sriram says meetings fail when an update slides into a decision without anyone naming the change, or when a team tries to push accountability upward by saying it cannot decide. He recommends a pre-read, the right people in the room, full attention, and giving everyone a chance to talk. He also hates 'hero meetings'—big, career-limiting reviews where everyone spends two weeks on a deck and the first 20 minutes go sideways—and prefers a regular rhythm that makes reviews a muscle.

Aarthi's startup failure was a consumer-electronics e-commerce side product inspired by the Uber and shared-ownership fad: let people rent out their own stuff while the main business was doing well. It was a total disaster because it required different logistics, fulfillment, and team focus, and they pulled the plug months later than they should have. Her lesson is not to chase fads and not to distract a small team from what customers are already willing to pay for; she cites a four-person founder trying to build both a consumer product and a B2B SDK.

Sriram's Netflix experiment was Netflix 3D, when TV OEMs like Samsung, Sony, and Panasonic insisted 3D was the future; he spent months on left-eye/right-eye codecs and imported seven titles before pulling the plug. That one at least had clear exit criteria, unlike Microsoft's Visual Studio for Devices, a pre-iPhone IDE for Windows Mobile and Pocket PCs that was built around the assumption that carriers controlled the market and the goal was to kill BlackBerry. The iPhone made the better experience obvious, but management dismissed it as a carrier-controlled market; Sriram's lessons are that the market is bigger than any team and that you should trust your instinct when a product simply feels better.

Sriram says he hates jobs-to-be-done and believes no successful company has been built on top of it. The canonical milkshake example assumes a single customer's job, but real companies face many parameters: the difficulty of building the milkshake, a competitor across the state, cup configuration in the car, and changes in the milk supply chain. He admits the rant is bombastic and that JTBD may be useful in niche cases, but not for building a mainstream company.

His concrete counterexample is Facebook's push to get new users to 10 friends in 14 days. People You May Know made an existing user's experience slightly worse to make a new user's experience better—it performed no job for the existing user, but it performed a job for the new one. Twitter's algorithmic ranking, which power users hated, was built to give regular new users a better experience, and Amazon stopped putting package contents in emails partly to keep data away from Google. Real product work is a series of trade-offs between different users and incentives.

Aarthi agrees that JTBD is too idealistic and maybe useful for a V1 or a hypothesis test, but it falls apart at V2 and V3 when hard trade-offs appear. Sriram prefers systems thinking—map every player, incentive, and interaction—and first-principles thinking—ask how you would build the product if it did not exist today. He points to Duolingo's growth post: jobs-to-be-done might say people hire Duolingo to learn a language, but the breakthrough came from leaderboards, streaks, and fire emojis that tapped psychological motivation, usually from one person's product intuition.

Aarthi's advice to immigrants and newcomers is to put themselves out there, even though it took her and Sriram more than a decade to feel comfortable doing it. They looked different, sounded different, and had strong accents; people told them their accents were hard to understand, and Aarthi was told before fundraising that no one would invest because her accent was too strong. She now sees those differences as what sets them apart, because being rare in a place is an advantage if you sharpen it.

Sriram frames their show as a story of outsiders becoming insiders in tech and Silicon Valley, and he says the playbook is cold emails, networking, and being proactive. At the end he tells listeners that if they are already listening to Lenny's podcast and reading the newsletter, they are already doing something right and putting themselves out there. The closing note is that building and reaching out is how people make it.