Reading Guide
UX focuses on the overall experience of a user interacting with a product or service; UI refers to the concrete interface; usability concerns how easily tasks can be completed. A good-looking interface does not prove a good experience; first clarify the problem to be solved, then select research and testing methods.
If you are confused about the concepts, start with Section 1; if you need to judge when to conduct user research, read Section 3; for choosing between interviews, behavioral research, or testing, see Section 4; if you cannot decide among multiple design options, go to Section 5. Section 7 includes career and portfolio advice, which is not a prerequisite for product validation.
A minimal exercise is: give a real user a clear task, observe where they get stuck, and map those problems to design assumptions to be validated. Record opinions from interviews and actual task performance separately; do not use feedback from a few people as a direct substitute for the proportions of the overall user base.
Recommended further reading:
This set of materials is NNGroup’s "entry map" — it strings together the most commonly confused foundational concepts in UX into a single decision-usable main thread. First, recognize three terms that are most often treated as equal but are actually different:
User Experience (UX) = the sum of all touchpoints when a user interacts with a company, its services, and its products (from seeing an ad, contacting customer support, to using an app).User Interface (UI) = one part of UX, specifically referring to "the layer through which the system interacts with the user" (buttons, menus, layout).Usability = a quality attribute used to evaluate UI (how easy it is to learn and use). The three have a containment relationship: UI ⊂ the object evaluated by usability ⊂ UX.
Remember it in one sentence:A beautiful UI ≠ good UX(Even if a movie website has a smooth interface, if its database has no independent films, the experience for users who want to watch independent films is still terrible).
The full text has seven parts: ① Conceptual foundation (UX/UI/usability definitions + how to measure them) → ② Design philosophy and process (HCD/design thinking/product triad) → ③ Why "there is no UX without user research" → ④ Research method system (three-dimensional framework/20 methods/9 quantitative methods/four stages/user interviews) → ⑤ How to choose among multiple solutions → ⑥ 10 heuristics (index, detailed table linked externally) → ⑦ UX career progression (entry/5 stages/portfolio/resume).
1. Conceptual Foundation: UX vs UI vs Usability, and How to Measure Usability
1.1 Three Definitions + One Core Formula
| Concept (EN / CN) | What it covers | One-sentence distinction |
|---|---|---|
| User Experience | All aspects of a user’s interaction with a company/service/product all aspects | The largest circle; it requires seamless cross-disciplinary collaboration across engineering, marketing, graphic/industrial design, and interface design to be done well |
| User Interface | The layer of interface through which the system interacts with the user that interface layer | A key component of UX, but only one part — a perfect UI can still result in bad UX |
| Usability | A quality attribute that evaluates the ease of use of a UI quality attribute, and also a set of improvement methods | More abstract than UI, narrower than UX; it is the scoring dimension for "how easy it is to use" |
Two primary conditions for excellent UX(definition by Don Norman & Jakob Nielsen):① Fully meet users’ real needs without making them exert extra effort;② Then use simple and elegant design to make the product a joy to own and a joy to use. Note the order — first "it works", then "it looks good".
The 5 quality components of usability (remember these 5 and you will understand what "easy to use" means):
| Component (EN / CN) | Plain-language explanation |
|---|---|
| Learnability | How easy is it for first-time users to complete basic tasks? |
| Efficiency | Once users have learned it, how quickly can they get work done? |
| Memorability | After a long period of not using it, how quickly can users get back up to speed? |
| Errors | How many errors do users make, how severe are they, and how easy is it to recover? |
| Satisfaction | Is it pleasant and satisfying to use? |
Key formula (clarify what "useful" consists of):
- Utility Utility = providing the functions users need(whether the capability exists)
- Usability Usability = how easy and pleasant those functions are to use
- Usefulness Useful = Utility + Usability
Core principle: Many teams only focus on Usability (polishing existing functions to be smooth), but forget Utility (fundamentally missing functions users need).Why: No matter how smooth a function is, if a key capability is missing it is still useless — Useful is the product of the two; if either is zero, the whole thing is worthless.
1.2 Why Usability Is a "Matter of Survival" (in the language of money)
- Websites: If it is hard to use, people leave — if the homepage does not explain what you do, information is unreadable, or key questions go unanswered, users leave immediately.
- The first rule of e-commerce: "If users cannot find a product, they cannot buy the product."
- Corporate intranets: Poor usability directly eats employee productivity = wasted time = wasted cost.
- Return on investment (do not lose the specific numbers): Investing 10% of the design budget in usability improves website quality metrics by an average of 2.6 times, and intranet quality metrics nearly double(improvements for software and physical products are smaller but still significant). Results: internally, save training budgets and improve employee efficiency; externally, increase sales/registrations/KPIs.
1.3 How to Improve Usability: Three Steps of User Testing + the 5-User Rule
The core method is User Testing, in three steps:① Recruit representative users(e-commerce customers/corporate employees);② Give representative tasks;③ Observe alongside, record successes and sticking points, do not intervene or help.
Key points:
- Test individually, give no help at all.
- 5 users are enough to find the main problems in a design — do not run one large study;run multiple rounds of small tests, fix issues after each round, then test again.
- User testing ≠ Focus Groups: User testing looks at real operations by individual users(to evaluate interaction); focus groups are suitable for market research (collecting opinions),and cannot be used to evaluate interaction design.
When to test (throughout the whole process, multiple times, fast and low-cost): Test the old design before designing → test competitors in competitive analysis → field observation → low-fidelity paper prototypes → test at every step as you gradually move to high fidelity → evaluate against usability heuristics → test again after launch to catch details.Counterexample: Waiting to test until the final design is done — by then most problems can no longer be fixed.
Where to test: A dedicated lab is only worth building if you test at least once a week; for most companies, a quiet meeting room/office is enough; the essential equipment is really just "real users + a notebook".
2. Design Philosophy and Process: HCD / Design Thinking / Product Triad
These are three ways of talking about "putting users at the center", at different levels:HCD is the worldview, design thinking is the actionable process, and the product triad is the team collaboration structure.
2.1 Human-Centered Design (HCD) — Worldview
Three core principles:
| Principle | Meaning | Counterexample/pitfall |
|---|---|---|
| Be Human-Centered | Everything revolves around end users; and not only direct users — in healthcare, this includes patients, families, doctors, nurses, technicians, cleaners, and schedulers | Only optimizing a few links, without looking at how the whole system affects different groups of people |
| Find the Right Problem | The task you are given is often a symptom, not the root cause; solve the root cause and the symptoms will naturally disappear | Only treating surface symptoms (this can be acceptable when resources are tight, but you should know you are treating the symptom) |
| Think in Systems | Every piece is part of the whole;local optima can drag down the whole | Optimizing a local part while reducing overall performance |
From experience to real goals: Tools are only a means — the purpose of a camera is not to give you a complex control interface, but to let you easily take good photos. Focus design on helping users achieve their end goals, do not get tripped up by the complexity of the tool itself.
2.2 Design Thinking — Actionable Cyclical Process
A cyclical, non-linear process that iterates continuously through feedback. This NNGroup version gives 5+1 stages:
| Stage (EN / CN) | Goal | How to do it |
|---|---|---|
| Empathize | Deeply understand users | Research, interviews, observation; dig into needs/behaviors/motivations |
| Define | Clearly state the problem to solve | Synthesize research, lock in key pain points |
| Ideate | Generate a large number of solutions | Brainstorming, mind maps, cast a wide net |
| Prototype | Turn ideas into visible mockups | Build simple models to test whether the problem can be solved |
| Test | Gather feedback, optimize solutions | Show prototypes to users, collect feedback and iterate |
| Implement | Deliver and launch | Execute and ensure user expectations are met |
Why it is good: ① User-centered — starts from real needs, tests real solutions; ② Team collaboration — gives the team a shared language and common understanding; ③ Stimulates innovation — explores multiple possibilities for the same problem. As Jakob Nielsen put it:"A brilliant interface that solves the wrong problem will still fail."
Flexibility (do not use it as a linear assembly line): After testing prototypes, you often need to go back to "Empathize/Define" to collect new data; repeated alignment within the "Define" stage is also very common.
Scalability: From optimizing a single search box to reforming teacher career development paths, the same set of ideas applies.
Historical context: In the early 20th century, Charles & Ray Eames proposed "learning by doing"; in the 1990s, David Kelley, Tim Brown, and Roger Martin of IDEO formally named the existing set of methods "design thinking". Design moved forward from being an "aesthetic supplement in business" to the front end of product development, and was proven to deliver financial success.
2.3 Product Triad / DVF — Team Collaboration Structure
Origin: The most common product team structure in agile organizations, aimed at breaking down silos between design, product, and engineering. Its source is IDEO’s synthesis that "successful commercial products must simultaneously satisfy" the DVF framework:
| Dimension (EN / CN) | Meaning | Who primarily owns it |
|---|---|---|
| Desirable | People want to use it, it has value to users (it should be usable and useful) | Led by designers, but shared |
| Viable | The business model is sustainable and profitable long-term (user behavior can be converted into revenue) | Led by PM, but shared |
| Feasible | The company has the technical capability to build it | Led by engineering lead, but shared |
The overlap of the three-circle Venn diagram is labeled Valuable. The structure consists of one designer + one product manager + one software development lead, hence the name "three-legged stool" (as opposed to the "two-legged stool" of only engineering + business).
The most common misunderstanding (also a counterexample): Thinking that each of the three people "owns" one DVF dimension (designer = Desirable, engineering = Feasible, PM = Viable).Wrong — the original intent of the triad is precisely to break down silos and share responsibility for all decisions; a decision may be led by one role, but responsibility is shared by all three.
What designers do in each of the three dimensions:
- Desirability: Conduct user research, clearly articulate "user problems", and become the team’s authoritative source for user needs; issue priority is weighed by the PM based on user + business value. If a designer lacks user-centered insight, the team will go in the wrong direction based on assumptions rather than real needs.
- Viability: You must at least understand business goals to make sound decisions; when a functional requirement conflicts with goals,the design solution should be the first step to reveal the contradiction and guide business stakeholders to correct it.
- Feasibility:Involve developers from the early stages of design(rather than handing off only after a "high-fidelity delivery" process is complete — that is a high-conflict zone); designers should also participate in backend structure definition; the vision must be dynamically adjusted as development progresses (development will expose edge cases not thought of initially).
Understand teammates’ roles: Engineering leads evaluate not only "can it be built", but also "is it worth building" (with unlimited resources anything can be built, but whether it is worth it involves business viability); the PM is the bridge between the product team and the broader business, defines success criteria (Requirements + Metrics), and presents scope and priorities through a product roadmap.
III. Why "UX Without User Research Is Not UX"
This is the firmest stance in this entire set of notes:Having a UX department / UX job titles ≠ actually doing UX.
- UX is everyone’s responsibility: product management, development, marketing, content, customer service, graphic design, interaction design —everyone must put users at the center at every step of the product lifecycle.
- Bridging business goals and user goals: A common ailment is making decisions based on assumptions of "we think this is great" rather than facts about "what users actually need"; in Agile/Scrum, user research is often cut due to time and resource constraints, leading to launching without a clear understanding of real user needs. The solution:Use user research to find the overlap between business goals and user needs, and cultivate an organizational culture where "solving user needs = the path to achieving business goals".
- Do the Right Research, Correctly— three common mistakes:
- Recruiting the wrong people: Colleagues and stakeholders are not target users; they are too familiar with the design to give authentic feedback.
- Leading questions: Biased questions contaminate conclusions.
- Choosing the wrong method: Surveys are good for collecting opinions, not for studying interactions; usability testing is good for observing interactions. Using the wrong method = misleading conclusions.
- The hidden value of user testing: team building— Data persuades stakeholders better than assumptions, and can resolve internal debates and speed up development(Instead of endlessly debating whether a website design is good or bad, spend one day running usability testing and see the answer on the spot).
- Iteration: Sketch and Test, Then Repeat— "You must finish building the product before testing" is wrong and wasteful;test sketches and wireframes before writing code, use the simplest prototype to answer the key questions of the current stage, and refine gradually based on feedback.
IV. Research Method System: Three-Dimensional Framework / Map of 20 Methods / 9 Quantitative Methods / Four Stages / User Interviews
4.1 The Three-Dimensional Framework of Research Methods (A "Coordinate System" for Classifying Methods)
Any UX research method can be positioned along three dimensions; once positioned clearly, you will know what questions it answers and when to use it:
| Dimension | Two Ends | Questions Answered |
|---|---|---|
| Attitudinal vs Behavioral | Attitudinal = what users "say" (mental models / brand perception) / Behavioral = what users "do" (task time / clicks) | "What users think" vs "What users actually do" |
| Qualitative vs Quantitative | Qualitative = direct observation to gain deep insights / Quantitative = measurement and statistics | Qualitative answers "why / how to fix it"; Quantitative answers "how many / how big the impact is" |
| Context of Use | Natural use / Scripted use / Limited use / Non-use context | Determines external validity (the more natural, the more authentic) |
Four-Quadrant Quick Reference (Attitudinal/Behavioral × Qualitative/Quantitative):
| Quadrant | Typical Questions | Representative Methods |
|---|---|---|
| Attitudinal + Qualitative (bottom-left) | What users want, how they perceive things | Interviews, focus groups, participatory design |
| Attitudinal + Quantitative (bottom-right) | How many people like a feature, what the preference distribution looks like | Surveys |
| Behavioral + Qualitative (top-left) | Where users get stuck, what their behavioral patterns are | Contextual inquiry, field studies, usability testing, eye tracking |
| Behavioral + Quantitative (top-right) | How many people complete a task, how much conversion improves after a redesign | A/B testing, clickstream analysis, remote unmoderated testing |
Some methods span both ends: Usability testing and field studies both observe behavior and collect self-reports (middle ground); eye tracking produces both quantitative (fixation duration) and qualitative (gaze path) data.
4.2 20 Methods Categorized by "Context of Use" (A Guide to Using UX Research Methods)
NNGroup classifies the 20 methods into five categories by "context of product use" (the original diagram uses colors to distinguish them):
| Category (Context) | Methods | Key Characteristics |
|---|---|---|
| Natural product use (green) | Contextual inquiry, field studies, diary studies, user feedback, clickstream analysis | User behavior in real environments, highest external validity |
| Product use in the lab (purple) | Usability testing, usability benchmarking, remote moderated testing, unmoderated testing, eye tracking | Scripted measurement of behavior in a controlled environment |
| Detached from the product (orange) | Interviews, focus groups (3–12 people), participatory design | Emphasizes opinions/attitudes rather than direct product use |
| Limited product use (blue diamond) | Concept testing, card sorting, tree testing, desirability studies | Validate concepts or optimize information architecture |
| Quantitative methods (blue) | Analytics, A/B testing, surveys | Large-scale data to answer "how many / how big" |
4.3 Overview of 9 Quantitative Research Methods (Cost/Difficulty/Sample Size — Don’t Mix Them Up)
Quantitative methods give UX a numerical value— quantifying usability, comparing designs, and tying UX improvements to business goals. Horizontal comparison of the nine methods:
| Method (EN / CN) | Purpose | Cost | Difficulty | Data Type | Context |
|---|---|---|---|---|---|
| Quant Usability/Benchmark | Track usability, compare with competitors | Medium | Medium | Behavioral | Task-based |
| Web/App Analytics | Detect problems, prioritize, monitor performance | Low | Low for collection / High for analysis | Behavioral | Actual product |
| A/B Testing / Multivariate Testing | Compare which of two design options is better | Low | Low | Behavioral | Actual product |
| Card Sorting | Define labels and structure for information architecture | Low | Low for collection / Medium for analysis | Attitudinal | Does not involve the actual product |
| Tree Testing | Evaluate whether the hierarchy of information architecture is easy to navigate | Low | Low for collection / Medium for analysis | Behavioral | Task-based, does not involve the product |
| Surveys | Collect attitudinal and behavioral information | Low | Low | Attitudinal | Any scenario |
| Clustering Qual Data | Find high-frequency themes in qualitative data | Low | Medium for collection / Medium for analysis | Attitudinal | Any scenario |
| Desirability Studies | Measure brand attributes / attractiveness (select descriptive words) | Low | Low | Attitudinal | Task-based |
| Eyetracking | Measure the attractiveness and discoverability of elements | High | High | Behavioral | Task-based |
Key sample size note: Quantitative usability testing requires around 35 or more participants to be reliable (in contrast, qualitative testing only needs 5 people — see NNGroup Usability Testing and the 10 Usability Heuristics (Full List of 10 Heuristics · Application to Complex Apps · User Pleasure Hierarchy · Testing Methods: 5-User Rule / Recruitment / Remote / Task Scenarios / Step-by-Step Tasks / Attitudinal vs Behavioral / 4-Step Analysis / Small-Sample Bias / Competitive Evaluation) §IV for the 5-user rule).Three steps for choosing a method: ① Choose by question (overall questions → quantitative testing/analytics/surveys; specific questions → A/B/card sorting/tree testing/desirability); ② Choose by budget (digital tools and remote methods are cheaper); ③ Ensure the statistical minimum sample size is met.
4.4 Choosing Methods by Development Stage + The Four Stages of the UX Research Cheat Sheet
Methods corresponding to the three stages of product development:
| Stage (EN / CN) | Goal | Methods |
|---|---|---|
| Strategize | Explore new directions / opportunities | Field studies, interviews, diary studies, concept testing, participatory design |
| Design | Improve usability | Card sorting, tree testing, usability testing (lab/remote) |
| Launch & Assess | Evaluate performance, compare with old versions / competitors | Usability benchmarking, A/B testing, clickstream analysis, surveys |
Three principles for research timing:①Start now— the earlier you research, the greater the impact on the product; ②Do research at every stage;③Concentrate resources in the early stages, but reserve budget for supplementary research later.
The four-stage cycle of the UX Research Cheat Sheet (Discover/Explore/Test/Listen)— this is a finer-grained way of slicing the same thing as the three stages above:
| Stage (EN / CN) | Goal | Applicable Methods | Key Activities |
|---|---|---|---|
| Discover | Explore the unknown, test assumptions, understand needs | Field research, user interviews, diary studies, stakeholder interviews, competitive analysis | Validate assumptions; bring sales/support/training together to identify pain points |
| Explore | Define scope, solve problems | Task analysis, user journey maps, prototype testing, card sorting | Build user personas; iterate on design to reduce risk |
| Test | Validate design, ensure usability | Qualitative usability testing, benchmark testing, accessibility evaluation, diary studies | Test early and test often; build a usability issue tracking repository |
| Listen | Continuously discover problems and trends | Surveys, behavioral data analysis, search log analysis | Collect feedback from social media/comments/customer service; regularly summarize common issues |
Highest-priority methods (Top UX Methods):①Qualitative usability testing(most effective for improving existing systems); ② Field research + interviews (dig for deep insights); ③ Card sorting + tree testing (optimize information architecture); ④ Behavioral data analysis (discover trends, but must be combined with user testing to understand "why").
4.5 User Interviews 101 — The Most Commonly Used Discover-Stage Method
What it is: Understanding "who users are, what their experience is like, and what their needs/values/desires are" by asking questions, listening, and following up as needed. Also known as: in-depth interviews / semi-structured interviews / qualitative interviews. Mostly used in the Discover stage / the Empathize stage of design thinking.
Can collect: Content and impressions of the user experience, pain points, views and feelings, concerns, Mental Models, motivations/desires/needs. Outputs can feed into: user need statements, Empathy Maps, Personas, customer journey maps.
Interviews vs Usability Testing (the two most easily confused):
| Item | User Interviews | Usability Testing |
|---|---|---|
| Purpose | Explore experience/needs/pain points | Evaluate design performance, find problems and causes |
| Research Type | Attitudinal(thoughts/self-reports/feelings) | Behavioral(observe how users interact) |
| Stage | Empathize / Discover | Test |
| Whether a design is required | Not required | Requires users to interact with a design |
| Interaction atmosphere | More natural, more eye contact, friendly | More formal, less eye contact, avoid being overly friendly |
6 implementation steps: ① Clarify research goals → ② Prepare an interview guide (open-ended questions such as "Describe your day" + follow-ups such as "How did you feel at the time", flexible and not necessarily linear) → ③ Pilot the guide (test with colleagues/target users to expose ambiguities) → ④ Easy opening (state the purpose first, start with "Tell me a little about yourself") → ⑤ Build trust (nod, repeat key words, do not interrupt or rush) → ⑥ Probe deeper ("Can you tell me more about that?" "Why is that important to you?").
Limitations (why interviews cannot be used alone): Self-reported behavior has recall bias / information omission / social desirability bias; if interviewers ask leading questions, they will contaminate the data.Countermeasure: Combine with observational research or behavioral analysis to piece together users’ real behavior.
V. How to Make Choices Between Solutions
Design often requires choosing one among several solutions; NNGroup provides a 6-step decision method:
| Step | What to do | Action suggestions / counterexamples |
|---|---|---|
| 1 Clarify goals | List user goals / business goals / project constraints (time, budget, resources) | For beginners → prioritize ease of use; for advanced users → prioritize efficiency and feature depth |
| 2 Balance conflicting points | UX is full of opposing needs that require tradeoffs | UI vs UX, general users vs advanced users; use user segmentation to set weights — optimize simple workflows for 69% regular users, while retaining advanced entry points for 5% advanced users |
| 3 Data-driven | Quantitative data provides metrics (completion time/number of clicks), qualitative data provides reasons/emotions | If two solutions are hard to distinguish by features → choose the one with the highest satisfaction; if one is easier to use and the other is more comprehensive → weigh tradeoffs according to priorities |
| 4 Adjust dynamically | Decision criteria change with the project | Large projects use systematic processes (full research + prototypes + iteration); small projects launch quickly and then optimize based on feedback |
| 5 Focus on long-term impact | Evaluate from a holistic perspective, don’t only look at the short term | "The London Underground example: early design has a profound impact on subsequent experience — invest extra time early to ensure the architecture/direction is correct, don’t compromise core needs for short-term gains |
| 6 Grasp key decision criteria | Know when to let go of details | First set 1–2 key criteria (ease of use or feature coverage), move forward quickly around core priorities, don’t get stuck in endless comparisons |
Mindset (the attitude that appears repeatedly throughout the set): "The simple thing about UX is — when facing a single project, you only need to make clear decisions and execute quickly, rather than obsessing over every problem." Decision paralysis itself is an anti-pattern.
VI. The 10 Usability Heuristics (Index, see the dedicated article for the full table)
The 10 design rules of thumb proposed by Jakob Nielsen in 1994 design heuristics(heuristic = a rough, practical rule of thumb that tells you “where to look” but does not make decisions for you); it serves both as a self-check checklist during the design phase and as the basis for experts conducting “heuristic evaluation”:
| # | Heuristic (EN / CN) | One-sentence explanation + real-life analogy |
|---|---|---|
| 1 | Visibility of System Status | Let users know what the system is doing at all times (the “You Are Here” marker on a mall map) |
| 2 | Match Between System & Real World | Use words and conventions familiar to users (stove knobs arranged to match the positions of the burners) |
| 3 | User Control and Freedom | Provide “emergency exits” for undo/redo/exit (emergency exits in public places) |
| 4 | Consistency and Standards | The same things should mean the same thing (hotel front desks are always near the entrance) |
| 5 | Error Prevention | The best error message is one that stops the error from happening in the first place (highway guardrails) |
| 6 | Recognition Rather than Recall | Keep information visible; don’t force users to remember (“Is Lisbon the capital of Portugal?” is easier to answer than “What country is Lisbon the capital of?”) |
| 7 | Flexibility and Efficiency | Accommodate novices while also providing accelerators for experts (locals taking shortcut routes) |
| 8 | Aesthetic and Minimalist Design | Only include information relevant to the task (a functional teapot vs. a showy, impractical teapot) |
| 9 | Help Users Recognize/Diagnose/Recover from Errors | Error messages should clearly state what went wrong, why, and how to fix it, instead of just dumping “Error 404” on users |
| 10 | Help and Documentation | Ideally users should not need it, but for complex interfaces it must be searchable, task-focused, and provide concrete steps (airport information desks) |
For the full detailed table of “core principles + Do/Don’t + counterexamples + version for complex enterprise applications”, as well as usability testing methods (the 5-user rule, recruitment, remote testing, task design, data analysis), see the dedicated article NNGroup Usability Testing and the 10 Usability Heuristics (full table of 10 heuristics · application to complex apps · user delight hierarchy · testing methods: 5-user rule/recruitment/remote testing/task scenarios/step-by-step tasks/attitude vs. behavior/4-step analysis/small-sample bias/competitive evaluation)—this article will not repeat that content in depth.
VII. UX Career Advancement: Entry / 5 Stages / Portfolio / Resume
7.1 How to Start a New Career in UX (Jakob Nielsen) — Two Paths
| Your situation | Strategy | Key actions / counterexamples |
|---|---|---|
| Already employed | Gradual transition, no need to change jobs immediately | ① Start with a small 5-person user test (low cost, no special permissions needed) → ② Do more UX work in your next project → ③ Gradually become the in-house UX authority at your company |
| New graduate / career changer | Join a mature UX team | Choose a company with multiple UX professionals, mature methodologies, a dedicated UX manager (who can shield you from external questions like “is UX important?”), and ample learning opportunities.Counterexamples (to avoid): Startups with no UX team — you will lack guidance, easily fall into self-teaching and fending off skepticism, with the risk of “growing into an unprofessional practitioner via unorthodox, self-taught methods” |
7.2 The 5 Stages of UX-Career Progression
Career growth is nonlinear, but there are identifiable levels:
| Stage (EN / CN) | Definition | Main challenges | Growth path |
|---|---|---|---|
| Novice | New to UX, with no formal training/practice (students/recent graduates/career changers) | Difficulty putting theory into practice, difficulty gaining user insights, insufficient collaboration skills | Participate in small end-to-end projects, find a mentor, take diverse courses |
| Contributor | Understands basic principles,completes tasks under supervision (1–3 years) | Time/priority management, digesting feedback, communicating with stakeholders | Proactively ask for targeted feedback, learn from colleagues, deepen expertise in one specific skill |
| Practitioner | Able to complete projects independently and apply methods flexibly (mid-level) | Balancing user needs and business goals, understanding technical constraints, synthesizing research themes, avoiding overly rigid processes | Lead projects to build leadership skills, deepen expertise to become a specialist, adjust processes as needed |
| Specialist | Deep expertise in one area, able to influence team UX strategy | Limited skill expansion, difficulty understanding the perspective of junior practitioners | Mentor newcomers, share in the community, learn skills outside your specialty |
| Visionary | Influences the future of the UX industry (author/speaker/field leader) | Staying relevant, avoiding burnout (fatigue from repeating the same message) | Collaborate with others to expand impact, continuously learn new trends, test existing practices in new environments |
4-step self-assessment: ① Analyze growth attributes (hard skills = tools/methods vs. soft skills = communication/storytelling/problem-solving); ② Conduct a career SWOT analysis; ③ Seek feedback from colleagues/managers/mentors; ④ Set goals and align them with new opportunities.
7.3 Top 10 Researcher Portfolios (Portfolios for UX Researchers)
Build your portfolio the way you do UX:Audience-centered, content over visuals.
- Understand your audience — hiring managers want to know what research you do/how you solve problems/whether you can deliver results;Content > visual trends; highlight your real contributions within the team.
- Curate selected projects — only include 3–5, sorted by impact > methodological rigor > recency, to avoid information overload.
- Show the right documentation — process artifacts (research plans, usability test tasks, early sketches, wireframes, interview/test session quotes) + outcome artifacts (affinity diagrams, storyboards, report/presentation excerpts).
- Explain context and team — goals/timeline/user types/key findings + your role and the parts you were directly responsible for + cross-functional collaboration (name and thank specific colleagues).
- Show breadth — qualitative + quantitative, large projects + guerrilla small studies, independent work + collaboration.
- Communicate clearly — use plain language, avoid jargon; your audience may be non-UX managers.
- Summarize key findings — focus on 1–2 most critical findings + data visualizations + answer “why this matters.”
- Demonstrate value — quantify outcomes (reduced support calls/lower bounce rate/increased conversion) + before-and-after user feedback + how the research drove key decisions.
- Acknowledge constraints — admit limitations of budget/small samples/convenience samples, explain what you would do with sufficient resources;Handling NDAs: de-identify sensitive information, ask clients for permission to share partial content or cite recommendation letters.
- Iterate continuously — update regularly, seek feedback, treat your portfolio as a living document.
7.4 Portfolios and Interviews (UX Portfolios: Preparing for Interviews)
- Don’t be overly detailed: information overload during application will make hiring managers miss key content;leave white space for questions and expansion during the interview.
- Don’t read your portfolio verbatim in the interview: select 1–2 key projects to talk in depth about your unique contributions and behind-the-scenes details (project complexity + your solution approach).
- Tell the story behind the case studies: hiring managers care more about your thinking process and way of working — share innovative attempts (how you adapted new technologies/frameworks), challenges and solutions, decision-making processes, and how you collaborated with the team, so interviewers can “feel what it’s like to work with you.”
- Present with confidence: carefully prepare several case studies + a few interesting project stories (demonstrating innovation or problem-solving ability) + clearly explain the specific advantages you can bring to the team.
7.5 Resumes (General Tips for Career Changers + Students/Graduates)
First understand how hiring managers read resumes (behavioral facts determine all formatting choices):
- They spend only 6–7 seconds on average scanning, focusing on headings and high-priority information;
- They commonly use Applicant Tracking Systems (ATS) — complex layouts like tables and multi-column formats will cause ATS parsing errors;
- They value team collaboration and interpersonal skills;
- They remain overly sensitive to “short tenure” (even though research shows short tenure has no correlation with future performance).
General formatting rules (work for both groups):
| Rule | Key points |
|---|---|
| Format | Provide both PDF + Word — PDF for human readers, Word for ATS parsing |
| Page count | One page (unless you have 20+ years of experience) |
| Margins/fonts | Margins of 0.5–0.75 inches; safe serif/sans-serif fonts, font size 10–12 points, do not use decorative/wide-spaced fonts |
| Layout | Keep it simple —avoid headers/footers, tables, multi-column layouts (ATS killers) |
| Ordering | Chronological reverse order, most recent first; consistency (match LinkedIn/portfolio); printable; zero typos;Truthful information (falsification will always be discovered) |
Core sections to include: contact information (you may use initials for your name to reduce bias, city + state + zip code is sufficient, short portfolio link, professional email address, clear voicemail greeting), UX experience, UX education, non-UX experience/education (reframe transferable skills).
Quantify achievements using this formula:[动词] [定量结果] [背景] 使用 [技能/工具/技术]. Examples: “Increased e-commerce conversion rate by 10% via Figma prototypes and A/B testing”; “Assisted the bank website team in conducting 32 sessions of user interviews.”
Things to absolutely exclude (counterexample list):
- Skill/technology lists — cannot prove ability without context;
- Skill proficiency charts/bar graphs — highly subjective, wastes space (NNGroup’s exact words: self-rated skills are “highly subjective and lack information about where and how the skill was used”);
- Photographs — trigger unconscious bias;
- Objective Statement — redundant, unpersuasive;
- Project details — save those for your portfolio;
- (Additional for student versions) High school and earlier education, hobbies (unless relevant to the profession), reference information.
Differentiated strategies for the two groups:
| Career Changer | Student/Graduate | |
|---|---|---|
| Where experience comes from | Accumulate UX experience through internships/volunteer projects/freelance work; reframe past work from a UX perspective, highlight transferable skills | Highlight academic background, extracurricular activities, internships; do not use filler content |
| Employment gaps | Use “year/month” to summarize durations to reduce the visibility of gaps; if unavoidable, explain how you used the gap to improve your skills | —— |
| Professional email (avoid outdated domains like AOL) | recommended.edu.edu email (research shows it is viewed more favorably by hiring managers), remember to switch after graduation | |
| Bonus points | Targeted, concise, customized (tailored to the position) | High GPA (especially in UX courses), above-and-beyond work experience, extracurricular leadership (ACM SIGCHI / UXPA / HFES), professional network;Resume ≠ academic CV (do not use an academic CV to apply for industry roles) |
Scope reminder: these recommendations are primarily for North American internship/job applications; resume conventions in other regions may differ.
Sourced from NNGroup Topics / UX Basics - UX Fundamentals (19 articles). The complete core methods/Do-Don’t/complex application version of the 10 heuristics + usability testing methods (5-user rule/recruitment/remote testing/task design/data analysis/competitive evaluation) can be found in NNGroup Usability Testing and the 10 Usability Heuristics (complete table of the 10 heuristics · application to complex use cases · user delight hierarchy · testing methods: 5-user rule/recruitment/remote testing/task scenarios/step-by-step tasks/attitude vs. behavior/4-step analysis/small-sample error/competitive evaluation); for the essence/types/creation of Personas and comparison with tools like JTBD, see NNGroup Personas (essence/three types/scope hierarchy/creation/comparison with JTBD-prototypes-segmentation/application/maintenance/5 major failure modes). Images (3D framework diagram of research methods, product triad Venn diagram, design thinking cycle diagram, resume examples, quantitative method illustrations, heuristic real-life analogy diagrams, etc.) and original documents are retained in sources.
Sources and Related Materials
- NNGroup Usability Testing and the 10 Usability Heuristics (complete table of the 10 heuristics · application to complex use cases · user delight hierarchy · testing methods: 5-user rule/recruitment/remote testing/task scenarios/step-by-step tasks/attitude vs. behavior/4-step analysis/small-sample error/competitive evaluation)
- NNGroup Personas (essence/three types/scope hierarchy/creation/comparison with JTBD-prototypes-segmentation/application/maintenance/5 major failures)