Vickie Peng on Building Less, Measuring Customer Value and Finding Product-Market Fit

Vickie Peng argues that before product-market fit, a team should pick a measure tied to an action that indicates customers are getting value. She prefers this to relying on a survey score, and says teams usually overestimate how much they need to build before they can learn.

Peng describes product management as bringing structure to messy questions. She enjoys a cycle of building conviction, taking action and using the result to strengthen or revise that conviction.

At TrialPay, she joined a small group testing whether an existing business model could work in social gaming. The work was a side project for a company with an established core business, so she had to show colleagues why it deserved attention as well as build a product customers valued.

Building belief has been a recurring theme in her work at Polyvore, Instagram and Sequoia. Founders, she says, must both build and tell a compelling story to the people who need to understand the opportunity, inside and outside the company.

A common storytelling mistake is to describe the company and its features instead of the customer’s problem and how life changes when it is solved. Differentiation matters most when a customer can repeat the difference in a clear sentence, not merely when the founder can explain it.

At Polyvore, a fashion community, Peng saw users already combining products and making shopping decisions. The company relied on banner advertising, but she believed a performance-marketing business could coexist with the community’s supportive culture.

Rather than build a sophisticated ad platform immediately, the team ran its performance-marketing operation from a spreadsheet for roughly a year. Advertisers emailed account managers to change bids, and the team updated the sheet manually. The experience taught her how much can be learned with very little product.

Peng’s rule is to build only what is needed to move an important measure or learn how to move it. She recommends considering what a product must actually do and what can temporarily be handled by people behind the scenes, even if that manual process will not scale.

At Instagram, she worked on advertising for small businesses, an audience often treated as secondary to larger advertisers. The original goal was to increase monthly active advertisers, based on the belief that acquiring enough small customers would compensate for their smaller budgets.

Looking behind the headline growth, she found a severe retention problem: she says six out of every ten customers who tried the product were gone the following month. New advertisers concealed the losses. She reframed the problem as retaining customers rather than simply acquiring more of them.

Peng joined Sequoia after former Polyvore CEO Jess Lee and partners at the firm considered whether an internal technology platform could help its investment work. She was attracted by the chance to build tools for the firm and now works with early-stage founders in its Arc program.

Her product framework starts with a mission: a qualitative description of success. A strong mission is customer-centered and large enough to guide a team for a decade, rather than describing the next quarter’s feature or business target.

She uses Airbnb’s “belong anywhere” as an example: it describes a change in the customer’s experience and remains an ambition the company can work toward over time. The metric is a separate, quantitative compass that can change as the company matures.

Before product-market fit, Peng recommends measuring an action that represents value delivered to the customer, such as an API call, a query or a dashboard created. She prefers this to NPS for that purpose because behavior can be closer to the moment a customer receives value.

For a robotics company serving laboratories, signed contracts or robots installed are useful business measures, but she suggests robot hours or actions in the lab as a closer measure of value. Other metrics may sit upstream or downstream from that event.

A product strategy starts with the mission and metric, then asks why the metric is below its potential. A team can form hypotheses about the gap and examine behavioral data by customer type, geography, platform or step in a workflow.

Quantitative analysis should be paired with conversations: users can explain why they do not return. Peng cautions that finding a small group that cares deeply is essential, but founders must also ask whether enough similar customers exist to support a meaningful business.

Her own mistake at Instagram was taking a complex advertising platform designed for large advertisers and trying to simplify it for small businesses. A local baker does not have a specialist team managing ad campaigns. The efficient route of reusing the existing product did not necessarily create an effective product for that customer.

Stebbings observes that product-market fit changes by segment and product. Peng agrees: companies may need to find it in a new market, protect it against changing competition or extend it elsewhere. She treats it as an ongoing process rather than a permanent certificate.

Peng’s framework distinguishes three customer mindsets according to their relationship with the problem: “hair on fire,” “hard fact” and “future vision.” The right product and route to adoption depend on whether customers urgently seek a solution, have accepted the problem or do not yet believe the proposed future is possible.

A hair-on-fire customer urgently wants help and actively compares alternatives. Demand may be clear, but the company must stand out in a crowded market. The customer needs to understand and articulate why the solution is meaningfully different.

Founders can overstate how much customers care about a problem. Peng recommends asking the frightening question directly: does the problem actually matter, and does this solution solve it compellingly? An honest answer can quickly challenge an internal story that everyone wants to believe.

For product marketing, she advises using customers’ words. Founders may describe a category and feature set while customers explain a completely different benefit. Even a horizontal product requires listening across use cases and finding the common value in what committed users say.

A hard-fact customer has resigned themselves to an inconvenient state of affairs: “It is what it is.” The obstacle is habit and inertia rather than a crowded set of alternatives. A founder must show that a problem people have accepted can actually be solved.

Peng recalls waiting for taxis after late nights in investment banking, with drivers sometimes refusing to cross the bridge to Berkeley. She accepted the difficulty as normal until new marketplace options offered another way. Changing a habit, she notes, can be harder than differentiating in an established market.

To overcome inertia, the problem must matter and the new solution must be compelling enough to break the habit. Peng describes trying Instacart during COVID after previously taking her young child grocery shopping, then continuing to use it. Stebbings notes that an external event can break habits without guaranteeing the resulting behavior will last.

The third path, future vision, starts with a founder seeing a possible future that others do not yet believe. The obstacle is disbelief. Peng says founders must establish technical validity and find stepping stones that deliver real value on the way to the larger vision.

She uses OpenAI as an example: GPT products and ChatGPT found commercial uses on a path toward the company’s stated AGI ambition, which she says had not yet been achieved. She contrasts progressive milestones with spending a decade in isolation before showing anyone a product.

Peng says Sequoia’s portfolio includes examples across all three paths. Some founders discover that their struggle is not crowded competition but persuading customers that an accepted situation can change. Investors may also gravitate toward different customer mindsets.

Stebbings argues that crowded, urgent markets can require expensive marketing, continuous product improvements and may offer limited pricing power. Peng responds that they also offer a clearer advantage: customers already recognize the problem and may have budgets ready. Each path has trade-offs.

Stebbings describes looking for large, underserved markets with entrenched incumbents and poor underlying infrastructure. Peng introduces a “delta four” heuristic: on a ten-point scale, ask whether the new product is at least four points better. Improving a weak incumbent can be a different challenge from trying to beat an already excellent one.

Stebbings argues that an incumbent’s distribution can outweigh a somewhat better product. Peng agrees that a small improvement may not justify the cost of unbundling a suite. A product needs to be sufficiently better for the particular barrier—competition, habit or disbelief—and the necessary difference depends on the customer and buying process.

Asked why founders fail to reach product-market fit, Peng’s answer is simple: they do not solve a problem that matters with a sufficiently compelling solution. She again urges founders to describe their product in customers’ words instead of assuming they know how customers experience it.

She cautions founders and product leaders against hiring a senior product leader too early without agreeing who owns vision, strategy and execution. At an early stage, she expects the founding team to anchor at least the first two; tension can arise when a founder is not actually ready to delegate them.

Cross-functional tension often comes from rigid boundaries: product, engineering, sales and marketing each insist that the others stay in their lane. Peng favors a team where people have clear responsibilities but can contribute to the whole discussion.

For a new product leader, she recommends first building conviction by meeting customers and studying existing research. Then learn how decisions are made inside the company, who has influence and how work gets done. Both outside understanding and internal execution matter.

Peng admires Linear’s decision to target engineers in issue tracking, rather than starting only with managers and product leads. At Sequoia, she says engineers defended Linear so strongly against a possible tool consolidation that they wrote a four-page memo explaining why they valued it.

She sees Linear’s opportunity as expanding from that core of engineer enthusiasm to products for managers and product teams. The example illustrates her larger point: understanding a specific customer deeply can create a base from which to grow. Stebbings thanks her for the conversation.