Tools vs UX: Why Learning Figma Won’t Make You a UX Designer
The design industry is changing fast. AI can generate interfaces, tools can automate workflows, and almost anyone can create a polished screen. So, what makes someone a UX designer today?
Open LinkedIn, YouTube, or any design community, and you’ll find plenty of advice about becoming a UI/UX designer. Learn Figma. Master auto layout. Build a portfolio. Explore AI tools. Create a few projects, and you’re ready to apply for jobs.
It sounds simple. But somewhere along the way, we started confusing the ability to use design tools with the ability to design meaningful experiences.
Knowing how to use a tool is a skill. Knowing what to build, why to build it, and how to make it work for people is design.
And the difference matters more than ever.
The tool is not the job
Let’s start with a simple example : Imagine two designers working on the same project (a mobile banking application.)
The first designer opens Figma and starts creating screens. They choose colors, build components, apply a modern layout, add micro-interactions, and make everything look polished. The result looks impressive in a presentation.
The second designer starts with questions.
Why are users struggling with the existing application? Where do they abandon the process? Do they understand the difference between their available balance and their current balance? What happens when a transaction fails? Are users confident enough to complete a payment?
The second designer might also use Figma, create beautiful interfaces, and build prototypes. But the screens are a consequence of their thinking, not the starting point.
Both designers know how to use the tool. Only one has demonstrated that they understand the problem.
This is where the real difference between tools and UX begins.
What design tools actually give us
Tools like Figma, FigJam, Framer, Adobe Creative Cloud, and AI-powered design platforms have transformed how we work.
They help us create faster, collaborate more effectively, explore alternatives, build prototypes, and communicate ideas. Tasks that once required hours of manual effort can now take minutes.
With AI entering the workflow, we can generate initial layouts, explore visual directions, produce content, and even turn prompts into functional prototypes.
These are meaningful improvements. Designers should absolutely learn to use them.
But tools have a limitation: they can help you execute a decision without necessarily helping you make the right decision.
You can create a beautiful checkout page without understanding why users abandon their carts. You can build an elegant dashboard without knowing which metrics actually matter to its users. You can generate an onboarding flow without considering the anxiety someone feels when submitting personal documents.
The output might look complete, but the underlying experience could still be broken.
A tool makes execution easier. It doesn’t automatically make your decisions better.
So, what is UX really about?
User experience design begins long before the first pixel appears on the screen.
It begins with understanding people, their needs, their behaviors, their environments, and the challenges they face.
It involves asking questions, identifying patterns, defining problems, exploring possible solutions, and validating whether those solutions actually work.
A typical UX process might involve:
- Research: Understanding users through interviews, observation, analytics, and feedback.
- Problem framing: Identifying the real problem instead of immediately accepting the requested solution.
- Information architecture: Organizing information so people can find what they need.
- User flows: Defining how people move through a product and where they might encounter friction.
- Interaction design: Making actions, decisions, and system responses understandable.
- Usability testing: Observing real users to discover what works and what doesn’t.
- Iteration: Improving the experience based on evidence, not personal preference alone.
Not every project needs every activity in equal measure. Good designers adapt their process to the problem, the available evidence, and the project’s constraints.
The important part is the thinking behind the work.
UX isn’t about following a checklist. It’s about making informed decisions that balance user needs, business goals, and technical realities.
UI matters too. But it isn’t just decoration.
There is another misconception worth addressing: UX is thinking, while UI is simply making things look good.
That’s an oversimplification.
User interface design is not just about choosing colors, typography, shadows, or attractive illustrations. It involves visual hierarchy, readability, consistency, accessibility, interaction feedback, and helping people understand what they can do next.
A well-designed interface reduces cognitive effort. It makes important information easier to recognize and actions easier to understand.
Consider a dashboard containing twenty metrics. You could arrange all twenty into perfectly aligned cards using Figma. Every component could follow the design system, and every color could be consistent.
But if users cannot identify the most important information, the interface still has a problem.
The UI designer must understand what deserves attention, how information should be prioritized, and how visual decisions support the user’s goals.
Get Shivam Sachdeva’s stories in your inbox
Join Medium for free to get updates from this writer.
Good UI isn’t just how a product looks. It’s how effectively the interface communicates.
UX and UI have different emphases, but they work together. Neither can be reduced to knowing a particular application.
AI is changing the workflow, not eliminating the need for design thinking
This is where the conversation becomes even more interesting.
Previously, learning a design tool required time and practice. Building components, arranging layouts, maintaining consistency, and creating interactive prototypes demanded considerable effort.
Today, AI tools can accelerate many of these tasks. Some can generate complete interface concepts from a text prompt. Others can help with research synthesis, content generation, prototyping, and front-end implementation.
As these capabilities improve, producing a visually acceptable interface becomes less of a differentiator.
That doesn’t mean design skills are becoming irrelevant. It means the valuable skills are shifting.
When more people can generate interfaces, the ability to identify the right problem becomes more important. When prototypes can be created quickly, knowing what to test becomes more important. When AI offers multiple possible solutions, evaluating those solutions becomes more important.
AI can suggest a layout, but someone still needs to determine whether it fits the user’s context, meets accessibility requirements, supports the business objective, and handles real-world edge cases.
AI-generated output can also introduce misleading assumptions, inconsistent interactions, inaccessible patterns, or solutions that look convincing without being usable.
Designers must know how to evaluate, challenge, and improve what these tools produce.
The future isn’t necessarily about designers who avoid AI or designers who use the most AI tools.
It’s about designers who know when to use them, how to direct them, and how to judge their output.
The mistake aspiring designers are making
Many aspiring designers spend months learning tools and only a fraction of that time learning how to think through a design problem.
They collect certificates, recreate popular interfaces, follow tutorials, and build portfolios filled with polished screens. These activities can help develop foundational skills, but they don’t automatically demonstrate UX capability.
A portfolio that shows only the final UI leaves important questions unanswered.
Why was this problem worth solving? Who experienced it? What evidence informed the decisions? Which alternatives were considered? What changed after testing? How did the final solution improve the experience?
You don’t need a large research budget or access to hundreds of users to start answering these questions. Even a small project can demonstrate thoughtful problem framing, informed assumptions, usability evaluation, and iteration.
Instead of merely recreating an existing application, investigate one of its real usability problems. Instead of presenting ten beautiful screens, explain the reasoning behind three important decisions.
Show the journey from problem to solution, including what you learned and what you changed.
A strong portfolio doesn’t just show that you can design a screen. It shows that you can explain why that screen should exist.
What should you learn, then?
The answer isn’t to stop learning tools. That’s the wrong conclusion.
Tools are essential, and practical proficiency matters. You should understand your primary design software, components, responsive layouts, prototyping, collaboration, and the AI capabilities relevant to your workflow.
But your learning shouldn’t stop there.
Develop your research skills. Learn to conduct interviews without leading participants toward your preferred answers. Practice mapping user journeys and identifying friction. Understand usability principles, accessibility, and information architecture. Learn to interpret product analytics and connect design decisions to measurable outcomes.
Most importantly, practice explaining your decisions.
Why is this button placed here? Why does this flow ask for information at this stage? Why should this action be the primary one? What happens when the user makes a mistake? How would you know whether your solution worked?
If you can answer these questions with clear reasoning and appropriate evidence, you’re building a skill set that extends beyond any particular tool.
Tools will change. Interfaces will evolve. AI capabilities will continue to improve.
The ability to understand people and make thoughtful decisions will remain valuable.
The real difference between a tool user and a designer
A tool user may ask, “How can I create this screen?”
A designer also asks, “Should this screen exist in the first place?”
A tool user may focus on completing the flow.
A designer considers whether the flow makes sense to the person using it.
A tool user may celebrate a polished prototype.
A designer wants to know what happens when someone tries to use it.
These aren’t rigid categories. Every designer uses tools, and every designer continues learning. The distinction is the depth of thought behind the output.
You don’t become a UX designer simply because you know Figma. You become a stronger UX designer by learning to understand problems, make informed decisions, test your assumptions, and improve experiences.
And you don’t need to master every new tool to prove your value.
Learn the tools. Experiment with AI. Stay curious about emerging technologies. But invest just as much effort in understanding people, products, and problems.
Because the goal of UX isn’t to produce more screens.
It’s to make the right things easier for the right people.
And no tool can replace the responsibility of thinking carefully about what that means.
What’s your take? As AI makes interface creation easier, which skills do you think will distinguish great UX designers from everyone else?
