Smithery is now a part of Arcade.dev! Read more in our announcement here
Strategic guidance for design-focused founders and product leaders based on Dylan Field's experience scaling Figma from a WebGL experiment to an 8-product company with 1700 employees...
Strategic insights from Figma's founder on building design companies, recognizing product-market pull, and positioning design in the AI era.
Design becomes the primary differentiator as AI makes development easier. Designers must step into founder and leadership roles to capture this value.
Product-market fit is necessary but insufficient. Look for product-market pull:
| Signal | Product-Market Fit | Product-Market Pull |
|---|---|---|
| User engagement | Users find value | Users are obsessive |
| Feedback tone | "This is useful" | "I see where this is going" |
| Behavior | Regular usage | Users pull features out of you |
| Vision | Solves current problem | Users buy into future vision |
Application: When evaluating early traction, passionate negative feedback ("this isn't ready yet") may indicate pull—users care enough to be frustrated because they see the potential.
Frame decisions by downside and upside:
Downside (worst case): Is this acceptable?
→ Working with smart people, learning, returning to previous state
Upside (best case): Is this significant?
→ Building something meaningful at scale
If downside is acceptable and upside is significant → proceed
1. Identify what you're doing most
2. Get someone else to help with it
3. Find resources if needed
4. Repeat
Apply this continuously as you scale. Your role should constantly evolve.
When users develop workarounds or emergent behaviors in your product:
Example: FigJam emerged from observing how users were using Figma for brainstorming.
When to use: Seeking early users, mentorship, or expert feedback.
Key insight: People respond more than you expect. Dylan credits cold emails for critical early relationships.
Default bias: Launch and charge money faster than feels comfortable.
Figma's mistake: Waited 5 years to monetize. Don't repeat this.
If asking "Should we launch yet?"
→ Probably yes
If asking "Should we start charging?"
→ Probably yes
If asking "Is the product ready?"
→ Ship it, get feedback, iterate
Exception: Deep technical infrastructure (like WebGL rendering engine) may require longer development before launch.
Maximum cadence: 1-3 months
When presented with epic roadmap:
1. Challenge any item planned beyond 3 months
2. Ask: "What can we ship in the next month?"
3. Slim down to what delivers value fastest
4. Reassess after each cycle
Anti-pattern: Multi-year roadmaps with detailed specifications. The market and technology change too fast.
Combine multiple signals to understand user needs:
1. Support requests → What's broken or confusing
2. Qualitative interviews → Deep context and emotion
3. User observation → What they do vs what they say
4. Data analysis → Patterns at scale
5. Social media signals → Unfiltered reactions
No single signal is sufficient. Synthesize across all channels.
As AI makes development faster and easier:
Implication: Invest in design capabilities. They compound in value as AI improves.
Key practice: Embed designers in AI research teams.
Traditional: Researchers build → Designers polish UI
Better: Designers contribute to model evals
Why: Designers understand end users better than researchers.
They can evaluate whether outputs actually serve user needs.
We are in the "MS-DOS era" of AI:
Opportunity: Design the next paradigm of AI interaction.
Reframe rejection:
- Not: "They said no, my idea is bad"
- Instead: "They said no, what data can I extract?"
Mine rejection for:
- Specific objections to address
- Market timing signals
- Positioning adjustments
Figma would not exist if they had stopped at 6 months.
Before starting:
1. Calculate minimum runway needed
2. Add buffer for pivots and exploration
3. Secure that runway before starting
4. Protect the time—don't let arbitrary deadlines kill good ideas
When successful people make decisions you don't understand:
Default assumption: You're missing something
Not: They're making a mistake
Action: Ask questions to understand their reasoning
| Term | Definition |
|---|---|
| WebGL | JavaScript API for GPU-accelerated 2D/3D graphics in browsers |
| WebGPU | WebGL's successor with more modern GPU access |
| MCP Server | Model Context Protocol—allows AI tools to access external data/designs |
