所谓战略，就是一句简单的为什么，再加一件难而正确的大事

Asked for the mindset that most contributed to her career, Anneka Gupta says it is learning to have fun at work even in the hardest times. When things are hard it is easy to operate from scarcity and see everything as an unachievable hurdle. She received this advice when she had to replace all her direct reports in a short period, and reframing the situation helped her get through it and opened her mind to more opportunities.

In practice, she asks what she can learn from a hard situation and what positive outcome it could produce. She also starts difficult meetings on a light note, which lifts her own mood and adds levity for others. As a leader, she says, the point is not only your own mindset but how you transfer it to the people you work with.

She links this to energy management. Skipping lunch with a protein bar lowers her energy, and she knows 5 to 6 p.m. is her worst time of day, so she avoids scheduling hard meetings or strategy writing then. Architecting her day around her energy, she says, helps her keep an abundant mindset.

Gupta credits Paul Graham with naming something many people had seen, and says it opened a valuable discussion for founders and the people who work for them. Working for a founder in founder mode, she says, means recognizing that they have power to redirect or fundamentally change the company, and activating them as an ally for initiatives you know are best.

When a founder pushes an idea she doesn't agree with, she first tries to understand why they are pushing it and what objective they are after. If the idea is the wrong mechanism, she brings alternative options to the conversation. If the founder is set on a pet project, a head of product has to decide which hill is worth dying on and which to let go.

As a leader who is herself said to operate in founder mode, she argues against avoiding the details in the name of empowerment. She collects deep information on what is working, the financial goals and how decisions are made, even when she does nothing with it, so that she knows where to make a big or small course correction.

To bring teams along, she gets in early and asks people to present their strategy so she can ask questions and suggest improvements without overriding their work. She also shares hypotheses, such as feedback from a customer advisory board, instead of only asking questions, because junior people may not voice concerns to a senior leader.

Gupta received the feedback that she wasn't strategic enough in a performance review and again while interviewing for head-of-product roles. Her conclusion is that people asking for someone strategic want two things: someone who can articulate a compelling and simple why behind decisions and direction, and someone who champions hard changes that serve the long-term interest of the product or company.

She says you need both. Great articulation with only small ideas isn't strategic, and big ideas without a clear why won't be seen as strategic either. She focuses on championing a few big ideas that could change the company's direction and explaining each in a simple why.

For Rubrik's three-year planning in cybersecurity, her first tactic is summarization: bringing many voices together, summarizing what was said and what it implies, and checking whether everyone agrees. People treat effective summarization as strategy even when she adds no new idea. She then thinks offline about how to make an idea one click better, from an outside-in view of customer problems and go-to-market, ignoring technical difficulty at first.

Lenny connects this to Roger Martin's idea of betterment and Alex Komoroske's "adjacent possible". Gupta says in the past three to six months she has seen a material difference in the number and quality of big ideas the company pursues.

Gupta says summarizing makes people feel heard and helps diverse perspectives, which yield better decisions, move past conflict toward the heart of an issue. In her view, getting to the very heart of a problem is what the PM job is all about.

In a meeting she might say, "Let me pause here for a second and try to capture what has been said", then state the customer challenges, the way to solve them, why the company has a right to win, and the action. She ends with a question about whether people agree, so she isn't just declaring where the group is. That invites responses like "I agree with 90% of that" and breaks circular debates.

If interrupting is hard, she suggests summarizing on a whiteboard as people talk, or posting the summary in Zoom chat so it can be pulled into the live conversation. Lenny's recap of the two lessons: be crystal clear on the why behind your ideas, and be the person who makes them happen rather than just writing a doc.

Having spent 11 years at her previous company, Gupta was its historian. When she joined Rubrik about three years ago, she set out to learn which products failed and why, how development decisions were made and how people perceived them. She says this lets her learn from mistakes she didn't live through and understand the baggage people carry when she proposes something similar.

A former colleague, Rachel Wolan, remembers Gupta's parting advice: it's not about making the right decision, it's about making the decision. Gupta says leaders always work with imprecise information, and committing teaches you far more than waiting for one more data point. If a decision is around 70% right, you can iterate on the remaining 20 or 30%.

To avoid a culture of fear around bad decisions, she makes the hypotheses behind a decision explicit, including what is known and unknown. If it fails, the team returns to those hypotheses to see what they learned. She says the way to encourage risk taking is to reward the learning, not the outcome.

She shares two lessons from experience: a valuable product that the team initially decided not to monetize and later had to package for monetization, and a product built for a new persona without realizing how hard it would be to sell internally. Her takeaway is to know how you will sell something and who will sell it before building.

Lenny passes on a former colleague's praise for how Gupta brings together high-ego leaders with disparate views. Gupta says she believes she can work with anyone. With a difficult personality she tries to understand what drives them, whether it is the company's success or their personal career, and what would motivate them to care about what she needs.

She also tries to replace anger or frustration with gratitude, asking what she can learn from that person. It could be their communication style, how they marshal people or how they generate visionary ideas, and she then thanks them. Approaching it with an abundant mindset, she says, makes the gratitude genuine.

To learn what someone wants, she talks to people who have worked with them successfully, such as their reports or peers, to build empathy and understand their motivations. Lenny summarizes the technique as connecting what they want with what you are trying to achieve.

On receiving hard feedback, Gupta lets herself feel the defensiveness or upset first, sometimes for hours or days, and does not react. She then asks where the feedback comes from, goes back to the giver or asks a peer for context, and decides whether to act. She believes people's feelings are valid even when you don't act on every item, and coming back curious makes people want to give more.

To decide what to act on, she anchors on what the company needs from her and her team now, separating must-haves from nice-to-haves. Common complaints are that the roadmap isn't moving fast enough, or disagreement about a direction a competitor is not taking. Feedback that attacks her team's culture or says the team isn't listening cuts deeper.

When giving feedback, she says you can't control the response, only your words and body language. She states explicitly that she cares and wants the person to succeed, and then is direct, since passive-aggressive feedback is the worst. She prepares, frames the issue so it doesn't feel like an attack, gives examples including her own, and brainstorms solutions together.

She often opens by asking where the person wants to go in their career, because feedback for an aspiring CPO differs from feedback for someone who never wants to manage. She frames points as how the person is being perceived, which gives them the benefit of the doubt and shifts the conversation to changing that perception.

Gupta moved into product from engineering at the same company, as Lenny did. She says it's easier to switch roles within a company because you have already built credibility. Raise your hand, take on projects, and build a relationship with a product leader who may take a chance on you, drawing on knowledge from support, sales or engineering.

She recommends joining a product-adjacent function, which is nearly every function, and finding your way in from there. Whether to say you want to be a PM in the interview depends on size: at a 20-person startup she said it, but at a 5,000-person company it might land badly. At a very small startup, take on product work that nobody else is doing.

At Stanford, she says, students asked her to teach Figma and other tools, but she believes the real skill is taking ambiguous situations and consistently driving clarity. Teaching also helped her crystallize answers to questions about working with engineering or choosing when the data doesn't pick a direction. In her observation, most students enter through product-adjacent roles or small startups, sometimes as chief of staff or first PM.

In AI Corner, Gupta says her team uses Dovetail to summarize and tag user research calls, so past insights are searchable with context and transcripts. She thinks summarization is a big unlock for PMs and says it's still the very early days of AI making a meaningful difference to how they work. Lenny notes that Dovetail is a podcast sponsor.

Her closing point is that the mindset you bring to work matters more than anything else. To build it, she journaled every day from age 13 to 23 and still writes down negative thoughts, asking why she feels triggered. Putting them on paper lets her see which are irrational and which point to something she should change or discuss, which she compares to doing cognitive behavioral therapy on herself.

In the lightning round she recommends Ben Horowitz's *The Hard Thing About Hard Things* and Brandon Sanderson's fantasy books, and likes the show Fallout and an eight-foot iPhone charger. Her motto is that everyone has something to teach and something to learn, which also helps against imposter syndrome. She can be reached on LinkedIn and is redesigning her Stanford PM class, asking for input from people without PM experience.