In an AI-enabled workflow, designers should accept that engineers can ship features without their direct oversight. Building robust systems and automations allows for good-enough initial versions, enabling designers to focus on higher-leverage problems instead of being a bottleneck.
The role of an expert designer in an AI-powered organization splits in two. They must build systems to harness the influx of competent work from non-designers, and also use AI to explore and create entirely new, previously impossible user experiences.
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.
As AI automates baseline design and coding work to a "7 out of 10" quality, the designer's role shifts. Instead of only executing craft, their unique value lies in applying deep "care" and intention to the user experience, focusing on the thoughtful details that AI misses.
To combat the isolating nature of AI work and share learnings, have AI agents operate in public Slack channels. This allows team members to passively observe how others prompt the AI, revealing new use cases and techniques in a natural, collaborative environment.
To innovate at the speed of AI, adopt the mindset that anything you build today could be made obsolete by next week's model release. This forces you to hold ideas loosely, constantly update your beliefs, and prioritize learning and exploration over perfection.
As AI automates UI generation, a designer's strategic value shifts. Instead of designing pixels, they will architect user experiences by defining which components are fixed for consistency (like a login flow) and which are flexible canvases for AI-driven personalization (like a user dashboard).
When working at the frontier of AI, designers must resist the urge to polish every detail. Since underlying models and product shapes change rapidly, time is better spent on future-looking conceptual problems that AI cannot yet solve, rather than on features with a short lifespan.
Successful organizational transformation with AI isn't driven by special "AI working groups." The key indicator of success is when the CEO and leadership team are hands-on with AI tools every day. This direct experience builds the necessary intuition to lead an AI-native team.
True "AI fluency" is less about prompt engineering and more about leveraging AI to automate administrative "noise" like scheduling user research. This frees up cognitive capacity for high-level systems thinking, like consolidating 15 single-purpose features into four multi-purpose ones.