AI Won't Take Your Job - It Will Redefine It: What Dylan Field Wants Product Teams To Do Now
Figma CEO Dylan Field is clear: AI isn't here to replace people. It's here to remove the dull work so teams can focus on the hard problems and the customers who need them.
On a recent appearance on Lenny's Podcast, Field noted that many professionals already see this shift. The fear is loud, but the data points in a different direction.
What the Data Says
Figma's September survey of 1,199 professionals - designers, PMs, developers, researchers, data specialists, and marketers - shows a pattern worth your attention. Nearly 60% said AI helps them spend more time on high-value work by cutting repetitive tasks. About 70% reported feeling more productive after adding AI to their workflow.
Field's takeaway: automation is stripping the drudgery, not the role. Teams keep the thinking and taste. Software handles the repetitive lifts.
Why This Matters for Product Development
- Speed without burning out your team: AI drafts, you direct.
- More shots on goal: faster iteration, more experiments, quicker feedback cycles.
- Wider collaboration: non-designers and non-coders contribute through natural-language tools.
- Higher bar for taste and judgment: human choices become the differentiator.
Figma's Lens: Keep the Human in the Loop
Figma has added generative features that spin up design variations, summarize feedback, and automate routine steps. The intent is simple: give designers and product teams more time to think, test, and decide.
As Field puts it, "There's a need for designers to lead the charge, and AI will only get you so far." Concept, emotion, and product sense stay human.
Practical Playbook for Product Leaders
- Audit workflows: Map your design, research, planning, and QA steps. Circle the repeatable parts (handoffs, summaries, first drafts, test case generation).
- Set use rules: Define where AI assists vs. where humans decide. Require human review for UX copy, data claims, and user-facing changes.
- Integrate in the stack:
- Design: generate variants, component docs, and usability summaries.
- PM: draft PRDs, trim meetings with auto-notes, synthesize research.
- Eng: scaffold tests, comment code, write migration plans from specs.
- Research: cluster feedback, propose follow-up questions, tag insights.
- Measure what matters: Track cycle time, experiments per quarter, user-facing fixes per week, and time spent on deep work.
- Upskill the team: Create short playbooks and internal demos. Reward people who improve the system, not just output.
- Pilot, then scale: Start with one squad for 30 days. Keep what moves the needle, cut what adds overhead.
- Compliance and quality: Document prompts, data sources, and review steps. Add red-team checks for bias, privacy, and security.
Org Shifts You Should Expect
- PMs act as editors of AI drafts, owning intent, constraints, and prioritization.
- Designers move from pushing pixels to directing systems - components, tokens, and flows - with more time for concept and craft.
- Developers spend less time on boilerplate and more on architecture, integration, and performance.
- New responsibilities: prompt patterns, data governance, review gates, and experiment ops.
Risk Controls That Don't Slow You Down
- Use non-production data for ideation and drafts. Keep secrets out of prompts.
- Mandate human review for anything public or user-facing.
- Log AI-assisted changes like code commits. Make review easy to audit.
- Adopt a simple risk framework for your org size. If you need a reference, see the NIST AI Risk Management Framework.
A 90-Day Plan for Product Teams
- Days 1-30: Pick two use cases (e.g., PRD first drafts, usability summaries). Set quality bars and a review checklist.
- Days 31-60: Expand to one more team. Start tracking cycle time, experiment count, and rework rate.
- Days 61-90: Trim what doesn't help. Bake winning patterns into templates, components, and SOPs.
The Mindset Shift
Field's core point: "This is not coming for you." It's an assist, and your advantage comes from how fast you learn to use it.
"You can see it as a path for you to learn and grow, and explore the world and human consciousness." The teams that treat AI as a partner will ship more, fix faster, and keep the parts of the job that make them proud.
If your org needs structured upskilling for product roles, explore curated options by job here: AI courses by job.
Your membership also unlocks:
