Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

To fully leverage AI tools, designers need direct access to production code. This proximity to the end product and user data is crucial for meaningful influence and building effective solutions, moving beyond traditional, gatekept workflows and risky sandboxed environments.

Related Insights

The traditional design-to-engineering handoff is plagued by tedious pixel-pushing. As AI coding tools empower designers to make visual code changes themselves, they will reject this inefficient back-and-forth, fundamentally changing team workflows.

Instead of throwing away a designer's "good-looking but poorly-architected" prototype, use an AI agent as a translation layer. Give it the designer's styled code and the engineer's performant code, and instruct it to apply the styling to the functional version.

Prototyping directly in the production environment makes high-quality interactions achievable without extensive resources. This dissolves the traditional design dilemma of sacrificing quality for speed, allowing teams to build better products faster.

To keep pace with AI development, the barrier between design and engineering must fall. Intercom made it a non-negotiable job requirement for every product designer to ship code to production. This empowers them to fix UI bugs directly and accelerates the entire development cycle.

Designers use AI tools like Claude Code to connect directly to production data sets. This allows them to build realistic, interactive prototypes that challenge preconceived technical limitations and demonstrate the viability of new product directions without deep engineering support.

Connecting to a design system is insufficient. AI design tools gain true power by using the entire production codebase as context. This leverages years of embedded decisions, patterns, and "tribal knowledge" that design systems alone cannot capture.

AI's productivity gains mean that on a lean, early-stage team, there is little room for purely specialized roles. According to founder Drew Wilson, every team member, including designers, must be able to contribute directly to the codebase. The traditional "design artifact" workflow is too slow.

With AI coding assistants, the barriers to shipping software are eroding. At Ramp, designers and customer support agents are now shipping code to production. This suggests a future where the traditional, siloed Engineering, Product, and Design (EPD) team structure becomes obsolete.

AI tooling is creating a 'fluid model' where any employee, regardless of role, can potentially ship code. This dramatically expands the design system team's responsibility, which must now create tooling and guardrails to support a much broader and less technical user base across the entire organization.

Designers need to get into code faster not just for prototyping, but because the AI model is an active participant in the user experience. You cannot fully design the user's interaction without directly understanding how this non-human "third party" behaves, responds, and affects the outcome.