Once AI flattens the speed advantage, community becomes the new moat — four practical directives from the PM behind Figma's community products.
The most important component: community ft. Alicia Kranjc (Figma) | Config 2026 · Alicia Kranjc
22 min total·Actually worth watching closely: ~4 min·2 must-watch clips
- 0:11 – 3:50Listen
Opening: build speed is no longer a moat
As AI and the tools improve, building software fast and at high quality is no longer a competitive advantage; beyond speed, taste and craft, you need a new source of differentiation.
The line between products people love and products people forget is shifting from building ability to community.
Purely spoken framing of how the industry is changing — nothing to watch, fine to listen to on a commute.▶ Jump to 0:11Speaker · Alicia Kranjc - 3:50 – 7:14Listen
Defining community, and how you know you got it right
Community is users' relationship with you and their relationship with each other, and most teams never think about designing it.
The sign you built the right community: users make your product better without permission and without being asked.
Mostly definitional — the argument comes through the language, not the screen.▶ Jump to 3:50Speaker · Alicia Kranjc - 7:14 – 10:50Listen
Identity: from user to part of something bigger
Figma's plugin ecosystem and engineers evangelizing Linear on their own show how a distinct identity builds a relationship users find very hard to give up.
The users who love your product are your best growth channel, because what they'd be giving up isn't a tool, it's an identity.
The examples unfold as stories, so the density is in the telling; the visuals add nothing on their own.▶ Jump to 7:14Speaker · Alicia Kranjc - 10:50 – 14:15Listen
Community is the truest product signal
User interviews and surveys have built-in limits; what users say to each other in Slack and on social media, without permission, is the real feedback.
To learn what people really think of your product, look at how users talk about you to each other, not at what they say to you.
A spoken argument about the bias in feedback channels — better heard than watched.▶ Jump to 10:50Speaker · Alicia Kranjc - 14:15 – 17:00Watch
Directives one and two: build connection in, gather people where they are
Connection can't be a side feature; it has to live inside everyday tools. Online challenges should be fun with a goal and a deadline, and offline you support what the community started rather than building it for them.
Adding badges to community profiles proves connection can be designed into the product itself — and that one engineer can carry it all the way to shipped.
This section holds the talk's only genuinely watch-worthy visual (the community profile badges at 860s); seeing the interface beats hearing it described.▶ Jump to 14:15Speaker · Alicia Kranjc - 17:00 – 20:43Listen
Directives three and four: embrace the unscalable, celebrate publicly
The instinct of a growing company is to systematize everything, but the most meaningful community moments come from unscalable, personal gestures — and you should celebrate the people building alongside you publicly, so they know they're seen.
Resist the instinct that everything must scale: the unscalable personal gesture is what people remember.
Mostly spoken examples like Notion's ambassador program — no live demos.▶ Jump to 17:00Speaker · Alicia Kranjc - 20:48 – 22:23Listen
Closing: three things you can start this week
Three immediately doable actions: meet five community members, celebrate one of them publicly, and brainstorm regularly about how your product can strengthen connection.
Community building doesn't wait on budget or headcount — this week it can start with meeting five people.
The action list is delivered verbally, short and tight; worth hearing straight through and writing the three down.▶ Jump to 20:48Speaker · Alicia Kranjc