What can designers learn from how developers are using agents today?


Developers are the leading indicator here. In Anthropic's 2025 data, software developers made up 3% of U.S. workers but nearly 40% of all Claude conversations, and a year later software engineering accounted for roughly 50% of AI agent deployments. Whatever developers are doing with agents now, design is likely to follow.

So what have they been doing? Mostly watching their role move up a level. First humans wrote code, then machines suggested completions, then people chatted with models, then agents got tools, and then came orchestration, where a coordinator agent delegates to sub-agents and you review and approve the plan. Designers should expect the same shift: less time producing every artifact by hand, more time directing, steering, and judging the output.

Developers also figured out early that speed without process changes just makes a mess faster. Amazon's Joe Magerramov described how developers moving at 200 mph had to rethink a lot of their process to keep quality high while shipping 100 commits a day instead of 10. If you simply bolt an agent onto your existing design workflow, you'll miss most of the benefit.

Next, work in the actual medium. One product manager I talk with now prompts agents on a branch of his company's production codebase instead of writing a PRD (product requirements document), giving the whole team something they can actually use. Designers can work iteratively with production code too, and that hands-on work creates better designers who handle issues that used to get left for developers. You can even fix those "small" production issues you could never get engineering resources for. And watching an agent work through its steps teaches you a lot about how a system works, even if you never use the code it writes.

Finally, developers learned that agents are only as good as the context you give them. For designers, that context is the design system. When agents write most of the code, the design system can become a steering layer that keeps every update aligned with brand, design, and development guidelines. That also fixes the old problem of the design system describing a product that no longer exists.

Put all of this together and you get a workflow where designers, developers, and PMs all build and ship in parallel with agents, and developers review the work. My advice: get your hands into the real codebase, invest in the context your agents work from, and spend your time reviewing and steering.