Kevin Weil on Product Conviction, Communication and Learning from Twitter and Instagram

Harry Stebbings welcomes Kevin Weil, then president of product and business at Planet and an operator in residence at Scribble Ventures. Weil says he once planned an academic career in mathematics or physics. His wife Elizabeth introduced him to the possibilities of startups, and he left a physics PhD to build software.

He joined Twitter when it had about 40 people and progressed from engineering into product leadership. After seven years he moved to Instagram, and later to Planet. He describes the path as unplanned and credits both luck and colleagues who trusted him with opportunities.

A mentor told him that after seven years he might confuse the way Twitter did things with the only correct way. At Instagram he learned another approach from founders Kevin Systrom and Mike Krieger. Weil especially admired Systrom’s editing: refining details until a new feature felt integrated into the existing product.

Instagram teams worked from hypotheses about a user problem rather than simply proposing a feature because it sounded interesting. Weil recalls Systrom deciding that Stories would appear at the top of the main tab and that the team would improve it rather than retreat if the first version was imperfect. The decision gave the team a clear commitment and a hard design problem.

Stebbings asks whether Stories was a reaction to Snapchat. Weil credits Snapchat with discovering a format people wanted and says Instagram had become a place where permanent, public posts felt increasingly pressured. He believes copying a format alone would not have been enough: the team had to understand the problem and integrate it into Instagram.

Weil identifies three design changes. Stories made sharing temporary instead of permanent, feedback private rather than public, and viewing more of a user-selected pull than a feed push. In his account those changes reduced the pressure to post only polished moments. He attributes success to the combination of design and integration, not one feature in isolation.

Prominent placement helped people notice Stories and see friends using it, Weil believes. He contrasts that commitment with hiding a new feature in a remote tab. His account is a retrospective product interpretation from a former Instagram leader, not an experimentally isolated measurement of each design choice.

Testing does not require a timid product, he argues. A team can test an ambitious experience, use a large treatment group with a small holdout, or run a bold test in a limited market. Testing provides information; the scale of the idea and the design of the experiment are separate choices.

On feedback, Weil says there is no formula for knowing when to change direction. Quantitative data is essential, but individual anecdotes can reveal questions that aggregate metrics obscure. He encourages teams to investigate the need beneath a request and avoid leading users toward the answer the team already wants.

His most immediate leadership mistake was indecision after taking responsibility for Twitter’s consumer product. He respected experienced colleagues and heard many competing directions, but disagreements too often led to another meeting. In hindsight he would have made a decision, shipped, learned and corrected course instead of debating indefinitely.

Prioritization starts with a strategy that explains where the organization is going and why. A clear direction gives teams a test for deciding which work belongs and allows them to act without escalating every choice. Without shared understanding, he says, the organization repeatedly debates isolated requests.

For an early startup, the situation is different: before product-market fit, the product or market may change substantially. Weil advises remaining anchored to the underlying problem or belief while staying flexible about the route. He does not recommend treating an early plan as a permanent commitment.

Communication becomes more effective when a leader repeats a small number of important messages. Weil says a leader can feel bored with a point just as the team begins to absorb it and use it in decisions. Repetition only helps if the points themselves are the right ones.

He writes to clarify his own thinking, finding that a narrative forces him to complete ideas more fully than bullet points alone. At Planet he wrote a regular Monday note about his priorities. A reliable all-hands or written cadence gives a team context before a crisis and creates opportunities to prepare people for change.

Communication can break down when one team becomes two and must coordinate across a boundary. Weil warns that “us versus them” language can create tribalism. He tries to emphasize the shared mission and use “we,” whether the split is in a small startup or inside a large organization.

Stebbings asks how to balance revenue with a coherent user experience. Weil recalls Twitter developing advertising within the feed when mobile left no desktop-style sidebar. The team tried to make ads feel native to the product. He argues that monetization and experience can be designed together, although poorly executed advertising can still conflict with user interests.

Looking back at Twitter, Weil describes learning humility. During the Arab Spring he recalls a US State Department request to change planned maintenance because Twitter was important to people in Egypt. The team saw the service’s potential to help people communicate, and adjusted the timing in his account.

Over the following decade he also saw social platforms used for misinformation, bullying and other harms. He says the trade-offs are as complex as human interaction and rejects the idea that the answers are easy. Stebbings responds that users can shape their own feeds and argues against treating all social media experiences alike; they present different perspectives.

His central leadership lesson is to hire people who are better than he is, set direction, support them and give them room to act. Hiring errors happen because interviews provide limited information. A person can excel in one environment and struggle in another, so a departure or failure is not automatically proof of inadequate ability.

People also differ in how they approach uncertainty. Some thrive with a blank page; others excel at improving a system that already works. Weil says these mindsets can be learned and are not destiny, but the situation and the work still need to fit the person.

For references, Stebbings asks what a person hired beneath the candidate should be good at, hoping to reveal complementary weaknesses. Weil describes seeking a balance between people who challenge and initiate change and those who bring people together. Asking what peers would say may elicit observations a reference hesitates to state directly.

Both worry that excessive process can crowd out product craft. Weil acknowledges his own tendency to introduce process too late, but prefers some freedom to too much control. He believes a bold direction, talented people and room to execute can produce ambitious work; the organization’s incentives affect what it gets back.

At Scribble, an early-stage fund, Weil gives the founder particular weight because the initial market and product can change. He looks for ambition, clear thinking and conviction while still requiring a plausible market. Stebbings places more weight on market risks that a founder may not control; their emphasis differs.

Weil also cautions that a market can grow as a new product creates demand, citing the historical development of software as a service. At Planet he sees the company as helping build a market and expects it to become much larger. That is his forecast as a Planet executive, not proof of future market size.

Scribble asks what must be true for an early company to become roughly 100 times its current size or valuation. A story dependent on one central development is easier to evaluate than one requiring several unrelated events to align, Weil says. This is a screening heuristic with uncertain assumptions, not a forecast of a 100-fold return.

Investing has made him a better operator by exposing him to many company journeys. Biographies often make success appear linear, he says, while actual paths include pivots and unexpected turns. He and Elizabeth had invested in more than 100 companies by the time of the interview, broadening the examples he could draw on.

There is likewise no single way to lead or invest. Weil says trying to copy a leader whose style is unlike his own would not work for him, even if that leader achieved a great deal. Stebbings agrees that investors should identify their particular strengths instead of trying to copy every successful model.

Weil places substantial weight on mission: in a difficult period, a team that understands why it exists can ask whether that purpose is still achievable. Stebbings adds that few companies can explain what they do succinctly. Weil believes clarity matters internally as well as externally because employees need to carry that mission into decisions.

Asked about successful investments, Weil mentions Whatnot and emphasizes that a promising idea must eventually be matched by team building, strategy and delegation. He acknowledges luck in investing. His discussion reflects his and his firm’s financial interests, and he does not provide a verified realized return for the example.

Stebbings challenges the idea that founders and investors are always aligned, especially when a fund wants a larger allocation. Weil admits he sometimes worries about being too accommodating, but says he would rather earn future opportunities through useful work and long-term relationships than damage trust to obtain more ownership immediately. This is his approach, not a guarantee of aligned interests.

His missed investments include people he had worked with who struggled in a previous setting and later built successful companies. He had attributed their earlier performance too strongly to the individual rather than the environment. The lesson for him is to reassess people in the context of the role they are taking on.

In the quick-fire round, Weil describes using difficult moments in long races as a reminder that feelings can change. He says consistent exercise has mattered more to him than switching between training trends, and describes varying intensity based on how he feels. These are personal experiences, not training or medical advice.

He praises board members Peter Fenton, David Rosenblatt and Carl Bass for being available and useful when a company needs help. He would like to see less hype and more practical work for founders in venture. His assessments are personal and reflect his working relationships.

Among product leaders, he credits David Marcus with setting a direction, trusting the team and stepping in when needed. Weil has tried to carry that combination forward. He views building a strong team and giving it responsibility as central to effective product leadership.

Asked how he balances work, investing, training and family, he says he has not solved it and describes sacrificing sleep. He recognizes that very little sleep is probably not good for him and wants to improve his efficiency and ability to say no. His schedule is a personal account, not a recommendation.

He and his assistant regularly review recurring calendar commitments for usefulness. His latest publicly announced investment at the time was Fig, a developer terminal company. He says he first invested personally and then through Scribble; his praise of the founders and product therefore comes with a direct financial interest.

Stebbings thanks Weil for a broad conversation covering product leadership, investing and personal routines. The available captions end during the closing exchange, so the final words are not reconstructed.