产品负责人最该早问自己的四个问题

Shreyas Doshi opens with the question Why am I so busy? He says he spent most of a roughly 20-year product career feeling completely stressed and busy, often going home dissatisfied even after working hard. He only fixed the problem in the last three or four years of his PM leadership career, which means he endured about 16 or 17 years of chronic busyness. That stress eventually showed up as minor physical aches and pains, including a back injury from tennis that left him horizontal for days.

He does not dismiss productivity advice: to-do lists, the LNO framework, and calendar-based work can help. But he argues that product leaders eventually hit an immovable force called scope. As scope grows, no efficiency technique, prioritization framework, or to-do-list system can prevent the leader from being incredibly busy.

The real lesson is that tools are insufficient once scope is too large. Instead of asking how to squeeze more work into the day, Shreyas asks why the workload and scope exist in the first place. He later connects that question to planning rituals and to the quality of product decisions.

Shreyas uses annual planning as a concrete example of busyness that feels mandatory. High-level leaders can lose four to six weeks to spreadsheets, meetings, dependencies, priorities, and stakeholder conversations. During that stretch they may feel guilty about the team they are not supporting and the product decisions they are not making.

The ritual often produces a plan that is revised as soon as customer escalations arrive. By the last week of February, Shreyas says, everyone has forgotten the plan and is executing from some other list. When someone points this out, a smart person in the room invokes the saying that plans are useless but planning is everything, even though nobody knows what it means.

At Stripe, Shreyas had built a real, aligned product strategy for Stripe Connect earlier in the year. When planning season arrived, that strategy let him finish planning for a major product in about three days instead of four to six weeks. He also bent rules by skipping templates that did not make sense. Resource allocation still mattered, but false precision such as arguing over eight versus nine engineers did not.

His tactical advice is to invest upfront in a clear product strategy that everyone understands and has pre-aligned on. With that in place, planning becomes much easier, prioritization becomes more rigorous, and escalations can be evaluated against a framework rather than absorbed ad hoc.

Shreyas's second realization about busyness is that he was not making good enough product decisions. Even after 15 years of building products and 11 years as a product manager, he had to admit that his self-image as a strong decision-maker was not fully accurate. In one pattern, a team meets to decide whether to build a feature and someone invokes Bezos's two-way door idea to justify deciding quickly. The team then skips clear thinking about customer motivation, differentiation, and distribution, and sometimes decides based on whether a particular engineer is free.

In reality, the feature takes five or six weeks to build and more time to ramp. By the quarterly business review, adoption is weak, so the PM leader reaches for favorable anecdotes instead of data. Sales then says the team is still not winning deals because the feature is not complete, and someone says it needs more table stakes.

Once table stakes is uttered, the PM leader says it is already in the plan and asks the engineering leader to confirm that engineers are allocated. The team exits the QBR feeling good, but it has signed up for more work on a feature it should not have built. This is how product leaders accumulate feature debt and stay busy.

Shreyas warns that most doors that look like two-way doors at Bezos's level are one-way doors for a PM leader. His tactical suggestion is to pause for two minutes, two days, or two weeks before making the decision. Thinking is cheap, so leaders should do more of it, not less.

The second question is whether Shreyas actually has good taste. At Google, early in his product career, he was told in some parts of the company that strategy was for MBAs and that execution was everything. He was naive and heard the message consistently, so he repeated it. A wiser PM at his level tried to ask him about his strategy, and Shreyas dismissed the question as unnecessary.

At Twitter after its IPO, he saw a company with a powerful product, network effects, a strong brand, and great talent that was still not meeting its potential. After six to nine months there, around 2014, he concluded that Twitter's biggest problem was a product strategy problem. That experience overturned his Google-era belief, and his later work at Stripe reinforced the value of a clear strategy.

Shreyas argues that taste is not only about beautiful pixels or Steve Jobs-like product polish. For product leaders, taste also applies to the beliefs they choose to create within themselves, because those beliefs shape how they manage, lead, and decide. He realized he did not have good taste in what to believe, what content to learn from, or whom to learn from, even if he had product skills. That realization sent him on a journey to develop better taste.

Shreyas defines taste as the ability to identify what is really good without needing to see its results. Saying in 2024 that NVIDIA's Jensen Huang is a genius requires zero taste because the stock price already proves it. Saying it in 2010 required recognizing qualities that persisted between 2010 and 2024. He calls this game recognize game before the game is called, or recognizing quality in the practice session.

Senior leaders can become tough graders who say everything is crap, but Shreyas says that also requires zero taste. He warns that people get overly excited by catchy metaphors like one-way and two-way doors, even though the same idea was once called reversible and irreversible decisions. They also get impressed by alliterations such as fail fast, which would be less attractive if it were called fail quickly, and by complicated charts or math they do not understand.

He says everyone claims to be a critical thinker, but most people are not. To become a real first-principles or rigorous thinker, Shreyas had to shed social proof and authority proof and evaluate ideas separately from them. That change made him a more critical thinker and marked a meaningful step in his growth as a product leader.

The third question is why the job feels so frustrating. Shreyas says he loved PM leadership and would not exchange the experience, but he faced daily frustrations. A major cause is that the PM leader's job is extremely lonely, even more lonely than the PM's job on the team.

He realized that frustration grows when people spend most of their time behaving in misalignment with their superpowers and who they are at their core. Product work happens at three levels: impact, execution, and optics. Every leader has a preferred level, and Shreyas's happy place was the impact level. As leaders rise, they must spend more time on optics, and willpower is finite, so forcing themselves outside their preferred level day after day breeds frustration.

At Stripe, when the team he managed reached a fan-out of about 50 people, Shreyas decided that was enough. He believed larger teams at the 50, 100, and beyond level would require too much optics work. Rather than push against who he truly was, he went back to an earlier-stage product.

His advice is to identify your superpowers and be true to yourself. Career decisions should not come from expectation, envy, or LinkedIn comparison. When people work in accordance with their superpowers, they do the best work of their lives and feel less frustrated.

The bonus question is whether Shreyas is really listening. He used to think he was a good listener because he would listen, recap, make eye contact, and tell people what he heard. He later realized there is an entirely different level of listening beyond those behaviors.

He calls it perhaps the hardest question for himself. That deeper level of listening, he says, is what enables someone to become a world-class leader. He notes that very few people talk about what real listening means and points listeners toward Rick Rubin and Drucker for further resources.