I’ve tested a lot of AI tools in the last two years. Most of them don’t save time. They create a different kind of work: prompt writing, output reviewing, direction-correcting, and explaining to stakeholders why the AI-generated thing isn’t quite right. The overhead is real.
But some things actually work. Not in the “this will change everything” sense that every tool launch promises — in the sense that I now do them this way and wouldn’t go back.
Here’s what’s actually useful, and where it reliably wastes your time.
Research synthesis is genuinely faster with AI. Feeding twenty user interview transcripts into a language model and asking it to surface themes, contradictions, and unresolved questions compresses two weeks of synthesis work into two to three days. The researcher validates AI-generated themes rather than creating them from scratch. The important caveat: AI will occasionally hallucinate a pattern that isn’t there, or flatten a nuanced finding into something neater than the data supports. Your job shifts from synthesis to verification — which is faster, but requires you to stay critical rather than trusting the output.
Generating quantity at the early stage is also genuinely useful. When you need ten layout directions to show that you’ve explored the space, AI produces them fast. When you need five versions of a microcopy line to test in research, AI produces them in seconds. The output is rarely what you ship. The value is the exploration that would have taken a day now taking twenty minutes — leaving more time for the judgment work of selecting and refining.
Writing first drafts of documentation, design principles, and annotation copy is another real win. AI produces serviceable first drafts that you edit into your voice. That’s faster than starting from a blank page, and the editing process is often where clarity emerges anyway.
Using AI for anything requiring precision or specificity early in a project wastes time. AI has no access to your users, your product context, your design system, your business constraints, or the seventeen conversations that shaped this brief. It generates plausible-looking outputs that look more informed than they are. The time you spend directing, correcting, and restarting often exceeds what you’d have spent starting from scratch with your actual knowledge.
Generating UI in production contexts is consistently slower than designing it yourself. The outputs drift from your design system, miss interaction context, and create work for the developer who has to reconcile them with what actually exists. For early exploration, useful. For anything that touches production, not.
Treating AI output as a starting point when it should be a direction-setter is the most common mistake. Taking an AI-generated layout and trying to iterate from it anchors you to the AI’s assumptions. Better to use AI to generate options, extract the principle behind the ones that feel right, and build from that principle in your own design environment.
AI is most useful when the task is well-defined, the context is available, and speed of generation matters more than precision. It is least useful when the task is ambiguous, the context lives in your head, and precision matters.
Most of the important work in design — defining the right problem, making the judgment call, pushing back on the brief — falls into the second category. The tools help most with the work that was never the hard part.
AI assists with wireframe generation, placeholder copy, and user flow mapping. Human-led work covers design critique, brand alignment, usability, accessibility, and final decision-making. That division isn’t a concession — it’s the correct allocation.
References