Saroj

What AI is really teaching designers about being human

A man sitting at a desk with a computer, displaying a lightbulb and cloud icon, against a backdrop of stylized clouds and futuristic buildings.

We talk a lot about how designers can use AI these days. But I’ve been thinking about something else. AI is teaching us how to be better designers, especially the “people skills” that make all the difference.

When you look at how the best conversational AIs work, it’s pretty wild. They’re being built to act exactly like the best human designers. We’re teaching computers the same communication and thinking habits that help us do great work with our clients and teammates every single day.

Six of those habits stand out to me.

1. Ask good questions (like, really good ones)

Imagine telling an AI, “Design a cool logo.” A basic AI (or a designer who jumps ahead) might give you what it thinks is cool. It assumes it knows best, which often leads to missed marks and frustrating revisions.

A really good AI, like a skilled designer, would follow up right away: “I can help! To get started, what industry is this for? Is it a tech startup or a bakery? What kind of vibe are you going for? Minimalist, playful, serious? Modern or classic? Any specific colors to avoid or include?”

It works the same way in design. If a client says, “Make the button stand out,” a good designer doesn’t make it bright red. They ask: “What action do you want users to take? Why isn’t it standing out now? What’s the most important thing on this page?”

What designers can learn:

  • Don’t guess what your client wants. Their first request is the starting line.
  • Dig deeper. Ask open-ended questions to understand the needs, context, and goals behind the request.
  • Better questions lead to better designs and save hours of rework.

2. Take your time to think (it’s not wasted time)

When you give AI a tricky task, like summarizing a long document or generating a complex image, you often see that “…” or “Thinking…” message. It takes a moment to process everything, connect the dots, and form a structured response before it answers.

If a team asks, “Can we add a new feature for X?” a good product designer doesn’t immediately sketch a UI. They pause. They ask, “What problem does this solve? For whom? How does it fit into our current roadmap? What are the potential trade-offs?” They gather information before committing to a solution.

What designers can learn:

  • We often feel rushed to have an answer or start designing right away. Pushing pause pays off, especially on complex problems.
  • That thinking time is where the real problem-solving and planning happen.
  • It’s totally okay, and often professional, to say, “That’s a great point. Let me think this over, research a bit, and I’ll get back to you with some ideas later today/tomorrow.”

3. Offer choices (don’t just give one)

The best generative AIs give you more than one option. If you ask for an image of a “futuristic city,” they might give you three variations: one sprawling and neon-lit, one with flying cars, and another that’s more eco-friendly and green.

When presenting a new website layout, a thoughtful designer might show “Option A: Clean and minimalist for speed,” “Option B: Feature-rich for discovery,” and “Option C: Bold and brand-focused.” Each option solves the problem slightly differently, so the client can compare real trade-offs.

Creative problems often have many good answers, and personal taste, business goals, or user preferences decide between them. Showing a range also manages expectations.

What designers can learn:

  • Don’t fall in love with your very first idea. Exploring multiple paths often leads to a stronger final solution.
  • Show multiple options. It shows you’ve explored the problem from different angles.
  • It lets your client take part in the decision, turning “Is this right?” into “Which of these works best for us, and why?”

4. Be patient (even when asked the same thing again)

You can ask an AI the same question ten times. You can change your mind completely, or forget something it told you and ask again. The AI doesn’t get annoyed, frustrated, or subtly judge you. It processes the request and answers again, calmly.

A client might ask about the navigation strategy in a meeting, then email about it later, and then bring it up again a week later. A patient designer understands that people absorb information differently, need reminders, or have new concerns. They don’t sigh or say, “We covered this.” They explain it again, perhaps with a new angle or more context.

What designers can learn:

  • Drop the ego. When a client or teammate asks the same question for the third time, they’re usually not trying to frustrate you, and they probably were listening.
  • It often means our last explanation wasn’t clear enough, they forgot amidst other tasks, their priorities shifted, or they need reassurance.
  • Every repeated question is a chance to improve how we explain our work. Meet it with calm, clearer wording, and a willingness to re-explain.

5. Adapt to feedback (and learn from every interaction)

When you tell an AI, “That image is good, but make the colors warmer,” it doesn’t argue or defend its original choice. It takes the feedback and tries again.

A user test reveals people are confused by a certain icon. A good designer doesn’t blame the users; they observe, ask “why?”, and then iterate. They might test a few new icons, learn from the results, and improve the design based on what users did.

What designers can learn:

  • Treat feedback as data for improvement. Your initial design is a hypothesis.
  • Be open to changing direction, even if you put a lot of work into the first version. The goal is the best solution for the user and the client.
  • Seek out critiques and user testing. The more feedback loops you build into your process, the better your final design will be.

6. Anticipate needs (before being asked)

A really smart AI doesn’t wait for you to type. If you ask for a recipe, it might also offer to create a shopping list or suggest wine pairings. If you book a flight, it might ask if you need a hotel. It tries to predict what you might need next.

When designing an e-commerce checkout, a designer doesn’t stop at the payment fields. They might add a “guest checkout” option, show shipping estimates early, or add a “save for later” button, so common frustrations are handled before anyone has to ask.

What designers can learn:

  • Think beyond the immediate request. What’s the next logical step for the user? What might they forget or need right after this interaction?
  • Look for chances to simplify journeys before users hit friction. It builds trust and makes the experience feel intuitive.
  • Use user research and empathy to put yourself in their shoes and spot friction points or unspoken needs in their journey.

Related articles

Person taking the steering wheel, a metaphor for owning your career direction

Take the wheel: why you cannot wait for someone else to plan your career

A manager sits at his desk, visibly stressed, surrounded by crumpled papers, while two employees argue in the background

Why some managers are afraid to be the 'bad guy', and it hurts the team

Astronaut taking an interview

Getting hired as a designer: a hiring manager’s perspective