Theory
You are not your user
You built FestConnect, so YOU know exactly where the register button is, what every icon means, how the flow works. It is obvious: to you.
But you are a computer-science student who wrote the code. The actual user is a nervous first-year from a Gujarati-medium school, on a cracked phone, on hostel wifi, registering for the first time. What is obvious to you is a maze to them.
The philosophy that fixes this has a name: user-centered design. Its first commandment: you are not your user.
Theory
User-centered design, formally
User-centered design (UCD) is a design philosophy and process that places the needs, goals, contexts and limitations of real end users at the centre of every decision, at every stage.
You design WITH and FOR users, guided by evidence about them, not by the designer's own assumptions or the technology's convenience.
The opposite: designer-centered design ("I find this obvious, so it is fine") or technology-centered design ("the database stores dates this way, so users will type them that way"). Both put the wrong thing at the centre. UCD puts the human there.
At a glance
Core principles of user-centered design
| Principle | What it demands |
|---|---|
| Understand users explicitly | Base design on real knowledge of users, tasks, contexts |
| Involve users throughout | Users participate across the whole process, not just at the end |
| Evaluate with users | Design is refined by user-centered testing, not opinion |
| Iterate | Repeat the cycle; first attempts are rarely right |
| Address the whole experience | Not just screens: the entire journey |
| Multidisciplinary team | Diverse skills and perspectives shape the design |
Theory
The UCD cycle: four repeating phases
UCD is not a one-shot; it is a LOOP of 4 phases (mirroring the ISO 9241-210 standard idea):
1. Understand the context of use: who are the users, doing what, where, on what?
2. Specify user requirements: what must the design achieve for them?
3. Design solutions: wireframes, prototypes, screens
4. Evaluate against requirements: test with real users
Then you LOOP: evaluation reveals problems, you understand more, redesign, retest. The rest of this subject is these 4 phases with real tools: research and personas (understand), wireframes (design), usability testing (evaluate), iteration (loop).
Quiz
What is the CENTRAL idea of user-centered design?
- Design whatever is easiest to build with the available technology
- Place real users' needs, goals and limitations at the centre of every design decision
- Design based on what the designer personally finds obvious and elegant
- Add users' opinions only at the very end, after the product is finished
Show the answer
Place real users' needs, goals and limitations at the centre of every design decision
UCD's defining move is to centre REAL users: their needs, goals, contexts and limits: in every decision, backed by evidence about them. Option A is technology-centered design, a classic anti-pattern (the database's convenience is not the user's need). Option C is designer-centered design, the you-are-not-your-user trap. Option D violates the involve-users-THROUGHOUT principle: consulting users only at the end means discovering fatal flaws too late to fix cheaply. The whole philosophy is a rejection of designing for yourself or the machine: design for the human who will actually use it.
Think first
Spot the anti-pattern
FestConnect asks students to type the date as YYYY-MM-DD because that is how the database stores it. Which anti-pattern is this, and how would UCD reframe the decision? Then tap.
Show the answer
This is technology-centered design: the DATABASE'S storage format leaked into the user's task, forcing a nervous first-year to know an engineering convention. UCD reframes it by asking about the USER: how do Indian students naturally write dates? (DD/MM/YYYY, or better, they should not TYPE a date at all: a date picker removes the question). The context of use (a stressed student, a small phone) drives the design; the database adapts to the human, converting formats internally. The rule: never make the user serve the technology's convenience: make the technology serve the user.
Watch out
UCD slips
"I tested it myself, it works": you are not your user; self-testing hides the assumptions users do not share.
Users only at the end: involve them THROUGHOUT; late feedback is expensive feedback.
One-and-done: UCD is ITERATIVE: the loop is the method, not a nicety.
Confusing user-centered with user-LED: users reveal needs and problems; they do not design the solution for you: you synthesise their input into design (a common exam nuance).
Theory
From philosophy to satisfaction
UCD is the WHY behind everything ahead: research, personas, testing and iteration are all just UCD's phases made concrete. Before diving into the tools, the next lesson answers the natural business question a manager would ask: WHY should we spend on all this? What does good UI/UX actually BUY: in user satisfaction and product success? Then Unit 2 begins the real work: researching FestConnect's actual users.
Summary
Key takeaways
- User-centered design (UCD) puts real users' needs, goals, contexts and limitations at the centre of every decision.
- Its first rule: you are not your user; design for them, backed by evidence, not your assumptions.
- Anti-patterns: designer-centered (design for yourself) and technology-centered (design for the machine's convenience).
- Principles: understand users explicitly, involve them throughout, evaluate with them, iterate, address the whole experience, use a multidisciplinary team.
- The UCD cycle loops 4 phases: understand context, specify requirements, design solutions, evaluate.
- The rest of the subject is these phases with concrete tools (research, personas, testing, iteration).
- Memory hook: centre the human, not yourself or the technology; and repeat the loop.