Best reads for PMs & Designers
Get 5 personalized best reads each week, with TL;DR and clear next steps.
One free email every Tuesday · No sponsored posts · See a sample email
Topics
Sources
First seen 13 May 2026
This week's episode is with Nev Flynn and we're doing a deep dive into how he's bringing artful expression into enterprise design as the Head of Design at ElevenLabs. Some highlights: Inside look at ElevenLabs internal brand tools Why Nev is prioritizing specialists over generalists What Nev looks for when evaluating a design portfolio How they built a shader orb system for 40 million voices What happens when non-designers are designing with AI How the team is making their design system agent-native a lot more
Ben's Bitesbensbites.com · 11 September 2026 · 2 posts · not counted as a party
Ben’s session #6
Sidebar.iojudgmentkit.ai · 4 September 2026 · not counted as a party
The judgment layer for AI-generated UI Stop AI from building the wrong interface. A design system tells an agent how interface elements should look and behave. JudgmentKit tells it which interface the user’s work requires, what should stay hidden, and what must be repaired. Use JudgmentKit’s design system—or bring your own. Judgment before components A design system can make the wrong interface consistent. JudgmentKit prevents that mistake before the components are composed. Traditional design system Defines how interface elements look, behave, and remain consistent. JudgmentKit Defines what the interface must help someone do, decide, and understand. Together JudgmentKit uses the design system you choose and tells the agent what to repair. Failure-to-repair preview First drafts should start from the work, not from available internals. Failure The screen follows the system, not the work.Generated interfaces often mirror available internals instead of the activity a person is trying to complete. Judgment The activity is named before the UI.JudgmentKit asks what the user is doing, what decision matters,
commandline.microsoft.comcommandline.microsoft.com · 3 September 2026
When I returned from maternity leave in March 2026, I felt like I had entered an alternate universe. I rejoined a newly restructured organization, moved to a different team, and was managing a new portfolio of products and people within Azure Developer Services. I expected to spend time learning a new product space, but I didn’t expect to spend time relearning what it means to be a designer. The teams around me were already using GitHub Copilot and agents in their daily work. Designers on my team were moving beyond making static mockups and clickable prototypes in Figma. Some were contributing directly to production code using VS Code or the GitHub Copilot CLI. The traditional boundary between design and engineering seemed more blurred than ever. Even though I had spent portions of my leave experimenting with AI, I was still blown away by how quickly things had changed in such a short period of time. The same forces that were helping teams execute faster were also making it harder to achieve consistency across surfaces. As I acclimated to my new surroundings, I found myself asking a lot of obvious questions (my kinder rebrand of “
pipshea.netpipshea.net · 2 September 2026
Product resource · Agentic IDEs · 2026 A remix of the 2011 Critical Engineering Manifesto for Design Engineers. Explainer In 2011, Julian Oliver, Gordan Savičić and Danja Vasiliev published the Critical Engineering Manifesto, urging engineers to treat the technologies we depend upon as objects of study, suspicion, and intervention. Fifteen years later, I’ve remixed their manifesto for the Critical Design Engineer: a person who wishes to critically inhabit the space between software design and engineering. I have created this manifesto as a set of guardrails for myself as I navigate agentic engineering capabilities as a software designer. The structure, numbering, and cadence belong to Oliver, Savičić and Vasiliev. Where possible, I have tried to maintain kernels of their ideas in each statement. The manifesto’s source text lives in version control, published as a public Github Gist, under the same GNU Free Documentation License as the original. It carries a commit history, an author signature, and an open invitation to fork. Manifesto 0. The Critical Design Engineer considers code to be a design material, and works it directly. 1. The Criti
Figma blogfigma.com · 2 September 2026 · 2 posts
The Coinbase Design System (CDS) team supports the largest U.S. cryptocurrency exchange across mobile and web for consumers and businesses. They’ve scaled a design system for quality, consistency, and accessibility—but what needs to change when its primary users shift from engineers to agents? Technical Lead Erich Kuerschner saw an opportunity to improve agent output with the Figma MCP serverThe TL;DR on MCP: Why context matters and how to put it to workFigma’s MCP server brings your design decisions into the tools where code gets written—so what gets built actually matches what was designed. Here’s what that unlocks for everyone who builds products., Code ConnectBetter code, fewer tokens: The benefits of Code Connect in MCPWhen going from design to code, agents lack the context of your production components. With Code Connect in Figma’s MCP, they get that context. We measured its impact on token usage, task duration, and code quality., and CDS’ own agent skills. To test this, he ran an evaluation and found that on average, Code Connect cut costs by 22.5% and task completion time by about 22%.“The tests showed us