Everything Mihika Kapoor said on any show that made the record, most notable first. Each card names its show and opens the statement there.
Kapoor: Figma prototypes before greenlighting projects rather than relying on TAM
“We lean heavily into designing and prototyping even before a project gets a green light. So I think that's something that's really unique about Figma is normally you will like talk about like the market space or the opportunity or the sizing and then decide to…”
Kapoor: AI products fail users by optimizing for demos over interactive control
“In my mind, one of the biggest shortcomings of AI, the way that a lot of people are building it today is that it's like optimized for the demo. Or optimized for the tweet, right? And it's basically this situation where, like, I think about it as, like, in my m…”
Kapoor: Exposing early products before they seem ready accelerates learning
“I think what you find is that if you push your product to get visibility, maybe even beyond what like the current stage of product development merits, is that you have really incredible learnings. Because the more that you can put your product in front of peop…”
Kapoor: Disagreements over product strategy stem entirely from differing assumptions
“When two people disagree about product strategy, it is because they have different assumptions. Because if you have the same assumptions, Like, there is no reason why a person should think, like, we should do X versus we should do Y.”
Kapoor: Product managers should lean into their individual spikes and strengths
“And so I think that, you know, based on how you fell into it, you might have different spikes and different strengths and leaning into those is really important. For the other things, it's also, of course, important to have like a sort of growth mindset and to…”
Kapoor: Anchoring teams on a singular vision makes pivots feel like progress
“It is really important to create a vision that you believe in, that your team believes in, and that your company believes in. Because the reality of the product development cycle is that it's so messy. It's so chaotic. You're going to have, you know, extreme h…”
Kapoor: Describing product ideas in words is less compelling than visual proof points
“You know, you kind of find that, or I've found, that words will only get you so far. So when I put together a vision with my team at Figma, it's all about, like, not just your traditional, like, okay, here are pain points, and then here are solutions, and then…”
Kapoor: Product vision presentations require a single shared artifact across disciplines
“When you're actually presenting a vision, one of the most important things is that there is, like, a single artifact that the team is creating together, so I think, like, a common occurrence is to kind of have, like, the research readout, followed by the desig…”
Kapoor: Limiting hackathons to engineers is a massive mistake
“I think that most people think that like, oh, hackathons are only a time for engineers to build. And I think that that's one of the biggest mistakes ever. I think that anyone can have an idea and can literally, what I did was like walk around the New York offi…”
Kapoor: Proposing wrong ideas accelerates reaching the right solution
“Putting out an idea, even if it's totally wrong, is a much better catalyst for getting to a good solution, because people are much more likely to react to an idea than to nothing.”
Kapoor: Product managers must explicitly state their confidence level on opinions
“If you are a PM who has strong opinions is to be very direct about how much you care about your opinions. So like now I'll do this thing. Where I'll be like, oh, I think we should do this, but I feel like medium confidence on it, so if you feel stronger, like,…”
Kapoor: Solicit feedback from coworkers before delivering your own
“If you have feedback to give someone else, I think you can start by asking, hey, do you have feedback from me? And kind of taking the feedback first. So then that person feels like, okay, like maybe I have my way of seeing this situation. Like, let me communic…”
Kapoor: Interviewing non-users yields more valuable insights than interviewing existing users
“Something that I find incredibly useful Is to not just ask users of your product what they think about your product, but to ask non-users about your product why they are not using your product. And actually, I think that those are the most insightful conversat…”
Kapoor: Founder-market fit accelerates product development by serving as user litmus test
“I think this is also why like founder market fit at startups is so important is because like to the extent that you can use yourself as a litmus test for what user needs there are, that's helps you move really fast in the product development cycle.”
Kapoor: Internal founders cannot make unilateral executive decisions
“There are things that are harder inside of an existing company, right? It's like harder to take an executive decision. You actually cannot take an executive decision. You need to receive buy-in on every single decision that you make. Sometimes it's like harder…”
Kapoor: Airbnb and Pinterest led tech by differentiating on interface design
“Companies like Airbnb and Pinterest
Were leading an industry, and they were leading not just because they, like, built technology and made it accessible, but because they were really using the interface layer to differentiate.”
Kapoor: Teams should hire spiky individuals to make the team well-rounded
“As you scale your team it's really important to be self-aware of what those blind spots are and to sort of hire for that because at a team level, you want individuals to be spiky and you want team to be well-rounded.”
Kapoor: Figma's Multi-edit, JamBot, and widgets all originated as hackathon projects
“At the company, you know, some of our most monumental launches have come out of hackathons and have come out of bottoms up projects. So like recently this week, we had a launch of multi-edit, which was like a long clamor for a feature where folks can, you know…”
Kapoor: 0-to-1 success requires optimism bordering on delusion
“I think the key to being successful at zero to one is to honestly have optimism that borders on delusion. You need to have insane almost like reality distortion field where You don't hear the word no, or at the very least, you translate it into a not yet.”
Kapoor: Figma runs nearly every internal workflow and meeting inside FigJam
“We use Figma the way that everyone uses Figma, but we use FigJam on steroids. Like, every single activity in this company is done in FigJam. It's like, our product reviews are in there, our Gantt charts are in there, our bug bashes are in there, like, every si…”
Kapoor: Meta distills the PM role into product sense and execution
“Meta basically distilled the product role into two core capabilities. One was product sense and one was execution.”
Kapoor: Internal founding offers distribution, platform leverage, and lower risk
“Like the reasons why you would found inside of an existing company is if you think that there is a distribution advantage that you want to take advantage of, if there is a technical or platform advantage that you want to take advantage of, or there's also like…”
Kapoor: Figma maintains a multi-month internal dogfooding process before launching products
“I think something that's very unique about Figma as compared to other companies is we have a multi-month plus long staging our dogfooding process.”
Kapoor: Pika succeeds by letting users manipulate generated video outputs
“I think Pika is doing a really great job of, like, not just investing in the foundational video models, But also giving you the ability to manipulate the output.”