By Fatskills Exam Guides Team — the exam nerds behind 28,500+ quizzes and 2.1M practice questions across 500+ global exams.
(For aspiring product designers, graphic designers transitioning to UX, and bootcamp students)
Staying current in UX means continuously learning from trusted sources (like NN/g, Smashing Magazine, and the Figma Community) to design products that are usable, accessible, and delightful. It’s not just about trends—it’s about applying evidence-based principles to solve real problems.
Example: A hospital’s patient portal has a 40% drop-off rate during appointment booking. By studying NN/g’s research on form design and Smashing Magazine’s accessibility guidelines, you redesign the flow with progressive disclosure (showing only essential fields first) and clear error messaging, reducing drop-offs by 25%.
Jakob’s Law (Consistency): Users expect interfaces to work like others they’ve used. Example: Placing a shopping cart icon in the top-right corner (like Amazon) instead of inventing a new location.
Hick’s Law (Decision Paralysis): The more choices a user has, the longer it takes to decide. Example: Netflix’s "Top Picks for You" row (limited options) vs. a grid of 50 movies.
Progressive Disclosure: Showing only essential info first, revealing details as needed. Example: A "Show More" button in a product description instead of dumping all specs upfront.
Heuristic Evaluation (NN/g’s 10 Usability Heuristics): A quick way to find usability issues by comparing a design to best practices. Example: Checking if error messages are clear and actionable (e.g., "Password must be 8+ characters" vs. "Invalid input").
Design Systems: A single source of truth for UI components, patterns, and guidelines. Example: Shopify’s Polaris system ensures consistency across their admin dashboard.
WCAG (Web Content Accessibility Guidelines): Standards for making digital products usable for people with disabilities. Example: Ensuring text has a 4.5:1 contrast ratio (e.g., dark gray text on a light gray background fails).
Micro-interactions: Small, functional animations that improve feedback. Example: A "like" button that fills with color and bounces when tapped.
Guerrilla Testing: Quick, informal usability tests with 3–5 users. Example: Testing a Figma prototype on coworkers in a coffee shop.
Dark Patterns: Deceptive UI tricks that manipulate users. Example: A "Free Trial" button that auto-enrolls users in a paid plan unless they opt out.
Figma Community: A hub for free, reusable design files (e.g., UI kits, plugins, templates). Example: Downloading a mobile banking UI kit to speed up wireframing.
Design Thinking (Empathize → Define → Ideate → Prototype → Test): A problem-solving framework. Example: Redesigning a food delivery app by interviewing users (Empathize), defining pain points (e.g., "Users struggle to find dietary filters"), then prototyping solutions.
Affordance: A design element that suggests its function. Example: A 3D button that looks "clickable" vs. a flat, ambiguous shape.
Figma Action: Create a "UX Resources" file with links to articles, plugins (e.g., A11y Color Contrast Checker), and templates.
Apply Research to Real Projects
Figma Action: Use variants to test different button placements (e.g., "Buy Now" at the top vs. bottom of a product page).
Join the Community
Figma Action: Duplicate a popular UI kit (e.g., Material Design) and modify it for your project.
Test Your Knowledge
Figma Action: Use the Figma Mirror app to test prototypes on your phone.
Document Your Learning
Portfolio Tip: Include before/after comparisons (e.g., "How I reduced drop-offs by 30% using progressive disclosure").
Explain Your "Why" with Principles
Tricky Distinction: Heuristic Evaluation (quick expert review) vs. Usability Testing (observing real users).
Talk About Failures (And What You Learned)
Tricky Distinction: Design System (components + guidelines) vs. Style Guide (colors, typography).
Use the STAR Method for Behavioral Questions
Answer: Use Hick’s Law ("More choices = slower decisions") and Jakob’s Law ("Users expect familiar patterns"). Propose A/B testing the button in a less prominent spot (e.g., bottom-right corner) or using a sticky widget that appears only after scrolling.
Scenario: You’re designing a form, and the PM insists on making all fields required. How do you advocate for a better user experience?
Answer: Cite NN/g’s research on form design (users abandon forms with too many required fields). Propose progressive disclosure (e.g., "Billing address same as shipping? [Yes/No]") or lazy validation (only show errors after submission).
Scenario: Your team wants to add a complex animation to a "Submit" button. How do you decide if it’s worth it?
Final Tip: Bookmark this guide, but apply one principle per project. Mastery comes from doing, not just reading. ?
Join 4M+ learners. Unlock unlimited quizzes, wrong-answer tracking, flashcards + reminders, study guides, and 1-on-1 challenges.