Intermediate concepts in Design & UX, page 12
Figma Pages: The Folders Inside Your Files
Think of Figma pages as folders within a single file. They let you organize complex projects by giving you separate canvases for different design stages, user flows, or component libraries. The main footgun: free plans limit you to only three pages per file.
Reduce Time-to-Market with a Design System
A design system is a shared toolkit of pre-built UI components, not just a style guide. It lets teams build interfaces from a library of pre-coded parts, drastically cutting repetitive work. The footgun is treating it as a static document, not a living system.
Participant Communication Strategy: The Pre-Session Bias Shield
Participant communication shapes data quality before sessions start. It is vital in remote or longitudinal studies where you cannot course-correct live. Oversharing study goals in recruitment emails primes rehearsed answers and destroys validity.
Figma Permissions Cascade Downward
Figma permissions flow downward: team access opens every project and file inside it. Use share links for quick reviews, but direct invites gate specific files. Inviting someone to a team exposes every project, while a file invite keeps the rest hidden.
Figma's Library Analytics API: Quantify Your Design System's Impact
Figma's Library Analytics API lets you quantify your design system's impact by tracking component usage. Use it to find adoption trends or get a snapshot of where components are used. The footgun: data for files you can't access is obfuscated, not omitted.
No-Show Management: Research Calendar Insurance
No-show management treats research calendars like airline seats: you expect flakes and overbook so one absence doesn't ground your sprint. It is vital for moderated sessions with hard-to-recruit users.
Design Token Transformation: One Source for All Platforms
A design token standard is a universal adapter for your style. It defines properties like color in a standard JSON format, which tools then transform into platform-specific code for iOS, Android, and web. The footgun is building bespoke transformation logic.
Niche UX Recruiting Is Targeted Diplomacy
Niche recruiting trades reach for precision. You need it when studying tacit knowledge like enterprise admin workflows. The footgun is screening for demographics instead of domain depth, which fills sessions with imposters who teach you nothing.
Motion Tokens Turn Timing into a System
Motion tokens standardize animation like color tokens standardize palettes. A team can retime an entire product from one file. The footgun is naming tokens after CSS curves instead of intent, locking implementation details into your design language.
Figma Variables: Grouping Primitives with Collections
Think of Figma variables as raw ingredients. A collection is a recipe book ('Spacing') and modes are variations ('Mobile'). This lets you manage design tokens, themes, and responsive layouts.
Shadowing Reveals What Users Actually Do
Shadowing follows users in real tasks to catch where stated behavior diverges from reality. Deploy it when workflows cross tools, rooms, or teams and interviews miss the real friction. Your presence changes behavior; filter genuine habits from performance.
Elevation System: Height as a Token
Elevation is spatial height, not just shadows: it maps every surface to a specific z-height. Use it for modals, dropdowns, and draggable cards. The footgun is tuning shadows without locking z-index, so visually higher elements still get buried.
JTBD Interview: Map the Job, Ignore the Persona
A JTBD interview reconstructs when a user fires one solution and hires another for progress. Use it to discover causal forces, not preferences. The footgun is profiling demographics instead of the struggle that triggered change.
Card Pattern: Self-Contained Content Objects
A card groups related info into a bounded, scannable object you can rearrange like playing cards. Use it for dashboards, product grids, or feeds where items need equal visual weight.
Fair Use: Using Copyrighted Work Without a License
Fair use is a legal defense, not a right, allowing unlicensed use of copyrighted work for criticism, commentary, or education. It's essential for reviews or tutorials.
Usability Benchmarking: Quantifying Product Friction
Usability benchmarking is a fitness tracker for your product: you measure task success against a baseline or competitor to prove changes reduce friction. Use it to justify redesigns, but the footgun is testing too few users and mistaking noise for trend.
Dashboard Layouts: Information Architecture, Not Just Grids
A dashboard layout is an information hierarchy, not grid; it controls what users see in first three seconds. Use it for monitoring and admin panels where users scan for anomalies. Biggest mistake is filling every pixel with widgets, destroying glanceability.
Figma: Local vs. Published Library Assets
Local Figma assets are private drafts; published assets are the team's shared toolkit. Use this to manage a central design system, but remember: if you don't publish your changes, your team will be using outdated components and variables.
Creative Commons: Granting Permissions Beyond 'All Rights Reserved'
Creative Commons licenses provide a standard way to grant permissions for your work, moving beyond copyright's 'all rights reserved' default. They're used on platforms like Wikipedia and Flickr to allow sharing while defining terms.
Saturation: When to Stop Interviewing
Saturation is when new interviews stop yielding fresh themes, like wringing a dry towel. It gives UX researchers a data-driven stopping rule instead of an arbitrary quota. The footgun is claiming it after only talking to lookalikes who share the same context.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles