![]() ![]() Having fun with product demos and making bug reports less painful Just like that, they have something written and suddenly claap replaced this meeting. The decision maker either adds a comment at the end with "go/build" or they write their feedback. While recording, teams give stakeholders a walk-through with Figma where they explain their plan, show the hedge cases and ask for a decision. With Claap, they completely replaced this decision-making meeting. So sometimes we were stuck for a week just because we didn't get the go from the right person. And the people who give the go are often people who have a crazy agenda. Before (Claap) it was a bit of a hassle because we needed to bring people together. Both meetings require communicating the plan, collecting feedback, and deciding on the next steps. And then they hold a second design review that’s really a decision-making meeting that they call the “go build”. Here they exchange ideas and often they have several designers participating too. At Kavak, they used to have two meetings for this: the internal design review with the designer, the product manager, and the tech leader. The first use case Timothée tested was with design reviews. People quickly saw the benefits of time-saving, structuring of thoughts, and the ability to open mini threads right in the video, instead of having a conversation just on Slack. Everyone that received one of his claaps said to him “that’s great. I want to structure it a bit.Ĭlaap expanded very organically in the Product org. Before recording their claap, people will say to themselves: "Wait, I don't know who is going to see this video. The magic? Having time to think, instead of talking on the spot. Timothée quickly found that what would have taken half an hour in a meeting to be communicated, with a claap it took 5 minutes. Since people are very comfortable with the writing exercise, a claap is more interactive, more intuitive and at the same time, it forces the person to structure their thoughts. The power of asynchronous video collaboration I thought Claap could be another way to do asynchronous work. He first tested with one-pagers, but soon realized that not everyone had this mindset, to write a document and pass it on. Timothée knew he needed to find a way to solve this, to limit synchronous communication a bit. ![]() This resulted in six to seven hours of meetings per day, a big problem for Product teams that need at least 3 to 4 hours a day of deep focus. As soon as someone has a project on which they want to move forward, they will send you a Slack, or they will book a meeting. It’s horrible because you’re constantly switching contexts. The two big product issues we have today that are specific to Kavak are internationalization and how do you change the habits of a company that already has 8,000 employees.Īs Timothee explained to us, opening in new markets with a Fintech product is a balancing act: you want to build a global product – to benefit from economies of scale – while respecting local laws.Ī third underlying problem that amplified the first two was the instant culture: everything was going through Slack and Meetings. So we sat down with Timothee Trichet, Kavak’s Head of Product, to understand the challenges of this rapid growth. Just in the tech team, they are around 1,000 people. They expanded very quickly from a car reseller solution to a company that now offers additional services like car maintenance or financing plans for buyers.įounded in 2016, Kavak is now present in seven countries with an impressive 8,000 workforce. Valued at almost US$ 9 billion, they are also the first Unicorn Company in the history of Mexico. Kavak is one of the most successful companies in Latin America.
0 Comments
Leave a Reply. |