UX/UI design often looks like a profession you can enter after a few weeks of video tutorials. In reality it is a craft, and what counts is not how many courses you have watched but how many problems you have solved and how much honest feedback you have received. This guide doesn't promise quick results. It is a sequence of steps that keeps you from getting lost at the start or spending months on things that don't move you towards a first job.
Step 1. Understand what a UX/UI designer actually does
UX (user experience) is about how a person reaches their goal in a product: which steps they take, where they get confused, what stops them. UI (user interface) is the visual language: grid, typography, colour, components, button states. In practice an interface designer combines both, but the emphasis differs from team to team.
Before learning tools, look at familiar apps with fresh eyes. Open your banking or delivery app and write down what task you wanted to complete, how many screens it took, and where you paused and thought “where now?”. That is your first UX exercise: noticing friction.
Step 2. Build the foundation: core principles
You don't need to learn everything at once. To start, it is enough to understand a few topics well and be able to explain each in your own words:
- Typography: heading hierarchy, body text size, line height, line length.
- Grids and spacing: why spacing is a multiple of one base unit and how that makes a layout cleaner.
- Colour and contrast: how to check that text is readable on its background, and why colour must never be the only carrier of meaning.
- Components and states: a button is not one rectangle but a set of states: default, hover, pressed, disabled, loading, error.
- Basic UX heuristics: visible system status, the ability to undo, consistency, error prevention.
A useful habit is to keep your own collection of examples: a screenshot of a good solution and one sentence on why it works. In a few months this becomes your personal pattern library.
Step 3. Learn Figma through real tasks
Figma is the main tool in most product teams, so start there. But don't try to learn every feature; learn what you need day to day: frames, auto layout, components and variants, text and colour styles, and prototyping transitions between screens.
The best method is recreating. Take a screen from an app you use every day and rebuild it in Figma pixel for pixel, using auto layout and components. Then change the screen width and see what breaks. This exercise teaches more than an hour of theory.
Recreating is training, not a portfolio. Someone else's design, however perfectly rebuilt, doesn't show your decisions. Use it to build skill, and put work in your portfolio where you made the decisions yourself.
Step 4. Learn by doing, not by collecting courses
A typical beginner trap is endless learning with no output. Set yourself a rule: for every hour of theory, at least one hour of practice. Practice means any task with constraints: a specific user, a specific goal, a specific deadline.
Ideas for practice tasks worth trying:
- Simplify a process that annoys you: booking a doctor, paying utility bills, finding a timetable.
- Design onboarding for an app you know, for someone opening it for the first time.
- Add a missing state to an existing interface: an empty list, a network error, a very long user name.
- Join a design game or challenge with a deadline: limited time teaches you to make decisions.
Design games are one of the most honest practice formats: everyone has the same brief and deadline, and other people see and judge the result. You can read how we run them in Activities.
Step 5. Finish two or three first projects end to end
Your first project doesn't have to be big, but it has to be finished. Finished means you went through the whole path: framed the problem, talked to at least three to five people who face it, made drafts, tested them, improved them and polished the final screens.
- State the problem in one sentence: who, what they want to do, what gets in the way.
- Talk to people. Ask about past experience (“tell me about the last time you did this”) rather than hypothetical wishes.
- Sketch several quick options, on paper or with plain grey boxes.
- Build a clickable prototype and ask someone to complete a task while you watch in silence.
- Fix the places where they got stuck, and only then move on to visual design.
- Write down what you decided and why: this is the basis of your future case study.
Step 6. Seek feedback regularly
Without an outside view it is easy to repeat the same mistakes for years. Show your work early, while it is still a draft and changes are cheap. Ask for specific feedback: not “what do you think?” but “is it clear what to do on this screen?” or “what catches your eye first here?”.
Treat criticism as data, not a verdict. A useful rule: listen, ask a follow-up question if something is unclear, say thank you, and only then decide what to take from it. Not every piece of advice is right, but each one shows how another person sees your work.
Step 7. Become part of a community
A community gives you what no course can: live examples, answers to “silly” questions, feedback on your work and the motivation not to give up. In Spaceberry Community, more than 1,500 designers discuss their work, share resources and take part in games and workshops. You don't have to post a lot straight away: read, ask questions and show your work now and then.
The people who get the most out of a community are the ones who give as well as take: they comment on others' work, share a useful link, and help a newcomer with a question they were searching for themselves not long ago.
Step 8. Prepare for your first job search
Once you have two or three finished projects written up as case studies, you can start looking for a first role. A few practical tips:
- Your portfolio matters more than your CV. For how to structure a case study, see the guide How to build a design portfolio.
- Tailor your cover note to each role: one or two sentences on why this particular product interests you.
- Be ready to talk about your decisions: interviews often ask you to walk through a case and explain why you did things that way.
- Consider internships, volunteer projects and tasks for civic initiatives: they are real experience with real constraints.
- Keep a spreadsheet of applications: where you applied, when, and what the response was. It helps you see progress and keep going.
A rejection is not a judgement of your talent. Often it means your experience didn't match that specific request. Ask for feedback after interviews: even a short answer helps you see what to improve.
A short checklist for your first months
- I can explain the difference between UX and UI using a familiar app.
- I use auto layout, components and variants in Figma with confidence.
- I have recreated at least three existing screens for practice.
- I have two or three finished projects of my own, with my decisions described.
- I show my work regularly and get feedback.
- I have taken part in at least one design game or challenge with a deadline.
- I have a portfolio I'm not embarrassed to send.
Getting into the profession is a marathon, not a sprint. Take small steps, but take them regularly, and don't be afraid to show imperfect work: that is exactly how it gets better. Learn more about our learning formats on the Programs page.