01 / recommendation
Likes OKRs.
“I love how OKRs could just be anything, could be every six months, could have objectives, could have key results.”
- Speaker
- Lenny Rachitsky
- Publisher
- Lenny's Podcast
Lenny's Podcast / episode intelligence
Speakers in the public record
Claim mix
Evidence policy
Every row below preserves an exact excerpt. Identified speakers are linked; unresolved voices are labeled and excluded from people counts.
Claim ledger
32 published records
01 / recommendation
“I love how OKRs could just be anything, could be every six months, could have objectives, could have key results.”
02 / belief
“I think in terms of 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 Miroverse.”
03 / belief
“" I think once people 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.”
04 / belief
“Mironeers. 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 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.”
05 / belief
“There are a few learnings and I would say maybe this is one area where we are working on how we could be doing better in terms of bringing ourselves 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.”
06 / belief
“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.”
07 / belief
“Like we describe, it's the AMPED 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.”
08 / belief
“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.”
09 / belief
“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.”
10 / belief
“We have multiple offices in US, four different offices, and then multiple hubs in Europe as well, and presence in AsiaPac as well. I think by now we have a global footprint, yeah.”
11 / commitment
“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.”
12 / belief
“I think you can take that philosophy to a bunch of things in life, but I'm going to take the lens of products, which is my core philosophy is 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.”
13 / belief
“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.”
14 / belief
“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 a key part of lighting the fire, if you will, the proverbial way people start to talk about the product.”
15 / belief
“I think the other accelerant in all of this is the templates that we have, in particular the role that Miroverse plays in all of this.”
16 / belief
“I would say with most things 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.”
17 / belief
“The reason for that is that if you consider yourself as an innovation-centric company and you believe that 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 my experience, in terms of who ends up being more successful versus not.”
18 / belief
“I think there's maybe one more pearl we can actually thread into the needle right here.”
19 / belief
“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.”
20 / belief
“I think having this motto of great 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.”
21 / belief
“" I would say that's an area where we're still working on and more recently we put more focus and energy and there's a product manager who's now leading that particular charter.”
22 / belief
“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.”
23 / preference
“I'll talk a little bit around how we are structured in the product organization so that it's a cross-functional perspective 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.”
24 / evaluation
“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.”
25 / evaluation
“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.”
26 / preference
“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.”
27 / recommendation
“I would say 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, we could do better on some of those dimensions, but all of this data is available and we provided it openly and folks can benchmark themselves against that.”
28 / commitment
“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% position level, which means that 80% of the things that we claim to be on the roadmap will get done.”
29 / evaluation
“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 cells of organizational challenges, they could be priority challenges and so on and so forth.”
30 / preference
“I really like this discussion, especially because often the advice is, "Don't worry about the competition, just focus on the customer, it's going to be fine.”
31 / evaluation
“Next day in the morning one of the engineers from this core team that was exhibiting at Miro Connect looks at the poll 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.”
32 / evaluation
“I think 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.”