Soleio’s guest is Rasmus Andersson: founding designer of Spotify, one of Figma’s first designers, co-creator of GraphQL, and creator of Inter. The part that stayed with me is his description of how Figma operated: one person on one problem for a year, sometimes binned at the end, while shipping something visible every month. He also makes a case that the production side of design — the part AI is eating fastest — was never actually the hard part. What’s left is the intention. The other link in this section is Soleio’s talk on the geometry of luck, making this pair worth watching together.

“Luck isn’t something that you have. It’s something that you leave behind.” Soleio — designer of the Like button and angel investor in Figma, Cursor, and Framer — delivered this as the closing line of his Tokyo Design Forum talk, and it’s the kind of sentence that reorganizes how you think about a career. The talk, now archived by The Forum Library, reframes luck as a generative force you shape through how you live and work, not a resource you accumulate.

Matt Colyer, Figma’s director of product management for developers, makes the case on Dan Shipper’s AI & I podcast that the SaaS apocalypse narrative has it exactly backwards. He’s been running his own agents for two years and is buying more software subscriptions than ever, because shipping and maintaining a personal agent teaches you fast why people pay for someone else to run it. The more interesting half is about design specifically: chat is linear, which makes it good at converging on a single direction but terrible at generating lots of options. Figma’s on-canvas agent is a first attempt at the divergent side — letting you branch frames in different directions, then bring in a convergent agent to cluster them. He also walks through how the MCP server closes the code-to-design loop, and why ​“review” has quietly become the biggest bottleneck in AI-assisted product work.

Designer Fund surveyed 900+ designers across 60+ countries and conducted 20+ interviews with leaders from Anthropic, Framer, Linear, Notion, Shopify, Sierra, and Stripe. The headline number: half of respondents have shipped AI-generated code to production, and designers are now using double the AI tools they were a year ago. Designers are quietly absorbing PM and engineering work, but hiring loops, performance reviews, and team shapes haven’t caught up.

Tom Scott breaks down how the Staff role differs from Senior in kind, not degree. Senior designers execute well-defined features. Staff designers question whether the work should happen at all, spot where teams are solving the same problem in three different ways, and turn that into reusable patterns. Useful if you’re trying to figure out which of your current habits actually point toward Staff, and which are just more Senior.

Daily curated design news and resources for product designers, design engineers, and PMs — read all week, then get the best links in your inbox every Tuesday.

Config 2026 lands June 24–25 at Moscone. The agenda confirms the obvious: this year is about AI workflows and design systems built for them. Build your schedule now — last year the best talks filled up fast.

The May edition is mostly a demo of Figma’s MCP server, with Amy Lima and Anthony DiSpezio walking through three workflows: code-to-canvas import of a vibe-coded prototype, round-tripping a dark mode so variables stay in sync between code and Figma, and using the pre-installed figma-use-scale skill to generate first-pass directions on a production dashboard. The closing update reel includes vector editing up to 10x faster, memory warnings down 92%, macOS eyedropper now samples anywhere on screen, FigJam MCP can read and write boards (ERDs, architecture diagrams), Make Kit packages your design system’s code for Figma Make, and Weave gets a timeline for video.

Luis Ouriach makes the case against single-number design system adoption metrics. His argument: one number collapses three things that should stay separate, across artifacts (a brand token and a complex data table component need different definitions of ​“used well”), surfaces (a logged-in dashboard component has no business on a sign-up screen), and people (a marketer, a senior product designer, and a front-end engineer all want different things from the same system). The throughline is that compliance with a benchmark is not the same as value, and most design system dashboards are quietly measuring the wrong one.