High Signal Podcasts Evidence ledger
Method
Browse
← Back to evidence

Evidence receipt / recommendation

Published · transcript-backed

Mentions personal use of FigJam.

21 Apr 2024 Lenny's Podcast Vision, conviction, and hype: How to build 0 to 1 inside a company | Mihika Kapoor (Product at Figma)

“And one thing that happened during one of the meetings was I literally walked them through, this meeting, this is how I use FigJam. In this meeting, this is how I use FigJam. In this meeting, this is how I use FigJam, blah, blah, blah. And what that resulted in was I actually made a Loom video walking through my weekend FigJam, that our sales team later distributed to a bunch of companies to inspire them as to like, "Hey, not only can you use FigJam for this, you can use Fig Jam for X, Y, Z.”

— Mihika Kapoor

Source trail

Everything needed to verify it.

Speaker
Mihika Kapoor
Attribution
Verified speaker
Claim type
recommendation
Recorded
21 Apr 2024
Publisher
Lenny's Podcast

Transcript context

…Awesome. Let's go actually one layer deeper here. So you're talking to people all the time about FigJam, "Aren't you using FigJam? What do you think of Figma? What do think of this?" You're hopping on sales calls. What do you do with what you hear? Is there kind of an operational approach where you... Do you just put in your head and sticks in your head and rolls around and comes up, things emerge? Do you have a place you put these insights, you're learning? Are you putting post-its in FigJam, for example. And then on the sales side, do you have a cadence where I'm going to join a sales call once a week, here's a person I love in sales, I'm going to try to join all the calls. How do you actually operationalize these things? The insights get operationalized in a number of ways. So first is... So yeah, let's continue using FigJam as an example. I think, like I mentioned, Figma as a company uses FigJam for everything. Multiple FigJam files are made per day, per meeting, et cetera. We had this initial situation where people outside of the company were mostly using FigJam for brainstorms. And so as we were scaling our FigJam sales team, I sort of set up a recurring cadence with the folks in our sales team in order to understand like, "Okay, what are you guys hearing?" And then I would share what was coming, and then I would use their input as signal as to what should be prioritized or deprioritized on the roadmap. And they would use my signal to understand what were the various use cases that they could be pushing with the customers. And one thing that happened during one of the meetings was I literally walked them through, this meeting, this is how I use FigJam. In this meeting, this is how I use FigJam. In this meeting, this is how I use FigJam, blah, blah, blah. And what that resulted in was I actually made a Loom video walking through my weekend FigJam, that our sales team later distributed to a bunch of companies to inspire them as to like, "Hey, not only can you use FigJam for this, you can use Fig Jam for X, Y, Z. You can use it for your team pickups. You can use it for your retros. You can use it for planning your mom's birthday party. You can use it for planning your all hands. You can use it for sketching out the contents of what's going to go into your next deck," so on and so forth. And so it basically manifests in two way, the first is having it inform the prioritization of your product roadmap. And then the second is what ideally creating artifacts that the sales team can use to evangelize the things that you are seeing and the stepping stones to that vision that you creating. And then the last thing is that sometimes the conversations aren't immediately actionable, right? Sometimes the sales team has an insight or has a request that is just objectively not feasible because the team has too much on its plate. Conversely, sometimes the team might have a suggestion for something that might be pitched to sales folks that's too early given the stage of the conversation. And for that, we basically have... We store it in Asana basically. We have this integration, which many companies might have, which is like Slack integration, where you can react with an Asana emoji, and then any piece of feedback that comes in from sales or from the rest of the company gets turned into a task in your backlog, and then you do a weekly grooming of that. Amazing. Cool. Very tactical and useful. This episode is brought to you by Vanta. When it comes to ensuring your company has top-notch security practices, things get complicated fast. Now you can assess risks, secure the trust of your customers, and automate compliance for SOC 2, ISO 27001, HIPAA, and more with a single platform Vanta. Vanta's market leading trust management platform, helps you continuously monitor compliance alongside reporting and tracking risks. Plus, you can save hours by completing security questionnaires with Vanta AI. Join thousands of global companies that use Vanta to automate evidence collection, unify risk management, and streamline security reviews. Get $1,000 off Vanta when you go to vanta.com/Lenny. That's V-A-N-T-A.com/Lenny. Another thread that I've noticed, and I wasn't planning to go in this direction, but you just care so deeply about the things you work on. You actually really, really love it and want it to be incredibly successful and feels like you're just always thinking about it. Reminding me of this quote from your colleague Karl, they shared that, "It feels like you care deeply, which makes me care deeply. Who wants to be led by someone who doesn't care about what they're building?" It feels like that's an important part of the way you work and think. Is there anything you want to say about that?…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.

Named in this claim

Books, apps, tools, and people.

Search evidence