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 252
Clickstream Analysis: Following the User's Footsteps
Clickstream analysis is like watching a replay of a user's journey through your site, click by click. It's used to optimize conversion funnels and find friction points. The footgun is focusing on the *what* (the path) without asking *why* a user took it.
Survey Response Bias: When Answers Mislead
Survey answers aren't raw data; they're filtered through human psychology. Response bias describes the predictable ways people answer inaccurately, common in user surveys and market research. The footgun is taking responses at face value, ignoring biases.
Customer Effort Score (CES): Measure Task Friction
Customer Effort Score (CES) measures how much work a customer expends to complete a task. It answers 'How easy was it?' right after a support interaction, purchase, or onboarding.
P-Value: Gauging Surprise, Not Certainty
A p-value measures surprise: it's the probability of seeing your results by chance, assuming your change had no effect. It's used in A/B testing to decide if an effect is noise or significant. A small p-value doesn't prove your hypothesis is true.
Heatmaps: Visualizing User Attention
Think of a heatmap as a weather map for your app, showing 'hot' spots of user clicks and 'cold' spots they ignore. It reveals if users are clicking key buttons or getting distracted. The footgun: a hot spot can mean rage-clicks, not just engagement.
CSAT: Measuring If You Met Customer Expectations
CSAT measures if your product met a customer's expectations for a specific interaction. It's used to evaluate experiences like a support call or purchase, giving a direct pulse check on service quality.
Likert Scale: A Ruler for Opinions
A Likert scale turns subjective feelings into data by asking users to rate their agreement with a statement on a balanced scale. It's used in UX surveys to gauge attitudes.
Pluralistic Walkthrough: Diverse Roles, One User Task
A pluralistic walkthrough is a group critique where developers, users, and UX pros role-play as end-users to find flaws in a design. It's used early to catch issues cheaply. The footgun is letting developers defend their work instead of listening.
GOMS Model: Predicting User Performance as a Script
The GOMS model predicts expert user performance by breaking down tasks into a script of Goals, Operators, Methods, and Selection rules. It's used to get quantitative estimates of task efficiency, but its footgun is assuming a perfect user who never makes…
Eye Tracking: See What Your Users Actually See
Eye tracking reveals what users actually look at, not just what they say they do. It's used in UX to generate heatmaps showing which UI elements draw the eye. The footgun: a long gaze can mean interest, but it can also mean confusion.
Desirability Testing: Quantifying User Feelings
Desirability testing quantifies user feelings with a controlled vocabulary, asking them to pick words from a list that describe a design. It measures emotional response to visual appeal or UX, often with just a screenshot.
Cognitive Walkthrough: See Through a New User's Eyes
A cognitive walkthrough is like role-playing a new user trying a specific task for the first time. It finds usability flaws early by simulating a first-time user's journey. The footgun is confusing it with a holistic review; this method is for specific tasks.
Tree Testing: Validate Your Site's Navigation Structure
Tree testing validates your site's navigation by asking users to find items in a text-only hierarchy. It's used to test a proposed information architecture before any UI is built. The footgun is confusing it with card sorting, which creates a structure.
First Click Testing: Predicting Task Success with One Click
First Click Testing predicts if users can complete a task by tracking where they'd click first on an interface. If the first click is right, success is far more likely. It's used to validate navigation and UI clarity. The footgun is a poorly phrased task.
Task Analysis: Mapping User Goals to Actions
Task analysis maps the specific actions (tasks) a user takes to achieve their larger objective (goal). It's used to ensure a product actually helps users, not just creates busywork. The key mistake is designing for the task instead of the user's true goal.
Think Aloud Protocol: Hear Your User's Inner Monologue
See your product through a user's eyes by having them narrate their thoughts live during a task. It's used in usability testing to uncover confusion, mismatched expectations, and the "why" behind clicks.
Cultural Probes: Inspire, Don't Analyze
Cultural probes are like a creative care package for users, designed to capture inspirational moments, not to collect analyzable data. They help designers understand a user's world and values early in a project.
User Mental Models: What Users Believe About Your System
A user's mental model is their internal story of how your system works, based on belief, not facts. It shapes every interaction, from predicting button actions to checkout flows.
Participatory Design: Designing With, Not For, Users
Participatory design means designing *with* users as co-creators, not just *for* them. It's used in software, architecture, and urban planning to ensure the final product truly fits the community.
Open Card Sorting: Map Your User's Brain
Open card sorting reveals how users mentally group your content. You give them topics on cards and ask them to sort them into groups they create and name. It's ideal for designing intuitive navigation.