给创作者做工具,自己得先当创作者

原标题Make a Podcast to Build for Podcasters: Maya Prohovnik on Dogfooding, Gut Calls and Anchor's Unscalable Hacks

Spotify 播客产品负责人、Anchor 一号员工 Maya Prohovnik 谈狗粮测试、直觉与数据的配合,以及被收购后如何保住创业节奏。

MPMaya Prohovnik嘉宾
频道
Lenny's Podcast
视频
1:07:36
阅读
1 分钟
原文
英语
在 YouTube 打开
往下滚动阅读时,视频会缩到右下角继续播放。字幕跟随阅读语言。
阅读语言共 2 种语言可读
简体中文目前只有摘要,下面的完整文稿是英语原文。
摘要

30 秒看懂

Maya Prohovnik 认为,给创作者做产品的人必须自己过一遍创作者的日子:她本人做了四档播客,也逼着团队去录。她把直觉当成一种需要讲清楚的数据,用两次痛苦的产品转向证明使命可以钉死、其余都可以改。Anchor 早期靠实习生手工提交节目做出“一键分发”的魔法感,被 Spotify 收购后又经历了类似抑郁的空虚——她说,那段过渡几乎没人谈,也几乎没人帮。

  1. 1只看功能需求列表,体会不到创作者真正卡在哪里。Maya 自己做了四档播客,并要求产品经理也去录一档,因为“感觉到问题”和“听说过问题”不是一回事。
  2. 2把直觉当成一种数据,但必须能解释它从哪来只说“我信这个所以我们做”,项目从一开始就完了;用经历、自己的使用和用户故事把直觉讲清楚,别人才跟得上。
  3. 3Anchor 两次大转向都跟当时最开心的用户对着干:第一次离开语音社交去做内容创作,第二次又承认自己就是播客工具。唯一不能改的是“让音频民主化”这条使命。
  4. 4所谓一键上架 Apple Podcasts,背后是一群拿了薪水的大学生实习生,手工注册账号、提交了几十万档节目。包装成魔法,比把流程做得可规模化更重要。
  5. 5被收购在账面上是好事,但创始人常会陷入类似抑郁的存在危机。Maya 希望这种过渡能被公开谈,也希望有人帮一把。
  6. 6上台前的紧张,她重新解释成身体在用肾上腺素帮你准备。笔记定稿后整场至少彩排十遍,并且真的在乎自己讲的东西。
全文

按章节阅读完整文稿

01

不自己做一档播客,就做不好给创作者用的工具

Host Lenny Rachitsky opens by noting that Prohovnik leads podcast product at Spotify, which she says now holds over a third of global podcast listening, and that more than 75% of new shows are hosted with Spotify for Podcasters, the product formerly known as Anchor. A colleague, Wilma Chu, told him the first thing to ask about was dogfooding, so they start there.

Prohovnik has four podcasts of her own. The first was about Stephen King books, which she started when she joined Anchor because she knew nothing about production or what it felt like to be a creator. Another is a weekly Big Brother show with her husband, recorded entirely on a phone with almost no editing, which has survived six or seven years thanks to a community of callers. She also made a niche show about the novel *Children of Time* and a parenting podcast.

She says dogfooding is simply her natural state, shaped by starting her career in customer support and by building tools for people whose livelihood depends on them. Looking at a list of feature requests, she argues, is not the same as feeling a problem, and her product managers who finally start a show tell her they now understand what creators need. She also keeps a mental playbook for would-be podcasters: record with a friend, do not follow a script, and do not publish a 30-second test and call it done.

To keep the habit alive, her team elevates colleagues who have their own shows, builds podcast creation into offsites, and she personally listens to every show her team makes. She admits she once DMed an engineer about an iOS bug at nine at night after recording, and the fix shipped the next day. She is also known for talking nearly everyone she meets into starting a podcast, one person at a time.

02

直觉也是一种数据,但你必须能讲清楚它从哪来

Prohovnik thinks product management has grown more formal and scientific, with teams so focused on frameworks and roadmaps that they build things without thinking about the end user. She loves Spotify's insights team and says data is hugely valuable, but warns against relying on it alone. The trouble starts when a process like running the same insights study for every feature replaces judgment.

She describes a healthier flow: form a hypothesis informed by data, do user research and try a few things, then set success metrics before launch. Different kinds of data suit different moments, and the PM's job is to choose among them. In her view the creative part of the role sits inside that loop rather than outside it.

Moving from a 20-person startup to a large organization taught her that being gut-driven does not mean telling people "I told you so." At Spotify she has to influence many people outside her team, so she explains as objectively as she can why her gut feels the way it does, citing past experience, her own use of the product and user stories. Projects pushed through over everyone's disagreement are, she says, doomed from the start.

03

Anchor 两次改道,都跟当时最开心的用户对着干

Anchor 1.0 was a voice messaging and short-form product, comparable to the Clubhouse rebrand, and people loved it: users stayed up all night, met and even married through it, and the numbers were healthy. Prohovnik and CEO Mike Mignano still felt it would never be big enough for their original goal of democratizing audio. Version 2.0 moved toward content creation, a kind of personal radio station, and she says the decision was made largely on gut and was painful for loyal 1.0 users.

Building a whole new app took a few months, during which the team doubted itself and felt guilty ignoring user requests. Once 2.0 launched, numbers shot up and new kinds of people arrived. The lesson she draws is to tell signal from noise: the team used an 80/20 rule, building for the broad majority rather than the loudest 20%, and she says you must be willing to "kill your darlings."

The second pivot ran the other way. Anchor had avoided the word "podcast" and used nautical terms like waves, but the top request was to export episodes as a podcast. After resisting for around six months, the team tested a small export feature, and the data showed the start of its hockey-stick growth. They then rebuilt the app around RSS and podcasting.

Prohovnik concludes that the mission, democratizing the medium, was the only thing that stayed fixed while everything else was negotiable. She credits her co-founders for sticking to that goal through the acquisition, and notes that you never know which tiny product change will become an existential moment for the business.

04

大学生实习生让一键分发显得像魔法

One of Anchor's early principles was to build things that don't scale. Distributing a podcast meant proving ownership of an RSS feed, sometimes handling 301 redirects, and having an Apple ID, which many people do not have. The team was obsessed with reducing that friction.

Their solution was to hire college interns, whom Prohovnik stresses were well paid. A creator would press one button in the app, and the interns would do all the manual work behind the scenes. People assume Anchor had a secret deal with Apple, but it was students creating Apple accounts and submitting hundreds of thousands of podcasts through them.

The packaging mattered as much as the mechanics. Promising a human response within three days would not have felt magical, while a button that put you on Apple Podcasts about 24 hours later was a huge benefit over commoditized rivals. She believes it was a major reason Anchor won hosting share so quickly, and she urges product teams to answer silly ideas with "yes, and" instead of "no, because." One of those interns is now a PM on her team.

05

收购能做成,是因为你持续有用,并且把价值观带着走

Prohovnik calls Anchor's integration into Spotify a mix of luck and hard work. Both companies faced a chicken-and-egg marketplace problem, with creators on one side and listeners on the other, and both wanted a more democratized, two-way podcasting future. Anchor was about 20 people at the time, and she notes that Spotify had already grown into a company that still makes bold strategic shifts quickly.

Her team deliberately avoided getting lost in the large organization by doing lots of internal marketing, building relationships with every team and constantly offering help. When Spotify's strategy shifted, which she says has happened dozens of times in almost five years, they stayed excited and useful without blindly following. Lenny adds that even performing enthusiasm and then steering things in the right direction is effective.

The team has slowed somewhat, since Spotify's idea of a "small" project was about a quarter, but it kept its four core values, one of which is to move fast. She recalls that Daniel Ek told the team he did not want them to slow down and that he wanted them to help teach the rest of Spotify to move faster. She now sees her job as pushing back on unnecessary things that slow people down.

06

退出的隐性代价是隔离,然后是类似抑郁的空虚

Ek's advice at the time was to say no to meetings and keep being Anchor for a year. Prohovnik says that worked on speed but backfired on belonging, because the team did not build relationships and felt detached from Spotify's mission. The next phase involved integrating deeply, even dropping the Anchor name internally, accepting that closer embedding means slower progress.

She also speaks candidly about something she thinks is rarely discussed: founders who get acquired often go through a deep depression and existential crisis. She did not expect it, since the exit was objectively good for the team, users and the industry. After meeting other acquired founders, she believes everyone must decide either to commit to making a big company work for them or to leave and start something new, and that there is too little support for this transition.

Lenny shares that he had a similar feeling after selling his company to Airbnb, where he ended up staying seven years. Prohovnik says she underestimated how much of her purpose came from the daily survival of a startup, and her fear of being a cog in a wheel faded once she saw she could still run her team her way. Knowing your core values, she concludes, lets you take them with you.

07

反馈要真心关心也要直接挑战,待办则每天清一次

Her favorite leadership book is *Radical Candor*, which she requires all of her managers to read. Its core is to care personally and challenge directly, since doing only one gives ineffective feedback. She has come to see feedback as a gift and to view underperformance as usually a role mismatch, which lets her frame hard conversations around helping someone find the right next step, even if that is outside her team.

The only other framework she leans on is the Eisenhower Matrix, or the four Ds: do, defer, delegate, delete. She skips the grid and runs it as a to-do list in Todoist, going through everything at the end of each day before she lets herself stop working. Getting tasks out of her head matters because deep thinking and problem solving are impossible while she is juggling a list mentally. Lenny recommends *Getting Things Done* and its "mind like water" idea.

08

把上台前的紧张当成肾上腺素,完整彩排至少十遍

Prohovnik says she once decided in high school that she simply would not hate public speaking, after losing sleep over a presentation. Her biggest tip now is to reframe the anxiety as adrenaline preparing you to perform, and to let it wash over you rather than fight it. She also finds that rehearsing at least ten full run-throughs once the notes are final lets her adjust jokes and awkward wording.

She suggests experimenting to find which note style works, whether full sentences or bullets, aiming to be able to ad-lib around half of the material, and maintaining eye contact. Her unfair advantage, she says, is genuinely caring about her topic, since audiences can tell. Personal stories and a bit of humor help too.

Looking ahead, she says Spotify's strategy still centers on its audience of more than 500 million monthly active listeners. She calls discovery and audience growth the biggest problem to solve for podcasters, alongside monetization so creators of all sizes can make a living and more interactive formats. She declines to give specifics but promises more next year.

同频道的其他文章

1:10:27EN → 简体中文
Lenny's Podcast播客 · 2 人对谈硬技能让你进门,软技能决定你能走多远嘉宾 Jules Walter · 主持 Lenny RachitskyYouTube 产品负责人 Jules Walter 把 PM 能力拆成 IQ 与 EQ,并讲怎样用最小请求找到导师、把反馈变成习惯。产品与体验Product ManagementLeadership+3
1:30:46EN → 简体中文
Lenny's Podcast播客跳过「末日漏斗」:Cursor 招顶尖 50 人的打法主持 Lenny RachitskyCursor 人才负责人 Adam Ward 讲如何界定角色、画出全球大约 50 人的名单,再持续追他们,而不是招漏斗里活下来的人。企业与战略Company BuildingLeadership+3
1:42:04EN → 简体中文
Lenny's Podcast播客 · 2 人对谈先做生命体征测试,再谈把付费增长拧到最大嘉宾 Timothy Davis · 主持 Lenny RachitskyShopify 绩效营销负责人 Timothy Davis 讲何时开始买量、怎么做小测试、测哪些平台、看什么指标、以及先招什么样的人。企业与战略Go-to-MarketGrowth Strategy+3
1:21:44EN → 简体中文
Lenny's Podcast播客从划桨到掌舵:OpenAI 如何把 Agent 做成持久共事的同事主持 Lenny Rachitsky负责 Codex 与 ChatGPT Work 产品的 Tara Seshan 解释:当 Agent 负责划桨、人负责掌舵时,产品经理的工作会变成什么样。智能体Product StrategyAI Product Management+3
1:01:00EN → 简体中文
Lenny's Podcast播客 · 2 人对谈谁掌握注意力:Substack 如何按「控制权」做产品嘉宾 Sachin Monga · 主持 Lenny RachitskySubstack 产品负责人 Sachin Monga 讲路线图背后的原则、Recommendations 如何长成增长引擎,以及他认为互联网写作的下一阶段会怎样。产品与体验Product StrategyGrowth Strategy+3
1:26:22EN → 简体中文
Lenny's Podcast播客先从小处开始,再挣来自主权:五十多次企业 AI 落地教会他们的事主持 Lenny RachitskyAishwarya Naresh Reganti 和 Kiriti Badam 解释,为什么 AI 产品需要另一套构建流程,以及怎样一步步提高 Agent 自主权而不丢掉客户信任。产品与体验Product StrategyAI Product Management+3