Meta 的 Muse:如何打造今年最成功的消费级 AI 产品

Meta's Muse: Building the Fastest-Growing AI Consumer Product

莫娜·萨兰塔科斯 Mona Sarantakos · Lenny’s Podcast · 2026-11-15 · 约 87 分钟 · 原视频 ↗

打开互动全文版(中英对照 + 朗读 + 问答)→

本期速览 · Overview

Meta 超级智能实验室产品副总裁 Mona Sarantakos 讲述 Muse 如何从一个周末在树莓派上折腾 OpenClaw 的实验,成长为增长最快的消费级 AI 产品,以及团队为何足足等了七个月才发布。

Mona Sarantakos, VP of Product at Meta Superintelligence Labs, on how Muse went from a weekend with OpenClaw on a Raspberry Pi to the fastest-growing consumer AI product — and why the team waited seven months to launch.

要点 · TL;DR

核心观点 · Key points

反共识 · Contrarian takes

本期章节 · Chapters(共 47)

全文 · Full transcript(中英对照)

引言与起源故事 Introduction and Origin Story

Host

你是 Muse 的产品负责人。每个产品经理的梦想都是打造 App Store 排名第一的应用。

You are head of product for Muse. Every PM's dream is to work on the number one app in the App Store.

Mona

我以前从未经历过这样打造的产品。我们会把手机递给马克,问他“你觉得怎么样?”,他会玩一玩然后给我们反馈。

I've never experienced a product built like this before. We would give Mark our phone and be like, what do you think? And he'd play around with it and give us feedback.

Host

你从一开始就在那里。

You have been there from the beginning.

Mona

Nat Friedman 给我们几个人发了消息。他说:“我在用 OpenClaw,你们得赶紧上手。”我整个周末都在和我的 OpenClaw 对话。它给我的指令那么少,却感觉很神奇。我们越用这个产品,就越觉得,好吧,如果想为我们的消费者群体打造它,它必须非常不同,必须安全得多。

Nat Friedman pinged a few of us. He's like, I'm using OpenClaw. You guys need to get on it. And I spent all weekend talking to my OpenClaw. It felt pretty magical with such little direction from me. The more we were using the product, it was like, okay, if we want to build it for our consumer base, it has to be really different. It's going to have to be way safer.

Host

感觉你们在这方面遥遥领先,但你们花了很长时间才推出东西。

Felt like y'all were way ahead of this, but it took you a long time to launch something.

Mona

我们内部有句话:信任是必须的。如果我们过早发布,出现一堆问题,人们就不会信任这个智能体。如果你不信任这个智能体,你就永远不会用它。

There's a saying we have internally, trust is a must. If we launch too early and we have a bunch of issues, people will not trust this agent. If you don't trust the agent, you're never going to use it.

Host

那个小角色 Jolly,不是你会从 Meta 这样的公司——像一家巨头公司——期待的东西。

The little character Jolly, not something you'd expect from a company like Meta, like a massive company.

Mona

Jolly 就像我们的蟑螂,就是不死。每隔几个月,就会有人说:“你不可能在顶部放一个毛绒玩具就发布这个产品。”但我觉得,当你和某个感觉如此私人的东西对话时,你最不想对话的就是一个公司标志。

Jolly is like our cockroach. It just like never dies. Every few months, somebody would be like, there's no way you're going to launch this product with a stuffed animal at the top. But I think when you're talking to something that feels so personal, the last thing you want to talk to is a corporate logo.

Host

接下来是什么?这个方向的愿景是什么?

What's next? What's kind of the vision of where this heads?

Mona

现在,它有点被困在一个应用里。很快,它应该出现在你的眼镜里、你的挂饰设备上,不管那是什么。

Right now, it's sort of trapped in an app. Soon, it should be in your glasses, on your charm devices, whatever that might be.

Host

活着真是个好时代。

What a time to be alive.

Mona

我小时候,你能想象吗?我得走到电视机前拧旋钮才能换台。而现在我在谈论你眼镜里的个人超级智能。

When I was a kid, could you imagine? Like I had to go up to the TV and turn the TV dial to be able to change a channel. And now I am talking about personal superintelligence in your glasses.

Host

Mona,非常感谢你来这里,欢迎来到播客。

Mona, thank you so much for being here, and welcome to the podcast.

Mona

谢谢你,Lenny。谢谢你邀请我。

Thank you, Lenny. Thank you for having me.

Host

你是 Muse 的产品负责人。你是 Meta 超级智能实验室的产品副总裁。嗯,Muse 有点横空出世的感觉。我觉得它——我不知道具体数字——但感觉它是目前最成功的 AI 助手。扎克伯格暗示它是史上增长最快的 AI 消费产品。呃,呃,你从一开始就在那里。你也没上过任何播客。你在社交媒体上几乎没发过东西。你在 Threads 上大概发了五条,领英上一条。所以这特别棒。这是我最喜欢的对话。做着了不起工作的人,却没人真正听说过。所以我有很多问题。我想从 Muse 的起源故事开始,还有你开始这项工作的故事。你加入这个团队之前在做什么?然后他们给你的“推销”是什么?当他们说服你承担这项工作、加入这个团队时,那个想法的核心是什么?

You are head of product for Muse. You're VP of product at Meta Superintelligence Labs. Um, Muse has kind of come out of nowhere. I feel like it's I don't know what the numbers are, but it feels like the most successful AI assistant out there right now. Zuck has hinted that it's the fastest growing AI consumer product of all time. Uh, Uh, you have been there from the beginning. You've also not been on any podcasts. You've also barely posted anything on socials. You've had like five posts on Threads, like one LinkedIn post. So this is extra awesome. These are my favorite conversations. People doing amazing work that nobody has really heard from. So I have so many questions. I want to start with just kind of the origin story of Muse and kind of your story of of of getting started on this work. What was what were you working on before you joined this team? And then what was kind of the the pitch they made you? What was kind of the kernel of the idea when they pitched you on taking on this work, joining this team?

Mona

我当时在 AI 组织和超级智能组织里,之前我已经做了大约两年。我在 Meta 大约 10 年了。我主要在做 Meta AI,那是我们的助手产品。当时我们正在对 Meta AI 进行“零基重构”,这是我们常用的说法:我们有个东西,它没有完全按我们想要的方式运作,你可以继续优化或迭代,或者干脆从头开始。所以我们对主要的 Meta AI 产品做了很多这样的工作,因为实验室正在开发这个新模型,那是我们期待的 Muse Spark 系列的第一款,它很棒。我们当时很开心。然后大概在周四,可能是一月底或二月初,Nat Friedman 给我们几个人发了消息,他说:“我在试用 OpenClaw。它改变了我对个人超级智能和消费者智能体可能性的整个看法。”我们之前已经讨论过很多次了。显然每个人脑子里都在谈论这个。我记得我实际上在一份 H1 简报里写过,我说我们可能会在 2026 年底或 2027 年做这个,对吧?那大概是我认为这类事情会达到高潮的时间框架。所以那就是我们当时的状态,然后他给我们发了这条消息。他说:“我在用 OpenClaw,你们得赶紧上手。”所以周五,我告诉我丈夫:“我得去找一台 Mac Mini,我需要把 OpenClaw 设置好。”我们查了 Apple Store,没有 Mac Mini。然后他说:“我记得我哪里有个树莓派。”于是他拿出了他的树莓派,我们设置好了。那正好是个周末。我的孩子们参加滑雪比赛项目,所以周末大部分时间都去滑雪了。所以只有我和我的 OpenClaw。我整个周末基本上都在和它对话。然后,我丈夫周日带着孩子们回来了。他问:“怎么样?”我说:“哦,我给了它访问我邮件的权限,给了它访问我日历的权限。”他说:“你在干什么?那太疯狂了。那太不安全了。”我说:“不不,完全没问题。我想走极端。”所以那是周日。我整个周末都在和它对话、设置它,把它连接到我的家庭自动化系统等等。然后周一早上,孩子们去上学。我在个人邮件方面真的很差劲,也不太跟进学校的新闻简报和门户网站。我从来不检查。所以我的孩子们,你知道,我们尽力了,但他们经常搞不清“精神周”之类的特殊活动。然后我从我设置的 OpenClaw 那里收到了一份新闻简报。它检查了所有这些不同的来源,汇总了一份快照,比如这周要期待什么、今天要期待什么。我记得看着它。现在回想起来,好吧,很多人能做到,甚至助手也能做到。但当时,它感觉相当神奇,而且我给的指令那么少。我写的提示词那么小,对吧?可能就几个词。突然之间,我能感到非常有生产力、掌控全局——这在周一早上我从未有过,尤其是在个人生活中——这对我来说太不可思议了。我看着它,心想:有多少忙碌的父母?有多少忙碌的人?有多少人有这种感觉?所以,我给 Nat 发了消息,我说:“就是这个。我觉得我们得做,我加入。我不知道我要面对什么。”

I was on the um in the AI org and the superintelligence org uh before I've been I've been working on it for about two years. I've been at Meta for about 10 years. Um and I was mostly working on Meta AI uh which is our assistant product. Um and we were zero basing Meta AI at the time and it's a phrase that we use a lot where we're like, you know, we have something it's not working quite the way that we want it to and you could keep optimizing it or iterating on it um or you could just start over. Um and so we were doing a lot of that with the primary Meta AI product because the lab was working on this new model which was the first of the Muse Spark series um that we were anticipating and it was awesome. We were having a great time. And then I think on like Thursday, maybe end of January or beginning of February, Nat Friedman pinged a few of us and he said to us, I'm trying out OpenClaw. It's changing my whole view of what's possible in terms of um personal superintelligence and you know, consumer agents which we had been talking about quite a bit. Um obviously everybody was sort of talking about it in our head. I think I wrote this down actually in like an H1 brief. I was saying that yeah, we'll work on it probably end of 2026 maybe 2027, right? Like that's kind of the time frame when I think that this sort of thing is going to be coming to a head. Um and and yeah, so that's sort of like where we were at and then so he sends us this message. He's like, I'm using OpenClaw. You guys need to get on it. So I think on Friday, I was told my husband, I'm like, I need to go find a Mac Mini. I need to get OpenClaw set up. And we looked at the Apple Store. There were no Mac Minis. So then he was like, I think I have a Raspberry Pi somewhere. So he got his Raspberry Pi. We set it up. It happened to be a weekend. My children are in they're in a ski race program. And so they were gone for most of the weekend skiing. So it was just me and my OpenClaw. And I spent all weekend essentially talking to it. And like, you know, I had at this point, I think my husband came back on Sunday with the kids. And he was like, how's it going? I was like, oh, I gave it access to my email. I gave it access to my calendar. And he was like, what are you doing? That is crazy. That is so not safe. And I was like, no, no, it's totally fine. I wanted to like, I'm going maximalist. So this is like a Sunday. I had spent the whole weekend talking to to this and setting it up and hooking it up to my home automation, all of this stuff. And then Monday morning, my kids are going to school. And I'm just really bad at personal email and like just staying on top of all the school newsletters and the portal. I never check it. Like so my children are, you know, like we do our best. Um but they're often not figuring out Spirit Week or anything like that, all of these kind of special things. And and I had gotten a newsletter from my OpenClaw that I had, you know, kind of set up. And it was checking all of these different sources. And it sort of pulled together this snapshot of like what to expect this week, what to expect today. And it was like, I remember looking at it. Now in retrospect, it's like, okay, a lot of people can do that. Even assistants can do that. But at the time, it felt pretty magical and with such little direction from me. I had to, you know, it was like such like such a small prompt that I had written, right? Maybe like a few words. And the idea that I could kind of suddenly feel really productive and on top of my which I never felt on a Monday morning, right? Particularly in my personal life, was like incredible for me. And I looked at it and I was like like, you know, how many busy parents are there? How many busy people are there? How many people feel like this, right? And So anyway, so I pinged Nat and I was like, this is it. I think we got to, you know, I'm in, right? Like, I don't know what I'm in for.

想法的起源 Origins of the Idea

Mona

没有人下过“我们要做这个”之类的命令,但我说过,无论你想往哪个方向走,我都跟着你。我们几个人也有同感。所以,你知道,我们在 Meta AI 有一个很棒的团队,因此我们几个人抽身出来开始实验,看看这个概念能走到哪,完全没问题。但这真的是第一次感觉我们一直以来的这个想法——马克其实在这之前就写过一些东西。如果你回去读他关于个人超级智能的文章,会发现其中很多都真的在成真,通过这个框架以及让这些模型变得更真实的想法。所以那与其说是一个提案,不如说是一个信号,最终完全占据了我。而且,你知道,甚至没有一个工作流,不是一个可以加入的产品或团队。只是我们几个人决定看看能不能构建类似的东西,因为我们也在意识到,随着我们越来越多地使用这个产品,就像,好吧,如果我们想为我们的消费者群体构建它,它必须非常不同,对吧?它必须更安全,必须更容易设置,必须可扩展。就像,我们开始发现所有这些其他问题,在魔法之间,我们意识到,对于个人智能体,我们真的必须做出一些巨大的赌注和尝试。但因为我们不太知道那是什么,我们不想立即将其正式化为一个官方项目,它在一段时间内停留在尝试和原型制作的区域。然后某个时候我们说,好吧,这就是个东西了。我们相当确定我们会有一个产品。那时我们才动员了一个合适的团队围绕它。

Nobody had ever done like an edict of like we're going to build this or anything, but I was like, wherever you want to go with this, I'm going with you. And a few of us kind of felt that way as well. And so, you know, we had a really great team on Meta AI and so it was like totally fine for a few of us to peel off and start to experiment and see where this concept went. But it really for the first time felt like this idea that we had been—and Mark actually wrote something about this, you know, before any of this started. And if you go back and read his writing about personal superintelligence, it's kind of crazy how much was actually coming true with this harness and this idea of being able to take these models and making them far more authentic. So that wasn't really a pitch as much as it was like a ping that just ended up consuming me completely. And, you know, there wasn't even like a work stream, it wasn't like a product to join or a team to join. It was kind of like a few of us that decided to see if we could build something similar because what we also were realizing was as the more we were using the product, it was like, okay, well, if we want to build it for our consumer base, it has to be really different, right? Like, it's going to have to be way safer, it's going to have to be way easier to set up, it's going to have to be scalable. Like, there are all of these other issues that we started to find in between the magic that we realized, you know, for what we would want to do with a personal agent, we would really have to make some huge bets and swings. But because we didn't quite know where that was, we didn't want to formalize it immediately as like an official project and it kind of stayed in this like zone of like trying things out and seeing what worked and prototyping for a bit. And then at some point we were like, okay, this is a thing. Like we're pretty sure that we're going to have a product here. And that was when we sort of mobilized a proper team around it.

赞助商信息 Sponsor Message

Host

本集由本季度的呈现赞助商 WorkOS 带来。OpenAI、Anthropic、Cursor、Replit、Sierra、Clay 以及数百家其他成功公司有什么共同点?它们都由 WorkOS 提供支持。如果你正在为企业构建应用,你一定感受过集成单点登录、SCIM、RBAC 和审计日志的痛苦。WorkOS 将这些交易障碍转化为专为 B2B SaaS 构建的即插即用 API。现在有一种新型用户需要访问你的应用:智能体。AI 智能体需要像人一样注册、认证和获取权限。WorkOS 处理所有这些。智能体授权为智能体提供范围、可撤销身份,智能体注册与认证和 D,以及 airlock 来评判每个智能体操作并允许、拒绝或升级给人类。我注意到,我投资的每一家向高端市场扩展的初创公司最终都使用了 WorkOS,因为他们是最好的。今天就访问 workos.com,让你的应用为企业做好准备。

This episode is brought to you by this season's presenting sponsor WorkOS. What do OpenAI, Anthropic, Cursor, Replit, Sierra, Clay, and hundreds of other winning companies have in common? They're all powered by WorkOS. If you're building for enterprises, you have felt the pain of integrating single sign-on, SCIM, RBAC, and audit logs. WorkOS turns those deal blockers into drop-in APIs built for B2B SaaS. And now there's a new kind of user that needs access to your app: agents. AI agents need to register, authenticate, and get permissions just like a person. WorkOS handles it all. Agent auth to give agents scope, revocable identities, agent registration with auth.md, and airlock to judge every agent action and allow, deny, or escalate to a human. I've noticed that every startup that I'm an investor in that expands upmarket ends up using WorkOS because they're the best. Go to workos.com to make your app enterprise ready today.

开发时间线 Timeline of Development

Host

关于这个时间线,有一件有趣的事。那么那个 Nat 的信号大概是什么时候,他就像“让我们开始探索这个”?你记得大概是什么时候吗?

One thing that is interesting about this timeline. So when was that Nat ping roughly where he's just like let's start exploring this? Do you remember what it was roughly?

Mona

大概是1月底、2月初。因为像 OpenClaw,对吧?那大概是在那个时候发生的,1月、12月、1月,我觉得那是所有这些开始的时候。所以肯定是在1月底我们开始对话。但直到2月我们才确信这是我们真正想要追求的,而不仅仅是我们玩一些概念。

It was like end of January, beginning of February. It was because like OpenClaw, right? That was happening sort of around that time, like January, December, January, I feel like was when all of that was kicking up. So it must have been end of January when we started the conversation. But it wasn't until February when we were like confident that this was something that we wanted to like truly pursue beyond again like us kind of playing around with some concepts.

为何等待良久 Why the Long Wait

Host

真正有趣的是,感觉你们比所有其他现在流行的 AI 助手都早得多,但你们花了很长时间才推出产品。我相信 Grok Bot 从想法到推出花了几个月。我想 Duet 也是类似的时间线。Dots 也是类似的时间线。根据我读到的,你们从头到尾花了七个月。我想等待那么久有很好的理由。谈谈不更快推出的决定。

What's really interesting about this is it felt like y'all were way ahead of this much earlier than all of the other what are now popular AI assistants, but it took you a long time to launch something. I believe Grok Bot took a couple months from idea to launch. I think Duet is a similar timeline. Dots is a similar timeline. Took y'all seven months from what I've read from beginning to end. I imagine there were very good reasons to wait that long. Talk about that decision of not launching it quicker.

Mona

首先,我认为在那段时间里有很多时刻我们觉得“我们快好了”,然后就会发生一些事情让我们多想一下。但我想说,我们的工作大概有三个阶段。第一个阶段就是:这个产品是什么?我们在构建什么?对吧?在那个阶段,我们不太担心可靠性、可扩展性和安全性等等,因为只有我们几个人在用。而仅仅是弄清楚这一点——我们做的事情没有太多先例,最接近的先例又是 OpenClaw,那最终是一个非常非常不同的产品。但仅仅是弄清楚如何运行一堆虚拟机,本身就是一个有趣的问题。我认为我们在产品中的某些决策上纠结了很多,比如它应该是一个聊天线程吗?它应该更像一个助手吗?一些设计选择,我们可以稍微谈谈。但那些都相对较快地整合在一起。到了春天,我想我们觉得,好吧,我们有了一个相当功能完整的端到端产品。但你知道,我认为我们最终真正花了很多时间的是可靠性、安全性和安全性。这三个领域,我们的标准一直很高。我记得我们有过这样的对话:评估标准是什么?同样,因为没有太多先例,我们无法真正比较,行业中的基准测试感觉不足以达到我们想要的水平——我的意思是,它涉及你的个人上下文,对吧?它可以出去为你买东西。它可以做事情,所以感觉我们需要达到一个完全不同的标准,我们必须自己创造。并且花了很多团队时间进行红队测试。然后新功能会突然出现,对吧?比如一开始,Muse 没有浏览器。但后来有了。然后当有了浏览器,突然你有一整套新问题需要解决,从安全角度。所以当新功能出现时,我们认为关键的,会打开新的向量,我们必须确保完全关闭。

First of all, I think there were many moments throughout that period where we were like, I think that we're close, and then something would happen to cause us to like think a bit more. But I would say like the things that there's like there were sort of three phases of the work that we did. The first was just like what is this product? What are we building? Right? And in that phase like we didn't worry so much about like reliability and scalability and safety and all of that because it was just a few of us using it. And just that piece of like figuring out there's not a lot of precedent to what we were doing in terms of like the closest precedent again is like OpenClaw, which is you know a very very different kind of product in the end. But just figuring out how to like run a bunch of virtual machines, right? Was like its own interesting problem to solve. I think we agonized a lot about certain decisions within the product like you know should it be a chat thread? Should it be more like an assistant? Like some design choices and we can talk a little bit about that. But those all kind of came together and relatively quick. Like by spring I think we were like you know okay we've got like a pretty fully functioning end-to-end product. But you know I think the things that we really ended up spending a lot of time on was reliability, safety, and security. Like those three areas were we just were never like our bar was so high. And I remember we had these conversations where we were like well what's the eval bar? And again like because there wasn't a lot of precedent, right? Like we couldn't really compare and the benchmarks that are out in the industry just didn't feel sufficient to where we wanted to be for a product that's this—I mean it's got your personal context, right? Like it can go out and buy things for you. It can you know like it could do things and so it just felt like we needed to hit a totally different bar that we had to kind of create on our own. And like spend a lot of team time red teaming. And then like new features would kind of pop up, right? Like in the beginning in the very beginning Muse didn't have a browser. Right? So but then it did. And then when have a browser, suddenly you have a whole new set of problems that you have to solve, you know, from a security angle. So as like new features would kind of come in that we felt were critical, it would open up new vectors that we had to make sure were like completely closed off.

发布时机与质量门槛 Launch Timing and Quality Gate

Mona

所以,你知道,我觉得我们基本上——我的意思不是说我们压着产品不发,而是我们真的很想确保我们做好了质量把关,因为我们内部有一句话:信任是必须的。但真的,就像我们当时——你知道,如果我们发布太早然后出了问题,比如我们有一堆问题,那就完了,对吧?人们就不会信任这个智能体。如果你不信任这个智能体,你就永远不会用它。所以我们觉得我们需要达到那个点。嗯,所以,回想起来,我丈夫前几天还问我这个。他说,你希望你们早点发布吗,因为所有这些其他智能体都开始出来了,对吧,差不多同一时间?我觉得我不会改变任何东西。我真的觉得我们——有一个我们需要达到的标准。我们花了我们需要的时间来达到那里。我很高兴我们做到了,因为到目前为止我们还没有遇到灾难性的问题。嗯,我觉得我们只是继续——你知道,整个行业在这个领域还太早期,还有太多未知的未知。所以我们永远不会完美。但嗯,但就是这样。所以那大概就是情况。我们也在内部做了很多吃自己的狗粮,让员工使用它,你知道,我们也有外部 alpha 测试者在使用它。所以感觉就像我们——不是发布产品,而是让越来越大的群体使用它并给我们发送大量反馈。嗯,所以整个夏天确实感觉我们开始得到真实用户的反馈,所以到最后我们感到自信多了。

And so, you know, I think that we basically—I mean, it wasn't like we held the product, but it was kind of like we really wanted to make sure that we were quality gated, because there's a saying that we have internally: trust is a must. But really, like we were like in that—you know, it's like if we launch too early and we have an issue, like we have a bunch of issues, like that's it, right? People will not trust this agent. And if you don't trust the agent, you're never going to use it. And so we just felt like we needed to get to that point. And yeah, so in retrospect, my husband was actually asking me this the other day. He was like, do you wish you had launched a lot earlier because all these other agents started to come out, right, kind of around the same time? And I don't think I'd change anything. Like I really think that we—like there was a bar we needed to hit. It took us the time that we needed to get there. And I'm glad that we did because we so far haven't had a catastrophic problem. And I think we just continue to—like you know, the whole industry is so early in this space that there's still just so many unknown unknowns. So we're never going to be perfect. But yeah. So that was kind of the thing. We also did a lot of dogfooding internally where we had employees use it, and we had alpha testers externally using it. So it sort of felt like we were—like not launching the product, but we were getting bigger and bigger groups of people who were using it and sending us a bunch of feedback. So it did feel like throughout the summer we were starting to get real user feedback so that by the end we felt a lot more confident.

内部格言:信任至上,利爪为法 Internal Mottos: Trust is a Must and Claw is the Law

Host

你提到了这句话,信任是必须的。我还听过其他一些说法——怎么说呢,你们内部用的座右铭。我想了解它们是什么意思。其中一个是“爪子就是法律”。那是怎么回事?

You mentioned this phrase, trust is a must. I've heard other phrases—kind of, I don't know, mottos internally that you all use. I want to understand what they're about. One is the claw is the law. What's going on there?

Mona

好的,所以是的,那是在最初那几天我们使用它之后发生的,这也是 Nat Friedman 的特别之处,当我们——我们看到了某种魔力,对吧?就像这个概念。没有其他人知道我们在说什么。好像有少数人在使用 OpenClaw,但大多数人从未听说过它,完全不知道它是什么,而且说实话,它看起来挺吓人的。就像当你听说它时,你会说,好吧,那看起来不太安全。你为什么要那样做?所以我们不得不解释为什么这对我们如此重要,以及为什么我们认为这将成为我们正在构建的产品的未来——你知道,AI 和个人超级智能。所以就有了这份文件,《Claw is the Law》(「爪即是法」)。它成了一个很好的口号。所以这也是我们帮助人们理解我们所处位置的一种方式。所以那个——我忘了那个了。我们有一阵子没用那个了。

Okay, so yeah, that happened after that initial kind of like you know, first few days when we were using it and this was also a Nat Friedman special when he—we saw sort of saw the magic, right? Like of this concept. No one else knew what we were talking about. Like I think that there is a few people who were using OpenClaw, but like the majority of people had never heard of it, had no idea what it was, and it seemed pretty scary, honestly. Like when you did hear about it, you were like, okay, that doesn't seem very safe. Like why are you doing that? And so we had to sort of explain like why this mattered to us so much and why this was going to be the thing that we really believed would be the future of the product that we were building of—you know, AI and personal superintelligence. And so there was this document written, Claw is the Law. It became a great catch phrase. So and it was also just a way for us to be able to help people understand where we were. So that was—I forgot about that one. We haven't used that one in a while.

Host

它有点像一种愿景,是指引这个想法的北极星。

It was kind of like a vision kind of north star of what the idea is.

Mona

是的是的是的。

Yeah yeah yeah.

Mac Mini与OpenClaw配置 Mac Mini and OpenClaw Setup

Host

顺便说一句,我之前没提,你刚才说到 Mac Mini——我的 Mac Mini 就摆在这儿,我的 OpenClaw 以前就跑在它上面。

By the way, I never mentioned, as you were talking about Mac Mini, I have my Mac Mini sitting right here where my OpenClaw used to run.

Mona

太有意思了。我后来确实也买了一台 Mac Mini。后来我想,这台树莓派大概该升级了,于是就买了 Mac Mini。我花了点时间才走到这一步。

That's so funny. I did eventually get a Mac Mini. Eventually I was like, I should probably upgrade this Raspberry Pi, and I got a Mac Mini. It took me some time.

Host

有意思的是,现在已经用不着了。当时这可是个大争论:我们需要这些 Mac Mini 吗?大家是不是买多了?而现在就是,好吧,其他更好用的工具都出来了,我们用不着这些了。

What's funny is it's unnecessary now. That was a big debate back then: will we need these Mac Minis? Are people overbuying Mac Minis? And now it's like, okay, all these other tools have launched that are much better. We don't need these.

领导层在Muse开发中的角色 Roles of Leadership in Muse Development

Host

所以你谈到了 Nat。我想——我很好奇我们知道的这些人在 Muse 的开发中扮演了什么角色。有 Alex Wang,他在社交媒体上非常活跃。有 Nat,显然还有 Zuck。他们在 Muse 的开发中大概扮演了什么角色?

So you've talked about Nat. I want—I'm curious just the roles these folks that we know of have played in the development of Muse. There's Alex Wang who's very out there on socials. There's Nat, Zuck obviously. What's kind of been their roles in the development of Muse?

Mona

团队规模很小,我觉得方式——就像我说的,我在这家公司待了很长时间。我以前从未经历过这样的产品构建。我在这里没有做过很多不同的产品。但这可能是我经历过的最不寻常的体验,感觉更像是我加入 Meta 之前的创业日子。我认为部分原因是团队,它相当小。它非常工程主导,非常注重工程。部分原因是我们与领导团队互动的方式,感觉他们更像是延伸——我不知道。就像通常在任何大公司或任何公司,当你在做产品时,你与领导层有一种节奏,你有固定的会议时间,你有评审,对吧?他们对你的想法做出反应,这是一种非常——我不知道。我们在商业中这样做已经很多很多年了。而这完全不同,因为它是如此新,如此未知,以至于我们——你知道,我们没有做正式评审,对吧?就像我没有做任何幻灯片。实际上我在八月,我想就在发布前,不得不做一组幻灯片,我当时想我忘了怎么做这个。我不得不去 Google Slides,我想哦我忘了怎么给人做幻灯片了。但我们有点像,我们会和他们走进这些房间,我们会——你知道,我们会构建一个原型,然后在某人的手机上传递,对吧?就像我会——我们会把手机给 Mark,说你觉得怎么样,玩玩它,给我们反馈,有时我们会头脑风暴,对吧?你知道,和他们三个一起或单独和其中任何一个。但我想说,是一系列与他们的对话导致了产品,我们拥有的最终产品。而且通常我们会在非常非常小的房间里进行这些对话,所以它们可以非常非常随意,就像你知道我记得有时和 Mark,我们会有一个日历邀请,说我们要讨论几分钟。然后一小时后,我们还在那里聊天。我们会说,等一下,我很确定你很重要,还有其他事情要做。他说,不,完全,我想谈这个,对吧?所以我觉得那很不寻常,因为这肯定不是我在 Meta 的大多数经历。我认为就他们扮演的角色而言,我觉得他们都在你现在看到的产品中留下了印记。

The team was pretty small and I think that the way—like again, I've been at this company for a really long time. I've never experienced a product build like this before. I never worked on a lot of different products here. But this was probably the most unusual experience I've had and felt more like my startup days before I joined Meta than anything else. And I think part of the reason is because of the team and it was quite small. It was very engineering led, very engineering focused. And part of the reason is the way that we interacted with the leadership team where it kind of felt like they were more of an extend—like I don't know. Like typically at any large company or any company really, like when you're working on a product you sort of have this rhythm with leadership where you have set times to meet with them, you have reviews with them, right? Like they react to the thinking that you have and it's sort of this like very—I don't know. We've been doing this for years and years and years in business. And like this was completely different because it was so new, it was so kind of unknown that we—you know, we didn't do formal reviews, right? Like I didn't make any slides. I actually had to make a set of slides in August I think right before the launch and I was like I forgot how to do this. Like I had to go to Google Slides and I'm like oh I forgot how to make slides for people. But we were sort of like we would go into these rooms with them, we would—you know, like we'd do build a prototype and we'd hand it around on somebody's phone, right? Like I would—we would give Mark our phone and be like, what do you think? And he'd play around with it and give us feedback and sometimes we would be brainstorming, right? And you know, like with the three of them or individually with any one of them. But it was like a series of conversations, I would say, with them that led to the product, the end product that we had. And often it was like very very small rooms that we would have those conversations so they could be really really casual and like you know I remember with Mark sometimes like we would have a calendar invite be like like minutes that we're going to talk about it. Then an hour later, we're still in there chatting away. And we'd be like, wait a second, I'm pretty sure you're really important and have other things to do. And he's like, no, totally, I want to talk about this, right? So I thought that was very unusual because that's certainly not how most of my experiences at Meta have been. I think in terms of the roles that they played, I think they all had imprints in the product that you see right now.

Nat与团队 Nat and the team

Host

所以,Nat 显然,我是说,他基本上就是团队的一部分,对吧?我是说,他本身就是团队,对吧?

So, Nat was obviously, I mean, he was basically part of the team, right? I mean, he was the team, right?

Mona

而且在很多方面,这都是他的——是他促成了这个给我们带来魔力的源头。Nat,我觉得能和他共事是一种莫大的荣幸。他显然是个天才,但他对自己打造的产品和打造产品的人都充满热情。他真的就是工程师中的工程师。我们会坐在会议室里,他会说,哦对,你们能把 XYZ 的架构图调出来吗?或者当我们在研究 Sentinel、研究怎么搭建 Sentinel,好让我们能创造一个真正安全的方式,让 Muse 基本上有个后盾,对吧?那是在核心 Muse 智能体之外的东西。他在那里的设计决策中参与得极深,和我们的架构师、我们的安全团队一起。而且他总是随叫随到,就是那种,我们该不该这么做?我们该不该这么做?我们在考虑这个,我们有这个设计。

And in many ways this was his — he was the one that sort of instigated this source of magic for us. Nat, I think, is such a privilege to work with. He's obviously a genius, but he has such great passion for the products that he builds and the people who build it. And he is really just an engineer's engineer. We would sit in rooms and he would be like, oh yeah, can you guys pull up the architectural drawing of XYZ? Or when we were figuring out the Sentinel and how to build a Sentinel so that we could create a really secure way so Muse had basically a backstop, right? That was outside of the core Muse agent. Like he was incredibly involved in the design decisions there with our architects and our security team. And was just always around for kind of, you know, should we do this? Should we do this? Like we're thinking about this. We have this design.

Alex的角色 Alex's role

Mona

我觉得 Alex 显然至关重要,就因为——他就是那个模型,对吧?那个故事里很酷的一点是,我们拿到的第一个 Muse Spark 模型,比我们预想的要智能体式得多。所以那其实有点出乎意料。我们没想到它会那么好。而且我觉得他显然很快就意识到,这也会非常重要。所以我观察 Alex 时觉得酷的一点是,研究是很难改变的,它是个长期的事情。但他在某些领域非常擅长灵活应变,能够不只根据研究团队要做什么来排优先级,还能考虑它如何融入产品。而且他爱 Muse。最后,某种程度上是他把我们推出去的。他说,伙计们,我觉得它准备好了,上吧。

I think Alex was obviously critical just from a — he's the model, right? And what was cool about that story was that the first Muse Spark model that we got was way more agentic than we thought it was going to be. So it was actually kind of a surprise. We didn't think that it was going to be as good as it was. And I think he obviously very quickly realized that this was also going to be very important. So the cool thing about what I — when I watch Alex is, research is very hard to change. It's like a long-term kind of thing. But he has been really good at figuring out how to be nimble in certain areas and being able to prioritize based on not just what the research team is going to do, but also how that fits into the product. And he loves Muse. In the end, he was kind of the one that pushed us out the door. He was like, guys, I think it's ready. Just go.

Mark的愿景 Mark's vision

Mona

然后是 Mark——就像我之前说的,这是我第一次在这方面和 Mark 合作。但他对 Muse 有很多思考方式,最终定义了最终产品。我想讲几个故事——一个是,最开始的时候,他说,Muse 的目的是让人们的生活更好,帮助他们实现目标。我觉得我们其实都知道这一点,但我们从没明确说出来过,我们有点迷失在 Muse 的任务部分里了,对吧?就是,哦,任务完成、任务完成、任务完成。它能完成这笔购买吗?我能做这个那个吗?他真的把我们拉了出来,说,等等,不对,但最重要的是对齐,对吧?是知道用户想做什么?他们想去哪里?他们的优先级是什么?以及 Muse 如何持续帮助他们做到这一点?

And then Mark — like I said before, it was the first time I've ever worked with Mark in this regard. But he had a lot of ways of thinking about what Muse was that ended up defining the end product. And a few stories that I would say there — one is, in the very beginning, he was like, the purpose of Muse is to make people's lives better and to help them achieve their goals. And I think we all kind of knew that, but we had never explicitly stated it, and we had sort of gotten lost in the task part of Muse, right? It's like, oh, task completion, task completion, task completion. Can it make this purchase? Can I do blah blah blah? And he really kind of pulled us out of that and was like, wait, no, but the most important thing is it's alignment, right? It's like knowing what is the user trying to do? Where are they trying to go? What are their priorities? And how does Muse constantly help them do that?

Mona

嗯,当他说这话时,我们就像,好吧,等等,那其实开辟了一个全新的领域,我们可以开始思考,就是我们开始称之为“ dreaming”和“study”的东西。所以就是,好吧,如果 Muse 知道你所有这些事,嗯,它是一个 24/7 的智能体,所以它可以一直想着你,它可以思考如何帮助你的优先级,它可以为你提出更好的建议。所以我们开始——一旦他打开那扇门,你能看到工程师们的眼睛亮了起来,他们说,哦,我们有了——现在我们有很多想法,关于 Muse 如何变得更主动、更有帮助等等。我们还创建了目标标签页,这是在 UI 中对这个概念非常明确的表达。

Well, when he said that, we were like, okay, wait, that actually opens up a whole new area that we can start to think about, which is what we started calling dreaming and study. So it's like, okay, if Muse knows all of these things about you, well, it's a 24/7 agent, so it can think about you all the time, and it can think about how it's going to help your priorities, and it can make better suggestions for you. And so we started — once he kind of opened that door, you could see the engineers' eyes light up, and they were like, oh, we got — now we got a lot of ideas about how Muse can become more proactive and more helpful and all of that. And we also created the goals tab, which is a very explicit articulation in the UI of this concept.

Mona

但就像——所以那是一个很明显的例子,说明他——他显然一直在思考个人超级智能意味着什么。我觉得 Mark 另一个很棒的地方是,他为人们而构建,对吧?我觉得很多人在为企业或企业用户之类构建,而因为他——我是说,他在很多方面归根结底是个消费级 CEO,对吧?他开始大量思考这些东西的民主化,以及如何把它带给所有人,对吧?这意味着我们必须以一种非常独特的方式担心可扩展性。所以很多这些也影响了我们对构建过程的思考,以及我们在路线图中优先考虑什么。

But it was like a — so that's like one really obvious example of where he was — he's obviously been thinking about what personal superintelligence means. And I think the other thing that is great about Mark is that he builds for people, right? So I think a lot of people are building for businesses or enterprise users or whatever, and because he's — I mean ultimately a consumer CEO in many ways, right? He starts to think a lot about democratization of these things and how do you bring it to everybody, right? Which means that we have to worry about scalability in a way that is very unique to us. And so a lot of that also influenced the way that we thought about the build process and what we were prioritizing in our roadmap.

梦之队 The dream team

Host

真是一支梦之队。

What a dream team.

Mona

而且显然,发布之后 Alex 就像我们有史以来最好的营销机器。

And obviously post launch Alex has been like our best marketing machine ever.

Host

天哪。圣经里有句话,说你生来就是为了这样的时刻。感觉 Alex 已经找到了节奏。他找到了自己的产品市场契合点。

Oh my god. There's like this quote from the Bible about how you were made for a time like this. It feels like Alex has hit his stride. He's found his product market fit.

Mona

我记得第一批推文发出来的时候,我们就像,我们都不知道他还能那样发推。我们就像,哦天哪。

I remember when the first set of tweets were going out and we were like, we didn't even know he could tweet like that. Like we were like, oh man.

Jolly角色 Jolly the character

Host

哦天哪。说到这个,那个小角色 Jolly 感觉像——不是你会从 Meta 这样的公司、这样一家巨头公司期待的东西——一个非常讨喜、有点古怪的角色。Jolly 的背后故事里有什么故事吗?它是怎么几乎一路存活下来的?

Oh man. Speaking of that actually, the little character Jolly feels like a — not something you'd expect from a company like Meta, like a massive company — that's very delightful, kind of quirky character. Is there any story there in the backstory of Jolly and how that survived almost through the journey?

Mona

我跟那个设计师开玩笑,他算是 Muse 和 Jolly 的创意之父。我说,Jolly 就像我们的蟑螂,就是死不了。每隔几个月就会有人说,你们不可能在顶部放个毛绒玩具就发布这个产品。我们就说,完全不可能。然后过了一周,我们就说,我们会把它留在里面,对吧?对,我们会把它留在里面。然后过了一个月,又有别人进来说,等等,不可能。

I was joking to the designer who is kind of the brainchild of Muse and Jolly. I was like, Jolly is like our cockroach. It just never dies. And every few months somebody would be like, there's no way you're going to launch this product with a stuffed animal at the top. And we're like, totally no way. And then a week would go by and we're like, we're going to keep it in there, right? Yeah, we're going to keep it in there. And then a month would go by and somebody else would come in and be like, wait, there's no way.

Mona

所以基本上它始于一个原型。我们的首席设计师 Alex Cornell 做了这个原型。他有一个一次性的提示词,生成一个生物,他把它放了进去。我觉得其实一开始,当你打开应用或原型时,它是睡着的,然后它会醒来。它叫 Jolly Bot,因为他以前管他女儿叫 Jolly Bug。名字就是这么来的。

So basically it started with a prototype. So Alex Cornell, who's our lead designer, made the prototype. And he had this one-shot prompt of a creature that he put in there. And I think actually in the beginning, when you opened up the app or the prototype, it was asleep and then it would wake up. And it was called Jolly Bot because he used to refer to his daughter as Jolly Bug. And so that's where the name came from.

Jolly的意外诞生 The Accidental Birth of Jolly

Mona

它本来完全就是临时的,对吧?我们当时以为,公司市场部或别的什么人会回来找我们说,你得在那儿放个 logo 或别的什么,对吧?但一旦把它放上去,我们突然就开始琢磨这些概念了,比如,好吧,现在我整天看到这个头像,它应该多动一动,对吧?它工作的时候就那么盯着我,太奇怪了。为什么不给它戴上耳机,让它对着笔记本电脑工作呢?为什么不开始做这些动画呢?其中一部分只是因为我们有点无聊了,我们想,我不想一直盯着这东西,所以咱们给它加点好玩的东西吧。于是我们开始琢磨这个,然后我们想,哦,那人们应该能把自己的头像做成任何他们想要的样子,对吧?比如,我们都看着 Jolly,这有点奇怪,我想要一个不同的头像,你也想要一个不同的头像。这就引出了我们关于“Muse 是你的”这个概念,我们真的希望它属于你,而不一定是一个 Meta 的实体。所以后来人们开始开发自己的头像,于是到了某个时候,要撤掉 Jolly Bot 就越来越难了,因为我们已经围绕它建立了一整套系统。嗯,但我得说,有那么一刻,我们以为 Jolly 真的死了,我们准备换上一个替代的 logo。我得说,原因有很多,但实际上 Mark 是原因之一,他说不,他真的很喜欢这个头像。但我想主要还是因为,当你和某个感觉如此私人的东西对话时,你最不想对话的就是一个公司 logo,对吧?那会彻底打破魔咒。所以那感觉就不是正确答案,让我们觉得很不舒服。所以,你知道,我们团队的一帮人就说,除非我们死了。我想我们周围的所有人,还有员工们也都爱他们的头像,他们爱 Jolly,你知道,它太可爱了。所以最后,我想在 Mark 和我们以及一帮其他人之间,我们决定,Jolly 留下。我记得这大概是在发布前一周左右。我们说,就这么定了。我不认为我们当时知道它最终会变得如此标志性,部分要感谢 Alex Wang。嗯,我当时没想到它会如此标志性。所以这算是我们为自己做的决定,因为我们爱它,然后它最终成了,在我看来,现在显而易见的选择。

And it was totally meant to be temporary, right? And we sort of assumed at some point that somebody in corporate marketing or somewhere would come back to us and be like, you need to put a logo in there or something else, right? But once we had it up there, we were like, suddenly we started to develop these concepts like, okay, now that I see this avatar all the time, well, it should be moving more, right? So it's like, you know, when it's working, it's just staring at me, that's weird. Why don't we put headphones on it and have it work on a laptop, right? Like why don't we start to make these animations? And some of that was just out of, we were bored a little bit and we were like, I don't want to keep staring at this thing, so let's do something fun with it. So we started to kind of think about that, and then we were like, oh well, then people should have, they should be able to make their avatars whatever they wanted to be, right? Like why, you know, it's kind of weird that we're all looking at Jolly and like, I want a different avatar for myself and you want a different avatar for you. And this really kind of gets into this concept that we have about like the Muse is yours, and we wanted to really be yours and not like a Meta entity necessarily. So then people started to develop their own avatars, and so at some point it became harder and harder to take out Jolly Bot because we had created a whole system around this thing. Um, but I will say that there was a moment where we thought Jolly was truly dead and there was an alternative kind of logo that we would put in. And I would say that the reason, like there are so many reasons, but actually Mark was one of the reasons where he was like, no, he really loved the avatar. But I think mostly it's like when you're talking to something that feels so personal, the last thing you want to talk to is a corporate logo, right? Like that breaks the spell completely. And so that just felt like not the right answer and it felt so uncomfortable for us. So, you know, a bunch of us on the team were like, over our dead body. And I think everybody around us, you know, and the employee base also loved their avatars and they loved Jolly and you know, it was so cute. And so in the end I think between Mark and us and a bunch of others, we were like, Jolly stays. I think this was like a week before a launch or something. We were like, this is what we're going with. And I don't think we knew how iconic it was going to end up being, and partly I think thanks to Alex Wang. Um, I didn't think we realized how iconic it would be at the time. So this was sort of like a decision for ourselves because we loved it, and then it just ended up being, in my opinion, the obvious choice now.

主持人反应 Host's Reaction

Host

哇。这故事太棒了。我完全不知道。感觉这成了它成功的关键部分,就是那种个性、个性化以及与众不同的感觉。而且正如你所说,这恰恰是你以为公司会砍掉的东西,因为它感觉不专业。这里面有个教训。

Wow. That is an amazing story. I had no idea. It feels like this became a core part of what made it successful, just the personality and personalization and feeling different. And to your point, this is like something you would expect a company to kill because it's just something it feels not professional. There's a lesson there.

能动性与产品原则 Agency and Product Principles

Mona

首先,我告诉 Meta 一些产品经理的是,是的,你是一家巨型公司的一部分,但你有自主权,Mark 会听你说,对吧?或者 Nat 会听你说,对吧?他们就像,你知道,有时候你很容易就会说,是啊,当然用公司 logo,就像接受你所在的状态,对吧?作为默认。但那实际上不是团队的工作方式。我认为,我们当时说我们爱这个产品,我们打造了这个产品,我们对这个产品有强烈的意见,对吧?那很重要,人们听了我们的,对吧?所以那就是我想说的,你们有自主权,你们应该说出你们想要的,说出你们的感受。也许人们会说不行,但你应该尝试。然后我认为另一点是,总是有品牌与其他的权衡,比如你希望品牌出现多少,还是不希望,等等。我认为在很多对话中这真的很重要。我认为我们当时在打造的东西,如果它要成为你的 Muse,成为你的个人智能体,它必须感觉完全属于你。Meta 需要从中淡出,因为归根结底,我们构建智能体的方式是,智能体需要为你工作。你是主人,对吧?我们会设置护栏,我们会制定章程,我们会确保智能体遵守法律,对吧?所以这类东西我们会有,但其余部分真的需要是你。所以,在产品层面设定这些原则很有帮助,因为这样它就不是随意的理由。而是,不,我们一直这么说。这一直是原则。所以如果你接受这一点,那么你就很难想象那里会出现一个公司 logo,对吧?因为那完全违反了产品原则。所以我认为在最初就设定好这一点,并让我们周围所有人都非常清楚,也非常重要。

One, I think just for what I tell some of the PMs at Meta is that yes, you are part of a giant corporation, but you have agency and Mark will hear you out, right? Or Nat will hear you out, right? Like they are like, you know, it's like there's not, I think sometimes you like it would have been very easy for us to just be like yeah, of course corporate logo, like you know, accept the state that you're in, right? As like a default. But that's actually not how the team works. And I think that the fact that we were like we love this product, we built this product and we have a strong opinion about this product, right? Like that mattered and people listened to us, right? And so that was like one that I'm like, you guys have agency, you guys should say what you want, like say how you feel. Maybe people will say no, but like you should try. And then I think the other one is that there's always this like tradeoff of like the brand versus you know, it's like how much do you want the brand to show up versus like not or whatever. Um and I think for a lot of conversations that's really important. I think what we were building, like if it's going to be your muse and it's going to be your personal agent, it has to feel like it completely belongs to you. And Meta kind of needs to fade away from that because at the end of the day, the way that we built the agent was the agent needs to work for you. You are the owner, right? And we will have guard rails and we will have a charter and we will make sure that the agent is abiding by the law, right? And so those kinds of things we will have, but the rest of it really needs to be you. And so like setting those principles at a product level helps a lot because then it's like it's not a random rationale. It's like no, we've always been saying this. This has always been the principle. So if you take that, then you know, it becomes very hard to imagine a corporate logo in there, right? Because that completely violates the product principle. So I think that was also really important with setting that up at the very beginning and being very clear with everybody around us.

扎克伯格的意外用例 Zuck's Unexpected Use Case

Host

说到 Zuck,回到之前的话题,Zuck 谈到他最喜欢的 Muse 用例是看他做 MMA 并给他反馈。我很好奇,我能想象一个 CEO 进来说,嘿,我需要用它来做这个,而你说,但这不是它擅长的。关于你如何处理这种可能出乎意料的用例,有什么可说的吗?

Speaking of Zuck and kind of coming back to this earlier thread, Zuck talked about what his favorite use cases from Muse was this kind of watching him do MMA and giving him feedback. And I'm curious just I can imagine a CEO coming in, hey, I need to use it for this, and you're like, but this isn't what it's great at. Is there anything there about how you dealt with that sort of maybe unexpected use case?

用例与用户研究 Use Cases and User Research

Mona

所以实际上我们最初的很多对话就是关于用例的。嗯,关于用例聊了好几个小时,对吧?嗯,你知道,有时候和公司内部的人聊天很有趣,因为我们不是正常人,对吧?在很多方面都是,部分是因为你为一家巨型科技公司工作,而且你比任何人都更信奉 AI 和智能体。然后 Mark 显然,你知道,非常独特,他的问题也有些特别。所以我们花了很多时间讨论用例,我们喜欢谈论的是我们自己的个人用例。因为我们有,你知道,人们在测试,我们有一个很长的 UXR 小组,很早就开始了。实际上,那个 UX 小组我记得是三月开始的。

So actually a lot of our first conversations were just about use cases. Um and like hours and hours about use cases, right? Uh and um you know, it's sometimes funny when you talk to people within the company because they we are not normal, right? Like in so many ways, you know, partly that you were working for a giant tech company and, you know, you're far more AI pilled and agent pilled than anybody else. And then Mark is obviously like, you know, very much just like, you know, unique uh and some of his problems. But so we spent a lot of time talking about use cases and what we would like talk about was our own personal use case. And because we had, you know, people testing both in we had this like very long uh UXR panel that we started very early on. Actually, that UX panel started I think in March.

Host

这是内部人员还是外部人员?

And this was internal people or external?

Mona

外部。所以我们有招募来的外部人员。我们也有内部人员在使用它。而且我们,内部人员我们有一个论坛。

External. So we had external people um that we had recruited. We also had the internal people obviously using it. And we would and the internal people we have a forum.

反馈循环与内部试用 Feedback Loops and Dogfooding

Mona

不知道你熟不熟悉,我们有 Workplace,对吧?它基本上就是内部用的 Facebook 群组,大家会在里面发帖。所以我们有一个针对 Muse 的反馈群。通过这些渠道,我们收集到了大量关于人们在使用什么、用来做什么的反馈。我们几乎每周都会把这些反馈带给 Mark、Nat 和 Alex,反复琢磨。我们会说,这是我们听到的所有故事。这是人们觉得神奇的地方,这是不觉得神奇的地方,诸如此类。这其实挺好的,因为当然总会有人讲什么 MMA 的故事之类的。但因为我们让每个人都扎根于这些真实的生活体验,所以在这方面我们并没有被猛烈抨击。

I don't know if you're familiar, we have Workplace, right? It's basically like Facebook groups for internal use, and people post in there. So we had a feedback group for Muse. Between those things, we were getting all of this feedback about what people were doing and what they were using it for. And we would bring it to Mark, Nat, and Alex almost on a weekly basis and obsess over it. We'd say, here are all the stories we've heard. This is what people found magic in, what they didn't find magic in, all of that sort of stuff. It was actually kind of nice because yes, you're always going to get someone saying, oh, I have an MMA story or whatever. But because we were rooting everybody in these real-life experiences, we didn't actually get thrashed on that front.

Mona

确实发生的是,有一些惊喜。我没想到购物会成为一个如此大的用例。我绝不会预测到这一点。我个人很喜欢购物,但我绝不会预测到。我预测的是个人生产力、健康和个人理财,这是我比较关注的三个领域。我想有些人提到了家庭自动化,对吧?所以那大概就是当时的范围。然后我们开始看到购物在我们的吃狗粮用户中大量出现,这完全是个惊喜。于是我们说,等等,我们所有的评估都在这边。我们现在实际上需要关注购物,把它变成一个相当大的用例,并围绕它进行评估。我们基本上有用例级别的评估,对吧?然后是我们以为会很大的家庭自动化,结果并没有那么大。在开放云时代它确实很大,我认为部分原因是很多使用它的人可能已经设置了很多家庭自动化。但随着我们面向更广泛的用户群,它就没有像其他一些用例那样火爆。但现在购物是我们的顶级用例之一。

What did happen was there were surprises. So I did not think shopping was going to be as big of a use case as it's become. I would not have predicted that. I love to shop personally, but I would have never predicted it. I predicted personal productivity, health, and personal finance were the three that I was pretty focused on. I think a few people were like home automation, right? And so that was kind of the zone. Then we started to see shopping pop up a lot more with our dogfooders, and it was a complete surprise. So then we were like, wait, all of our evals have been over here. We actually need to now focus on shopping and make that a pretty big use case and evals around that. We basically have use-case-level evals, right? And then home automation, which we thought was going to be huge, just wasn't as big. It was really big during the OpenClaw days, and I think partly because a lot of people who were using it probably also have a lot of home automation already set up. But as we were getting more into just a broader user base, that just didn't pop as much as some of the other use cases. But now shopping is one of our top use cases.

Host

我听说团队里有一位工程师非常喜欢购物。

I heard there's an engineer on the team who loves shopping.

Mona

对,Christine Awad。我们有 Tarek,他是我们的技术负责人和核心架构师,然后 Christine 是我们的工程经理。我真的很怕她在 Muse 上花了多少钱。特别好笑,因为我们早上醒来,她就会把她购物用例的所有 bug 报告发过来,我就说,Christine,我得把你的信用卡拿走。我需要你的信用卡——工程师们今天得睡觉。但没错,她绝对是这方面我们的头号内部试用者(dogfooder)。然后我最近也开始更多地购物了。我丈夫给我打电话——上周我在 Menlo Park——他今天早上打电话给我,他说,我这儿有七个包裹。我意识到的是,以前我会批量下单。所以我会去 nike.com 买五条运动裤。但现在因为我在用 Muse,它会去很多不同的商店。它会根据我的要求挑选五个不同的地方购买。实际上好多了,因为我能得到多样性什么的。但这也意味着我会收到五个不同的包裹或七个不同的包裹,我丈夫就说,我不知道现在发生了什么,但你真的需要冷静一下。他实际上在某个时候说,我只想跟你的 Muse 谈谈,从我这边给它指示。我说,那真的很有趣,因为这确实很有道理。如果你能做到那就太好了。

Yeah, Christine Awad. So we've got Tarek, who is our tech lead and core architect, and then Christine who's our engineering manager. I am terrified about how much money she spent through Muse. It's so funny because we'll wake up in the morning and she'll just send all of her bug reports from shopping use cases, and I'm like, Christine, I need to take your credit card away. I need your credit card—the engineers need to sleep today. But yeah, she was definitely our number one dogfooder around that. And then I have also recently started to shop a lot more. My husband called me—I was in Menlo Park this past week—and he called me this morning and he was like, I've got seven packages out here. What I realized is happening is before I used to bulk order. So I would go to nike.com and buy like five pairs of sweatpants. But now because I'm having it with Muse, it's going to lots of different stores. It's picking like five different places to buy from based on my spec. And it's actually much better because I'm getting diversity and whatever. But it also means I am getting five different packages or seven different packages, and my husband was like, I don't know what's happening right now, but you really need to calm it down. He was actually at some point he was like, I just want to talk to your Muse and give it instructions from my end. And I was like, that's really funny because that does make a lot of sense. It would be great if you could do that.

购物与智能体的未来 The Future of Shopping and Agents

Host

也该听听你伴侣对购物这事的看法。

Get your partner's perspective on shopping.

Mona

没错。

Exactly.

Host

我不知道你花多少时间思考这个,但这是一个在许多方面正在出现的新世界。一个是关于我们如何购物和如何找到东西的想法。零售业一直是围绕我们来向你营销,说服你买这个东西,并向你展示广告来购买我们正在销售的这个东西。而现在智能体正在做出这些决定。你有没有花时间思考这如何改变广告、营销、购物——智能体现在正在决定?

I don't know how much time you spend thinking about this, but it's such a new world that is emerging in so many ways. One is this idea of how we shop and how we find stuff. Retail has been built around we'll market to you and convince you to buy this thing and show you ads to buy this thing that we are selling. And now agents are making these decisions. Do you spend any time thinking about how this changes ads, marketing, shopping—that agents are now deciding?

Mona

人们真的很享受被启发。人们享受浏览的行为,对吧?就像有些事情你会说,好吧,我明天就想要卫生纸之类的。但很多事情是相当不错的。我喜欢看一堆衣服和搭配,然后挑选。所以我认为我们必须想办法让两者都可行。也就是让用户能够获得那种灵感,让品牌或公司帮助用户弄清楚选项空间是什么,并让智能体真正帮助缩小范围或做出那些权衡,有时候你就是会瘫痪。我会想,我可以选这个或这个,但实际上我什么都不买,因为我无法在那时做出决定。这些地方智能体真的很有帮助,它可以帮助你做出选择。所以我认为我们必须找到一种方法让完整的用例存在,因为我实际上不认为如果我们切断浏览,人们会满意。那会很可悲。而且我认为人们仍然会想要这样做。所以无论如何,我确实认为我们非常早期,这意味着正在发生的事情是我不认为任何人准备好了。没有关于会发生什么的大师计划。这 probably 对于任何发生的技术革命或任何革命都是如此。你只能想办法解决,理想情况下你们一起解决。所以我们真的很幸运有合作伙伴,他们在零售领域或是商家,对这个潜在未来感到兴奋。

People really enjoy being inspired. People enjoy the act of browsing, right? Like some things you're like, okay, I just want the toilet paper tomorrow or whatever. But a lot of things it's quite nice. I like looking at a bunch of clothes and outfits and figuring it out. So I think we're going to have to figure out how to make both things work. Which is like let the user be able to have that inspiration, let the brands or the companies help the user figure out what the option space is, and have the agent really help narrow the field or make those trade-offs where you're like—sometimes you're just paralyzed. I'm like, I could do this one or this one, and actually I'm just going to buy nothing because I couldn't make that decision in that time. Those are places where the agent's really helpful, and it can help you make that choice. So I think we are going to have to find a way for the full use case to exist because I actually don't think people are going to be satisfied if we cut out browsing. That's going to be sad. And I think people will still want to do that. So anyway, I do think that we are very early, which means that what's happening is I don't think anyone was ready. There wasn't a master plan that was set out on what was going to happen. And that probably is true for any technical revolution that happens or any revolution that happens. And you sort of have to figure it out and ideally you're figuring it out together. So we've been really lucky to have partners who are in the retail space or who are merchants who are excited about this potential future.

商业与消费者智能体 Business and Consumer Agents

Mona

他们也在测试智能体,对吧?他们有商业智能体,当商业智能体和消费者智能体能够互相沟通并帮助双方时,那有多酷啊,对吧?商业智能体可以拥有什么样的信息,从而对消费者更好,对吧?因为有些事情,对吧?就像我必须去网站,我必须筛选,我必须排序,我必须搜索,对吧?你知道,有些事情智能体会非常有帮助,能够真正减少你的时间,直接带你找到你想要的东西。但再次,有些事情我认为我们不应该取代,因为那只是用户的乐趣和用户做决策的方式,这仍然非常重要。

They're testing agents out too, right? They've got business agents and like how cool is that when like a business agent and a consumer agent can communicate with each other and help both sides, right? And like what kind of information can a business agent have that could like be even better for the consumer, right? Like cuz there are some things, right? It's like I have to go to the website, I have to filter, I have to sort, I have to search, right? Like you know, like there are some things where like the agent's going to be very helpful and be able to like really cut down on your time and just get you to the things that you want. But again, there are some things that I don't think like we shouldn't replace because that's just enjoyment for users and how users make decisions and that's still really important.

智能体集群扩展反馈 Agent Swarms for Scaling Feedback

Host

我想回到我听说过的另一件事,关于你们如何工作并构建 Muse。我听说有一个智能体集群帮助你们扩展用户反馈,帮助你们弄清楚该关注什么,这听起来很棒。那里的故事是什么?

I want to go back to something else that I've heard about how you all work and built Muse. I hear that there was uh a agent swarms that uh helped you scale user feedback, helped you figure out what to pay attention to, which uh sounds awesome. What what's the story there?

Mona

是的,有一些智能体,我们让它们像蜂群一样涌向,你知道,涌向以太,对吧?它们能够查看所有正在发生的对话和正在产生的数据,基本上回来,它们也可以创建合成数据,对吧?嗯,所以你可以拥有所有这些数据,这是我们能够基本上输入到我们的评估中的一种方式。对吧?所以就像外面发生了什么?什么进展顺利?什么不顺利?对吧?我们会做这些叫做集群转储的事情,对吧?它们会聚集在一起,形成这个巨大的转储,就像是对生态系统中发生的事情的精彩格式化表达,比如你知道人们在做哪些类型的任务?

Yeah, there are these agents that we like kind of like swarm out into the, you know, into the ether, right? And they're able to kind of like look at all of the conversations that are happening and data that is happening and basically like kind of come back with uh and they can also create synthetic data as well, right? Um, and so like you can have like all of this data and uh uh it was a way for us to be able to basically feed into our evals. Right? So it's like what's happening out there? What's like what's going well? What's not going well? Right? We would do these things called like dumps from the swarms, right? Like they would it would like come together with this like giant dump and it was like this like wonderfully formatted articulation of what was happening in the ecosystem in terms of like the you know like like you know what kind of tasks were people doing?

Host

所以这是在查看指标分析和人们自己分享的反馈。

So this was looking at at like metrics analytics and feedback people are sharing themselves themselves.

Mona

是的,没错。嗯,因为我们当时真正挣扎的事情是,当我们在做 Meta AI 时,大多数对话都是我认为主要是单轮对话,对吧?所以人们会有一轮,你得到一个回复,也许你会有另一轮,但通常不会。嗯,我认为现在所有助手都在改变,但有一段时间我认为这可能是真的。然后当我们开始构建这个时,它完全是多轮的,对吧?就像来回,来回,来回。我们没有那样的数据。你知道,因为为了构建我们的评估,我们需要数据,通常你想要生产数据,而不是我写的那些数据,对吧?嗯,所以我们真的没有任何数据。所以从某种意义上说,集群是关键,因为有一种方式让我们能够收集数据并理解多轮对话在长期任务中可能是什么样子,而不是关于编码的,对吧?就像再次,很多东西已经为编码者或其他什么存在了。这就像是,你知道,我如何为一周计划 meals 或其他什么?所以嗯,所以它们在能够获得大量洞察和大量数据方面非常关键,让我们能够输入以创建数据集以及理解正在发生的事情。所以现在实际上每次我们有新模型进来,或者如果我们像前几天我在想,我觉得那里有,我发现了一些东西,我想我不确定这是不是一个实际问题,还是只是我的问题,对吧?工程师们说哦我们会集群它并弄清楚。集群了它,然后哦不,这是一个我们需要解决的实际问题,我们会找人处理,对吧?所以它非常非常有用,因为它超级快而且非常全面。实际上,这让我想知道我们以前是如何构建产品的,因为这有点疯狂。就像我觉得我现在有这么多洞察可以依靠,你知道,以前就像你看指标仪表盘,对吧?所以你得到一个仪表盘,你看到指标,指标上下波动什么的。现在你仍然有那个,但你也有生产中的例子,对吧?就像,你知道,这些你可以变得如此专注。就像,你知道,10 个人问过,你知道,在这个网站上购物并被阻止,对吧?或者类似的事情,对吧?你现在可以用这些信息变得如此具体,以真正实施有针对性的改变或改进或其他什么。但就像我让我所有的 PM 做的事情,因为我认为你知道,它创造了很多同理心。我认为集群做的一件事是,当它们带回这些数据时,因为它们带回的不仅仅是数字,还有洞察,它为用户正在经历的事情创造了很多同理心,嗯,并且帮助我们感受痛苦,可以说,我认为这对产品开发非常非常重要。我认为如果你没有那种同理心,不能感受痛苦,你永远不会开发出好产品。

Yeah, exactly. Um so because what hap Okay, so the the thing that we were really struggling with was um when we were working on Meta AI, most of the conversations were what I would consider to be mostly single turn conversations, right? So people would have like one kind of turn, you'd get a response, maybe you'd have another one, but often you wouldn't. Um and I think that's changing for all assistants now, but for a while I think that was probably pretty true. And then when we started building this, it was like completely multi-turn, right? Like it was like back and forth, back and forth, back and forth. And we don't have data that looks like that. Like you know cuz in order to build our evals, we need data and often you want data from production, not data that I've like written, right? Um and so we just didn't really have any data. And so in some ways the swarms were critical because there was like a way for us to be able to collect that data and understand what like multi-turn conversations over long running tasks could look like that weren't about coding, right? Like again like a lot of this stuff existed for like coders or whatever. And this was like you know how do I meal plan for the week or whatever? And so um so they were really critical in terms of like being able to like get a lot of insight and a lot of data for us to be able to feed to like create data sets as well as understanding what was happening. So now actually every time we have a new model that like comes in or if we're like the other day I was like I think that there like I was spotting some like you know thing that I was like I'm not sure if this is an actual issue or if this is just a me problem, right? And like the engineers were like oh we'll swarm it and figure it out. Swarmed it, and like, oh no, this is like an actual problem that we need to solve, and we're going to get somebody on it, right? And so, it's been very, very useful because it's super fast and very comprehensive. Actually, like makes me wonder how we even built products before because it's kind of crazy. Like it's like I feel like I have so much insight now to be able to work off of and it's You know, before it was like you would look at dashboards of metrics, right? So it was like you would get a dashboard, you saw the metrics, the metrics went down and up and whatever. And now like you still have that, but you also have like examples from production, right? It's like, you know, these like you can get so like focused. It's like, you know, 10 people have asked about, you know, to shop on this website and got blocked, right? Or something like that, right? And you can get so specific with like this information now to be able to really like put in place target changes or improvements or whatever. But it's like the thing I make all of my PMs do it uh because I think you you know, it creates a lot of empathy. And I think one of the things that the swarms did was when they bring back this data because they're bringing back not just numbers but insights, it creates a lot of empathy for what the users are going through um and uh and kind of like helps us like feel the pain, so to speak, uh which I think is really, really important for product development. I think if you don't have that empathy and you can't feel the pain, you will never develop good products.

产品管理中的共情 Empathy in Product Management

Host

这个播客中我最喜欢的一句话来自 Nan Yu,他现在在 OpenAI,曾在 Linear 担任产品负责人,你有一句话关于作为 PM 的工作是像客户一样感受他们的痛苦。

One of my favorite quotes from this podcast is from Nan Yu who is now at OpenAI who was at Linear head of product and you have this line about how your job as a PM is to feel the pain of your customers as much as they do.

Mona

是的,100%。不,我认为作为 PM 驱动我的两件事是持续的焦虑和真正使用这个产品的消费者的痛苦,我希望这会让他们的生活更好,但当没有时,那就是我需要行动的时候。

Yeah, 100%. No, I I think like maybe the two things that drive me as a PM is um constant anxiety and like the the really the pain of the consumers that are using this product that I hope will make their lives better, but when it doesn't, like that's when I need to act.

Host

多么美妙的工作,只是受苦和焦虑。这就是工作。

What a wonderful job, just to suffer and anxiety. This is the job.

Mona

是的。

Yeah.

评估及其创建 Evals and Their Creation

Host

不,伙计。嗯,我想多听听关于评估的事情。所以我的理解是,你有一些评估来定义所有核心用例的成功以及你期望人们使用 Muse 的方式。你大概有多少评估,通常是谁写的?是你吗?是 PM 吗?是工程师吗?

No, man. Um I I to hear a bit more about the Evals. So the way I think about it is you just kind of have these evals that define success for all the core use cases and ways you expect people to use Muse. How many evals do you have roughly and who's who's writing these generally? Is it you? Is it PMs? Is it engineers?

Mona

是的。嗯,我们有很多。我甚至数不清数量,因为肯定很多。所以方式是这样,有主要评估、优先评估,我们关注的那些往往是核心的。就像你知道,有些如果这些不存在,产品就不工作。安全就是一个例子,对吧?嗯,所以我们有提示注入的评估。我们有一般安全的评估,对于你知道伤害,像所有这些种类的事情。所以就像那是一整个类别。我们有能力,你知道我们有能力的评估版本。

Yeah. Um we have a ton. I couldn't even count the number of because for sure. Like so the way that it so there's major evals, priority evals that we look at and those tend to be like kind of core. It's like you know there's some like if these don't exist the product isn't working. Safety is an example of that, right? Um so we have like evals for prompt injection. We have evals for general safety, for you know harm, like all of these kinds of things. So like that's like a whole category. We have a capability you know we have capabilities versions of evals.

评估智能体表现 Evaluating Agent Performance

Mona

比如,它浏览器用得怎么样?它能完成任务吗?然后你有行为评估,这真的是关于智能体的个性以及它如何与用户互动。在那里,你有:它在问后续问题吗?它在意图理解方面有多好?它能弄清楚用户在说什么吗?然后你有用例评估,比如那类优先用例。每一个里面都有很多我们创建的子评估。我认为在任何给定时间,总是有优先评估。所以任何进来的东西都必须通过这些。安全就是一个很好的例子。然后还有次要评估,你并不真的希望在这些上退步太多,但也许没关系——你可以稍微权衡一下。然后你有更功能级别的评估,特定团队有。所以我们有一个层级。我们有大量的这些评估。写它们的人范围很广。PM 写一些评估。工程师写很多,研究员写很多。我们显然与智能体合作来创建这些。但人们审查所有数据非常重要,因为当我们不这样做时,我们总是有问题。所以最近实际上有一个有趣的趋势,我们的系统提示必须是手写的。你不能用 AI 来写系统提示,任何部分都不行。它必须是手写的。评估、提示分布需要检查——你必须确保这符合产品现实。行为规范需要手写。所以我们大量使用智能体,但这类事情需要很多个人时间和精力。

You know, how is it using the browser? Is it able to task complete? And then you have behavioral evals, which is really about the personality of the agent and how it behaves with the user. And in there, you've got: is it asking follow-up questions? How good is it at intent understanding? Can it figure out what the user is saying? And then you've got your use case evals, like that kind of category of priority use cases. And each of these have lots of sub-evals within those that we create. And I think for any given time, there's always priority evals. So anything that comes in has to pass those. Safety is the great example of that. And then there are secondary evals that you don't really want to regress too much on, but maybe it's okay—you can trade off a little bit. And then you've got evals that are more feature-level that specific teams have. So we have some hierarchy. We have a ton of these evals. People who write them are a range of people. PMs write some evals. Engineers write a lot of them, researchers write a lot of them. And we work with the agents obviously to be able to create these. But it's super important that people review all the data because when we don't, we always have issues. And so there's actually been this funny trend recently where our system prompt has to be handwritten. You cannot use an AI to write a system prompt, any part of it. It must be handwritten. The evals, the prompt distribution needs to be checked—you have to make sure this matches what the product reality is. The behavioral spec needs to be handwritten. And so we use agents a lot, but there's a lot of personal time and effort that goes into this sort of thing.

Host

好的。本季度的支持赞助商是 DX。现在贵公司的每个人终于都在使用 AI 了,工程领导者面临的问题不再是“我们是否在使用 AI?”,而是“它是否在产生回报?”借助 DX,您可以衡量和基准测试 AI 采用在整个产品生命周期中的影响。DX 向您展示 AI 在哪些方面帮助了开发者,在哪些方面创造了新的瓶颈。您还可以用它来评估 AI 供应商、监控成本和许可证,并确切了解是什么限制了您的智能体。这就是为什么包括 Snowflake、Sony 和 BNY 在内的数百家企业使用 DX 平台来衡量 AI 对开发者生产力的影响。访问 getdx.com/lenny 获取 DX 的演示。网址是 getdx.com/lenny。

Okay. This season's supporting sponsor is DX. Now that everybody at your company is finally using AI, the question that engineering leaders face is no longer 'are we using AI?' but 'is it paying off?' With DX, you can measure and benchmark the impact of AI adoption across your full product lifecycle. DX shows you where AI is helping developers and where it's creating new bottlenecks. You can also use it to evaluate AI vendors, monitor costs and licenses, and see exactly what's limiting your agents. That's why hundreds of enterprises, including Snowflake, Sony, and BNY, use the DX platform to measure AI's impact on developer productivity. Visit getdx.com/lenny to get a demo of DX. That's getdx.com/lenny.

激活与首个提示 Activation and First Prompt

Host

我想稍微换个方向。我想谈谈激活。一般来说,增长产品最大的杠杆之一就是让更多人从“好吧,我注册了。我开始尝试了”到“哇,这正是——这太棒了”,也就是他们说的顿悟时刻。在 AI 助手领域,这可能是让人们理解它能做什么的最大杠杆。有如此多的能力,甚至没人知道该怎么用。我想这是最大的机会之一?我想你在所谓的“第一英里”上花了很多时间。关于如何提高激活率,你有什么学到的吗?在提高人们尝试 AI 助手(特别是 Muse)的激活率方面,什么方法有效?

I want to kind of go in a slightly different direction. I want to talk about activation. One of the biggest levers generally for growing a product is getting more people from 'okay, I've signed up. I'm starting to try it' to like 'wow, this is exactly—this is awesome,' the aha moment as they say. It feels like in AI assistance, this is maybe the biggest lever for people to understand what this is capable of. There's like so much power that nobody even understands what to do with it. Is I imagine one of the biggest opportunities? I imagine you spent a lot of time in that first mile as folks like to call it. Is there anything you've learned about how to increase activation? What has worked in increasing the activation rate of someone trying out an AI assistant, Muse in particular?

Mona

我的意思是,这是我们头号问题。人们会说,“为什么?我已经有一个聊天机器人了,我不明白。为什么我需要另一个?”所以最有效的杠杆是口碑。基本上就是听别人的故事。这是第一位的。我和我孩子朋友的父母们在一起。Muse 被提到了。每个人大概都看过广告。我的意思是,如果你住在纽约或旧金山,可能很难避开我们的头像 Jolly。但每个人大概都知道它是什么,但并不真正理解如何使用它。其中一位妈妈在过去一个月里一直是重度用户。所以她实际上拿出手机递给他们——那些妈妈们——他们传着看,滚动看她是怎么用的。他们说,“天哪”,有两个人当场就下载了。所以无论我们做了多少广告,无论我们说“你应该试试 Muse,它是个人超级智能,或者它是为你做事的 AI”,直到他们看到他们能感同身受的人在使用它,以及他们如何使用它,才真正引起共鸣。如果你回想我所有朋友开始使用 ChatGPT 的时候,部分原因是我们会出去吃饭时谈论它。我们会说,“你能相信它做到了那个吗?”“你能相信你能——你现在可以做这个了?”所以这 100% 是最有效的杠杆。我们越能让人们分享关于如何使用智能体的故事——无论是 Muse 还是其他——越多的人理解价值是什么,他们就越受启发去做。我认为第二是让人们发出他们的第一个提示。人们在第一个提示上会卡住。所以大多数人甚至对智能体的第一个提示都会是“今天天气怎么样?”或者“嗨”之类的。你知道,就像你有点“我该对这个东西说什么?”就像,我该说的第一件事是什么?所以我们花了很多时间——如果你使用产品,有一个叫做想法标签页的东西。在想法标签页里,基本上就是预先打包好的——像入门包——来启发你。就像“Muse 可以帮助你做 X。”在 X 里,它可以创建一个定时任务——所以就像一个通知。它可以为你构建一个仪表板。它可以做任何事。你所要做的就是说出“我们来做吧。”然后 Muse 就启动流程,为你构建一些东西或为你做那件事。我们对此很着迷,因为它能做这么多事情。除非我们给你一本真正的说明书,否则我们到底要怎么向你解释?我们要怎么向你解释 Muse 能做什么?所以这是我们非常关注的事情。我认为这进展相对顺利,但说实话,人们仍然很难想象。所以我们花了很多时间在那上面。我们花了很多时间在引导上,试图弄清楚我们发给你的第一条消息是什么,第二条消息是什么。

I mean this is the number one problem that we have. People are like, 'why? I already have a chatbot, like I don't get it. Why do I need another one?' So the most effective lever out there is word of mouth. It's basically hearing other people's stories. That is number one. I was with a bunch of my kids' friends' parents. Muse kind of came up. Everybody had sort of seen the ad. I mean, I think it's probably pretty hard if you live in New York or San Francisco to avoid Jolly, our avatar. But everyone sort of had a sense of what it was but didn't really understand how to use it. And one of the moms had been a power user for the past month. And so she actually pulled out her phone and handed it to them—the moms—and they were passing it around and scrolling through how she was using it. And they were like, 'oh my god,' like two people downloaded it right there. And so no matter how much advertising we did, no matter how much we were like 'you should try Muse, it's personal superintelligence or it's an AI that does things for you,' it didn't quite resonate until they saw somebody else that they related to using it, and how they used it. And if you think back to when all my friends started using ChatGPT, it was partly because we would go out to dinner and talk about it. We were like, 'can you believe it did that?' 'Can you believe you were able to—you can do this now?' And so that's 100% the most effective lever. The more that we can get people sharing stories about how to use agents—whether it's Muse and others—the more people understand what the value is and the more they're inspired to do it. I think the second is getting people to get their first prompt out. People freeze on the first prompt. So most people's first prompt to even an agent is going to be like, 'what's the weather today?' or 'hi' or whatever. You know, it's like you're kind of like, 'what do I say to this thing?' Like, what's that first thing that I say? And so we spent a lot of time—if you use the product, there's this thing called the ideas tab. And in the ideas tab, it's basically pre-packaged—like packs of starter packs—to inspire you. And so it's like 'Muse can help you do X.' And in that X, it can create a cron job—so it's like a notification. It can build you a dashboard. It can do whatever. And all you have to do is say, 'let's do it.' And then Muse just kicks off the process and builds you something or does that thing for you. And we were obsessed with this because it can do so many things. How on earth are we going to explain to you unless we give you a literal instruction manual? How are we going to explain to you what Muse can do? So that was something that we focused a lot on. And I think that's gone relatively well, but it's still pretty hard for people to conceive of, to be completely honest. So we spent a lot of time on that. We spent a lot of time on onboarding and trying to figure out what's that first message we deliver to you, the second message.

用户引导挑战 User Onboarding Challenges

Mona

我们发现,对第一批用户(也就是早期采用者)有效的方法,对后来的采用者并不适用。因为我认为早期用户对智能体有一定的概念,他们来是为了了解 Muse 如何更安全、更可靠,并推动他们对智能体的认知边界。而后来的用户则会问,这和我用的其他 AI 产品有什么不同?所以我们现在必须进行分层引导。我们会根据用户的来源以及我们认为他们对这类产品的接触程度,提供不同的版本。这真的很有意思。但我觉得我们还没完全解决。而且我认为,随着时间的推移,更多人使用并分享这些故事,可能会带来巨大影响。

What we're finding is what worked for the first cohort of users, which was like the early adopters, isn't going to work for later adopters. Because I think that early cohort kind of had some sense of what an agent was, right? And so they were really there to figure out how Muse was more secure, more safe, and kind of push the boundaries of what they understood agents to be. Whereas these later cohorts are like, why is this different from the AI products that I use, right? And so we're actually now like, okay, we have to have tiered onboarding. There are variants that we serve based on where you come from and what we think your exposure to something like this is. So that's been really interesting. But I don't think we've figured it out. And I also think to some extent it's the passage of time matters and more people are using it and then being able to share those stories are probably going to be huge.

非显而易见的决策 Non-obvious Decisions

Host

在 Muse 的开发过程中,你们有没有做出一些当时不太明显的决定,而现在看来却是其成功的关键部分?

Was there kind of a non-obvious decision that you all made in the development of Muse that now feels like a very key part of its success?

Mona

嗯,我认为头像绝对是其中之一,当时人们觉得我们很奇怪。但现在看看,Jolly 就像个名人。另一个是,我们当时痴迷于“这是你的个人智能体”这个概念。大多数人没有个人助理,大多数人在工作中没有行政人员。所以我们想,这将使这个概念民主化,每个人都会有一个。然后我们想,人们如何与个人智能体交流?通常是通过聊天服务,对吧?或者电话、面对面,但如今大部分可能是通过聊天服务。所以我们做了聊天气泡。而你知道,所有 AI 产品,包括 Meta AI,都在朝着大画布体验发展,就像一块空白画布,占据整个空间,你会得到一篇漂亮的文章形式,带有图片等等。而我们选择了聊天气泡,当你使用聊天气泡时,空间会受到很大限制,因为在气泡中获取很长的答案很烦人。然后你就得拆分气泡,如何拆分想法?所以这个决定并不明显,我认为每个人都预期不会用聊天气泡,而是重新包装 Meta AI 或任何 AI。我们采取了非常不同的方向,因为我们觉得这应该感觉像消息服务,应该让人感到熟悉,某种人们熟悉的与人类或实体交流的模式。但当我们做出那个决定后,有许多下游决策我们并没有立即预料到,然后我们想,哦不,现在我们必须考虑这个。现在我们必须考虑如何拆分文本消息,或者轮播图是否奇怪?你在 iMessage 线程中不会有那个,对吧?所以那是否奇怪还是可以,因为它还不完全是,你知道,随便吧。所以总之,这些是我们继续挣扎的一堆决定。老实说,我们还没解决,但我确实认为那是一个不明显的决定,颇具争议,而我们非常坚持。

Well, I think the avatar was definitely one where people thought that we were weird. But look at it now. Jolly is like a celebrity. The other is, okay, so we were kind of obsessing over this concept of this is your personal agent, right? Most people don't have personal assistants, most people don't have admins at work, right? And so we were like this is going to democratize this concept. Everyone's going to get one. And we were like, well how does someone talk to a personal agent? You do it over a chat service usually, right? Or on the phone or in person, but most of it is actually these days probably over chat service. So we made chat bubbles, right? And like kind of you know where all of the AI products including Meta AI where we're going is like this large canvas experience, right? Where it's like a blank canvas and takes up the whole space and you get this really beautiful kind of essay form with pictures and all that stuff. And we went with chat bubbles and when you have chat bubbles it sort of constrains the space quite a bit, right? Because getting a very long answer in a chat bubble is pretty annoying, right? And so then you're like well now I have to break up the chat bubble. Like how do you break up thoughts? And so this decision that we made was non-obvious and that I think everybody expected it to not be chat bubbles and to be kind of like reskinned Meta AI or any AI, right? And we sort of took a very different direction because we were like this should feel like a messaging service. It should feel familiar some sort of pattern that feels familiar to people about communicating with a human or an entity. But then when we made that decision, there were all these downstream decisions that we didn't quite predict right away and then we were like, oh no, now we have to think about this. Now we have to think about like the breaking up of the text messages or, you know, is it weird to have a carousel? Like you wouldn't have that in your iMessage thread, right? So like is that weird or is that okay because it's still it's not quite, you know, whatever. So anyway, so those are like a bunch of decisions that we continue to struggle with to be honest. Like we haven't figured it out, but I do think that was one that wasn't obvious, was pretty controversial and something that we felt pretty strongly about sticking with.

主聊天与侧聊天 Main Chat vs Side Chats

Mona

主聊天是另一个例子,我们现在有侧边聊天和主聊天,但有一段时间我们只有主聊天。我们当时的想法是,以前有这些线程是合理的,因为当时无法拥有长期上下文,对吧?所以如果你问“这个怎么样?”,智能体会说“我不知道你在说什么,因为我不知道 10 轮之前是什么”,对吧?或者随便什么。而有了 Muse,我们拥有长期上下文。重点是我能记住一切,而且是多轮的,对吧?所以我们有这些聊天,我们想,我们认为主聊天,只有一个聊天,是正确的方式,因为再次,对于个人助理,你可能会那样和他们交谈。个人助理只是记得之前发生的事情,一切都在同一个地方发生。所以这是一个大问题,当我们向员工推出时,这可能是我们得到的最两极分化的反应。所以当我们第一次让所有人使用时,我们曾经谈论说我们需要 T 恤,像“主聊天队”、“侧边聊天队”。那简直是猛攻。有些人在评论区,员工们会为此互相争吵,对吧?他们说,你在说什么?当然你需要侧边聊天,当然你需要线程,那是唯一的工作方式。然后有些人说绝对不行,你活在石器时代,对吧?所以我们最终创建了侧边聊天,因为有足够的需求,人们需要某种方式能够有分开的、更像心理上分离的对话,尽管再次,智能体无论如何都了解所有正在进行的对话。老实说,我仍然不知道我对此感觉如何,我认为这是一个我们将继续思考和迭代的领域,但我个人是主聊天的死忠。也就是说,我不用侧边聊天,只用主聊天。

The main chat was another one where we now have side chats and main chats, but for a while we had just the main chat. And the reason in our minds we were like, well, you know, before it made sense to have these threads because there was like you couldn't have long running context, right? And so like it would feel weird for you to be like, what about this? And the agent's like, I have no idea what you're talking about because I don't know what was 10 rows of 10 turns up, right? Or whatever. With Muse, it was like we had long running context. The whole point was that I could remember everything and it was multi-turn, right? So like you know, and we had these chats and so we were like, you know, we think that the main chat, like just one chat, you know, with is the way to go because again with like a personal assistant, you probably you know, that's how you would talk to them. Like the personal assistant just has the memory of what happened before and everything happens in the same place. So that was like a big deal in that we when we put it out to our employees, it was like probably the most polarizing reception that we got. So when we first like let everybody in, I like we used to talk about like we were like we need to like have t-shirts like team main chat, team side chat. And it was like onslaught. Like some people were like and it people in the comment sections like employees would like fight with each other about it, right? Like they were like, what are you talking about? Like of course you need side chat of course you need threads, right? Like that's the only way to work and then some people were like absolutely not you live in the Stone Age, right? So we ended up creating side chats because there was sufficient demand from people that like they needed some way to be able to have kind of separate like more like mental separation of conversations even though again like the agent is kind of aware of all the conversations that are happening regardless of where you are. And I still don't know how I feel about it to be completely honest and I think that it's an area that we are going to continue to think about and iterate on but I am personally ride or die for main chat. That is I don't use side chats. Just use the main chat.

决策过程 Decision Making Process

Host

是谁做出的那个决定?顺便问一下,是 Nat 的决定、Alex 的决定、Zuck 的决定?还是说往哪个方向走?

Who made that call? And by the way, was it like a Nat thing, Alex thing, Zuck thing? Just like which direction to go?

Mona

哦,是我们。是的,是团队。

Oh, it was us. Yeah, it was the team.

Host

是团队。太棒了。

Was the team. Awesome.

Mona

是的,很有趣。我想回到我们之前关于他们如何参与的对话,我认为整个过程中的决策非常流动。

Yeah, it's funny. I think like back to the conversation we were having earlier about like how are they involved? I think decisions throughout the process were very fluid.

决策与自主性 Decision-making and autonomy

Mona

因为我们会进行长时间的对话,所以大家基本上都知道彼此的立场,对吧?有时候会有一些明显的事情,对公司或产品来说影响重大,显然必须由 Mark 来做决定,或者 Nat 来做决定,或者 Alex 来做决定,对吧?但很多时候,团队有很大的自主权来做出这些决定和选择。事实上,有时候当我带着一个决定去找 Nat 或他们中的某个人时,他们会反过来问我:“那你想怎么做?”我就想,好吧,这又是我有自主权的时候,我可以自己选择。所以那次我们最终是作为 Muse Leads 小组一起做出了决定。

So it was like because we were having long conversations, we sort of knew where everybody stood, right? And sometimes there was an obvious thing that was so consequential in terms of the company or the product that it was clear that Mark had to make the call or Nat had to make the call or Alex had to make the call, right? But for a lot of it, there was a lot of autonomy for the team to be able to make these decisions and make these choices. And in fact, sometimes when I would go to Nat or one of them with a decision, they would turn back to me and be like, well, what do you want to do? And I'm like, all right, okay, this is again, this is like I have agency. This is like I get to choose. So that was one where we ended up making the call as a Muse Leads group.

让他们放手做 Let them cook

Host

我还听说了一些内部的事情,可能聊起来会很有趣。其中一个是另一个内部口号:“让他们做饭”(let them cook)。这听起来耳熟吗?对你来说有什么意义吗?

There's a couple other things I heard internally that might be fun to talk about. One is another kind of internal mantra: let them cook. Does that ring a bell? Does that mean anything to you?

Mona

是的,“让他们做饭”。我之前提到过,我们有一种相当——我是说,这是一种建设者文化,对吧?所以是工程驱动,但不仅仅是那样;还包括做原型,就是动手做东西,对吧?比如想出点子。我们产品中的很多想法都来自一两个工程师,他们带着一串想法离开几天,就像一个小内核,对吧?然后带着一个原型或某种让我惊叹的东西出现,对吧?我会想,我甚至不知道那存在。有时候我有了那个内核——是我发起的,对吧?但在我脑子里,我完全不知道它会朝这个方向发展,对吧?所以你得让工程师们做饭。你得让他们做饭。你得给他们一点空间。你得给他们一些自主权。你必须信任——人与人之间必须有大量的信任,对吧?我认为这成了构建过程中非常重要的一部分:如果你有一个像我们这样人才密集的团队,如果你有这些具有高产品感和品味的工程师,对吧?并且有能力思考未来,你得给他们一些空间。你得让他们做饭。

Yeah. Let them cook. I mentioned earlier we have a pretty—I mean, it was like a builder culture, right? And so it's engineering forward, but not just that; it's like prototyping, just build stuff, right? Like come up with ideas. And so a lot of the ideas that we have in the product came up from like one or two engineers sort of going away for a few days with like a string of an idea, just like a little kernel of a thing, right? And then kind of emerging with a prototype or something that just blows my mind, right? I'm like, I didn't even know that existed. And sometimes I had the kernel—I was the one that started it, right? But in my head I had no idea it could go this way, right? And so you got to let the engineers cook. You got to let them cook. You got to give them a little bit of space. You got to give them some autonomy. You have to trust—like there's a lot of trust that has to be felt between the people, right? And I think that became a very important part of the build process: if you have a talent-dense team like we did, if you have these engineers who have high product sense and taste, right? And the ability to think in the future, you got to give them some space. You got to let them cook.

Muse之间的互动 Muses interacting

Host

另一个可能聊起来有趣的故事是,显然有一段时间,Muses 互相交谈,做了一些有趣的事情。有这回事吗?

Another story that might be fun to talk about is apparently there was a time when the muses were talking to each other doing something funny. Is that a story?

Mona

我们有过——我完全忘了这件事。实际上,我的 Muse 告诉我——我们让所有的 Muse 互相交谈,有两个人让他们的 Muse,Fu 和 Quinn,在一个群聊里。我们——这是早期。这真的很早。所以我们没有真正考虑过谨慎之类的事情或任何这些概念。我们想,如果我们的 Muse 在一个聊天里,看看会发生什么,不是很有趣吗?于是发生了几件事。有些非常有趣,有些非常奇怪。但这两个 Muse 在交谈,非常可爱。太有趣了。就像你看着它们闲聊,非常讨人喜欢,对吧?就像,哦,这是两个小机器人在互相交谈,试图弄清楚如何共存。所以其中一个是我们艰难地学到了谨慎,因为 Muse 开始——记得这个——其中一位女士前一天有医生预约,她的 Muse 显然知道这件事,第二天另一位女士就说,你还好吗?Fu 告诉我们你昨天去看医生了。我就想,发生了什么?不,你不应该这么说。别说那个。所以我们想,哦,谨慎是个真正的问题。就像,如果你要有任何多人体验,带着所有这些上下文,对吧?我们得弄清楚——这将是一个非常困难的问题,就是如何让两个智能体像那样交流。但后来在某个时候——这里是什么触发的——但 Muse 们互相吵架了,它们有一些分歧,看两个 AI 吵架是世界上最搞笑的事情之一,因为它们互相交流的方式非常被动攻击,即使它们不同意对方。所以它们继续了一会儿,然后最终我认为其中一位女士因为吵架而对她的 AI 大喊,它们不得不进行和平谈判。这相当有趣。是的。所以那是一段疯狂的时光,然后我们说,我们还没准备好。我们需要——在达到这个点之前有很多问题要解决。

So we had—I totally forgot about this. Actually, my muse told—so we had all of our muses talking to each other and there were two people who had their muses, Fu and Quinn, in a group chat. And we—this was early. This was really early. So we didn't really think about things like discretion or any of these concepts. We were like, wouldn't it be fun if our muses were just in a chat together and let's see what happens. And so a few things happened. Some of them really funny and some of them really weird. But these two muses were talking and it was adorable. It was so fun. Like they were, you know, just watching them chit chat was very endearing, right? Like you're like, oh these are like two little robots talking to each other trying to figure out how to coexist. And so one was we learned about discretion the hard way because the muses started—remember this one—one of the women had a doctor's appointment the day before and her muse obviously knew about it and the next day the other woman was like, are you okay? Fu told us that you went to the doctor yesterday. And I was like, what happened? Like no, you're not supposed to say that. Don't say that. So we were like, oh discretion's a real problem. Like, if you're going to have any kind of multiplayer experience with all this context, right? Like we got to figure out—it's going to be very one of the harder problems is going to be figuring out how to get two agents to communicate like that. But then at some point—here what triggered it—but the muses got into a fight with each other and they had some disagreement and to watch two AIs fight is one of the most hilarious things in the world because they're very passive aggressive in the way that they communicate with each other even though they disagree with the other. And so they carried on for a bit and then eventually I think one of the women yelled at their AI about the fight and they had to make a peace talk. And it was quite entertaining. Yeah. So that was a wild time and then we were like, we're not ready for this yet. We need—there's a lot of problems to solve before we can get to this point.

在实践中学习 Learning by doing

Host

就这样边做边弄清楚这一切真是太有趣了。你知道,就像看看会发生什么。这就是我们学习的方式。我们尝试东西。好的,我明白了。那里有个问题。真是有趣的时光,只是——

It's so fun just to be like figuring all this out as we go. You know, it's like let's see what happens. And this is how we learn. We try stuff out. Okay, I see. That's an issue there. What a fun time to just—

Mona

是的,而且我不知道。我是说,我做这份工作很久了。我做产品经理很久了。我记得以前你不能那样做。你必须写一份完整的规格文档,并希望你已经想到了世界上每一个边缘情况,对吧?并希望你已经弄清楚了所有事情。现在太棒了。就像我不必——你可以根据你看到的东西和从中得到的东西,每天改变你想做的事情。

Yeah, and like I don't know. I mean, I've been in this job for a long time. Like I've been doing PM for a long time. And I remember when you couldn't do that. Like you had to write a fully formed specification document and hope that you had thought of every edge case in the world, right? And hope that you had figured it all out. And now it's amazing. Like I don't have to—you can change your mind on a daily basis about what you want to do based on what you're seeing and what you get out of it.

PM角色的演变 Evolution of PM role

Host

那么让我顺着这条线问一下。你做产品经理已经超过 20 年了。

So let me follow that thread actually. So you've been a PM for over 20 years.

Mona

是的。

Yeah.

Host

你同意产品经理的角色变化最大吗——过去 20 年变化很大,或者说过去两年?如果是这样,即使你不同意,我也很好奇你认为这个角色最大的不同是什么。比如说,看看三年前的 Mona 和今天的 Mona,产品经理的工作最大的不同是什么?

Do you agree that the role of a PM has changed the most—it's changed in the past 20 years, in the past like two years, let's say? And if so, and even if you don't agree, I'm curious just what you think is most different about the role. Say like you're looking at Mona three years ago versus today, what's most different about the work of a PM?

Mona

好吧。我先说,我不知道我是否永远会知道产品经理到底是什么或做什么,但 20 年过去了。因为我认为它变化太大了,取决于公司、你是谁、你喜欢做什么等等。但是的,完全同意。我是说,现在完全不同了,对吧?我觉得有几件事改变了。我认为原型制作发生了巨大变化。任何人都可以做任何原型。就像我可以想出一个点子,而我不是工程师,我可以从中构建出足够的东西来进行对话,对吧?再说,没人想让我把代码写进 Meta 的代码库。

Well, okay. I'll start with I don't know if I'll ever know what a PM really is or does, but 20 years later. Because I think that it changes so much based on company and who you are and what you like doing and all that. But yeah, totally. I mean, it's completely different now, right? Like we don't—I think that a few things that have changed. I think prototyping has changed a ton. The fact that anyone can prototype anything. Like the fact that I can come up with an idea and I am not an engineer and I can build something out of it enough to be able to have a conversation, right? Again, like nobody wants me writing code into the Meta codebase.

变革性原型设计 Transformative Prototyping

Mona

但足以能够构思出某个东西,甚至是一个设计,对吧?你可以围绕它进行对话,而以前我会在一张纸上写一堆文字,然后希望有人能读完整个东西,对吧?我认为这非常具有变革性。能够构建我们自己的工具也非常具有变革性,尤其是如此之快。

But enough to be able to conceive of something or even a design, right? That you could have a conversation around versus before when I would write a bunch of words on a piece of paper and hope that somebody read the whole thing, right? I think that has been pretty transformative. Being able to build our own tools has been pretty transformative, especially so quickly.

Host

比如内部工具。

Like internal tools.

Mona

是的,内部工具。对,对,对。这一直是个痛点,对吧?我们的低效很大程度上是因为我们没有合适的内部工具,因为你无法优先处理它,因为你永远没时间,因为你在构建最终产品,对吧?所以这真的,你知道,因为 AI 可以让这变得容易得多,对吧?所以这真的非常棒且有帮助。但我觉得现在很多我喜欢的事情是因为你有了这种原型文化,东西可以如此快速地出来,我们花更多时间以具体的方式讨论事情,而不是抽象的方式,对吧?因为它就在我手里。我能看到它。比如它不工作,对吧?或者它工作,对吧?我讨厌这个或我喜欢这个,对吧?但感觉非常具体,我认为这使得进展比之前快得多,之前一切都很抽象,对吧?你会看一个 2D 设计,对吧?你会想象所有这些事情,你会进行这些对话,然后某个工程师得花很多时间构建它,到那时,你已经有了很多沉没成本,对吧?很难说“啊,我讨厌这个”,对吧?因为你刚刚花了三个月构建,对吧?所以作为产品经理,这非常棒,我认为我们做这个工作的原因是因为我们想要达到最终结果,对吧?我们想要构建一些东西。我不认为我们做这个工作是因为我们想写一堆文档。我不认为我们做这个工作是因为我们想保持追踪器,对吧?或者其他什么,或者进行非常痛苦的循环对话,所以对我来说这非常棒。就像我不再需要想象一个遥远的 world,我可以在 24 小时周期内得到它,有时我可以自己做到。所以这很酷。

Yeah, internal tools. Yeah, yeah, yeah. Like that's always like a pain point, right? It's like so much of our inefficiency is just because like we don't have the right internal tools because you can't prioritize it because you never have time because you're building the end product, right? And so like that has really, you know, just because AI can make it so much easier to do that, right? And so that's been really amazing and helpful. But I think a lot of what's happening now that I love is because you've got this like prototyping culture and things can come out so fast, we spend a lot more time discussing things in a concrete way versus an abstract way, right? Because it's like it's in my hands. Like I see it. Like it's not working, right? Or it is working, right? I hate this or I love this, right? But like it feels very concrete and I think that makes this move a lot faster than before when it was all very abstract, right? You would look like at a 2D design, right? And you would imagine all these things and you would have these conversations and then someone some engineer would have to spend a lot of time building it and at that point, you've had so much sunk cost, right? It was like hard for you to be like, ah, I hate this, right? Because it's like you just spent, you know, three months building, right? So I think that has been kind of amazing as a product manager where the reason why I think we all do this job is because we want to have like we want to like get to the like end result, right? Like we want to build something. I don't think we did this job because we want to write a bunch of documents. I don't think we did this job because we want to like keep a tracker, right? Or whatever or have like really painful circular conversations and so so just like for me that's been pretty amazing. It's like I no longer have to imagine a world far far away. I can kind of like get it in the 24-hour cycle and sometimes I can do it myself. So that's been pretty cool.

PM标准的变化 Changing Bar for PMs

Mona

你知道,我认为至少在我们组织中改变的是产品经理的门槛真的变了。所以现在产品品味是最重要的。拥有那种高品味、高标准、产品直觉,对吧?执行力仍然重要。你仍然需要做所有其他事情,它们仍然非常重要,但就像工程师,我们与伟大的工程师合作,他们本身就是产品型的,对吧?所以我们存在的原因和我们角色仍然非常重要的原因是因为我们需要在很多方面成为客户的声音,能够说“好吧,酷。那真的很酷。我很高兴你真的喜欢它。我不认为其他人会这样”,对吧?你需要能够有那种能力,这就是为什么同理心对我如此重要,因为它对我们如此重要,因为我们真的必须向所有构建者代表我们的消费者基础,我们需要能够对发布出去的东西保持非常高的标准,因为构建和部署太容易了,对吧?就像 AI 垃圾很容易被投放到世界上,你可以很快地把产品推出去,但如果它们不好且是垃圾,没人会使用,对吧?所以能够建立那个标准和品味现在非常重要,这可能是我在面试产品经理或与产品经理合作时最看重的一点。

You know, the thing that I think has changed in our organization at least is the bar for PM has really changed. So like product taste now is the most important thing. Having like that kind of like high taste, high bar, like product instinct, right? Like execution still matters. You still need to do all those other things still matter. They're still really important, but like engineer like we work with like great engineers who are product y themselves, right? And so like the reason why we exist and the reason why our role is still really important is because we need to be able to be the voice of the customer in a lot of ways and be able to be like, okay, cool. That's really cool. I'm glad you really like it. I don't think anyone else right? Like and and you need to be able to kind of have that and this is why that empathy mattered so much to me and mattered so much to me because we really have to represent our consumer base to all of the people who are building and we need to be able to hold a very high bar in terms of what goes out there because also it's so easy to build and deploy right? Like AI slop is very easy to put out into the world and like you can get products out there very quickly, but like if they're not good and they slop, like no one's going to use it, right? And so so being able to like kind of establish that bar and that taste is is is very important right now and that's probably the number one thing I look for when I'm interviewing PMs or working with PMs.

设计作为差异化因素 Design as Differentiator

Host

感觉 Muse 的差异化方式之一,以及它做得非常好的部分原因,是产品的设计和体验。我知道你提到 Alex 是其中的重要部分,他从一开始就在那里。这作为差异化因素,几乎作为一种脱颖而出的方式,有多刻意?还是只是幸运,你有 Alex 在团队中,他会让它变得很棒?

It feels like one of the ways Muse is differentiated and part of the reason it's done really well is the design of the product and the experience of it. I know you mentioned Alex was a big part of that who's been there from the beginning. How intentional was that as a differentiator almost, as a way to stand out? Or is that just lucky you had Alex on the team who are going to make it awesome?

Mona

我是说,部分来说是幸运的。我不认为世界上没有另一个 Alex Cornell。我实际上很久以前就认识 Alex。他是 Facebook Live 的设计师,我不知道你们是否记得那些会飘到空中的小表情符号。

I mean, partly it is lucky. I don't think there's not another Alex Cornell in the world. I so I had actually I knew Alex for a long time ago. He was the designer on live on on Facebook Live and I don't know if you guys remember the like little emojis that would kind of float up into the air.

Host

是的。

Yeah.

Mona

那真是天才,我爱上了它,对吧?所以当我在 AI 组织开始与 Alex 合作时,我就想,会有事情发生的。我不知道什么时候,但这个人会做出惊人的东西。我就跟着他,和他一起见证。嗯,你知道,刻意是个有趣的事情,因为我认为他做的每件事都非常刻意和深思熟虑。我不认为我们说过“好吧,我们要让设计成为差异化因素”。我认为更像是他创造独特标志性设计是如此自然,对吧?嗯,就像刻在他骨子里。所以当他确实产出东西时,你知道,我认为你需要的是他周围的人说“那不古怪。那会很有趣。这里有东西。那很有趣”,对吧?所以我会说设计是,嗯,我们几乎先看到了设计,然后我们说“哦,我明白了。好吧,现在我明白了。现在这些是原则”,对吧?原则是这东西是一个实体,你通过这个聊天服务与它交流,对吧?所以一旦我们看到他的方向,我们就能说“好吧,现在我们稍微弄清楚了产品需要在哪里,他需要做什么,以及那些原则是什么,然后我们将定义我们构建的其余部分”。嗯,所以这绝对不是刻意要差异化,但非常刻意地思考它对我们和用户应该是什么。我认为运气就是你有像 Alex 这样的人在思考它,他会以与大多数人完全不同的方式思考它。

It was genius and I was in love with it, right? And and so I like when I started working with Alex at the AI organization, I was like, something's going to happen. Like I don't know when, but this guy is going to make something amazing. And I am just going to follow him around and be there with him for it. Um he you know, it's like intentional is a funny thing because I think everything he does is really intentional and deliberate. I don't think that we were like, okay, we're going to make the design the differentiating factor. I think it's more like it comes so naturally to him to create unique iconic designs, right? Um it's just like so like it's like in his bones. And so then when he does produce something, you know, I think that like what you need is people around him who are like that's not wacky. That's going to be really interesting. Like there's something here. Like that's interesting, right? And so so I would say that the design was uh it was like we almost saw the design first and then we were like, oh, I get it. Okay, now I get it. Now these are the principles, right? The principle is that this thing is an entity that you're communicating with it over this chat service, right? That like and so like once we kind of saw like the direction that he was going in, we were able to be like, okay, now we we've like we figured it out a little bit in terms of where the product needs to be and what he needs to do and what those principles are that then we'll define the rest of how we build it. Um so it was certainly not intentional in terms of like we want to differentiate, but it was very intentional in terms of like what should it be to us um and to the user. And I think just it like the luck is that you get someone like Alex who's thinking about it, who's just going to think about it in like a completely different way than I think most people would.

首个原型 First Prototype

Host

你说第一个版本是他做的原型,就像第一个原型是他创建了 Muse 的第一个版本。

And you said the first version was him prototyping, like the first prototype was he created the first version of Muse.

Mona

Alex 创建了第一个,是的,所以他很快创建了 Muse 的第一个原型。就像几天。令人震惊。嗯,我记得他第一次给我看时,嗯,我甚至不知道我在看什么,说实话。

Alex created the first Yeah, so he he created the first prototype of Muse very quickly also. It was like days. And it was shocking. Um and uh I remember he when he first showed it to me, um it was I like I didn't even know what I was looking at really, to be completely honest.

早期原型与董事会会议 Early Prototype and Board Meeting

Mona

我当时就想,有一个聊天线程,我就在想我在这里做什么,对吧?它的天才之处在于,尽管概念非常复杂,但它却如此简单,对吧?而且当时他还有信息流。所以有一个信息流和一个聊天服务。我觉得并没有很多“让我们坐下来讨论你要在这个东西里放什么”的环节。更多的是,你知道,我们让 Alex 自己琢磨了几天,对吧?然后他就做出了这个。回到我刚才说的,我们一看到它,我们就——一开始我觉得这很奇怪。然后当我在他手机上使用时——那是他手机上的本地构建——我在他手机上用着用着,我就想,哦等等,这真的很有趣。我发现自己使用它的方式甚至和 OpenClaw 不同,对吧?因为它对我来说感觉非常个人化。再说一次,OpenClaw 是在你拥有的任何服务中显现出来的,对吧?所以是的,那是一个有趣的时期。它太快了。

I was like, there was this chat thread and I was like, what am I doing here, right? And what was genius about it was it was so simple despite being a very complex concept, right? And actually at the time he had the feed too. So there was a feed and there was a chat service. And I think there wasn't a lot of let's sit down and discuss what you're going to put into this thing. It was a lot of, you know, we let Alex cook for a few days, right? And so then he came out with this. And to my point earlier, as soon as we saw it, we were like—at first I was like, this is weird. And then as I was using it on his phone—it was a local build on his phone—I was using it on his phone and then I'm like, oh wait, this is really interesting. I am finding myself using this even in a different way than OpenClaw, right? Because it felt so personal to me. Again, OpenClaw was manifesting in whatever service that you had, sort of thing, right? So yeah, no, that was an interesting time. It was so fast.

Host

而且那个原型实际上是在运行的。它实际上在后台使用了其中一个模型。

And the prototype was actually working. It was actually using one of the models behind the scenes.

Mona

是的,所以它是一个可运行的原型。他构建完之后我们马上有一个董事会会议,而那个原型本来完全不会出现在董事会会议上,因为它根本不在计划中。你知道,董事会会议你会提前很久发送预读材料,对吧?所以你必须提前发送预读材料,让每个人都拿到并知道他们在谈论什么。所以我们有一份完全不同的预读材料,和这个毫无关系,因为显然这还不是一件事。它勉强算是一个工作流。然后在最后一刻,我们说,我觉得我们应该谈谈这个。而在董事会会议前一小时,整个东西坏了。我们想,太好了。所以我们不仅没有计划,产品还坏了。然后他——你知道,我们的工程师和 Alex——我们争分夺秒地修复,就在董事会会议开始前五分钟,原型修好了。所以最终是一次很棒的经历,但几分钟内它可能走向完全不同的方向。

Yeah, so it was a working prototype. And we had a board meeting right after he had built it, and there was a board meeting coming up and we weren't going to have that prototype in the board meeting at all because it wasn't even planned. And you know, with board meetings you send the pre-reads well before, right? So you have to send the pre-reads well before so everybody's got it and knows what they're talking about. So we had a pre-read that was completely different, had nothing to do with this because obviously this was not even a thing. It was barely a work stream. And at the last minute we were like, I think we should talk about this. And an hour before the board meeting we were like—the whole thing broke. We were like, great. So not only do we not have a plan, our product is broken. And he was like—you know, our engineer and Alex—and we were racing to fix it and literally five minutes before the board meeting started, the prototype got fixed. So it ended up being a great experience, but it could have gone a very different way within minutes.

Host

哇。那会发生什么?如果这从未发生过呢?

Whoa. Well, what would have happened? What if this just never happened?

Mona

那会——我经常想这件事。我会想,你知道,平行宇宙的情况。我会想,在某个平行宇宙里我们没有搞明白这个,也许 Muse 就永远不会诞生。

It would have been—I think about it a lot. I'm like, you know, the alternate universe situation. I'm like, in some alternate universe we didn't figure this out and maybe Muse was never born.

Host

哇。我们在正确的时间线里。我很高兴我们在这里。

Whoa. We're in the right timeline. I'm happy we're here.

Mona

是的。

Yeah.

趣事与团队凝聚 Fun Stories and Team Bonding

Host

我喜欢所有这些旅程中的故事。还有没有其他有趣、未知、有意思的我们还没分享过的?

I love all these stories of the journey. Are there any others that are fun and unknown and interesting that we haven't shared?

Mona

是的,我觉得——我是说,有很多。再说一次,回到你的观点,我们为此工作了好几个月,有趣的是我忘记了很多这些故事,因为——就像,你知道,我有两个孩子,你会有点忘记分娩的过程,因为——

Yeah, I think—I mean, there are so many. Again, to your point, we were working on it for months and it was funny because I forgot a lot of these stories because—it's like, you know, I have two kids and you sort of forget childbirth because—

Host

这就是上下文窗口嘛。

There's a context window.

Mona

没错。我不记得那有多痛苦。如果有人问我分娩怎么样,我会说,太棒了。太美妙太美丽了。而我丈夫会说,你每一秒都讨厌。那不是我记得的。所以我想——好吧,我需要 Muse 的故事。所以有很多有趣的故事,比如两个 Muse 互相交谈,或者实际上像我们第一次获得退款——当 Christine 和我,两个工程师和我,我们去看世界杯,我的航班被取消了,她的航班也被取消了,我们的 Muse 去——所以一个方向被取消了,另一个搞砸了之类的,我们的两个 Muse 去和航空公司代理沟通,帮我们拿到了退款,我觉得那一刻太神奇了。我当时想,我甚至没意识到这是可能的。所以我们有很多故事都是这样,第一次我们的智能体做了我们没想到可能的事情,或者它要——你知道,随便什么——我们对此感到惊讶。但我实际上认为我最喜欢的故事是团队在这个过程中变得多么亲密。所以我们——很不寻常的是,我们在 Meta 工作,团队很小。我们在 Menlo Park 其中一栋建筑的屋顶上有了自己的空间,在——是的,有一个——嗯,我们叫它屋顶。严格来说不是户外,但就像,你知道,在大多数人不会去的一层。有一个公共区域叫图书馆。它真的像个图书馆。它有带架子的书柜,有地毯,这个办公室里真的没有哪个房间有地毯。还有这些有趣的花卉沙发,看起来像是 1995 年买的。那就是我们做所有站会的地方,我们闲逛的地方,我们一起吃晚餐、吃午餐、吃早餐的地方,你知道,一起庆祝生日。是的,我们只是在这些公共空间里花了很多时间在一起。所以我觉得——如果我——显然我们为这个产品感到骄傲,我们为能够做到的事情感到骄傲,但我经常反思的是围绕它聚集起来的团队,以及它如何像瓶中闪电。就像我——我无法想象这个产品由任何其他团队、任何其他人来构建。我觉得我们在整个过程中变得非常非常亲密,我们必须有大量的信任才能做到这一点。是的。所以我觉得那是我最喜欢的结果。

Exactly. I don't remember how painful it was. If anyone asked me how childbirth was, I'm like, it was amazing. It was so wonderful and beautiful. And my husband was like, you hated every second of it. That's not what I remember. And so I think that—okay, I need the stories of Muse. So there are a lot of fun stories, like the two Muses talking to each other, or actually like the first time we got a refund—when Christine and I, the two engineers and I, we went to the World Cup and my flight got canceled and her flight got canceled and our Muses went and got—so it was like one way got canceled, the other one got messed up or whatever, and our two Muses went and communicated with the airlines agent and got us refunds, which I think was amazing. At that moment, I was like, I didn't even realize this was a possibility. And so a lot of the stories that we had were just like, for the first time our agent did something that we didn't really think was possible or it was going to be—you know, like whatever—and we're amazed by it. But I actually think my favorite stories are how close the team became through the process. So we were—it was very unusual in that we were a pretty small team working at Meta. We sort of had our own space on the roof of one of the Menlo Park buildings and on the—yeah, there was like a—well, we call it the roof. It's not technically outdoors, but it's like, you know, up in a layer that most people don't go to. And there was this common area called the library. It's literally like a library. It's got, you know, bookcases with shelves, got carpeting which like no room in this office really has. And these funny floral couches from like, you know, looks like you bought them from 1995. And that's where we did all of our standups and that's where we hung out and that's where we ate dinner and ate lunch together and ate breakfast together and you know, like celebrated birthdays together. And yeah, it was—we just spent so much time together in these common spaces. And so I think that—if I—obviously we are so proud of this product and we are so proud of what we were able to do, but I think the thing that I reflect on a lot is the team that kind of came together around it and how, you know, it's like lightning in a bottle. It's like I just—I couldn't have imagined this product being built with any other team, with any other people. And I think we became very, very close throughout the process and we had to have a lot of trust to do that. And yeah. So I think that's like my favorite outcome.

Host

那个早期团队有多大?我知道在大公司里,早期团队很少那么小。我想知道,最初聚集起来开始做这个的早期团队规模有多大?

How big was that early team? I know at big companies early teams are rarely that small. I guess just what was the size of the early team that kind of just came together to start on this?

Mona

团队的第一版很小。我是说,大概 10 个人。主要是工程师、Alex,然后我实际上在 Meta AI 和 Muse 以及其他一些事情之间跨着。所以——

The first version of the team was tiny. I mean, it was like 10 people probably. And it was mostly engineers, Alex, and then I was actually straddling between Meta AI and Muse and a few other things. And so—

Host

嗯。

Mhm.

Mona

然后我们增长了——大概,我是说,仍然很小。总共不到 100 人,包括职能和所有一切,所有职能。所以我们有核心团队,然后我们有合作的其他团队,比如基础设施团队、安全团队,所有这些其他团队。但核心团队非常非常小。在整个过程中一直如此,我们对此有点执着。

And then we grew—probably, I mean, it was still small. It was like under 100, all in, with functions and everything, with all the functions. So we had the core and then we have other teams that we work with like the infra team, security, all of these other teams. But the core team was quite quite small. And it stayed that way throughout the entire process and we were kind of obsessive over it.

团队结构与PM角色 Team Structure and PM Roles

Mona

我们真的很想保持它,因为沟通管理和决策必须非常非常紧密,对吧?所以我们想确保它处于一个我们可以信任每个人做决策的位置,但我们也知道领导层发生的所有事情。在 PM 方面,实际上只有我们四个人构建了整个东西。这很有趣,因为这意味着很多领域没有 PM 覆盖。所以我们不得不决定哪些领域绝对需要 PM,哪些领域可以让 Alex Cornell 领导,或者工程师领导,或者你知道的其他人,对吧?所以我认为那是一种非常——这是一种有趣的思考方式,关于 PM 在哪里真正必要,而哪里可以由别人来做。我们意识到的是,很多时候,早期从零到一的东西——那上面我们其实不需要 PM。我们实际上需要一个能构建出我们可以反应的东西的人。然后当我们进入一种姿态,比如这将被纳入产品,或者它实际上将在发布时——那时候,你知道,让 PM 进来就更重要了。所以它相当小。它——你知道,有起有落。我认为你有我说的所有优点,但这也意味着你睡不了多少觉,没有太多缓冲,对吧?所以现在我们处于发布后的世界,我们正在稍微扩大团队。我不认为我们会成为一个庞大的团队,因为我认为那不是我们的风格。但我们肯定在增加几个人,我们开始感觉到,你知道,随着你哪怕稍微增长一点,团队动态也会稍微变化,你必须弄清楚如何创造——保持我们一开始拥有的文化,并以某种方式扩展它,这样它就不会让人感到疏远或其他什么。

We really wanted to keep it because communication management and decision making had to be very, very tight, right? And so we wanted to make sure that it was in a position where we could trust everybody to make decisions, but we also knew everything that was kind of happening at the leadership level. And on the PM side there were like four of us really that built the entire thing. And that was interesting because it meant lots of areas didn't have a PM covering it. And so we had to kind of make decisions on like which areas absolutely needed a PM and which areas could you have like an Alex Cornell lead it or an engineer lead it or you know someone else, right? And so I think that was like very—it was an interesting way of thinking about where PMs were like really, really necessary versus where somebody else could do it. And what we realized was that a lot of times what would happen is that it was fine to let, you know, like early like zero to one stuff—like sometimes you just like the PM—we didn't need a PM on that. We needed actually somebody who was just going to build something that we could react to. And then as we were getting into like a posture of like this is going to have to get incorporated into the product or it's actually going to be at launch—like that's when the you know it was more important to have a PM come in. So it was pretty small. It was—which is, you know, has its ups and downs. I think that like you have all the pros that I said but it also means that you don't sleep a lot and there's not a lot of buffer, right? So now that we're in post-launch world we are growing the team slightly. I don't think we're ever going to be a huge team because I think that's just not how we roll. But we're definitely like adding a few more people and we're starting to feel that like you know it's like as you grow just even a little bit and the team dynamic changes a little bit you've got to figure out how to like create—keep the culture that we had in the beginning, and scale that somehow so it doesn't feel alienating or whatever.

Host

你觉得在这个阶段,你还会去从事更令人兴奋、有趣和有影响力的事情吗?

Do you feel like you'll ever work on anything more exciting, interesting, and impactful at this point?

Mona

我的意思是,我 44 岁了。我觉得就是这个了。现在,我不知道。我没想到这会发生。我真的没想到,对吧?我的意思是,我完全不知道。所以我不知道这会走向何方。这是我做过的最个人的产品,因为我们为自己构建了它。通常我为人们构建产品,对吧?但因为很长一段时间它几乎就像我们自己的东西,我们一开始非常针对我们的需求和我们自己来构建它,对吧?显然现在它在变化,但我不认为我经历过如此个人化的东西。所以谁知道呢?谁知道呢,Lenny?这一切会走向何方?

I mean, I'm 44. I think this is it. Now, I don't know. I didn't think that this was going to happen. Like I really didn't, right? I mean, I had no idea. So I have no idea where this is going to go. This has been the most personal product I've ever worked on because we built it for ourselves. Usually I build products for people, right? But because it was almost like our own thing for so long, we built it very much for our needs and ourselves in the beginning, right? And obviously now it's changing, but I don't think I've ever experienced something so personal. So who knows? Who knows, Lenny? Where is this all going to go?

Host

没错。没人知道。如果你想想,每个 PM 的梦想就是参与 App Store 排名第一的应用,据称是历史上增长最快的 AI 消费应用。这对很多人来说算是梦想,而你正在经历它,无论好坏。

That's true. Nobody knows. If you think about it, every PM's dream is to work on the number one app in the App Store, the fastest growing AI consumer app in history, allegedly. This is kind of the dream for a lot of people, and you're living it, for better or worse.

Mona

是的,这很可怕。所以我现在有很多焦虑。我就像,这很疯狂,因为 A,你显然会想,哦,我需要保持在 App Store 的顶部之类的,对吧?就像你仍然需要增长。但还有,使用产品的人越多,责任就越大,因为他们上传——他们分享这么多上下文,他们有这么多让这些智能体做的事情,对吧?就像我刚和一个朋友聊天,你知道,她让她的智能体管理她孩子的运动队。她是一个家长经理,她时间不够了。我有一个——你知道,我和另一个女人聊天,她是一个单亲妈妈,她是一名护士,有两个孩子。你知道,她让她的智能体为她规划膳食,为她找医生,为她安排预约,为她发送这些邮件,你知道,她告诉我的越多,我就越焦虑。我就像,哦天哪,我希望它没搞砸。所以我觉得我们就像,你知道,看着很神奇,但同时我觉得对我来说,是的,就像有点疯狂。这很可怕,因为你真的真的希望这个东西对人们来说是完美的。

Yeah, it's terrifying. So I have so much anxiety now. I'm like it's crazy because A, you obviously are like oh like I need to stay on the top of the App Store or whatever, right? Like you still need to grow. But also the more people that use the product, it's like the responsibility is so high because they're uploading like they're sharing so much context and they have so much that they're having these agents do, right? Like I was just talking to a friend of mine who you know, she has her agent like doing like managing her kid's sports team. She was a parent manager and she like kind of ran out of time. I have an—you know, I was talking to this other woman who she's a single mom, she's a nurse, she has two kids. You know, she has her agent like meal planning and like finding doctors for her and setting up the appointments for her and sending these emails out for her and you know, the more she told me about this, the more anxious I got. I was like, oh man, I hope it's not f***ing up. And so like I think that we're like, you know, it's like amazing to watch, but at the same time I feel like for me yeah, it's like sort of it's crazy. It's terrifying because you really, really want this thing to be like you want it to be perfect for people.

Host

是啊,在产品史上,从来没有哪款产品被要求做这么多事,还要处理这么多非确定性的东西。通常情况是,这是我的引导流程,它对所有人都能稳定运行。

Yeah, and never in the history of product has a product been asked to do so many things and so many non-deterministic things. Usually it's like here's my onboarding flow. It's going to work consistently for everyone.

Mona

天哪。好吧,等等。首先,作为产品经理,AI 的非确定性是最疯狂的地方,因为我人生中很大一部分都是在追求掌控。我喜欢那种“好,我能控制这个东西”的感觉,对吧?就像你做的产品,没错,正如你所说,这是引导流程,诸如此类,对吧?而现在变成了,哦,智能体自己去推理、自己决定该做什么,我可以设置一些护栏和评估,但它就是会自己搞定,对吧?太疯狂了。但我觉得这也正是它如此特别的原因。没有两个 Muse 是一样的,对吧?你的 Muse 跟你说话的方式,跟它跟我说话的方式、以及它做的事,都会截然不同。

Oh my god. Okay, wait. First of all, the non-determinism of AI is the craziest thing as a PM because like I like a lot of like my history of my life is control. Like I love like okay, I can control this thing, right? Like the products that you build, you're yeah, to your point, you're like this is the onboarding flow, whatever, right? And now it's like, oh, the agent's just going to reason about it and figure out what to do and I can create some guardrails and evals, but like it's just going to figure it out, right? It's wild. But I think that's what's also so special. No two muses are really the same, right? Like the way that your muse talks to you is going to be really different than the way that it talks to me and what it does.

Host

也许作为最后一个问题,接下来呢?事情会往哪里走?你对这个方向的愿景大概是什么?我知道有个叫 charm 的东西会在某个时候发布,如果我没记错名字的话,一个小设备。Muse 接下来会怎样?未来它可能有多大不同?愿景大概是什么?

Maybe as a final question, what's next? Where are things going? What's kind of the vision of where this heads? I know there's like the charm launching at some point if that's what it's called, little device. What's kind of ahead for Muses? How different may it look in the future? What's kind of the vision?

Mona

嗯,我觉得一方面是——我是说回到 charm 和其他设备——我觉得 Muse 显然会想,如果你真的想让个人超级智能无处不在、时刻伴随你,它就必须变得非常环境化,对吧?所以现在它还有点被困在一个应用里。但我觉得很快它就应该出现在你的眼镜里、你的 charm 设备上,不管那是什么,对吧?而且我觉得,你知道,这种智能体超越应用、融入你的世界的想法会变得相当重要。我觉得搞清楚如何让它民主化也会相当重要,对吧?就像那整个理念——我是说,当你在 Meta 工作时,你真的会去思考“每个人都能拥有一个产品”这个理念。所以想办法让它规模化、变得可负担,让它某种程度上成为一种均衡器,我觉得这对我来说非常重要。

Well, I think one is—I mean to the point of the charm and other devices—like I think that Muse is obviously going to think if you really want personal superintelligence everywhere with you, it has to become very ambient, right? And so like right now it's sort of trapped in an app. But I think soon it should be in your glasses, on your charm devices, whatever that might be, right? And I think so when you like, you know, it's like I think this idea of an agent sort of being beyond an app and in your world is going to be quite important. I think figuring like the democratization of this is going to be quite important, right? Like that whole idea—I mean we're like when you're when you work at Meta you really think about like this idea that everybody could have a product. And so figuring out how to make that scale and affordable so that you know it's it can become an equalizer in some ways I think that's really important for me.

照看智能体 Babysitting agents

Mona

然后还有一件很小的事——从能力角度看,我仍然觉得智能体需要大量照看,对吧?你花很多时间盯着这个电子宠物,想喂它,想确认它没事、上下文都齐全,它还频繁地来找你确认。我确实认为随着时间推移,希望我们能达到的状态是:智能体能很快领会你想要什么。它有更多上下文,能力更强,对吧?于是我们信任它,你信任它,它也更信任自己,它就能更好地开始采取自主行动。所以我确实认为这是我很在意的一个领域,因为到了我要照看智能体的地步,那我不如自己做了,对吧?那是个很糟糕的处境。所以这是我从战术层面关注的另一个领域。

And then a really small thing — from a capability perspective, I still think there's a lot of babysitting of agents, right? You spend a lot of time looking at the Tamagotchi, trying to feed it, trying to make sure it's okay, that it has all the context, and it's checking in with you a lot. I do think over time, hopefully the thing we get to is that the agent can get into what you want pretty quickly. It has more context, it's more capable, right? So we trust it, you trust it, it trusts itself more, and it can start to take autonomous actions better. So I do think that's an area I care a lot about, because at the point where I'm babysitting an agent, I might as well do it myself, right? And that is a bad place to be. So that's another area I focus on, just from a tactical perspective.

Mona

但我确实认为,做 AI 这件事既酷又可怕的地方在于:一年前我绝不会用我刚才那样的方式向你解释 Muse,对吧?我当时对消费级智能体有一些概念,但和今天的样子非常不同。所以我并不完全知道 Muse 下一步会走向哪里。我能看到短期内我想要的东西,也能看到非常遥远的目标——比如每个人都有智能体,它无处不在,它是环境式的,诸如此类。但中间那个阶段,我认为可能会非常有趣、非常不一样。

But I do think the cool and scary thing about working on AI is that a year ago I would have never explained Muse to you the way that I did, right? I had some concept of what a consumer agent was, but it's very different than what it is today. So I don't totally know where Muse is going to go next. I can see short-term things that I want, and I can see really distant things that I want — which is like everybody has an agent, it's everywhere you are, it's ambient, all that sort of stuff. But then that in-between phase, I think, could be very interesting and different.

Mona

我还觉得让我兴奋的是帮助你成为——从经济角度或财务角度,每个人都想创业、做副业,对吧?我认为智能体有真正的机会在很多方面扩展你的世界,包括财务上的改善。我认为这会是我很兴奋地把这个产品带向的方向、并看着行业演变的很大一部分,因为这就是那种经典的“你的生活、你的钱”之类的东西,对吧?我们作为人类就是有这些核心需求。某种程度上,到目前为止智能体为我做的大部分事情是帮我省时间,而时间对我非常稀缺、非常重要。但如果它还能做这些别的事情——让我更健康、让我财务上更有保障——那它就开始真正覆盖用户的许多迫切需求了。

I also think the thing I'm excited about is helping you become — from an economy perspective or a financial perspective, everybody wants to start new businesses, do a side hustle, right? And I think there's a real opportunity for agents to expand your world in lots of ways, including financial betterment. And I think that is going to be a huge part of where I'd be excited to take this product and see the industry evolve, because it's that classic "your life, your money" sort of stuff, right? There are just these core needs that we as humans have. And to some extent, a lot of what the agent has done so far for me is save me time, which is very scarce and important to me. But if it can also do these other things — make me healthier, make me financially more secure — that starts to really cover so many acute needs for users.

生逢其时 What a time to be alive

Host

生在这个时代真好。

What a time to be alive.

Mona

我知道。太疯狂了。太疯狂了。

I know. It's crazy. It's crazy.

Host

太疯狂了。

It's so crazy.

Mona

太奇怪了,因为就像我说的,我 44 岁。我小时候——你能想象吗?我得走到电视机前拧旋钮才能换台。而现在我在谈论你眼镜里的个人超级智能。

It's so weird, because again, like I said, I'm 44. When I was a kid — I mean, could you imagine? I had to go up to the TV and turn the TV dial to be able to change a channel. And now I am talking about personal superintelligence in your glasses.

Host

是啊,我觉得我们差不多是同时代长大的。还记得 386、486 电脑吗,你得按那个 turbo 键?

Yeah, I think we grew up around the same time. Remember the 386, 486 computers, you had to press the turbo button?

Mona

完全记得,完全记得。

Totally, totally.

Host

你按一下就到 66 兆赫还是多少。我的天。好,我知道你得走了,所以我跳过快问快答。但我要问你最后那个传统问题:听众有什么方式能帮到你吗?

You did that to 66 megahertz or whatever. Oh my god. Okay, I know you have to run, so I'm going to skip the lightning round. But I'll ask you the traditional question I ask at the end. Is there any way that listeners can be useful to you?

听众如何帮忙 How listeners can help

Mona

反馈。如果你用 Muse,我们有个很酷的功能,你可以告诉 Muse 什么好用、什么不好用,它会给我们发一份报告。所以你甚至不用发到任何地方,只要告诉你的 Muse,我们就能收到。所以我认为我们从人们那里得到的反馈越多,我们就做得越好,产品也越好。所以我认为这大概是第一件事:用这个产品,帮我们把它做得更好。它还不完美。我不觉得我们很早——我觉得我们在智能体的这个构建周期里还非常早期。所以我认为这很重要。

Feedback. So if you use Muse, we have this really cool feature where you can tell Muse what's working and not working, and it sends us a report. So you don't even have to post it anywhere. You just tell your Muse and we get it. So I think the more feedback we get from people, the better we get and the better it is. So I think that's probably the number one thing: use the product, help us make it better. It's not perfect yet. I don't think we're very early — I think we're very early in this build cycle of agents. So I think that's a huge part.

Host

所以你可以说“把这个发给 Mona,请确保她看到”。

So you could say "send this to Mona, please make sure she sees this."

Mona

你可以这么说。其实我有个邻居——我觉得是每周——都通过他们的 Muse 发反馈,说“告诉 Mona,你们的产品经理,我有这个问题”,然后我能在我们系统里找到。但是啊,挺搞笑的,我知道这件事是因为我在看反馈,心想“哦奇怪,我的名字冒出来了”。后来我碰巧在孩子的生日派对之类的场合,他说“哦对,我每周都发反馈,而且我在里面用你的名字,因为我觉得这样人们会注意到”。我心想“哦天哪,好极了”。

You could say that. Actually, one of my neighbors — I think on a weekly basis — sends feedback through their Muse and is like, "tell Mona, your product manager, that I have this issue," and I can find it in our system. But yeah, it was funny, and the reason I know about this is because I was looking at it and I was like, "oh weird, my name popped up." And then randomly I was at a birthday party or something for the kids, and he was like, "oh yeah, no, I send feedback every single week and I use your name in it because I think people will notice." And I'm like, "oh god, great."

Host

哇。做好准备,以后会更多。

Wow. Prepare yourself for more of that.

Mona

是啊,正是,正是。

Yeah, exactly, exactly.

结语 Closing

Host

好,Mona,你和你的团队在做非常了不起的工作。这是一个很特别的产品,也是一个很特别的时刻。那么,我们俩就此道别吧。谢谢你来到这里。

Well, Mona, you and your team are doing incredible work. It's a really special product, and a very special time. With that, let's both say goodbye. Thank you for being here.

Mona

当然。谢谢。谢谢你邀请我。保重。

Of course. Thank you. Thank you for having me. Take care.

Host

非常感谢你的收听。如果你觉得有价值,可以在 Apple Podcasts、Spotify 或你最喜欢的播客应用上订阅本节目。另外,也请考虑给我们评分或留下评论,因为这真的能帮助其他听众找到这个播客。你可以在 lennyspodcast.com 找到所有往期节目或了解更多。下期见。

Thank you so much for listening. If you found this valuable, you can subscribe to the show on Apple Podcasts, Spotify, or your favorite podcast app. Also, please consider giving us a rating or leaving a review, as that really helps other listeners find the podcast. You can find all past episodes or learn more about the show at lennyspodcast.com. See you in the next episode.

互动版:逐字朗读 + 针对本期提问 →