UX Design Basics · Lesson 1 of 6
UX is not how it looks
Separate UX from visual design, and recognise bad UX in things you use daily.
User experience design is the work of making something usable, useful and worth returning to. Visual design — colours, typography, polish — is one part of it, and the part beginners mistake for the whole. A beautiful banking app that hides the transfer button is bad UX. A plain government form that anybody can complete correctly on the first attempt is good UX.
The questions a UX designer asks come before any screen exists: Who is going to use this? What are they actually trying to accomplish? What do they already know? Where will they be when they use it — a quiet office, or a crowded market on a cracked phone in daylight? What happens when they make a mistake? What is the shortest honest path from where they start to what they want?
You already have strong opinions about UX from being a user. Think about the last time you gave up on something: a website where the price appeared only after four steps, an app that logged you out constantly, a form that erased everything you typed because one field was wrong, a bank helpline menu with no path to a human. Each of those is a design decision someone made, and each cost that organisation real money.
The local context matters here and is often ignored by international courses. Pakistani users are overwhelmingly on phones, frequently on mid-range Android devices, often on mobile data that is slower and metered, often bilingual, and often with limited experience of software conventions that designers assume are universal. A design tested only on a designer's fast phone over office wifi is a design that has not been tested. So is one written only in English for an audience that reads Urdu more comfortably.
The practical definition to carry: UX is deciding what happens, in what order, and what it says — so that a real person, in real conditions, gets what they came for without help.
Find three things you used this week that frustrated you — an app, a website, a form, a machine. For each write: what were you trying to do, exactly where did it go wrong, and what would have fixed it. Then find one thing that worked so smoothly you did not notice it, and work out why. That second one is harder and more instructive.
Check what you learned
Create your free BvLogic ID to take the quiz and record your score.
Create your BvLogic ID