Hey everybody and welcome to Generative Now. I am Michael McDonough and I am a partner at Lightspeed and I am so thrilled to be sitting down with my good friend, my co-founder and the CEO of Oboe near Zickerman.
Nir and I co-founded Anchor together almost a decade ago, and we are back at it now again with a new company called Oboe, an AI learning platform with a mission to make humanity smarter. Nir and I talk all the time, like every day all the time, but in this episode, we go even deeper. We revisit the early days of Anchor. We reflect on some of the early decisions we made and the things we got wrong and maybe some of the things that we got right.
And lastly, we respond to the questions that some of you all sent in through Twitter about OVO. So take a listen to this conversation with Nir Zickerman, CEO of OVO. Hey, Nir.
How you doing, Mike? Going well. This should be interesting. Did we ever record any podcasts when we were building Anchor or when we were at Spotify? Like you and me. Obviously, like individually, I think we both did. But did we ever do any of these together? Shout out to Startup Soundtrack. Remember Startup Soundtrack? Oh, yeah. Yeah, yeah. That was you like talking about music with founders or something? Yeah, when Spotify released the music and talk feature, which I was...
It was one of the initiatives that I helped lead. You and I thought it would be fun. This must have been in 2020, maybe. We thought it would be fun to do
Podcast where we would talk to founders about the music that inspired them while they were on their startup journey. You and I actually did an episode that was about the anchor journey. Although I can't remember the songs that we talked about, but then we talked to a few others. It's still on Spotify. Is it? Oh, it's still up. I think so. I never took it down. Yeah. You didn't last too long with that, right? Maybe six episodes or less. Yeah. I think that's mostly experimental. Podcasting isn't for the week, you know, it's it's, it's tough.
I wouldn't be able to do it without our team. It's like, yeah, this is hard. This is hard. If there's anything that you and I learned during the anchor days, it's that, uh, and I think this is true for any type of content creation, but especially true for podcasting consistency matters more than anything. Oh yeah.
There's this podcast I may have told you about. It's relatively new. Technology Brothers. Have we talked about this? First of all, it's very funny and it's good. But those guys, I know one of the guys doing it. They're working so hard. It's probably more work than a startup. I think it's one of those things where if they're doing a good job, you don't realize how much work went into it. Yeah, exactly. Totally. I mean, I know everything about you.
Including about your new company because I'm a co-founder of it. But you're in the day-to-day. I'm not. This is not my full-time thing.
And so there's a lot that goes on in the day to day that I don't know about. So I'll probably ask you some stuff about that. For the audience, it's probably best for people to hear it in your words. You think about this all day, every day. So you're going to probably explain it better than I have. Plus, I'll probably like reveal something that we're not ready to reveal if I explain it. What is OVO? We're building the most personalized and efficient way to learn anything. The dream here is that
especially now and now that we can in the age of AI do this, to build a learning platform that is more effective and catered to a student's needs than anything else that has previously existed. I think the only analog that really has ever existed at the level of what it is that we're trying to build is a human tutor, which is one-on-one, completely personalized, completely goal-oriented to what the student needs. And the reality is technology is
for whatever reason has failed to deliver on the promise of, uh, of allowing people to learn as effectively as they could with a tutor, which is obviously a very cost prohibitive thing. It's not something that most people on earth have access to. So the dream is if you could take the effectiveness of a human tutor and the level of personalization and customization and control and, uh,
and motivation behind it, right? Because one of the big things that tutors do is they also focus on finding ways to motivate the student to continue learning and to be excited about what they're learning. If you can take that and leverage technology to democratize access to that type of learning across anything that someone might want to learn,
That'll change the world. I mean, that's, that's, I can't think of a more inspiring mission to work towards. And it's something that I'm personally really excited to work on. So when I tell people about this and I, and I give a similar pitch, I, the thing that people always ask me, it was like, isn't, isn't this just chat GPT? Like chat GPT can tutor me right now. I can ask it anything. It could tell me anything I want to know. I have a response to that question, but I'm curious, how do you, how do you respond to it?
Look, LLMs are incredible and candidly, what we're building would not have been possible to build prior to LLMs, which is why I think now is exactly the right time to build what it is that we're building. The fundamental architecture that powers large language models is inherently unable to sustain
effective, high quality learning over long periods of time. When I say long periods of time, I mean students that are taking courses for an entire semester, not just people who are cramming for their finals. Right. And I'm sure you know this, that Chachikati went down a few days ago. That's chaos. Chaos for anybody studying for finals. Yeah, I'm sure.
But the truth is that if you're not just cramming or trying to get a short answer to something, but you're actually trying to learn over a long period of time where you are retaining information, using it to learn more complicated and advanced things, synthesizing information that you've already learned before over months, over years, the way that true learning journeys are supposed to take place for anybody from K through 12 students learning things for school to higher education, to people teaching themselves programming or musical instruments or anything like that.
LLMs are just not effective at teaching that way. They deteriorate in quality over time. Context becomes increasingly inefficient to store over time. And because of the fact that they're all based on just probability models, the likelihood of errors and of drifting and of hallucination actually increases the longer you use them. If you've had long conversations with LLMs, any of these models, it's not just ChatGPT,
they deteriorate over time. And I think that's a fundamental limitation of the architecture. It's not because these models just have to get bigger and ingest more data. If you think about the way that they work under the hood, it's just probabilities multiplied by probabilities. And at a certain point, the longer the context window is and the longer the conversation takes place, the higher the likelihood of drift and of compounding errors. I think what needs to be built is a system that's actually the exact opposite. It's predicated on this idea that
the more you interact with this platform, the better it should get at teaching you. It understands how you learn. It understands what you're excited about and what motivates you. It understands what mediums and formats you like to learn in. Are you a visual learner? Are you a type of person who memorizes things really well? Do you need a lot of examples? What types of examples do you need? And just like a tutor, the longer you spend with this thing, the better it should get at teaching you, which is not what an LLM does. I'm curious if that matches. Does that match up with
with how you think about it? Yeah. I mean, yes, but you just say it better than I do. Probably because you think about it all day. I also talk about this all the time. Yeah. Yeah, of course. So an LLM can't do this. And so this is not an LLM. This is not AI. It is AI powered. But I think one of the important distinctions is that there are a lot of companies nowadays that are attempting to kind of serve as wrappers around the LLMs.
leverage LLM technology, but create unique interfaces for whatever the use case might be. And that's great. And I think for a lot of use cases, including certain educational use cases, that is very powerful.
But the problem with that is that if you're leveraging LLMs to power your architecture under the hood, then you are subject to all of the limitations that LLMs have, including what I just talked about and how the system will not improve over time generally. It actually gets increasingly inefficient and less accurate over time. So the approach that we are building is actually, I think about it as a hybrid. It's both
Reliant on LLMs and as I said, could not have existed prior to the advent of LLMs, but it is also half a unique proprietary architecture, a data architecture that I think allows us to do things that you just can't do with traditional LLMs alone. And it's a combination of those two things unlocks this magical ability to build a learning platform that's better than anything that's ever existed before.
And that really is what we're striving to do. We're striving to build a 10x better learning experience for whatever it is that you want to learn 10x better than anything you've seen before. So I've never been a startup CEO twice. I was a startup CEO once. You're now doing your second startup full time. And you and I have always talked about how we always imagined if we were to do it again,
which we are now, it would be so much easier the second time around. There are obviously so many things that happened with Anchor where we probably made mistakes we didn't need to. We wasted a lot of time, wasted a lot of money on something stupid. What are the shortcuts you have found in the day-to-day the second time around? Obviously, some of the things that we've done already with Oboe, like fundraising went way faster than I remember some of Anchor's first rounds.
I know it was easier for you to get a lot of the operational stuff set up where last time it's like navigating a maze. But what are the things in the day-to-day when you're with the team or building product that are just 10 times easier the second time around?
It is definitely easier the second time around. I'm pretty amazed by that every day because I think back on the early days of Anchor and how, for lack of a better word, I'm going to just pick the word stressful. Everything was stressful. And when you talk to first-time founders, when I talk to first-time founders, I advise or I invest and I
meet with them and I hear about how it's going and I just like, I can feel the stress. And that's not to say it's easy the second time around, but it's a lot easier because I think there is more perspective on what actually matters and is worth your time. I think there were a lot of things that you and I probably stressed out about the first time around with Anchor that
We learned later, it wasn't worth the energy of stressing about it or focusing on it because there were just more important things to do that were higher impact. Time is the most limited resource. And it is the thing, I think when you're a first time founder, at least this was the case with me. I'm curious if you felt the same way. I felt in the early days of Anchor, like it was our baby. We wanted to, obviously we wanted it to succeed. We were willing to do anything that it took. And as a result of that, I felt like I needed to be hands-on
in control of everything in the early days. Even if I wasn't controlling it, I needed to be involved in everything. It needs to be aware of everything. It took a while for you and I to feel comfortable giving up responsibility where there were parts of the business that you weren't aware of and that I wasn't aware of because we trusted each other and eventually delegating that to other people on the team. I mean, what a way to waste your time. Yeah, but doesn't that drive quality and like
perfection where it's needed. Obviously not everything requires perfection in the early stage, but there's benefit to the fact that you and I were very hands-on in the beginning of Anchor. I think the important distinction there is perfection where it's needed. There are many parts of running a business day to day that need to happen and they don't need to happen by the founder. And I actually think that it builds trust with the team and it builds a sense of more excitement if you could delegate
autonomy early on and allow people to have decision-making authority, or at least be involved in decisions in a way that was hard. I think it's hard for a first-time founder to do. This ties into a second thing, which is the second time you go through this, you also know what types of people you effectively work with.
right? Building a team is really hard. It's still really hard the second time around, but I now have a very great, reliable network that I could plug into. The people that I've hired are people that I've... The people that are on the team right now are both people that I've worked with before and that I love working with and that I trust already, and I have a way of working with them that's really effective. That's huge. I mean, you can... To my point about wanting to delegate responsibility early so that everybody could just focus on
things and move the ball faster, being able to do that with people that you've worked with before is key. And even if it's not people you've worked with, I think knowing the second time around what types of employees do and do not effectively thrive in startup environments, that part just gets easier. You have a better intuition for that the second time around. Yeah. What else? What else is easier? Iterating.
it, I think, becomes easier the second time around because you know how wrong. On the product, you mean? On everything, because you know how wrong your assumptions are going to be going into this. Like when you and I started Anchor, I remember in the early days, we were so sold on the vision that we were trying to build. And you need that. You need excitement about the long-term vision, right? 100%. Like you and I were very excited about that. But I think one of the issues is we were overly excited about the implementation.
that we had in mind. And when you're overly excited and enthusiastic about the implementation, what ends up happening inevitably, and I'm pretty sure any founder listening to this would agree with this, almost everything that you think going into building a business and a product will be wrong. Your assumptions are just going to be wrong. Your vision doesn't need to change. I hope that even if the product that I'm building right now evolves a million times, that long-term vision that I outlined at the top still stays the North Star. But the way to get there has to constantly be
iterated and refined and improved, and you need to put it in the hands of users so that you can learn and fail and learn and fail. And eventually you'll get to something successful. And I think first-time founders, they tend to be, to assume that they have an answer to the how I'm going to get there, not necessarily the what I want to achieve. You and I certainly did, but what ended up happening with Anchor was we had to do several major pivots to get to the product that we ended up building, none of which we could have done unless we had
These wake-up calls were like, oh, actually, these assumptions that we had in the early days about what people were willing to do and how good the quality of the content and how it was going to spread and where people wanted to listen and just what podcasting would turn into as a format. We were just wrong about so many of these different assumptions. So I think the second time going into this thinking, okay, I know I'm going to be wrong. I have...
What's that saying? Strong convictions, weekly health. Yeah, right. Yeah. That's how I feel about the way that I'm going to get there. It's like I'm trying. And I tell the team this too. Yeah, I was just going to say, is this something you talk about with the team? Like where you say, hey, we're going to spend however many months building this thing. But guess what? Like we might just throw it out when we're done. I say that all the time. Yeah. I think it's a critical thing for people to understand is that the work that you do is not necessarily the work that's going to end up being in the product, but it's necessary work, right? It's the steps that you need to get there. You know, it's like
I'm making up this analogy on the spot, but when you're cooking a dinner for your family,
they don't necessarily see that you're going to the grocery store to buy all the groceries, right? They just see the final output, but like you have to go to the grocery store. You have to, you have to shop the aisles. You have to walk down and realize what it is that you forgot to get before you actually make the meal. That's going to end up being delicious. Yeah. But you're going to use those ingredients regardless, you know, you're, you just talked to the while ago about building this new architecture. If your product implementation invalidates the need for that architecture, that's a lot of wasted food.
That's true. Yeah, I guess I'm actually kind of contradicting myself, right? Because I just said that we're investing heavily in building this foundational architecture. And I think that's part of the challenge of being a founder is you need to know where to draw that line. I have strong convictions weekly held on what this product will look and feel like when it's in the hands of users and whether it'll work. I have strong convictions more strongly held about what the architecture should be that powers the future of an educational platform. And that's where I think we're really investing our energy.
And then I have strong convictions, very enthusiastically held about what the future of education needs to look like in general, like philosophically. One thing I'm sort of feeling in the market is right now is we're moving away from a world of MVPs.
when you and I started Anchor, it was all about, there's this whole school of thought about around the lean startup and building the thin slice and the MVP and getting it out as quickly as possible, even if it's half broken. And I actually will say that that mentality, I think actually worked pretty well for us with Anchor. But I feel like the world seems to be moving away from that quite a bit. Maybe it's because AI has made it so easy to build products
There's just like a lot more crap out there. And now you're seeing things ship that are just like mind blowing and beautiful in the V1. How do you feel about this? And like, do you think that we are the viability of sort of MVPs, the viability of a minimum viable product is becoming less relevant? And how does it affect the work you and the team are doing on Oboe? To clarify, are you seeing the...
You think that from a consumer standpoint, there's maybe a higher bar that we need to reach, a higher expectation of quality? I think it's starting to happen. I think you're seeing more products being shipped that are really good right out of the gate.
And yeah, and I do think like it's going to, if it hasn't already, it will start to create more of an expectation with consumers, partially because, you know, if you want to stand out in an ocean of crap, like you got to make something pretty good. Yeah, I think I agree with that. Although I do wonder how much your perspective and my perspective is skewed by the fact that we're surrounded by people who are in tech, who are early adopters and who see things, they see a lot more in the early days from the average consumer perspective.
who is not an early adopter is used to seeing a final polished finished product anyway. It's almost like you're talking more about the initial traction phase of trying to go from zero to one and getting it, you know, find, finding your core audience and finding product market fit. Once the product has product market fit, I think, I don't know that I would say that the products today. How do you find it if nobody's going to give it a chance? Well,
Yeah. One of the things that we talk a lot about internally is we have a very ambitious vision long-term for the future of education and leveraging the same product to learn, you know, many, many things, any, any things getting from here to there is a very difficult process, right? You need to not only iterate, but like the long-term vision for this is really, you can come into this product and you can use absolutely, you can learn absolutely anything with it.
And I do not think, and maybe this is a contrarian approach. Like I don't know that a lot of companies take this approach when they build something like this. People tend to want to go big fast in terms of their offering. And I think that's probably inspired by products like ChatGPT, which is like the day that this thing shipped, it was able to do pretty much anything that you needed it to do. And it just increased in quality for different use cases.
And so there tends to be a tendency now, maybe this goes to your thing about building more polished products. There tends to be this tendency to want to deliver value to as many people as possible, as quickly as possible. And I don't know that that's actually the right approach. I don't know if that's going to be a sustainable thing in the industry.
I'm not referring to market size or TAM. I'm referring to like product quality, like something that feels great, is robust. It works. It's magical. Like it blows your mind. And again, like maybe it's because anyone can, like you said, build a GPT wrapper in under a day, especially when you have AI writing code for you. Yeah, I mean it less in terms of the TAM, more in just like the quality, you know? Look, I think in our case with TAM,
I think with a product like anchor, for instance, the user interface was the main thing that we were innovating on. You know, we were building in an industry, especially in the beginning, we were building in an industry that was very antiquated that had a lot of, uh, legacy wave ways of doing things. And we had this build the future core value, which was like, we don't care about how things were done in the past. We're just going to focus on building things the way that they should be built going forward in the way that podcasting should look like going forward. We were wrong about some of our assumptions as we talked about, but yeah,
That energy to innovate on the UX, I think, was critical. I think Oboe is very different. I think that for education, the issue has not been user experience. There are beautiful products that exist in education with gorgeous UIs and really fluid user experiences that are seamless and that are fun and gamified and approachable.
I don't think that's where the room for improvement comes in. I think when it comes to education, it's a fundamental underlying architecture and content issue. And so we're talking about quality. Actually, this is the thing that I do talk to the team a lot about is when we're building products, we need to build products that allow us internally to have what I call an oh wow moment where you're using this product and you're like, oh wow, this thing does something that I've never seen it do. That's kind of what I'm talking about.
You kind of need that now, right? You need that to stand out. And I think the distinction between us and a lot of the products that are out there is that we're working in an industry where I believe the innovation is not going to come from having a really polished UI or UX. The innovation is going to be because you are able to learn with this product more effectively, which is an underlying content and architecture issue. It's not a UX issue, right? It's a technical innovation. It's a technical innovation and...
um yeah it's a technical content innovation i'll call it and i think that the innovation on that front is the thing that's going to have people suddenly have light bulbs go off where they say wow i am able to do something with oboe that i can't do with any other product it's not to say we don't need a beautiful product and we don't need to look really polished and we are hiring a product designer right now so shout out that if you are a product designer who's inspired by this mission please reach out to us but i i think we are going to be capable of building that
product that has that oh wow moment that really blows people away by innovating fundamentally on like the architecture of how educational products are built. Yeah, makes sense. You mentioned Anchor and how in the early days we were trying to innovate on the user experience.
I actually coincidentally saw a tweet a little while ago that made me think about this in this moment. A tweet from Nikita. He was referring, he was replying to somebody who talked about how Naval had, you know, over the past, whatever, six months, launched AirChat, which was similar to the early version of Anchor, iterated on it, used it daily, you know, lots of daily activity. And then after all that, shut it down. And Nikita's response, which I thought was interesting, was,
quote, in a way it was a success. It was the very best version of open network audio chat to date and basically invalidated the whole space as viable. Meaning like it proved that this can't work. Social audio, as I take it. Have you reflected much on Anchor in the years since we've left Spotify, especially since we sort of pivoted away from the early versions of Anchor, which were very similar to AirChat? Do you agree with this? Like,
Can social audio work? Can sort of a non-podcast version of people talking and listening, can that work at scale? I think the biggest flood
expectation of the future that you and I had in the early days was that audio would be its own standalone thing that would stand differentiated from the rest of content on the internet. And that clearly has proven to be not true because you and I are recording a podcast right now. We're still calling it a podcast, but it's a video. Audio and video have merged in a way that you and I did not expect to happen. And the reason that we thought that it would not happen was, I think, we thought it wouldn't happen because
Our assumption was always that there were hours during the day when you could listen to audio that you wouldn't want to listen to, or you wouldn't want to consume video, right? It's a very different passive listening experience than sitting down and watching something actively. And we assumed that that meant that the content had to be different. There would be a bucket of content called passive audio content, and there would be a bucket of content that was lean in video engaging content. And those two buckets of content would be different. And what happened was something that you and I did not expect to happen, which is
they actually ended up being the same bucket. You just use it in different ways. People who want to consume this through video are going to be able to consume it through video. And every single person who wants to consume it through passive listening experiences as audio only does not need to go and find another version of this podcast. They just listen to the same content, just audio only. And it's obvious in retrospect, but you and I, I can't remember a single time we ever talked about the fact that that was...
a viable future is that actually video is a really unique format because video has the exact audio component that you want in a podcast plus this added optional visual layer. So to go back to your question, I think
Social audio, I actually do still believe in social audio, but I think the assumption, I do, but I think that the assumption that social audio is an audio only experience is the flawed assumption. Magic wand, back in time, able to build an anchor and we still wanted to build the very first version of anchor that was social. And then maybe there are other reasons why we wouldn't have wanted to do that. But if we knew that we wanted to do that and I could go back in time and give younger you and me a single piece of advice, it would be
put video onto the platform, stop treating it as an audio only platform, because the thing that'll allow this to really take off is giving people the ability to listen to audio if they want to, and the ability to consume it as audio and video if they want to. - Yeah, but it sounds like what you're saying is you actually have to match a format that already exists, whether it's like video calling or asynchronous video chat, or like aren't now, we're now just kind of like talking about Snapchat, right?
I guess I don't really understand what that would be if you just layer video on top of like asynchronous audio posts or synchronous audio posts right now, we're just streaming. Like now we're just on Twitch. Right. Okay. So I'm,
I have not thought of this before. Yeah, no, me neither. I mean, this is a really interesting question. Just to point out to the audience, Nir and I talk every day. We never talk about Anchor. We never talk about the early days of Anchor. So this is like, this is totally fresh for all of us. So let's, all right, let's frame the conversation. This is fascinating. Let's frame the conversation here. In the early days of Anchor, you and I believed that there would be a
an explosion in the demand of audio, audio consumption. And we believe that because of the fact that suddenly- Which happened, which did happen. We were right about that.
We believed that it would happen because suddenly accessibility to audio skyrocketed. The year that we launched Anchor was the year that the Amazon Echo came out. And it may have been the year that the AirPods came out. I don't remember. But connected cars started getting built where cars were connected to the internet. So there were all of these reasons to think that demand would skyrocket for audio. And our core assumption was that
We could build, we could piggyback off of that growth in demand by being the platform that made it easier than anywhere else to actually record content. And then we made a bet and this bet ended up being wrong. I think for the reasons that Nikita would probably agree with. Our bet was that yes, demand would grow and yes, there needed to be a growth in supply by making a platform that made it really easy to record this stuff and distribute this stuff.
But we assumed that the format of podcasting was broken and needed to be reinvented, right? So the first product that we built, the first version of Anchor, was basically... People called it like audio Twitter or audio Instagram. It was threaded conversations, short form audio. We called them waves. They were... How long were they? Two minutes max and one minute per podcast, right? Two minutes max, yeah. So...
You would record a wave. I would record a reply. Somebody else would record a reply to me. Person D could come in and listen to the entire conversation in order and hear us having an asynchronous conversation. I think there were a lot of awesome things about that. These conversations were super easy to record. We were right about that. I actually think in a lot of cases, they were compelling. We could have done a lot more to make them more compelling. The biggest challenge that we had was a distribution challenge. The issue that we had was that people had to come to Anchor to consume this
content. We did years of iterating on that flawed assumption only to realize that the only way to really make this work was to distribute through existing distribution channels. And that's when we lead into podcasting exactly. And in order to do that, you can record two minute waves. You have to record an actual real podcast and Anchor's growth skyrocketed the moment that we decided to invest in existing distribution channels.
Again, this is one of those things that in retrospect, it's like, oh, that's so obvious. It wasn't very obvious at the time. But doesn't this just doesn't this disprove your point, though, that social audio can work like the whole anchor journey to me?
is sort of proof that it couldn't. And podcasting was actually the format that was going to have staying power. And clearly it still does. I mean, look at how much Spotify is still investing in podcasts and video podcasts. YouTube's going all in on podcasts. I agree with Nikita, I guess, is the point. Okay. Okay. But hold on. So I think there was a fork in the road and we chose to go in one direction. And I'm just talking about a hypothetical where we could have gone in the other direction. The direction we chose to go in was to say, we were right about how to make it really easy to do this
And we were right about the fact that demand would grow. And the thing we were wrong about was distribution and therefore less leverage the existing distribution channel that existed, which was podcasting. Okay. We could have actually done a different pivot, which is we could have said, actually, distribution is not the issue. The format is the issue.
And we didn't innovate on the format the right way. Now, if you're a person who believes, hold on, you have to piggyback off distribution to have growth of anything. I don't know if that's true. Like look at TikTok. TikTok invented a completely new format. Snapchat invented a completely new format when they came out. And they, unless I'm, I mean, you know more about this stuff than I do, but like- TikTok, not a super fair comparison. They invested like billions of dollars in marketing.
Sure. But even then, like the product has to be good and compelling and have network effects for it to actually work. But let's take Snapchat as an example. Snapchat's a great example. Yeah. Because it was a completely net new format with the disappearing photo. Yeah. So clearly there is the ability. Twitter is another example when Twitter first came out, right? Clearly there is the ability. Instagram. Instagram too. To create a format that works.
is net new that doesn't piggyback off distribution and that does actually get adoption to a point where there's critical mass that you have network effects. So in this hypothetical universe that I'm talking about, rather than saying you and I should lean into podcasting, the alternative approach would have been
Actually, there are signals that show that video and audio are going to end up converging. And so our bet on an audio only social experience, asynchronous social experience was wrong. Let's layer video on top of it. What does that actually look like? It looks like asynchronous video messages back and forth, just like early anchor, right?
Waves public you can listen to them. You could watch the entire conversation. You could watch their replies You could see the whole thing you can listen to it passively if you wanted to with your headphones or you're in your car or you could be in front of your computer watching the entire conversation and we would have basically built the exact version of anchor that we had except it would have been Video optional video that's that's what you know, what's really interesting about this and now I'm maybe agreeing with you what I think of when I think of the format you just described is
Talking video clips on TikTok, on X, on Instagram. It's actually the format that podcasts are slowly becoming. And so, yeah, maybe it would have worked, actually. We'll never know. Well, maybe somebody out there listening to this will decide to build this. Yeah, if someone else is building this, let me know. Maybe we should talk about an investment. I still think audio is a really, really interesting thing.
format. I think there's a lot of opportunity in audio. I, you know, audio books being another really great example of this, that's like an industry that's just primed for innovation and ready for massive disruption and start said that starting to happen with Spotify's entry into the industry and things like that. There's a lot of room for growth in audio, but video is a key component of audio. And, uh, 10 years ago, we didn't know that. I just think, um,
If anything requires audio, it's going to always be really tough to compete with pure video or images or text because there are so many moments in your day it just cannot fit. Because again, you have to listen to it and you can't always listen to stuff. I also think video and anything visual is just going to always be more compelling to your brain. Like it captures more of your senses. And so...
I actually think it needs video. I think the format needs that you're talking about. Video can't be optional. I think it needs video. And I think it needs to have the option to consume without audio at all, which is why I think these talking head videos work because they all have captions on them. Right. Maybe that's what this ends up looking like on the video optional thing. Just to clarify, I meant video optional to consume, not video optional to create. I think everything you make on this platform has to be on this hype. But I think audio has to be optional, too.
Audio optional as well. Yeah. I mean, why limit yourself? Maybe this is the big takeaway is like, if to, you know, the thing I said earlier around having too strong, your convictions be too strong on the, how you get there. If you're making a format that you have to be really, really bold and really, really right to win on a format bed, um, based on core assumptions that could be flawed. And I think you're pointing out a key thing, which is we were wrong about the fact that audio only was a good experience.
Or sorry, it was a good experience. We were wrong about the fact that that was the key to success. But I think your other point is you'd also be wrong about assuming that like both of these things together would be the key to success. And you actually have to build a platform that allows you to be, have either one be optional whenever it is that you want to switch modes, right? Maybe flexibility from a consumer standpoint is the thing that really matters. And you just want to offer people as much optionality for how to consume content as possible. Yeah.
I mean again, it does feel like this that's where the podcast medium is organically going right? I mean even just look at Spotify Video is completely optional. You can watch it or you could put the phone back in your pocket It doesn't stream the video so you save the bandwidth they have captions that are auto-generated for every podcast now So even if it's not baked into the video, it just does it automatically I just think like this is
Maybe less intentionally. This is where, this is where like the culture and the, and the medium's going because, because of these exact demands from users. I want to, I want to switch things up a little bit. So before the podcast,
I posted on X, you know, letting everyone know that you and I were going to be talking and asking whether or not anyone had had questions. And so we'll just take through some of the questions now. I will say this first one from from Ann Burdetsky. She asks some things you've sort of already answered. She asked, what are you building? You talked about it. She also says, what non-obvious lessons from your first company are you taking into this one? I think you answered some like
Obvious ones, no offense. What is something really not obvious that is surprising you about how it's different this time around? I think there's a shift now post-pandemic of people saying in-person teams together 100% of the time is the way to go. That's the future. We're going to bounce back to that future. And in the early days of Anchor, you and I were both very, very gung-ho about having the team in person together every single day. There are huge benefits to that.
And there are huge disadvantages to being distributed. And when I say distributed, I mean not physically located in the same city so that you can't commute into the same office. Not co-located. Not co-located. What we have been doing at Oboe, and it has been awesome, is everybody that we hire is in the New York area. We have an office in New York. We go in two to three days a week. We have the emperors and daves.
What I'm finding is that the non-in-person days are incredibly productive because of the fact that we have the in-person days where we're able to spend time together and divvy up our week so that there are things that you're just more productive doing in person. And there are things that you're more productive doing when you're not distracted by being in person. And being able to approach every single day saying like, this is the day where I do category A and this is the day where I do category B has been really, really helpful because
I can think of many cases where in the early days of Anchor, we got together in the office five days a week, and it was really hard for me to do this stuff that today I would just allocate to my days working at home because I'm getting pulled into stuff. You and I are having conversations. There are team members all around. I'm surrounded by people. I'm surrounded by noise. I'm surrounded by distractions. That's not what building a company is like, right? Building a company uses different parts of your brain. And I think one of the hybrid advantages is that you're allowed to structure things
your days and you're allowed to structure how the team interacts with each other around how to utilize those different parts of your brain. I have days where I go into the office and I don't write a line of code, but those days are incredibly productive. And then I have days where I sit at home writing code exclusively, working on the product, working on designs, things like that. And those days are incredibly productive. And there are a million other things that I haven't done that I know I'm going to do tomorrow when I go into the office. So I actually think it's
you know, who knows how long it scales for and whether the dynamics change when the team is 10 people, 20 people. Right now in these very early days, I actually find this to be the most effective mode of working. Is the structure an individual thing or is, does the team, does the team, is the team sort of operating in the same wavelength in terms of the structure based on the days you're in the office and out of the office? Like Mondays are sort of heads down coding days, whereas Tuesdays are we cram all our meetings in, you know, like, is it that sort of thing?
Yeah, I think that sort of happened organically because there are conversations that we know we need to have at the start of every week. We say, you know, what are the conversations we know we're going to need to have this week?
oh, these are the types of things that are going to work when we're in office. Let's focus on putting those on the in-office days. And on the non-in-office days, let's have as few distractions as possible. And it really is a win-win because like I said, use different parts of your brain to do different things. And if you can allocate long stretches of time to really focus on those things and put yourself in the environment that benefits you for accomplishing those things, I think it's great. We're consistent. We know every single week, these are the days we're going into the office.
everybody can plan their week around that. Everybody can plan their work around that. And I don't see a lot of companies doing this, but I think it's worked well for us so far. I am skeptical just to be the contrarian here. Well, this is probably more in line. What you're saying is probably more contrarian than what I'm about to say. It's like, I don't think this can scale. I think probably the reason it's working right now is the team we have now, which is amazing. Like
You know them all. You work very well together. There's a lot of trust built in there. When we're at 50 people, 100 people, I don't know. I feel like that's when communication breaks down. You're right. And remote work is hard. I've seen distributed teams work
very effectively, but I think where it really takes a toll on distributed teams and a hit to productivity, it happens when you are unable to get together in person for long periods of time. I think that's necessary for a reset and for resetting the enthusiasm and realigning people. Here's a contrarian point of view to your contrarian point of view about my contrarian point of view. If I were to say to you in the early days of Anchor, when you and I were heads down building product, and I said to you, Mike, from
you know, 12 to 4 PM. I want focus time where I'm able to sit and focus. And I think you did say that. And I just constantly interrupted you. Let's pretend like you weren't interrupting me constantly. You would think that that's fine, right? We use the mornings to, I think people do this all the time, especially people who need to like get in the zone programmers and things like that. Um,
All I'm suggesting is a work environment where you extend that focus period of time that people constantly are trying to carve out for their days, extend it to the end and the beginning of the day. And the benefit that you get out of doing that, instead of having four hours of focus every day, is you have eight hours or nine hours of focus on a particular given day of the week. The huge benefit that you get out of doing that is that you don't need to commute. This is like forced no meeting days, basically. Yeah.
Yeah. Or fewer meetings. Yeah. I think it's, it's forced. It's forced focus time. Forced focus time to, and prioritize into this time, the things that benefit from that and deprioritize the things that will benefit from being in person tomorrow when we're able to actually talk about things in person. Going to debunked early anchor user. First question, he says, how's the baby? I'm assuming, you know, cause he was an early anchor user. He's probably referring to the fact that you and I both had kids and
They're not babies anymore. Not babies anymore, all grown up. And then his second question is, aside from the money, how did you guys know it was the right time to be acquired? And were there other suitors besides Spotify at the time? I've answered this question publicly a bunch, but I don't know if you have. And so I'd love to just sit quiet on this one and hear how you respond to it. How did we know it was the right time to sell? Yeah.
I think probably the biggest piece of it is that the vision that Spotify sold us on was exactly the vision that you and I wanted to set out to build when we first started Anchor. It was innovation on the format of podcasting, the ability to build at scale with existing distribution through Spotify, all of the things that you and I had failed to build because back to our conversation earlier, the number one thing that we realized we were missing is distribution.
And Spotify, more than any other platform, can't think of any other company in the world that could have been a better partner for us, allowed us to do that with existing distribution and with a team that was super aligned with the vision that you and I had. It was crazy. I remember you and I walked out of the first conversation that we had about the acquisition with Daniel. I remember we walked out of it and we said...
Wow. So much of what he just said was stuff that you and I had started talking to each other about five years earlier when we started talking about Anchor. And he just said it in a different way, coming at it from a different perspective. He was coming at it from the perspective of a person who had built a massive distribution platform and had all the demand, but they had not been innovating on the format. And you and I were originally purely innovating on the format and we had no distribution. And so we were just really like two sides of
The same strategy coming at it from two different sides that fit together perfectly. And I think once we realized that, for me, that was the moment where we were like, yes, this makes perfect sense. Like, this is exactly what you want an acquisition to look like. Yeah. How aligned is that with how you talk about it? Yeah, it's very similar. The other thing he asked was, were there other suitors besides Spotify at the time?
I don't know if we can totally answer that, but maybe one thing I'll say, which I don't think I've ever actually said publicly, is that another company who many thought were a suitor, Apple, was actually trying to kill us at the time. I don't think I've ever actually said that, but it was a long time ago, so whatever. Apple was trying to kill Anchor, was trying to get Anchor shut down. Not everyone at Apple. In fact, a lot of people at Apple were really supportive, but there was a
small, vengeful team that thought that Anchor was a detriment to Apple Podcasts. Look, I think we had people that were very aligned with our vision. That's true. At many companies, including Apple, I think that there were people who were not aligned with our vision at many companies, including Apple. That's true. Probably a bit of an exaggeration the way you said it, but
That story, the full story will probably never be told unless somebody maybe gets me really drunk one day and sticks a camera in front of my face on the spot. Or you can write a tell-all about our... Yeah, we'll write a tell-all one day. Okay, Basart asks, how does growth marketing look different today from the Anchor days? Anchor was probably already at the tail end of this period of time where you could
piggyback for free off of distribution on other platforms. Tell me if you agree with that. But when we launched Anchor and for the first few years of Anchor, Twitter had programmatic tweetability built into it. We did early Facebook integrations and Twitter integrations and other types of integration, medium integrations and things like that. So many different programmatic integrations that allowed us to
leverage our growing user base to amplify the content that was being created to then attract more users. And we got a flywheel spinning off of that. I don't know that anybody can do that anymore. It's so hard now to piggyback off other distribution. And I think that that makes running a startup harder. But I actually also think just a
point out a silver lining with this. I think the consequence of that is that more people now have to focus on building products and content that are organically discussed. And that's huge because that really allows the cream of the crop to, you know, like the best. This is my point from earlier, by the way.
You can't just like hack your way to product market fit anymore with some crappy MVP because distribution can hack your way to distribution is impossible. Correct. Yeah. Yeah. Then the only real distribution and yes, you know what, instead of go back to your point about higher quality, maybe the reason why there's more of an expectation of higher quality and why you can't really build MVPs anymore that are not high quality is
is because of the fact that the only real way to grow is to showcase user value. And that used to not be the case. You could basically hack your way to success, or at least to a critical mass of users, without having product market fit. Anchor being a great example of this. The Anchor core product for the first few versions of Anchor did not have product market fit. And despite that, we were able to grow very successfully because of our ability to leverage other distribution channels and to promote
the content and get an audience that way and grow our top of funnel. Today, the products that people talk about organically are the best products. Now, the downside to that is there are probably many amazing products that are created that nobody sees because they can't get that initial traction and they can't get that initial set of eyeballs to look at them or they're reaching the wrong audience. And that's a problem that I really don't know how you solve. If you have no distribution at all, if you have no audience at all, you're building an amazing product, but you don't have somebody to help amplify it, then you're
I don't know. That's a hard position to be in.
Obviously not the case anymore. Elon has like shut down the ability for tweets with links to gain traction. You know, now it feels like the thing that people have been taking advantage of for the past, I don't know, two years is TikTok algorithm. If you crack it, you can get crazy distribution. I'm sure that's not gonna last forever. Something about that will change, you know, either intentionally or not. So I think there's like these moments in time where these windows of opportunity open
You have to find out what they are and you have to exploit that. I think you have to exploit the hell out of them and you need to be really, really aggressive with them. I strongly believe that. And sometimes there's, there's pushback, right? And sometimes there's blowback. I remember in the earliest days of anchor, we did something that a lot of companies were doing. I,
Maybe in hindsight, it can be considered like a dark pattern or whatever, but we were trying to get you to automatically share to Twitter. There was like a checkbox, and if you put it on once, it was always on, and every time you posted audio to Anchor, it would tweet for you. And most people didn't care, but some people really cared.
And, you know, we got a lot of angry tweets about that and that and that opportunity was gone. Right. Like it was like, OK, this is no longer acceptable. We're turning it off. We definitely upset some people with that. Yeah. And so I think I think you have to find the arbitrage when it exists.
Because it goes away pretty quick. And it's so rare to be able to find one of these things. This is actually like the main reason or one of the main reasons I'm so excited to have Nikita as a partner at Lightspeed because he's like the master of figuring this stuff out. And it's been big help to our companies. Okay, last question from the tweets comes from
Maggie Mindy, very interested in your thoughts on memory formation and digital learning. Given studies showing lower retention with digital versus handwritten notes, I'm curious how Oboe approaches this challenge. Can AI tools effectively complement our natural memory processes? Or should we be thinking about learning differently in an AI augmented world? I definitely think we should be thinking about learning differently.
But I think the data that has shown how ineffective online learning platforms are relative to in-person learning, to me, a lot of that stems from what I talked about earlier, which is that there are just foundational decisions around how educational content should exist on the internet that I just don't agree with. And I think there's an opportunity now with AI to reinvent that. I realize it's a little vague, but it touches on this
you know, unique architecture that we're building, this unique foundation that we're building. That being said, I think if you have a unique foundation that allows you to generate extremely personalized content for the user and get better, the more the user uses it. I don't see why, maybe this takes five years or 10 years or whatever else, but I don't see why you can't take that technology and apply it to real in-person learning as well, right? Perhaps the future of
that is the real unlock for humanity, is leveraging AI and leveraging these innovations and how the foundation of educational platforms works, but plugging it into real life learning environments or real life studying environments, whether that's putting pen to paper or sitting in a classroom or allowing educators to use these platforms to actually incorporate them into their syllabus, into their curriculum.
I don't see these things as mutually exclusive. I think we could take the innovations that have happened in AI, we could combine them with the many, many centuries of learnings that we've had about how people learn effectively. We could combine those into this grand vision of what learning should look like in the future. I don't think there will be in the future such a thing as purely digital online learning. Everything is going to get more and more integrated into our actual physical lives. And maybe that's a good thing.
Last questions for me. And then we'll wrap after this. Um, Oboe's mission as we have defined it is to make humanity smarter right now. Uh, we are building, um, a new, as you mentioned, a new tech technical approach to both tutoring and learning through AI through, through a hybrid model of AI that, that couldn't exist before. But as you said, somewhere along in our, in our podcast, um,
you know, the vision stays the same, but the implementation doesn't. You know, so if the mission is to make humanity smarter, if you were just to sort of fast forward 10 years, 20 years of this company, in what like very innovative ways might we possibly be able to take this? And, you know, I'm curious to, you and I talked a little bit about this a long time ago, but I'm curious to know how your thinking has evolved. Like,
Is this the sort of thing where if our mission is to make humanity smarter, that we're eventually going to be sort of taking advantage of, you know, brain implants and, you know, things that go well beyond a consumer product that helps teach people things. So I guess your question is like, what's the sci-fi, you know, 20 years from now? How far can we take this? How far can we take this? I used to talk about Oboe. Used to meaning like two months ago. I used to talk about Oboe as an education tool.
platform. I don't do that anymore. I actually try not to use the word education at all. And instead, I say the word learning. And I think it's because the word learning is so much more ambitious. It's so much bigger. It represents so much beyond what people typically associate with education. And one example, I'll give you credit for this because you're the one who originally talked about this as like, maybe this could happen in the future, is the
the number of things that we interact with in the physical world on a day-to-day basis that we don't fully understand. And one of my dreams is like near term, anything you come across, you should be able to learn about in the digital realm. Anything that you don't understand, anything you need context about, you should be able to add this to your curriculum and fully understand it through Oboe's teaching tools.
But there's no reason to think that that should be restricted purely to the digital world. And you're the one who originally pointed that out. It's like, there's going to be more and more touch points between the physical world and the digital world. There's no reason to think why 20 years from now, I shouldn't be able to learn as much about
you know, this couch behind me or that guitar or anything in the physical world that I interact with just as much as I can through the digital world. It's all about entry points. It's like, how is it that I come into contact with the ability for Oboe to teach me about something? And what is it that Oboe can teach me about? And the real ambitious thing is like, it doesn't need to be everything online. It could be everything, period, right? And that's how you really make humanity smarter. That's how you really
level up what we're able to do. It's like anytime a person wants to understand anything better, regardless of where it is, regardless of how they interact with it, they should be able to come to Oboe to do it 20 years from now. Nir, always a pleasure. Thanks for doing this. Even I learned things about our company that I didn't know. So I'm sure the audience learned a bunch as well. I appreciate. Thank you. And thanks everybody for listening.
Thank you so much for listening to Generative Now. If you liked what you heard, please rate and review the podcast. That really does help. And of course, subscribe to the podcast so you get notified every time we publish a new episode. If you want to learn more, follow Lightspeed at LightspeedVP on YouTube, X, or LinkedIn. You can follow me at Mignano, M-I-G-N-A-N-O on all the same places. And if you want to learn more,
And Generative Now is produced by Lightspeed in partnership with Pod People. I am Michael McNano, and we will be back next week. See you then.