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 254
UX Ethics: A Professional Code of Conduct
UX ethics formalizes your responsibility to users. It's about centering human well-being, being transparent with data, and actively preventing harm. This guides decisions from research to launch.
Formative vs. Summative Evaluation: Improve vs. Judge
Formative evaluation improves a design in progress; summative evaluation judges a finished one. Use formative tests to find and fix flaws iteratively. Use summative tests to measure a shipped product against a benchmark, like a prior version or a competitor.
Jobs to Be Done: Sell the Hole, Not the Drill
The Jobs to Be Done framework says customers 'hire' products to get a job done. Instead of selling a drill, sell the quarter-inch hole. This reframes innovation around stable customer needs, not temporary product features.
Double Diamond: Explore, Then Focus, Twice
The Double Diamond model prevents building the wrong thing by forcing two cycles of 'go wide, then narrow down.' First, explore the problem space, then define a specific problem. Second, explore solutions, then deliver a tested one.
UX Research: Building for Real People, Not Assumptions
UX Research is about watching what people *do*, not just what they *say*, to build products that solve their actual problems. It's used to design everything from websites to medical devices, guiding development with real user feedback.
User Flow Diagrams: Mapping the Path to 'Done'
A user flow diagram maps the exact steps a user takes in your app to complete one task. It aligns teams on product goals and gives developers a visual guide, preventing confusion and rework. The footgun: it's not a customer journey, which is far broader.
Realistic UI Motion with Easing Curves
Easing curves control animation acceleration to make UI motion feel natural, not robotic. Use 'Ease Out' for elements entering the screen and 'Ease In' for those leaving. The footgun is overusing one curve; this makes motion feel unnaturally perfect.
Figma Widgets: Live Apps on Your Canvas
Figma Widgets are like mini-apps living on your canvas that everyone interacts with at once, unlike single-user plugins. Use them for collaborative tools like live polls or data tables.
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.
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.
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.
Figma Comments: Your Team's Built-in Critique Layer
Think of Figma comments as a critique layer on your design. They tie feedback directly to specific elements for asynchronous review, letting you iterate faster without constant meetings. The footgun: Over-mentioning creates notification fatigue.
Real-time Collaboration: Figma's 'Multiplayer' Model
Real-time collaboration uses a central server as the single source of truth for a file. Instead of passing copies, users connect to the same live document, enabling simultaneous editing in tools like Figma.
Figma Comments: Annotate Designs for Better Handoff
Figma comments are the inline documentation for your designs, bridging the gap between a static screen and its intended behavior. Use them to clarify interactions and edge cases directly on the canvas. The footgun is assuming the design speaks for itself.
Design System Docs: The Product, Not the Afterthought
Treat your design system documentation as a product, not a cleanup task. It's the instruction manual that prevents your component library from being misused. It's essential for scaling a design system to ensure consistency and speed up onboarding.
Drive Design System Adoption, Don't Just Build It
Treat your design system like an internal product, not a one-off project. To drive adoption, show quick, measurable wins and offer tiered onboarding for different roles.
Versioning a Design System with Semantic Versioning
Use Semantic Versioning (MAJOR.MINOR.PATCH) to signal the impact of design system changes. This tells teams if an update is a breaking change (MAJOR), a new feature (MINOR), or a bug fix (PATCH).
Design System Governance: Preventing UI Drift
Design system governance is the constitution for your UI, defining how components evolve, not just what they are. It prevents the slow drift where production code diverges from the Figma library as teams make local exceptions.
Prototype Animations: Guiding Users Between States
Think of prototype animations as visual storytelling, showing the relationship between a user's action and the resulting UI state. Use them to show menus expanding or pages sliding in.
Prototype Triggers: Defining How Users Interact
A prototype trigger is the 'if' in an 'if-then' UI interaction, defining the user input that causes a change. It's used in design tools to simulate app behavior, from clicks to drags.