An inside look at how Miro builds product: Lessons on outmaneuvering competitors, team structure, product quality, and moving fast | Varun Parmar (CPO of Miro)

Every single day, every single time somebody is pushing your code to production and you're releasing a feature or an enhancement, you are making the product better or you're making the product worse, but the products never remain same. And so with every release that your competitor is making and every release that you're making, you're either making chess points moves against them, positive points, or you're going negative. And I think that framework, it actually drives an insane amount of clarity in terms of what you're doing and what the impact is going to be. Welcome to Lenny's podcast, where I interview.

World-Class product leaders and growth experts to learn from their hard-won experiences building and growing today's most successful products. Today, my guest is Varun Parmar. Varun is Chief Product Officer at Miro, and prior to Miro, he was Senior Vice President and Chief Product Officer at Box. As I share with Varun at the start of our chat, I've always been really curious about the product culture at Miro, partly because everyone I've ever met from Miro has been super interesting and super smart, and partly because they've been able to grow as a business and a product in an incredibly competitive market. In our conversation, we get really deep into the product values and principles at Miro, their product development process, how Varun approaches competitive threats, how a bi-monthly company-wide product demo ritual led to saving months of engineering work on a feature, plus insights into how Miro got started, how they grow today, and what their product team has learned about working with a large sales org. Varun is amazing. I learned a lot, and I hope you find it as interesting as I did. With that, I bring you Varun Parmar, after a short word from our sponsors. Today's episode is brought to you by Miro, an online collaborative whiteboard that's designed specifically for teams like yours. I have a quick request. Head on over to my Miro board at miro.com/lenny and let me know which guests you'd want me to have on this year. I've already gotten a bunch of great suggestions which you'll see when you go there, so just keep it coming. And while you're on the Miro board, I encourage you to play around with the tool. It's a great shared space to capture ideas, get feedback, and collaborate with your colleagues on anything that you're working on. For example, with Miro, you can plan out Next Quarter's entire product strategy. You can start by brainstorming using sticky notes, live reactions, a voting tool, even an estimation app to scope out your team's sprints. Then, your whole distributed team can come together around wireframes, draw ideas with the pen tool, and then put full Miro boards right into the Miro board. And with one of Miro's ready-made templates, you can go from discovery and research to product roadmaps to customer journey flows to final mocks, all in Miro. Head on over to miro.com/leni to leave your suggestions. That's M-I-R-O.com/leni. this episode is brought to you by Braintrust, where the world's most innovative companies go to find talent fast so that they can innovate faster. Let's be honest, it's a lot of work to build a company, and if you want to stay ahead of the game, you need to be able to hire the right talent quickly and confidently. Braintrust is the first decentralized talent network where you can find, hire, and manage high quality contractors in engineering, design, and product for a fraction of the cost of agencies. Braintrust charges a flat rate of only 10%, unlike agency fees of up to 70%, so you can make your budget go four times further. Plus, they're the only network that takes 0% of what the talent makes, so they're able to attract and retain the world's best tech talent. Take it from DoorDash, Airbnb, Plaid, and hundreds of other high-growth startups that have shaved their hiring process from months to weeks at less than a quarter of the cost by hiring through Braingate's network of 20,000 high-quality, vetted candidates ready to work. Whether you're looking to fill in gaps, upskill your staff, or build a team for that dream project that finally got funded, contact Braintrust and you'll get matched with three candidates in just 48 hours. Visit usebraintrust.com/lenny or find them in my show notes for today's episode. That's usebraintrust.com/lenny for when you need talent yesterday. Varun, welcome to the podcast.

Thank you, Lenny. So excited to be here. Thanks for having me.

I'm really excited to have you here. I've been looking forward to having a chance to dig into Miro's product culture and the way Miro works for a while. We've actually had a few guests, ex Miro Mironers, is that what you call yourselves?

Yes, Mironers.

Okay, Mironers. So we had Elena Verna on the podcast, who's amazing, and Barbara, who I think worked in marketing. And everyone I've always met from Miro has been just like really smart and really interesting. And it just feels like you guys have a really interesting product culture that I haven't felt like has been shared a lot. And so I have a bunch of stuff I want to dig into there. And one question I have at the bat, you guys have a really interesting history and specifically the way your company is structured, which is that you're co-located in Amsterdam and San Francisco. So first of all, is that correct?

The company is a global company. So we've got 12 different hubs. So we have multiple offices in US, you know, four different offices, and then multiple hubs in Europe as well and presence in Asia Pac as well. So I think by now we have a global footprint.

Got it. A question I wanted to ask off the bat is just how has that cross-cultural approach to product teams impacted the way that you guys built product and the way the company operates?

The one thing that's really interesting, Lenny, around the way Miro is set up is that you know, our product organization is actually based in Europe and our go-to-market organization is worldwide. And, you know, so our product management team, our designers, our engineers are located across three different hubs in Europe. And what that sort of leads to is, you know, a couple of like practices that we have as part of our culture. So the first one is practicing empathy to gain insights. And it's not just practicing empathy in terms of customers and figuring out what customer pain points and problems we can solve. But given our distributed nature in terms of having a global footprint and a lot of our go-to-market teams, folks in sales and marketing and customer success are in different continents or geographies, we have to make sure that we actually practice that internally. So when we are interacting with folks, let's say in San Francisco, and those folks are out there meeting some of our large customers and stuff, how do we in the product organization understand their perspective? and bring that perspective into how we design, prioritize and build products. So I think that's one thing that's unique. I would say the other thing that's less to do with the location, but I think is the core cultural value or philosophy that Andre, who's the founder and CEO, has instilled in all of us, is practicing teamwork. How do we actually come together as a team and bring down the silos that might exist across functions. And I'll talk a little bit around how we are structured in the product organization so that it's a cross-functional perspective that we bring to everything that we're doing because we believe the best work happens when we bring different diverse perspectives to the problem and then co-create the outcome that the customer is looking for.

I want to pull on these threads actually real quick. So you talked about this value of empathy and the importance of having empathy across because you guys are locating different locations and have different cultures and also this idea of teamwork. What's something that you've done that helps you do that? Either build empathy and maintain empathy across teams or make sure that people work in teams and not like, Hey, there's this other team over there doing something else.

One of the most powerful sort of things that I've seen work is the questions that you ask. The questions that you ask when you're going through product review or you're trying to sit down and talk to someone and trying to understand why did they prioritize something over the other? And was it something that was done through interactions they've had with folks internally or externally? So I think it's the set of questions to ask in terms of how did they get to where they are today? And was it informed by understanding of the insights that collectively the organization has? Was it informed by their understanding of where the market is evolving, where the competition is going? was it informed through the series of insights they have either through inbound feedback that's coming through our different channels where customers are giving feedback or some outbound interactions that they've had. So I think sort of just like trying to double click and getting to the details in terms of what insight led them to recommend certain things or make a left turn or a right turn is where I think is the most powerful way to make sure that those things are informed through practicing empathy internally and externally.

Got it. So there's this kind of cultural value of just assuming good intention and asking questions to understand where someone came from. I don't know if you'll have something off the top of your head, but is there a story or an example of that comes to mind where that was done well or not done well? I don't know, and something you recently were building.

Maybe there are certain things, like for example, anytime we're trying to build a new experience, one of the approach we want to take is very quickly validate that our original hypothesis, is that sound or not? And we are big fans of the Design Sprint framework. And also what Jake Knapp has done, I think is really amazing. In a short five-day window, you can get a small set of people to quickly mock up a concept, convert it into some sort of a prototype, and then go out there and get some sort of a validation. So oftentimes when we are working on some of these new things, We have our product teams that are focused on zero to one initiatives, run this five-day initiative, and at the end of it, we say, oh, this is great. Who did you get insight from? So there's a capability that we recently released. It's called Miro TalkTrack, which essentially allows you to asynchronously do a synchronous collaboration by recording audio video on top of a Miro board. And we had sort of two fundamental choices we could make. One, we could go down the path of what everyone's doing, where you could do like a screen recording and then, you know, spit out a series of videos like pixels being captured. Or what we did was we actually went down a different path. And the path that we went down was we basically synchronized the movement of a board. So let's say, you know, Lenny's presenting a board, you know, some template he's created in terms of best practices for PMs, but he wants to have, some sort of a talk track on top of it, an audio video feed. And what we are doing is we're actually capturing the movement of the board that Lenny is going through along with the video talk track that's on top. And the reason why we did that was because we had an insight that came through some of our interviews. What our users want to do is they want to use Miro for collaboration. While communication is an important aspect of how teams come together where we believe our sweet spot is that we want people to use Miro for collaboration. And by making sure that they could actually use a video recording and while the video recording is playing, they could add in a sticky note, they could add in a comment, they could actually give a reaction. We were able to develop this insight by practicing empathy as part of the design sprint framework when we went and started to show our original concept and we evolved and built on top of that.

That is a really cool story. And that came out of the sprint framework. these five days sprint approach. That's right. That is cool. I gotta have that guy on this podcast.

Jake Knapp, you said, right? Yes, yes, yes. I can text him right now and.

I can make the introduction. So let's pull him right into this podcast live. Tell us how the sprint process works. That is awesome. This connects a little bit to another question I wanted to ask around the top is you guys are in a really competitive space and it feels like Miro was very early in online collaborative whiteboarding. space. And then I think during COVID it just became a huge, you know, with the remote work exploding, it's like, holy shit, everyone needs this immediately. And over the years, many companies have come into the space that you are all in. And it feels like Miro continues to do extremely well. Like, I remember when Figma launched FigJam, there was a lot of just like, Miro's dead. Figma is getting into the space, they're a juggernaut, game over. Clearly, that's not been the case, and it just feels like I don't know what it is internally that you all do that continues to allow you to compete and continue to innovate in the space. And I'm curious, just like, is there something to how Miro approaches competition and also just, I don't know, the way they approach these sorts of challenges that is unique or interesting that you can share?

If you look at the mission for Miro, we empower teams to create the next big thing. and our focus is to enable teams that are innovating. And generally, innovation happens at the intersection of a bunch of cross-functional folks coming together, like we discussed, folks in product management or design or engineering or analytics or product marketing or research. And what we find, Lenny, is that there are a lot of tools out there. And those tools are generally sort of focused on a particular persona and, you know, maybe they're trying to solve the needs of a designer and a designer has a workflow that they're trying to do and they're using a specific tool and they sit at the adjacency of extending that core use case. The fundamental value that Miro provides is that we enable teams. And I think like what's unique about our product and we can talk about the capabilities and roadmaps and use cases that we are, investing in, and we already have as part of the product, is that we take a team-centric lens. So we're not saying, hey, we're building a tool that just works for designers, or hey, we're building a tool that just works for engineers, because we fundamentally believe that innovation happens when cross-functional teams come together. And when you look at the problem through that lens, you realize that you have to actually architect your solution. You have to think about the use cases and you have to go and prioritize certain experiences. that are different and our customers see value in that. And I think that's probably one sort of big macro aspect of how we think about our capabilities and products and why our customers think of us differently. So let's say that's one point. I think the second thing is Miro is actually used, obviously by teams that are creating these innovative products. and we actually have broad applicability across industries and verticals. So while some tools might be hyper-focused on sort of digital experiences and Miro's has a great set of offerings there in terms of core capabilities, what we find is that Miro is used equally by companies in manufacturing, by companies in healthcare, by companies are in architecture and engineering and construction functions functions by companies that are in aerospace, governmental agencies and medical agencies and so on and so forth. So I think the platform is actually much more agnostic in terms of its capabilities and what we offer that actually makes it more accessible and appealing to organizations that want to go beyond just like digital experiences. And then I would say finally, there are a set of capabilities that are available very, very uniquely to Miro, that are valued by our users. That again is a big reason people come to Miro. So for example, if Lenny is trying to conduct a big workshop with a bunch of product folks and he wants to facilitate that workshop and wants to have certain folks focus on one part of the board and while others focus on the other part, then there are some advanced capabilities that enable certain use cases like workshops or if you want to use Miro for some team rituals or from some agile practices, there are core set of capabilities that you could use the product for that are missing in some of the other capabilities. So I would say a combination of all of those three things continue to drive differentiation. And I would say on top of that, we are a big fan of our community and we believe that Community love is what drives us. That's the fuel that keeps us going every single day.

Awesome. So just to kind of summarize, and as taking notes as you're chatting, just thinking about what allows you all to continue to do well in the market, considering all the competition constantly coming at you. One, as you mentioned, there's kind of like an innate multi-functional architecture, which is hard for someone to copy if they weren't built from that with that at the start. So it sounds like you are focusing on a much, like a wide spectrum of personas and it's not just tech employees basically. Also just, there's like specific features that end up being really important that maybe people have a hard time building and then this last piece of the community. Awesome. Let's dig into the product team a little bit and understand how you all build product and structure a product team. How many PMs are there at Miro and then just broadly how many employees just to give people a set of a little bit of context.

Give or take about 1800 employees at Miro globally across all of the 12 hubs. And specifically in terms of the number of product managers, we are over 450 PMs in the team.

And then how's the product team structured? Is it outcome oriented? Is it product area oriented? Is it user persona oriented? Is it something else? How do you think about the structure of the product team?

Yeah, so I would say it's maybe a hybrid structure that we have, but the foundation of the team setup is around persona. So we have what we refer to as streams, some companies refer to as domains, but essentially it's a set of individuals that are focused on solving the problems for a key persona. So just to give you an example, we have a stream that's focused on enterprise, and in enterprise, we are looking at the IT admin persona, we're looking at the security persona or the compliance persona. So there are a set of folks who are creating a roadmap and innovating in that for that audience. There's another stream which is called platform where we are going after the developer install base, folks that want to use Miro as a platform and build apps that they can actually make available either on the marketplace for everyone, to use, or they could be developers that are inside of a large organization and they're trying to integrate Miro with their specific use cases and workflows and business systems. So that's another sort of stream that's focused on that. And there are a couple of other streams like that. And then finally, there are some just like horizontal sort of streams, if you will. Like, you know, we have a big focus given that we are a PLG led company around growth and self-serve business. We've got a stream that's actually focused on our core internal infrastructure. We've got a stream that's actually focused on data science that's doing all of the magic that we've started to release in terms of Miro AI, et cetera, et cetera. So I would say it's a combination of those. At the heart of it is we are focused on personas and we are sort of aligning people around solving problems and creating value for that persona.

That is really interesting. One of the downsides of a persona-based approach, I imagine, is that products just features keep getting added that solve that user's pain points. What have you learned about keeping the product consistent and having kind of a holistic perspective on the experience? How do you address those challenges?

Architecturally, there are two sort of things that we have done that allow us to not pigeonhole ourselves into that specific way of working. And I completely agree with you. You could lead to that. The first one is actually When we think about the product org, we call our org, it's called AMPT, A-M-P-E-D. And this is actually going back to our earlier point, Lenny, we had around what's unique about the product culture, what's unique about Miro, and we talked about teams coming together, reducing barriers or silos cross-functionally. So AMPT stands for analytics, marketing, product engineering, and design. And everything that we do in the product org, when we say the product org, we actually don't need product managers. We actually don't need product managers, designers, and engineers. what we mean by product org in Miro is this AMP function. And by having this cross-functional representation where product marketing team is deeply, deeply embedded inside of each of these streams, what we do is that we have, you know, different perspectives that come in where they say, oh, wait a second, you know, did you think about the end user experience? And if you're thinking about the end user experience, you know, you have someone in the team that says, wait a second, did you actually think about the enterprise requirements or what's, what's needed in the largest corporation? So I the unique setup of bringing these cross-functional folks allows us to sort of course correct. The second thing is sort of the ways of working that we have. We have these product reviews that happen. So we generally classify anything that we are doing in terms of its complexity around small, medium, or high complexity and anything that's being worked on. is actually being shared with the entire organization. If it's something that's small to medium, it's actually shared with the entire product org. In fact, if you are non-product, you can actually subscribe to that Slack channel as well. So everybody sees what the product org is working on. Everybody sees what the core hypothesis is. What is the solution for that? What is the proposed design for it? How are we thinking about the capabilities? And then anything that's big actually goes through a formal process, like a product review, where there's a meeting and a bunch of us are in there. and it's up to sort of us, including the product leaders, to basically make sure that we are connecting the dots in terms of having a much more holistic perspective. And I would say lastly, as Miro has sort of scaled the spectrum of companies all the way from a team that might have two or three people and might be taking out their credit card and using Miro for their own team all the way to a large corporation that might have 50,000, 80,000 employees, all of them are using Miro. we've come to realize that at some point, the deep enterprise requirements need to be encapsulated in a set of requirements or best practices, and we need to make sure that those get democratized across all of the feature teams. When I'm thinking about building a new feature, I have a checklist in front of me where I can say, here are the 10 things that I need to think of that I need to incorporate early on in my thinking in the architecture, in the definition of the process, so that it doesn't come downstream. I would say that's an area where we're still working on. And more recently we put like more focus and energy and there's a product manager who's now leading that particular charter.

I love all these details. So this amped structure, I love that. So there's analytics, you said product marketing, Amazon marketing, and then product engineering design. It's rare that you see marketing as a part of teams, as a leadership kind of part of the leadership group. do you have a sense of what impact adding that had on the team or where that came from? Or has that just historically been something Miro has prioritized marketing and product marketing?

So this was done before I got here and I wish I could take credit for it, but I can't. And I think this was the result of an observation, which is quite similar to what you were saying, which is while we might be developing a lot of the features and PMs are sort of thinking bottoms up in terms of what we are building, we might find that what we have built might not be able to capture the imagination of what we originally thought it would. And a big part of that is how are you going to think about positioning? How are you going to think about competitive differentiation? How are you going to package it up so that the sellers that are out there are able to position it in a way that the customer, in this case, the buyer might be an IT professional, might be a line of business leader, can basically see the full vision of where we are going. And I think by having product marketing as part of AMT, we now bring that unique perspective that may be missing in certain teams. PMs are more acting as product owners or more focused on core sort of problem and solution, but not thinking about positioning because that's so important, especially when you're thinking about a market that we are increasingly in that there is competition there. And that's one of the first things we started off with, and that's top of mind for you as well, is that everything that we are doing, you know, has to be looked through that lens. And, and one of the core philosophies that I have, Lenny, is that the success of a company is a direct relation of what the competition allows you to do. I feel like not many people sort of talk about that, but, but in many cases in my professional career, and I've been at it for, you know, close to 24, 25 years, is that every single instance when I looked at a company accelerated their growth, or there was a deceleration of growth, it was a direct relation to what the competition allowed you to do. And obviously, you have to do everything that you should be doing, but competition is the biggest variable that allows you to figure that out.

I want to hear more about your core product philosophies. Let me dig into the one you just shared. What you find is that the way you grow or stop growing is often a direct result of your competition. Is there an example of that that comes to mind? Like I'm guessing maybe box versus Dropbox is an experience you had there, or if not, what's an example of that that you've experienced to make it a little more concrete even?

For those of us who've been in the collaboration space and I've been doing collaboration and productivity apps for over 20 years, over two decades, at some point, you have companies like Microsoft that get really attracted to a space and you can see the trajectory of a business that's growing at a certain clip and then all of a sudden there's a competitive product that enters that has the might of distribution and the might of pricing. And that's just like a direct example. And I think I've seen that multiple times. First at Adobe where I was part of the Document Cloud business, clearly saw that at Box as well. and I think you can in general look at every single category and you can say, there was a category leader and they were growing at a certain clip or a certain pace, and all of a sudden there were a bunch of entrants that get in and what happens to your growth rate. And it's all dependent on how strong is the competitor in terms of providing a good enough solution, that's one. And the second is how strong is the competition in terms of their distribution outreach. And then the third thing is how strong is the competition in terms of the pricing and packaging.

I really like this discussion, especially because often the advice is, don't worry about the competition, just focus on the customer. It's gonna be fine. Which, what you're saying is that's not right, and I agree. What do you do with that in mind? How does that impact the way you build product or strategy? Is there some you could share that maybe tactically someone could leverage and to have they're approaching their product strategy?

It depends on like who the competition is and what is their unfair advantage here. And we talked about one specific competitor and I have a lot of respect for them, by the way, and I learn a lot from them every single day in terms of how they make bets and how they enter markets and stuff. At some point I'm going to write a book on them, I feel.

We'll have to come back to talk about that.

That's right. Yeah. And I think it sort of comes down to how do you think about your unique place relative to all of these players. And in your customer's mind, are they able to clearly understand what is the unique value that you deliver relative to everything else? And part of that is the unique capabilities you provide. Part of that is how you're packaging those unique abilities to them and making sure that they, in their mind, can see how you coexist in this overall sort of tech ecosystem that they might be investing in. to enable their employees or, you know, to enable them to operate. And so I think it's sort of looking at that from that lens.

Yeah. Got it. So what I'm hearing is be very clear about your differentiator and continue to invest there and then make sure your positioning is clear around why you're just identifying here's why we're different and we're not just like a better or worse version of this thing. Here's why we're different and making sure that's really clear.

Exactly. And I think the other thing I would say, like there's another core philosophy I have, which is products either get better over a period of time or they get worse. Products never remain the same. And I think you can take that philosophy to a bunch of things in life, but I'm gonna take the lens off products, which is my core philosophy is like every single day, every single time somebody is pushing your code to production and you're releasing a feature or an enhancement, you are making the product better or you're making the product worse, but the products never remain same. And the lens for this Lenny is actually from a customer's perspective, from the end user perspective. And the thing is that, you know, if you are a player where there's no one else in the market, that's one thing, right? So that's great. Like, you know, kudos to you for actually identifying a blue ocean strategy and sort of executing to that. But most markets, most products actually have either direct or indirect competitors that are available. So from the customer's mind, you're doing something, the competitor is doing something. So in their mind, they're looking at these products and they're looking at these companies and they're saying, which is better versus not. And so with every release that your competitor is making and every release that you're making, you're either making chess points moves against them, positive points, or you're going negative. And I think that framework if you have in mind, it actually drives an insane amount of clarity in terms of what you're doing and what the impact is going to be. Because every single move that you're making, the customer has that sort of in their mind, if not explicitly, implicitly, that they are actually comparing these things. And I think it brings a level of focus in terms of where you need to invest and why you need to invest and why this is going to make those decisions. And so I think it allows, at least for product leaders, to make some high quality decisions around the bets that they're making. and how they're going to play out in terms of like eventual, you know, once the dust settles, you know, and, and the market at large is going to say, I'm going to standardize on something. And now I feel I need to go get it for everyone. Or, or this is the tool that I want to use for this particular use case that all of these decisions that they were making ladder up to that final sort of play that you have to do in terms of the market consolidation that eventually happens.

This is so interesting. Essentially what you're saying is that you find that being very close to and understanding the competition really well is really essential versus like this kind of the other end of the spectrum almost from just like, don't worry about the competition, don't pay attention. I like these, like this point metaphor of just like, are we moving ahead or further behind? Is there where you operationalize that to kind of track that? And then also just like, how do you not over obsess with, let's just catch up, get more features, that kind of thing? Like how do you find that balance?

I'll be honest, like I don't think we've figured it out. We haven't cracked the nut in terms of how to operationalize this, but I know you are based smarter than me on some of these things. So maybe we can come up with something.

All right, that'll be something we work on. Any other product philosophies that you want to share? That was awesome.

This is all like sort of related to it. It's like a string of pearls. I think like there's maybe like one more pearl we can actually thread into the needle right here.

Let's do it.

Which is, you know, we talked about sort of how do you ladder this up and stuff. And then the question is, okay, how do you know that everything that you're doing is that in the right direction or not? And should you move slow and be much more mindful about the things that you're doing, or should you move fast and make certain bets and then decide certain things and stuff? And I think there are two sort of views that are out there. My personal sort of perspective on this is that what you want to do is that you want to be the first one to hit the brick wall. And this is particularly true when you are in a market that is competitive. And the reason for that is that if you consider yourself as an innovation-centric company and you believe that you know, you are building experiences that fundamentally don't exist anywhere else and you're sort of paving the way for the rest of the folks to basically get inspired with how you are building these experiences. Speed is the single biggest determinant in terms of, in my experience, in terms of, you know, who ends up being more successful versus not. And I think like this, I don't know, maybe this is a little bit controversial where, you know, people say like, you know, go slow to actually go fast. And I think I have a lot of respect for that and there are certain areas you should do that. But when you are trying to figure out sort of new experiences and stuff, and you don't know if it's going to resonate or not, speed is something that you should accelerate for the organization. I think like Frank Slootman talks about this a lot in his book and how can you accelerate? And I think for me, from a product perspective, the fundamental concept is can you be the first one to hit the brick wall where you have the learning faster than anyone else in the market so that you can decide, oh my God, the path that I was going was not the right path. I need to do 10 degrees west or I need to do 30 degrees east. And I think as long as you're like one or two or three steps ahead of everyone else in terms of uncovering or discovering those insights, then I think you can continue to be ahead of the pack in terms of building building your product and business.

You're talking about urgency. I've never met a founder or a product leader who doesn't want their team to move faster. They're always encouraging their team, how do we move faster? I'm curious if there's something you've learned tactically about helping your team move more quickly. You mentioned Frank Sloutman's book, Amp It Up, is what it's called, by the way, in case folks want to check it out. And he's big on just like creating a sense of urgency, constant urgency. And we'll link to that in show notes. But yeah, what have you found helps create urgency and generally helps your teams move faster than just like move faster everyone.

My fundamental sort of belief here, Lenny, is that every product manager, I can talk to product managers because you know, there is reason certain ones, someone wants to be a product manager because like in my view, it's like one of the most thankless jobs. Like you get to do all of this stuff. You should watch. as like Baba you have to do this and there's like uh but like there it it attracts a certain personality and that personality is driven by challenge and that personality wants to prove that they can solve this challenge and do something amazing. So I think fundamentally, you know, the product persona actually wants to move fast. I think the reason why in some cases, we are not able to move fast is because of roadblocks that we run into. And those roadblocks can manifest themselves into technical challenges. They can manifest them in selves of organizational challenges. They could be priority challenges and so on and so forth. So my fundamental sort of approach to solving that is to ensure that the product leads who are working on these capabilities can instantly raise their hand and call out that there are challenges that they are running into. And then the job of the leadership team, the product management team is to essentially go and quickly resolve those issues, right? And I think like if you are able to resolve those issues, then what it does is it actually starts a virtuous cycle where you can actually start to see those wins. And once you see those wins, you actually create that courage to do more things. And maybe because you've seen how that specific roadblock was solved and you have a patent matching that you've developed now, you can solve a lot of those things on your own. And it's the next level of challenge that you're now going to raise your hand. And what that does is it starts to build this organizational competency in terms of how you can figure out what to build. And we all find these people in our organizations where there's someone somehow is able to do certain things in one-tenth the time that would take a normal person. It's not that they are like 10 times faster. It's just that in my observation that they've figured out which part of the code base they should build in versus not. Who should be part of their team and who should not be. How they need to define that from a scope perspective, what does success look like? And it's the architecture of bringing all of these things together that actually brings that magic formula in terms of like, Hey, we are able to deliver faster.

I really like this topic. What I'm hearing is one of the biggest roots of slowing slowdown in a company and product development is blockers not being unblocked. And I always feel the same thing. Like, I feel like a PM's job, like number one job is to unblock their team because like their job is basically make the most out of their team that they're marshaling towards some outcome. And the way you do that is just figure out what's slowing them down. You've talked about this idea of a PM raises their hand to leadership, hey, we're blocked by this thing. Is there a process you've come up with there to help you do that?

It's like an I would say we are trying to sort of systematically ingrain this in the culture of the organization. So we have a motto in the product org. It's very simple. single sentence, deliver customer value faster with high quality. That's it. And everything that we do. And when I say everything, everything, Lenny, like from like, you know, performance and reward system and measurements, everything is based on this one single statement. And it has three attributes. The first one is deliver customer value. And we believe customer value is only delivered when customers use it. So anytime as a PM at Miro, when you ship something, we're looking at, well, what was the metric you were going to move and how much did it move? And we have some original targets that we can go back to. So that's the first aspect of what we're doing, deliver customer value. The second one is move faster. And there are certain cycle times that we are measuring across the organization. Okay? You know, from the time you came up with the idea to the time that you actually pitched a solution to the time you actually shipped it to the time we actually moved the metric, it's information that has been collected and is being made available to the organization. And you can say, hey, if it was a small, medium, or large, you know, what's the average, what's the median, what's the variance? And you can say, hey, like looking at this data, what can be improved. So that's on the faster aspect of it. And then the last one is around high quality, which is, you know, we want to build best in class, you know, collaboration experiences. So we are always, always getting inspired by what we find, you know, in, in applications and experiences that we see around us. And we are saying, hey, when it comes to, you know, designing sharing flows, you know, we believe that these are the three, you know, apps that have the best in class sharing flows when it comes to designing some synchronous capabilities like these are the best in-class apps that we should look at. So we are always trying to make sure that we are benchmarking ourselves against that. And we have our design team on a regular basis, like when we ship stuff on a monthly basis, our design leadership team does a triage of everything that got shipped into like high quality or not high quality. It's just like a binary function. And we're doing that and we're saying, hey, the reason why we believe it's not high quality is because A, B, C, D, E, and we're making it available to other designers so they can actually start to build sort of that Telemetry in terms of like some things are more subjective, but you can start to see some pattern matching and say like, hey, you know, this is what this is what looks like.

This episode is brought to you by Linear. Let's be honest, the issue tracker that you're using today isn't very helpful. Why is it that it always seems to be working against you instead of working for you? Why is feel like such a chore to use? Well, Linear is different. It's incredibly fast, beautifully designed, and it comes with powerful workflows that streamline your entire product development process, from issue tracking all the way to managing product roadmaps. Linear is designed for the way modern software teams work. What users love about Linear are the powerful keyboard shortcuts, efficient GitHub integrations, cycles that actually create progress, and built-in project updates that keep everyone in sync. In short, it just works. Linear is the default tool of choice among startups, and it powers a wide range of large established companies such as Vercel, Retool, and Cash App. See for yourself why product teams describe using Linear as magical. Visit linear.app/lenny to try Linear for free with your team and get 25% off when you upgrade. That's linear.app/lenny. Okay, so every month or so, the design team looks at everything that's shipped and puts things into a bucket. Either this is, it's like a binary thing, high quality or not high quality. Yeah.

Wow.

That is so cool. And then one, what do they do with that? Do they send it out to the product team? And then two, is this just like FYI or is it like we need to fix all these low quality things going back or is it more just like for the future, please be aware these are not high quality.

Yeah, so it's actually both. So generally what happens is that the design leadership team is doing this and there's one particular design leader who's the designated person to make sure that this is happening on a regular basis. And right now the way we're using it is that we are actually using it to calibrate and align around the design leadership around what we mean by high quality. Because it's one of those things, right? It's like you know, if you've never seen colors, and I ask you, Lenny, describe pink and, and, and compare that to red. And, like, if you haven't seen, like, colors, how do you describe colors? You can. But, like, if I show you and I say, Lenny, these are three examples of what pink is, and these are three examples of red is, then you're like, oh, I get pink and I get red. So there are certain things that you just, like, when you write it, it's very, very hard to describe it. But if you show specific examples, it's very clear. Oh, I get it. I, I get why. how pink is different than red. But if I try to describe it, it's going to be very hard. So we got into these endless conversations at some point about a year ago where we were saying, we need high quality, we need high quality. And people were like, let's just go and define this thing. And we had like a bunch of our leaders go and write documents, like really long documents in terms of what are the attributes and how do we define those attributes and how do we measure those attributes and how do we enable people to do that? and it felt like it's a good thing because we are trying to codify it, but it also felt like, you know, it was a very heavy way of solving that problem. And then, you know, we just came up with this approach, which is like, what's great versus not great, and just start classifying it. And as you know, it's like modern.

AI systems are like classification systems, and we got- I was just gonna say.

It sounds like reinforcement learning approach to defining goals. That's right. That's right. And I think it's worked decently well, I would say, like with most things, like you know, we need to operationalize it and we need to make sure that now we are democratizing it and everybody has access to it and so on and so forth. But I think it's, it's been, it's been a good start. And now, you know, we are sharing this more openly with the, with others.

In the, in the org. When I said that I imagine you, from the outside, you have a very unique culture and approach to product. That's a great example of that. I've never heard of a process like this. So what I'm hearing is essentially you're trying to build the muscle within the organization of what is quality. It's like this. continued heuristic of like, okay, I get it. And so PMs on the team start to understand in their head what that means.

Right.

Super cool. You also talked about the middle part of that sentence of moving faster and then you track and measure that somehow. Can you talk more about that? Because that's something every product team is always trying to understand. How do we know if we're going faster, if we're going as fast as we could? How do you actually do that? How do you measure these things?

The core philosophy there is, you know, velocity is more like the game of golf where you're just playing against yourself. It's not like if Lenny and Varun are out of the golf course, it doesn't matter. I'm not competing against you. I'm just competing against myself because that's the only way I'm going to just hit the ball. So it's like how much better can we get? So I think our core philosophy is around that. And what we're trying to do is that on all the product teams, the feature teams that we have, we're just collecting all the information. and we are making it available to everyone so that they can actually see what the cycle times are. And what we are interested in is from the time that you have an insight, from the time you believe, I can do something unique for my user, for my persona, how long does it take for you to actually deliver that value? And we have a product process that we follow, which starts with the P-strat, which is a strategy, and then we go into P0, which is definition of the problem, then we go into P1, which is definition of the solution, and then we go into P2, which is once the solution is shipped, are we hitting the metrics that we originally had defined upfront before we decided to work on this? And you have all of these stage gates, and then we basically classify everything that we are doing in small, medium, large, and you can go in and you can say, hey, I thought this was a small thing, and small thing is something you can get it done in less than a month and so on and so forth. and there are like 50 other product teams that are shipping these features and what's the average, what's the variance, what's the median and oh, wait a second, actually it seems like I took way more time in the problem definition stage. Let me actually try to go talk to this other product team that actually did it much faster or oh, I actually did it really, really fast and the reason why I did it fast was because of this, let me go share this out with the broader team. And usually like the product ops function, we call it product excellence internally, like sort of product excellence function. is recording some of these things. I would say, you know, getting reliable data and then because we have some things that are going through meetings and there are some things that are going through Slack, like, you know, we could do better on some of those dimensions, but all of this data is available and we provide it openly and folks can benchmark themselves against that.

So cool. Okay, so you have this pstrapped, you called it, document, which is kind of like an initial concept. And then it's interesting to use the P0 or P1, which is often for bugs, but it's cool that you use it for defining your products. So PStrat is just like an idea pitch. P0 is a spec basically like a one pager for the product. And then P1 and P2 are basically getting to like, here's the actual product we're building. And you basically track time per step and map it to, here's how large this project should be. And over time you track per person, it sounds like. Just like, are you matching the benchmarks of how long a small project should take across each step? Yeah, exactly. Wow, that is extremely cool. Whatever templates you can share, these things that we can include in the show notes would be awesome.

Yes.

Because people are always looking for just like, I want to do some of this stuff and they just plug and play. The more the merrier.

Yes.

Shifting a little bit, it sounds like you guys are doing Scrum in some form. You just talk about just broadly the product development process, like how long are your sprints, how long do you plan for in the future in detail, specifically just like high level, how does the product development process work?

So there are certain things that, you know, I learned at Box and, you know, that inspired some things that we do at Miro. And there are certain things that we've evolved. So like one of the things that we've instituted is sort of, you know, our roadmap process, right? So that's sort of the first thing around how the different teams are looking at the things that they're going to work on. We have a rolling six months roadmap. It seems large, but we've got, like I mentioned, a number of enterprise customers. If I've learned one thing that large enterprises like is asking for a roadmap review. That tends to be my favorite meeting of sitting down with the enterprise leaders and walking through what we are working on. What we've done is we've tried to architect something which actually allows our customers to get what they're looking for, but at the same time does not remove the agility that is so important for us to deliver value faster. And so what we do is we have a rolling six-month roadmap that gets updated every three months. And the first three months of that roadmap, we have a 80% precision level, which means that 80% of the things that we claim to be on the roadmap Will get done. That's, that's the target. And for the, for the next three months, because it's six months, so the first three months is 80%, the next three months is 50%. So we have a much lower level of resolution in, in the next, you know, three months after that. And what that allows the product teams to do is actually have flexibility, which is based on what the customers are asking for and based on what the competitive moves are based on some technology breakthroughs that happen around large language models. They can pivot and they can pivot and move to towards that, and they won't get penalized either by the customer or internally in terms of doing that. So that's, that's what we do. And that's all on the backdrop of an annual strategy that we publish. So every year, you know, we publish a strategy white paper that it gets published internally available to every single Mirrornair, you know, across all functions that clearly articulates, you know, the key bets that we want to make. Why do we want to make those bets? What is the expected outcome? And how does that ladder up into the overall business outcomes that trying to drive from an OKR perspective, as well as the overall business strategy that we have. So people take that product strategy, white paper or artifact, and then against that, they're building their roadmaps, which get updated every three months. And then inside of the teams, we enable teams to be quite autonomous in terms of some of the rituals that they're doing. We want them to obviously embrace best practices. We've got a team of agile coaches. that, you know, share best practices are, you know, are available, you know, to help if there are certain specific, you know, needs that teams have. And then I think like on top of that, there are certain key, like I would say rituals that we do that maybe are unique. So for example, we have something called as Miro Connect, you know, which happens every other Friday. And, you know, every other Friday, For example, in our Amsterdam office, you can go in there and at four o'clock in the afternoon, four to seven or eight, and sometimes it goes really late. You've got a bunch of product teams sitting around tables and it feels like, oh, it's like a trade show or something and people are coming in, they're having a good time, you've got a drink in your hand. There's maybe some light music playing in the background and you're going from table to table and you have teams that are actually showing all the amazing work that they're doing. It, you know, if done right, like it happens once in a while, but like if done right, it's magical in terms of the outcomes that you can get. So I'll tell you, there was a team that actually was presenting at our Berlin hub and they were saying, we're working on this feature, you know, and there's an, you know, there's an engineer, you know, who walks over to that desk and says, what are you working on? And the team describes it, oh, we were trying to do, you know, something like this. And this engineer had actually worked on that paticulAr problem in their, in their prior life. Like literally they had implemented this. So he says, so, so how are you going to implement this? And the team, the engineer that's sitting there says like, this is the approach I'm going to take and it's going to take me three months. And he's like, oh, would you mind if I go and help you with this? And they're like, sure, more the merrier, go ahead. So this person, you know, you know, puts down their beer and says, okay, I'm having a good time. Let me just head back to, to my home. And in the next three or four hours goes and quotes the entire thing, makes a pull request. and next day in the morning, one of the engineers from this core team that was exhibiting at Miro Connect, looks at the pull request, reviews the code and says, yes, something that would have taken three months for this core team because they didn't have the expertise, literally got done in three hours because there was another engineer that ran into them and said, I know how this is done. I can actually help you here and went ahead and did the right thing. And so we're trying to create these magic moments. It happens once. once in a while, but we have one success story. And I like to tell that in every opportunity that I get. But that's another sort of, sort of unique thing that we've done in terms of bookending things around how, how we operate here.

That story is like a dream for any PM. Just imagine at least saving months of work with one conversation. I imagine people were like, how do we replicate this on often? I love that. with these meetings, just understand if their team is in Berlin, let's say, there's a screen there in front of a table and they're talking through a screen, like a video conference.

Yeah, right now what we've figured out is that it is really hard to do these events over audio video conferencing and stuff. So generally what happens is that you have an audio video bridge that's playing, but mostly it's people walking up to the respective teams and then having a live conversation. that's usually how these things are operated. Yeah.

Got it. Okay, so you have six month rolling roadmaps, you have a yearly vision strategy for the company, two week sprints. Is there also a quarterly OKR-ish sort of process or is it those or not?

There is.

Okay. Can you just talk a little bit about how that works?

Yes, yes, yes. At Miro, we practice OKRs and, you know, it starts off at the company level and then those company level OKRs are taken by the AMT organization, like we describe, it's the AMT organization. And then we break it up. And I would say we have refined it over the period of time, the two years that I've been at Miro. And early on, we were doing OKRs on a quarterly basis. And I would say more recently we've actually evolved to six-month OKRs. And what we found was that You know, six months was the right cadence in terms of giving enough time for teams to basically push forward in executing these KRs and minimizing the quote unquote overhead of doing replan every single quarter. And we found that it was much more effective and efficient for the entire organization to do it on a six month basis. However, we are doing traction on a monthly basis. So every four weeks, As AMT, we are looking at our KRs for the AMT organization on a monthly basis doing fraction. However, the planning, the targets are done on a six month basis.

I love how OKRs could just be anything. It could be every six months, could have objectives, could have key results. It's just such a term that just applies to anything that people do with goals, basically. That's true. And it works. It's great.

That is so true.

And again, if there's any templates that your team could share of the way you do that stuff, that would be amazing.

I'm gonna include that in the show notes. Yeah, absolutely. Because I think like as you would expect, like we run Miro on Miro, so there's like a lot of things that we could share as templates in terms of how we are running things on Miro, not just as OKRs, but in terms of product reviews and, you know, we have a ways of how we are doing asynchronous reviews combined with synchronous reviews, and there's this blended experiences that we have, and so we can we can definitely share out with the community how we do some of these things.

Awesome. And that's a great segue to another question I was going to ask is just what other tools, what's in the stack of the product team's workflow? So Miro, obviously, maybe talk about what you use Miro for, but then what else is in there? What do you use for task management, bug tracking, things like that design?

Sort of starting from the bottom up, infrastructure up view. So all of our tickets are handled in Jira. And we're using some of the newer capabilities in Jira in terms of coming up with roadmaps and coming up with the priorities and stuff. On top of that, all of the specs generally get recorded in Confluence. Having said that, we're actually a big fan of tools like Google Docs as well as Coda that allows us to track our KRs in a in a pretty effective way. On top of that, obviously, we use Miro a lot, I would say, for a lot of our things, especially on the product and design side of the team. Generally, all of our insights get captured inside of Miro boards. When we are going and conducting user experience interviews and stuff, we will record those and then those recordings get added to a Miro board. So Miro acts as the content hub or a team hub for a particular project. Once you capture all of those insights, then generally all of the brainstorming and team ideation happens on the Miro board as well. So Miro is actually also used as a tool to facilitate meetings and workshops. Once all of that is synthesized into a set of recommendations and outcomes, so when we go into these product reviews that we were talking about, Lenny, the same Miro board then gets manifested into a set of presentation. So we use Miro for presentations. We've actually made some really amazing updates in terms of our capabilities there and folks haven't checked them out. I would strongly encourage them. So there's a capability called Showtime that basically abstracts out the UI and lets people focus on the content, but do it in a way that it's interactive. So everyone that's on the call can have reactions, can share their comments and leave comments while the presentation is happening without actually disrupting any of the flow for the user. So we use that a lot for presentations as well. And I would say more recently what we've started to do is that we've started to move some of our synchronous meetings into async review. So I talked about this talk track feature that we have. And a lot of teams, what they would do is that they would actually send you, you know, five minute, 10 minute talk track in advance. And it's just a link to a Miro board. You click on it and then you just sit back and relax, you know. and then you have this magical experience where you're sitting back and the Miro board is automatically moving because Lenny was like recording it like that. And then you have the video play and then you can pause it anytime, you can add in your comments and stuff so that the next time when you meet, instead of actually providing context to everyone, those synchronous sessions are a lot more deliberate and focused on driving outcomes or achieving consensus. So people are just focusing on the comments that were added as part of the Async product review. so that when they meet synchronously, they can use that. So Miro boards are used for that as well. And I would say now a lot of our dashboarding shows up in Miro boards now. We recently released data visualization capabilities around most popular BI tools. So at Miro, we use Google Looker a lot. A lot of our dashboards are in Looker. And what you would typically find is that our analyst, team and product teams will just grab a link to a Looker dashboard, put it on a Miro board and it unfolds into a full visualization. and unlike a screen grab, you never have to go update it because right there on the Miro board, it's always updated and you can refresh that. So you basically have this experience where Miro acts as that single source of truth for a lot of the teams across the entire journey of product development, where a single Miro board is meeting the needs of multiple use cases there.

And then for the road mapping, is it in Miro, like each team's roadmap or do you use something like Jira. Yeah.

So I think we've got a couple of tools for road mapping. And our observation is that while those tools are great for the unique needs that they're solving, we haven't found a universal solution for road mapping. So there are some teams that use Miro for road mapping, and they would use the Kanban widget in Miro for that. What are they working on? What's coming next? What's in the backlog? But I would say it is a problem that is not completely solved in terms of how do we actually bring you know, these artifacts together at scale. What we are starting to see, and this is actually a unique use case of Miro, is that we actually enable our entire field organization using Talktracks. So what happens is that we have our entire roadmap published out as a Miro board for enablement purposes. So that's an artifact that is approved to be shown to a customer. And what you will see is that you'll see five or six recordings in there. And, you know, the leader for enterprise has done a five-minute recording on everything they're working on. The leader for platform has done that. The leader for end user experience has done that. You know, the person who's driving some of our AI experience has done that. And so you can go in and you can just click on that video and you can self-serve sort of meet your needs by using Miro and this capability that we have.

That's awesome. And it sounds like each team can basically choose the tools they want to use. There's not like standardized. Everyone needs to use Jira or Miro for their roadmap. I like that. I like how teams do that often. Maybe one last question around the product org. And then I want to shift a little bit to growth and how Miro grows and things I've learned about growing. So question I always try to get to is how do you think about balancing new bets and innovation with maintenance and just general incremental work? Do you have some sort of philosophy as a product leader broadly and then maybe at mirror specifically of just like how to balance investments in these two buckets and maybe three buckets, you know, bugs, incremental work, and then just big bets? how do you think about that?

So, you know, we have some, some rule of thumbs in terms of, like, how we want to allocate, you know, our, our Investments across these buckets. And I would say a lot of it, Lenny actually depends on sort of the state of the team. Like, there are, there are certain, certain teams that have more Tech debt than others. There are certain teams that are actually working on some really big zero to one features than other teams. And so I think, like, there is a variance, you know, the standard deviation actually is dependent on, like, which part of the spectrum that you're in, which are you a team that we believe needs to create the next generation experience on the platform? And hence we have to prioritize innovative work or are you the team that's actually so critical to actually meeting our objective around better board performance or any of the other things that we believe are important and hence we need to invest in those critical areas? But I would say in general, innovation versus not varies on a spectrum of anywhere from 60 to 80%. so I would say about 20 to 40% of the available capacity at any given time is either getting allocated to architectural initiatives. There's a technology roadmap that our CTO is driving that we believe is extremely important as the platform scales. And now, as you know, we have over 50 million people on the platform. So we continuously have to invest in making sure that the platform can scale. And there are certain teams that probably have 40 to 50% of their allocation towards that because they're a critical part of the component. and there are other teams that are maybe more end user focused and are more UI focused where that allocation is lower. But I think general rule of thumb is 20% is always a given, but it can go as high as 40.

To 50% on bigger bets and longer term thinking.

Yeah, 20 to 40% goes on the technology related initiatives.

Oh, got it. Like infrastructure maintenance, making sure everything's there. Run got it.

Exactly.

And then what about just big long-term bets that you're not expecting to pay off anytime soon? Do you have a heuristic of just what percentage of, say, total resources you put there?

You've probably seen this, the framework of like three horizon. It's quite popular in like McKinsey and like Harvard Business School and so on and so forth. It's like horizon one business, which is what we are, the thing that's delivering food on the table. Generally there's about a 70% allocation of resources that we have to or take. Then there is Horizon 2, which is an adjacent thing, you know, over the next 12 to 36 months, we believe it's material. Usually that tends to be around 20% of the allocation. And then there's Horizon 3, which is like three years out, you know, three to five years, you know, next generation things. And that's about 10% of the ratio.

So it's like 70, 20, 10 across Horizon 1, 2, and 3. Awesome. Any other thoughts along the lines of just how you think about product before we shift? And I only have a few questions around the growth. kind of story of Miro in which you've learned about growing?

In terms of product leadership and what we believe is the way we want product leaders to be developed. And I think it's more of a people philosophy. And so we have our product leadership, which constitutes of all of the folks who are running all of these streams. And I always tell them that you have two personas that you have to think about. Everyone who's on the product leadership team is a product leadership team member, and the fundamental thing that you have to do is drive accountability. So the number one thing that a product leader on the product leadership team needs to do is drive accountability with others in the product leadership team. The other persona that they have is that they are a stream leader. They're actually responsible for delivering value for the respective persona and respective customers and stuff. So when you put on the persona hat of a stream leader, which is different than the persona of a product leader, your number one metric, the number one goal that you have is drive improvement. So when you go back and you work with your team, always have the lens, are you improving things and whatever you want to improve, but you always have to ask yourself, today compared to yesterday, tomorrow compared to today, have I improved things? And that's the yardstick you should think about. When you go sit in the product leadership team every Monday morning, every Monday afternoon at one in the afternoon when we meet together, your number one goal is actually to drive accountability around this. And are you making sure that we as leaders in the organization are doing the right thing for the company? And I think that's a philosophical construct that I always remind people in terms of what they should be doing. So as an example, tomorrow we have calibrations. We have our annual review cycle happening in the company. Always a plus. Always fun and so critical as a leader. because it sets the tone for everything that you're going to do. And in my opening remarks, the only thing I'm going to remind everyone in the room is that your number one goal here is to be a product leader and accountability is what you have to write. That's it. Just hold each other accountable, including myself, in terms of making sure that as we go in, that's the key thing. And I think once people sort of understand the duality of how they need to operate across those two specific goals, It actually leads to really high performing teams and teams that actually are able to create somewhat of a magic if they are open and there is trust that has been built in the team.

And when you say accountability, what does that look like? Is it pointing out, hey, you didn't achieve this thing we were trying to achieve, or you didn't do a great job leading this meeting? Is it just direct feedback often or Is there some other way you see that manifested and what do you like to see?

Yeah, I think it's basically practicing feedback in a very open and constructive way and focusing on what is important for the business and not shying away from having some of those observations and conversations, not shying away from that. But it's all in the lens of like, what is the right thing to do for the business? And if you feel that one or more members of the leadership team are not living up to what needs to be done than just voicing it. And it's not like you're complaining or anything. It's just like, I have this perspective. Is this the right perspective or not? Because actually it ties very well with the overall cultural values that we have. If you do things with the lens that you are being empathetic, then you pose it as a question as opposed to a statement. And I think that's one of the things that we practice a lot at Miro is that I believe that I am seeing there are certain things that are happening that it could be just me that I'm not seeing the other things. But what is it? Can you help me understand? Can you help me figure out that why certain things are happening? Because I might just be missing the perspective. But because you bring it up and that's part of practicing accountability in an empathetic way, it actually gets the entire team in the right mindset in terms of how they operate.

Has anyone given you some sort of direct feedback recently or pointed out something you didn't do well that held you accountable that you could share all the time.

Yeah, all the time. When we do our offsites, this is actually a fun thing is that every offsite that I do with the leadership team, usually there's a one to two hour session. It is feedback to Varun and I actually do it openly. I will have about 8 to 10 people in the room and I will force people to be very honest and I want to show my vulnerabilities to everyone. that I am not perfect and I have lots of areas to improve. And every time people do it, like it's interesting like that, they open up in very amazing ways. And I think I love it because it helps me become better. It helps me identify my blind spots. But what it does is because I do it in an open way, it builds a lot of trust. It brings trust that, you know, I do it openly and I'm an open book and they can share whatever they want, not just with me, but openly in front of everyone.

Are you willing to share one thing they suggested that they pointed out that they wish you did differently or better?

Yeah, I think in general, finding time with me tends to be a bit of a hard thing. And generally, there's always this feedback, which is like, need more time, maybe more responsiveness over email or Slack or something like that. And that's an area that I'm constantly working on and I'm improving.

So, yeah, that feels like a cop out. Like, that doesn't feel too painful to hear. I'm like, yeah, yeah, I know. I don't have a lot of time. I'm sorry, but I get it. I get how, and that comes back to your point about blockers and how important it is to unblock teams because that leads to a lot faster progress.

That's true.

That's true. Okay. So let me shift a little bit to Miro's growth, and I only have a few questions here. I know it's getting late in your site, so I don't want to keep you too long. Sure. the first is something I'm on this constant quest to understand how companies got their first users. And I haven't actually heard the story of how Miro got its first thousand users or customers. I know you weren't there in the early days, but do you happen to know how Miro initially grew and got their first thousand users and customers?

I think the fundamental thing there is that we always had user-first approach and reaching out to certain communities. that were relevant to what was being, it was like a key part of lighting the fire, if you will, the proverbial way people to start to talk about the product. And, and given the collaborative nature of the product, you know, some of the early adopters invited people who were also early adopters and sort of the flywheel started to, to work. Uh, you know, I've heard that, we did a fair amount of content marketing and like, you know, listing the product on, on sites like Capterra sort of helped there was some early investments in terms of SEO and organic growth. So there was a focus there which was the main source of driving traffic. The top of the funnel came through that. The product teams were very intensely focused on sort of building viral loops as a key mechanism of driving growth once the traffic came in. And every interaction that actually introduced barrier, they looked at it and they looked at the data and they said, let's reduce this barrier, let's remove this so that, you know, the product could be effectively embraced. And it was an evolution over a period of time. You know, there was also the fact that early on in the journey, you know, some of the features were presented on a trial basis, you know, and then later on, like sort of the model was evolved from a trial basis, time limited to a premium model that further sort of accelerated, you know, the growth for the business. I would say like those were some of the approaches that were taken to get to the first thousand users or so.

So you talked about how Miro grows, where it has this magical loop of, I use Miro for myself, then I share it with my team, and in whatever way I'm using it, they're like, oh, Miro, this is cool. And then they start using it, and then they share it with people that they want to work with and increase this loop of growth. And I imagine that's how Miro mostly grew initially and continues to grow. Is there anything surprising or unintuitive about how Miro grows that is beyond that? I imagine sales are part of it and we can talk about that, but is there anything else that is interesting that is worth mentioning?

No, I think that's the key of the growth. I think there are specific use cases where they are uniquely geared towards inviting a lot of net new people. For example, Miro is loved as a workshopping tool and so generally one person is using Miro but they invite 10, 15, 20, 50, 100, 200, 300 people to that workshop. So there are specific use cases where people get introduced to the product and then go and sign up for it and then start to use it for that use case or other use cases. I think the other sort of accelerant in all of this is the templates that we have in particular, the role that Mirroverse plays in all of this. And just to give you an example here, like there was a template, you know, which was created around FIFA World Cup, right? So there was a FIFA World Cup diagram. Cornel X, you know, he's the founder and managing director of a Canadian strategic service design consultancy firm. He created this mirror was template and, you know, it, you know, it had over 100,000 views and about 15,000 copies were made of this single template. and given sort of the popularity of all of this, like it actually got indexed by Google. So when you went into search, you actually saw the Miroverse Figma template show up when you were trying to search for FIFA World Cup. And that was another sort of acquisition channel top of funnel that actually drew a lot of users to it. So I think I would say the Miroverse is also like a key accelerant to this.

If you had to think about the pie chart of how Miro grows, what percentage roughly would you say is word of mouth, organic versus what you just described, which is essentially SEO versus sales, outbound sales, how do you think about this? Is there a way to kind of model that simply?

Without getting into specific numbers and stuff, I would say fundamentally Miro is a product-led growth company and product channels are one of the highest contributors for growth of users. As the business has evolved to serve the needs of some of the largest corporations in the world, the enterprise segment and the enterprise persona when they're trying to provision Miro for tens of thousands of users who then go conduct hundreds of thousands of workshops on Miro that invite millions of users on the platform. is a key part of the flywheel that we are seeing. So I would say product channels are probably very strong and increasingly enterprise is a key part of that acceleration.

A great segue to our final question, which is the idea that you start a product like growth. Sounds like clearly it's a big part of growth today, but as every product like growth company does eventually, you have a large sales team, I imagine. What have you learned as a product leader working with sales, especially at a product-led growth company, but how to make that relationship work and have a product work effectively with a sales org.

There are sort of a few learnings and I would say maybe this is one area where we're working on how we could be doing better in terms of bringing our self-serve closer to our high-touch and bringing high-touch closer to self-serve in terms of how we operate overall. It's a lot of hard work, I would say, first of all, basically, to bring both of these organizations together. And you have to be very deliberate around the points of intersection. And you have to make sure that these organizations don't consider themselves as competition. It's one product, one company. It's just two channels of how we are serving our customers. There are some things that we've done, which is you know, have the product marketing team, you know, that basically works across both of these functions and makes sure that, you know, they are bridging, you know, what we are hearing from the sales organization in terms of what directly customers need on the enterprise side and then what do we need, you know, on the self-serve side. You know, there's a full sort of process in terms of how the handoff happens. across the maturity of the account. It can start as a self-serve, it drives adoption, and once there's adoption, there's a hand raiser that happens, and then there's a sales rep that gets engaged and you go through the qualification process, and then you have an opportunity to expand the account. So we've over the years sort of architected and built the entire funnel and what the process is. And that's also sort of a key part of how all of this operates. But like I said, I think there are a few areas where we could further streamline how we operate and think of it as one single unit.

I imagine that is true for every company out there. Yes. One maybe final question before we get to our very exciting lightning round. What are some features that people could look forward to that are coming with Miro?

We recently, about a month ago, announced Miro AI. on the backdrop of all the amazing work that's happening around generative AI and large language models and stuff. So I think it was really, really exciting to see all of the community enthusiasm around sort of the use cases that we launched. So we're going to be taking it across the finish line and doing a general availability in the coming weeks and months. So I think that's one big thing and we'll be adding more capabilities there. Just today we actually announced a bunch of really deep enhancements and updates around how Miro can be used for team rituals and agile practices. So now you can actually do retrospectives in Miro where you can have a private mode where while Lenny is typing his feedback during a retrospective, nobody else can see it. And then one click you can reveal it. And I just saw some of the results of the feedback and it was rated as the number one feature people saw. There's also some deeper integrations in terms of bringing an entire program board from Jira to start to do dependency mapping inside of Miro in a fun and collaborative way to use this dependency mapping along with Program Board to start to do PI planning, program increment planning, which is essentially scrum of scrums or big room planning that's happening. So there's some really amazing capabilities that we've added there, which is on the backdrop of some of the updates we've made in terms of estimation of sprint story points, and so on and so forth. So now there's a whole plethora of capabilities and apps that are available as part of the platform that allow you to have your entire team conduct your team rituals in Miro and you can automate certain things, you can streamline things, you can do certain things in Async and then do the rest in synchronous ways. So I think that's been a big update as well. Amazing.

With that, we've reached our very exciting lightning round. I've got six questions for you. Are you ready? Yes.

All right, let's do it.

What are two or three books that you have recommended most to other people? One is I love this, When Breath.

Becomes Air by Paul Kalanithi. You know, it's like one of those really emotional books that at the end of it, you might have tears in your eyes. But really, really amazing. We talked about Frank Suitsman's Amp It Up and then Satya Nadella's Hit Refresh. And I think like philosophically, like some of the things things that we talked about today are inspirations that I found in some of these books.

What's a recent favorite movie or TV show?

Ted Lasso. I don't know if it's a recent one or not, but something- Season 2. Yeah, I've enjoyed a lot. I think it's a very positive and uplifting message. I think the performance is huge. It's humorous. The characters are well developed. So I think overall, It's a treat, at least for me to watch.

What's a favorite interview question you'd like to ask?

I actually ask a math problem. So for those of you who interviewed with me, I have this math problem, which is based on how Adobe created its first Creative Suite bundle. And I was actually part of the team that came up with the pricing and packaging for the first Creative Suite post acquisition of Macromedia. and it's a math problem that allows you very quickly to sort of figure out people in terms of their problem solving skills. And usually, I give that problem to people. I've given it to, I don't know, 700, 800 people. So I now have a very well established standard distribution of how long it takes for people, where do they get stuck, and where they've gotten stuck. For those people I've hired, what evidence do I have in terms of using that as a framework in terms of them being able to solve things. So that's my favorite question.

And so you're saying you've mapped back people that have done a certain way on the problem with their success, and you've kind of found that it's a good signal of their performance. Yes, not directly, but like yes, correlation and stuff.

That's amazing. That's like one of the biggest problems with interviewing.

You think you're asking all these amazing questions and it's such a good signal. You have no idea. no one goes back and is like, oh, this person sucked, this person didn't. So that's really cool. They have that much data on that one question. Two more questions for you. What's something relatively minor that you've changed in how you do product development that has had a tremendous impact on your team's ability to execute? We talked about some of that, like.

Sort of removing the roadblocks. I think like having this motto of like, you know, create customer value faster with high quality, just the simplicity of that and It's actually part of our evaluation rubric. It's part of how we measure ourselves and stuff. So I think just coming up with these simple concepts that you can rally the organization around and I think it's still work in progress, but something that I believe is leading to positive outcomes.

Final question, what's your favorite mirror template?

It's the FIFA World Cup. Actually, I was so fascinated with what was done. Yeah, it's the latest one. But I think there's a bunch of them in terms of retros as well. And I think like your template as well.

Amazing. We will link to all of those. Varun, this was amazing. Everything I expected and more. Your team is as interesting and unique as I thought. And I am excited for people to learn from you. And we're going to share a lot of links alongside this episode in the show notes. Two final questions. Where can folks find you online if they want to reach out and learn more? And how can listeners be useful to you?

Thank you, Lenny. It was a lot of fun. I enjoyed our interaction. And you know, you folks can find me online on LinkedIn. I think that's probably the best way to connect with me. And I think like in terms of, you know, one or two things I can ask everyone is that one is if you are an existing Miro user and you use the product for something interesting, I highly encourage you to contribute it as a template as part of Miraverse. There's a lot of folks who use that and we would love for you to contribute there. And the second thing is, I know a lot of product development teams, PMs and designers are big fans of you, Lenny. So those are also the users that use Miro. So if there's anything we could do to make the product better, if there's things that you feel like we can expand the platform into, we would love to hear from you and just reach out to me directly over LinkedIn, direct message, connect with me there. And yeah, and let us know. You're here to help us.

Amazing. Varun, thank you again for being here.

Thanks Lenny. Awesome.

Bye everyone. 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.