DEV Community

Cover image for AI didn’t replace my design process. It changed how fast I could execute it.
Mustofa Al-Ameen Mustafa
Mustofa Al-Ameen Mustafa

Posted on

AI didn’t replace my design process. It changed how fast I could execute it.

AI didn’t replace my design process. It changed how fast I could execute it.

I’ve been experimenting with AI tools in my UI/UX workflow, and one thing has become clear:

AI is great at generating ideas.

But knowing what to build, what to remove, and why a user should care is still the designer’s job.

My workflow has started looking something like:

PRD → User flows → Wireframes → AI-assisted exploration → UI design → Prototype → Testing

The biggest win isn’t “AI designed this for me.”

It’s moving from an idea to something tangible much faster.

The tools are getting better every month.

The interesting part is figuring out how designers can actually use them without losing the thinking behind the work.

I’m still experimenting.

What’s your experience been like using AI in your design or development workflow?

Top comments (4)

Collapse
 
cathy_3c6121740b50c8a080f profile image
Cathy •

Totally with you on “AI = speed, not brains.” One tweak: add an explicit “AI brief” before AI-assisted exploration. Write 3 bullets: goal, constraints, success metric. Then force yourself to justify every AI suggestion against those. Keeps the thinking sharp while you move fast.

Collapse
 
mustofa_shonen profile image
Mustofa Al-Ameen Mustafa •

Yeah, I agree with you on that. Thank you for your input.

Collapse
 
alexshev profile image
Alex Shev •

That distinction is the healthy one: taste and problem framing set the direction, while generation shortens iteration. I would keep the decision record for why a design constraint exists, since that is the context most likely to disappear when the execution layer becomes fast and abundant.

Collapse
 
mustofa_shonen profile image
Mustofa Al-Ameen Mustafa •

Kindly let me know what you think?