Talk to designers about AI and the energy in the room is immediate. Everyone has tried something. Everyone has an opinion. The conversation moves fast.

Watch the same designers at work and the picture is different.

The workflow is largely unchanged. AI exists at the edges. A prompt to tighten an email. A rewrite to clean up a brief. ChatGPT used the way autocomplete used to be. The actual design work, the research synthesis, the ideation, the problem framing, the prototyping decisions, stays untouched.

This is not about awareness. Most designers know what AI can do. The reluctance runs deeper.

The unspoken calculation

There is a conversation happening privately among designers that almost never surfaces in public.

If I start using AI for solutioning, will my employer think they need fewer of us? If I deliver faster, will the expectation permanently shift? If I am honest about how I am working, does that make me easier to replace or harder to justify?

These are not irrational fears. They are reasonable readings of how organisations have historically responded to efficiency gains. The person who finds a faster way does not always get credit for the time saved. Sometimes they get a larger brief.

So the safer move, quietly, is to keep the old pace visible. Use AI where no one can see it. Or do not use it at all.

This is the shape of real reluctance. Not scepticism about the technology. A calculated decision to protect what you have by not showing what you can do.

Shallow adoption as a middle ground

For designers who do engage, most land in the comfortable shallow end. GPT for emails. Figma Make for a transition that a clear mental model could resolve in two minutes. MCP iterations in Figma for a colour decision that a trained eye could settle in seconds.

The shallow end feels safe because nothing fundamental has to change. The process stays intact. The deliverables look the same.

What it misses is where the actual value lives. Research synthesis where AI compresses hours of tagging into a starting framework you then interrogate. Ideation at the brief stage where you stress-test ten directions before opening Figma. Problem framing where a well-loaded prompt surfaces a perspective you had not considered.

Some designers swing to the opposite extreme. Rather than exploring AI as a thinking partner, they outsource the thinking entirely. Research synthesis gets delegated end to end. Whatever Claude or GPT returns gets dropped into the report without interrogation, without cross-referencing the source material, without asking whether the conclusion actually exists in the data or whether the model constructed it to fill the gap. AI hallucination in research does not announce itself. It does not look like an error. It looks like a finding, confidently worded, plausibly structured. That is what makes it dangerous. The output is only as trustworthy as the scrutiny applied to it.

Over-reliance is not efficiency. It is judgement on standby.

What I am currently trying

I am still working this out. But a few things have shifted how I approach a brief.

On a Day 0 merchant onboarding brief, I hit a wall early. The experience needed to work for someone who had just signed up, had no context, and needed to get to their first transaction without hand-holding. I had a direction but it felt incomplete. Loading the full context into a prompt, the user profile, the journey stage, the drop-off patterns, the business constraints, helped me stress-test my own thinking. The AI surfaced use cases I had not accounted for, edge conditions that shifted the narrative enough to change the design direction. It did not solve it. It challenged me out of a position I had settled into too early.

The RiskShield dashboard was a different kind of problem. The existing design had been built directly from a PRD by a previous designer. It was system-oriented, jargon-heavy, structured like a spreadsheet rather than an experience. Technically complete. Humanly unusable. Starting from that baseline with AI meant I could rapidly reframe what the dashboard should actually communicate to a user under pressure, stripping back the system logic and rebuilding around what the merchant needed to understand and act on. The AI helped me move faster through the reframing. The judgement about what good looked like was still mine.

The more interesting shift has been in how design decisions get communicated, not just made. One of my team members used vibe coding to build a working simulation of the Houzy chatbot experience rather than a static prototype. Persona defined, context loaded, conversation scripts written, APIs connected for actual content, guardrails in place. The result was something stakeholders could experience rather than interpret. The story told itself because the environment was real enough to inhabit. That is a different order of storytelling from a Figma deck, and it required the same core skill: knowing what you are trying to communicate before you build the thing that communicates it.

This is not an isolated experiment. The Razorpay design team has been publicly vocal about using similar approaches to push low-stakes design changes directly as pull requests, effectively closing the loop between design decisions and production without a full engineering handoff. It is an early signal of something larger: designers who can operate at the boundary of design and code are beginning to compress the distance between intention and outcome in ways that were not possible two years ago.

PR merges driven by design are not mainstream yet. But the teams already working this way are not waiting for permission. They are redefining what a design deliverable looks like.

The question for everyone else is how long to wait before that gap becomes visible.

Taste is still the filter

AI can generate ten directions in the time it used to take to sketch one. That speed is real and it is useful. But speed without a filter is just more options, and more options without judgement is noise.

Taste is what makes the output useful. The ability to look at what the model returned and know immediately what is close, what is wrong, and what the gap is between the two. That is not something AI develops with more prompts. It develops with years of looking at products, users, and outcomes and building a sense of what good actually feels like.

AI gets you to the decision faster. Taste is still the one making it.

Beyond taste, into adoption

There are things quietly blocking adoption that do not get named enough.

The first is tools. Designers in organisations where AI access is restricted or unprovided face a real structural barrier. You cannot build a workflow around something you cannot access. This is a leadership decision, not a designer's personal failing. Providing tools is the minimum. But provision without permission is still a closed door.

The second is the nudge that has to come from above. Not a mandate, not a policy. A visible signal from leadership that using AI is not something to hide, that showing a faster workflow does not mean your team will be cut, that efficiency is not a threat to your value but an expression of it. When that signal is absent, the unspoken calculation takes over and most designers choose safety over exploration.

This matters especially if you are in a leadership role. If you are not openly working this way, your team will not feel safe doing it either. Reluctance flows downward. So does permission.

The third thing, and this one sits with designers themselves, is the stigma that has quietly built up around AI adoption in creative fields. The idea that using AI is somehow less skilled, less original, less worthy of respect. That a design solved with AI assistance is a lesser design.

It is not. The judgement that shaped the prompt, interrogated the output, and made the final call is still yours. The craft is in the deciding, not just the making.

Designers have to be willing to talk about how they work. Share what is landing. Normalise the experimentation. The stigma does not dissolve on its own. It dissolves when enough people stop treating their AI workflow as something to keep private.

The tool is available to everyone. What you do with it, and whether you are honest about it, is still yours.

Where in your workflow are you still protecting the old way of working, and what would it cost you to let that go?