Shreyas Doshi on Product Metrics and Three Types of Product Leader

Doshi began as an engineer and came to Silicon Valley in 2003 to work with the former Loudcloud team. Exposure to customers drew him toward product questions.

At the time, an MBA was a conventional path into product management. He instead joined Yahoo as a product manager in 2006 and learned on the job.

He defines product management as the art, science and practice of making successful products and making products successful. The distinction matters: building something new is different from growing or turning around an existing product.

Success is not just shipping a feature. Adoption, customer satisfaction and business impact all matter, and the right evidence depends on the product and its stage.

Asked about adoption, Doshi warns against reducing product measurement to a single number. Teams need a set of measures that explains what is happening and what could improve it.

His six categories are health, usage, adoption, satisfaction, ecosystem and outcomes. Adoption is an output; usage can help explain whether customers find enough value to keep using the product.

Treating an output as the whole answer can conceal the inputs that create it. A team needs to understand the behavior behind adoption rather than celebrate an isolated growth figure.

Health metrics are hygiene: availability, latency, errors and data loss, for example. A growth funnel cannot compensate for a product that is unreliable or loses users’ data.

The North Star metric is frequently misunderstood. Doshi says an imperfect measure can still help a team align; finding a supposedly perfect single metric is not a substitute for judgment.

In the early days, qualitative input is particularly valuable. He describes reading free-form user feedback and gaining empathy and insight that a dashboard could not supply by itself.

The founder remains accountable for what the team measures, but need not personally select every metric. Doshi suggests asking honestly whether the founder has the competence to make that decision and delegating when someone else is better equipped.

He distinguishes three product-leadership personas: operator, craftsperson and visionary. These are useful descriptions of strengths, not rigid boxes into which every leader must fit.

The operator aligns functions, communicates priorities and creates the systems that help a growing organization execute. This work becomes valuable as the number of people and dependencies rises.

But an operator is not automatically the right first senior hire. Before product-market fit, a company may need product insight more urgently than the processes that help an established product scale.

Doshi recalls Stripe Connect starting with a small engineering team and growing into a much larger product. He prefers early-stage product work and later moved to Stripe Terminal; his preference is not a universal rule for every leader.

An operator can be powerful once an organization has something that works and needs to coordinate its expansion. A funding round by itself is not proof that this is the right moment.

The craftsperson’s superpower is product insight: translating an ambiguous vision into strategy, user experiences and a product people actually want. Craft also includes helping others develop their own product judgment.

For many early companies, a craftsperson is a strong candidate for the first senior product hire. The choice still depends on what the founder wants to retain and what work needs to be delegated.

If a founder already supplies the core product insight and mainly needs help with operational coordination, a more junior operator can make sense. Hiring should solve the real gap rather than follow a fashionable title.

Scaling changes communication. A message that could once be conveyed through a few direct conversations must be repeated to a much larger group, with care that people understand the mission and priorities.

External coordination also grows: product leaders spend more time with sales, support and other functions. This necessary meeting load may drain a craftsperson who wants to stay close to users and product decisions.

The visionary sees a compelling future others may not yet see. Doshi stresses that a competent visionary must also be right over time; confidence and a persuasive story alone are not enough.

Creative instinct can open a new direction, but translating an abstract vision into a sequence of concrete steps is another skill. A craftsperson can complement a visionary by doing that translation.

Founders often play the visionary role, but roles need not be assigned by formula. As users arrive, their requests pull the product in different directions, making an explicit strategy more important.

How much should a team listen to customers? Doshi says the answer depends on strategy: customer feedback is vital evidence, but following every request can produce a collection of features without a coherent direction.

At Stripe Terminal, the small team faced established competitors with many basic capabilities. Trying to match every feature would have consumed its limited resources and risked creating a me-too product.

His framework separates areas where a product is below table stakes, meets table stakes, and differentiates. A team should deliberately choose where it can accept a shortfall and where it must meet or exceed expectations.

Doshi says he favors being above table stakes in selected areas. The available transcript then has a gap from approximately 45:02 to 47:49; the missing discussion is not reconstructed here.

Angel investing changed his assessment of product ideas. An idea he wants to see exist can attract him, but an attractive idea is necessary rather than sufficient for a successful investment.

He now asks whether a founder is among the most capable people he has encountered and whether that person can build an outstanding team. Execution and the people doing it matter alongside the idea.

Discussing Stripe’s founders, Doshi sees Patrick Collison as a combination of visionary and craftsperson, and John Collison as unusually combining all three personas. He presents these as his own assessments.

Time to value depends on the customer’s motivation and alternatives. A product with many substitutes may need to show its value quickly; a customer with a stronger reason to adopt may tolerate a longer path.

Doshi calls products such as Workday and NetSuite “mandate products”: an organization may decide it needs one even though implementation, training and realization of value can take six to twelve months. Credibility and a clear organizational need help support that wait.

He cautions against treating any one product metric as universally decisive. The relevant signals depend on the product, customer and context.

When hiring a first product leader, founders can overvalue an impressive résumé and suppress their own concerns from the interviews. Look at the whole person and the actual needs of the role.

A new product leader should learn the customer and domain, and begin building strong relationships across the organization from day one. Resist pressure to announce a grand solution before understanding the situation, particularly in the first 30 days.

Doshi identifies product sense as a strength and communicating progress as a weakness. He also highlights Lead School in India, which he advises, for bringing a combination of curriculum, technology and operations to schools in smaller cities.

Stebbings thanks Doshi for the conversation, which closes with Doshi’s appreciation for the discussion.