All bites
The whole library, newest first. Filter by what you are here for, or pick a topic if you already know.
8668 bites
Page 107
Screening UX Research Candidates
Screening surveys separate real users from professional testers and biased insiders before they skew your research. Without manual vetting of screener answers, convenience samples and speedrunners still pollute your design decisions.
UX Roadmap: Strategic Alignment for Research Teams
A UX roadmap trades plans for alignment, mapping work across Now, Next, and Future horizons so teams share one North Star. Use it to justify research spend and prevent silos. The footgun is treating it as a static handoff instead of a living ritual.
Shopify's 0% to 100% Fix: Design Dialects Over Rigidity
Shopify Polaris hit 0% completion for gloved warehouse pickers until a dialect with 90px targets and dark UI hit 100%, cutting onboarding from three weeks to one shift. Atlassian formalized this into a three-tier Flexibility Framework. Rigid systems break.
Vienna Circle Café Culture Holds Web Civility Lessons
Vienna Circle's 1928-34 meetings kept Gödel and Wittgenstein productive despite vicious feuds. Leader Moritz Schlick and lingering-friendly cafés turned conflict into collaboration.
8 Free Personas Spot Accessibility Issues in Design
8 free accessibility personas shift designer burden from memorizing WCAG to recognizing exclusion during work. Applying Nielsen's heuristic #6 to creators means fewer bad websites from good designers. Add them to your design critiques this sprint.
How would you architect Figma for multi-platform, multi-team products?
This tests design-ops systems thinking at scale. A strong answer outlines a tiered library model: platform-agnostic primitives, platform-specific components, and team files consuming shared libraries, plus governance for breaking changes.
How would you structure design and Figma for phased rollout?
This tests whether you can architect Figma for parallel flag rollouts. A strong answer covers branch pages, versioned components tied to code flags, and a cleanup timeline. A red flag is a single-file replacement or big-bang launch with no coexistence plan.
Describe your process for preparing a high-fidelity Figma file for developer handoff
Tests operationalizing the design-engineering boundary. Strong answers cover file structure, auto-layout tokens, responsive annotations, all UI states, and exported assets with naming conventions.
How do you handle a technically complex interaction and propose Figma alternatives?
Cross-functional negotiation and rapid prototyping under constraint. Defer judgment, quantify delay, co-define success, then use Figma variants and low-fi prototypes to test trade-offs. Never sacrifice UX before grasping engineering effort or business impact.
First Figma steps to turn a brief into low-fi concepts
This tests whether you structure IA before pixels. Strong answers audit the brief, map flows with simple frames, block out grayscale wireframes at target breakpoints, and annotate for async review. Red flag: jumping straight to components or color.
How would you architect interdependent filter variables in a complex dashboard?
Tests reactive variable graphs, not interaction tangles. Strong answers centralize Figma variables, bind component properties to them, and chain conditional actions to derive downstream state. Red flag: duplicating frames instead of using variables and logic.
Describe how you would use variables and conditional logic to simulate input validation
Tests dynamic state management in Figma prototypes. Strong answers use a string variable bound to the password field, check length on submit, and conditionally route to error or success. Red flag: hardcoding static frames without variables.
How would you structure variables and expressions for a price configurator?
This tests reactive state modeling in Figma. A strong answer uses a string variable for the base model and booleans for add-ons, binding the price text to an expression that maps the base to its cost and sums active extras.
How would you use variables to calculate a real-time cart subtotal?
This tests reactive state in Figma using variables and expressions. Strong answer: store quantity in a number var, wire to a stepper, compute subtotal as qty times 25, and bind that to text. Red flag: static text or manual updates instead of live computation.
Build a Figma toggle switch that controls element visibility using variables
Tests prototype state management with Figma variables instead of frame duplication. A strong answer names a boolean variable, binds it to layer visibility, and wires an On click Set variable action. Red flag: suggesting frame duplication over variable state.
Monolithic or multiple libraries for cross-platform design system?
This tests cross-platform design system architecture. Pick multiple interconnected libraries, centralize tokens in a shared primitive layer, and branch platform components downstream. Red flag: one monolithic file ignoring native rendering constraints.
How do you merge a Figma branch and resolve component conflicts?
Review main changes, open conflict picker, compare side-by-side, accept or blend component edits, publish library updates.
How would you structure file covers and naming to communicate design status
Tests self-serve design ops for cross-functional partners. Strong answers cover color-coded covers, prefixed names with status and version, and role-based permissions. Red flag: relying on Slack updates instead of file-based clarity.
How do you update a component in a published Figma team library?
Edit main, publish with notes, consumers get update alerts, review or bulk-accept, verify overrides.
How do you structure Figma pages for a new project and handoff?
What it tests: systems thinking and empathy for cross-functional workflows. A strong answer names a Cover page, separate WIP and Handoff pages, and a linked component library with consistent naming.