Intermediate concepts in Design & UX, page 6
Inferential Statistics: From Sample to Population
Inferential statistics turns a small user sample into a claim about millions: you test hypotheses and estimate population properties without measuring everyone. The footgun is forgetting your data is just a sample and declaring truth about all users.
Accessible Form Design: A Conversation, Not an Interrogation
Think of a form not as a data bucket, but a structured conversation. Every field is a question needing a clear prompt. This is vital for logins and checkouts, especially for users with screen readers. The footgun: using placeholder text as a label.
T-test: Are Two Groups Actually Different?
A t-test asks whether the gap between two groups is a real signal or just sampling noise. UX researchers use it to compare task times or conversion rates between designs. The footgun is trusting results from tiny samples where the math gives false confidence.
Touch Target Size: Bigger is Better, Spacing is Key
A button's clickable area is more than its visible pixels; it includes the space to avoid fat-fingering neighbors. WCAG requires targets to be at least 24x24 CSS pixels for users with motor impairments.
Double Opt-In: Confirming User Consent
Double opt-in confirms a user wants your emails by making them click a confirmation link after signing up. This ensures the person owns the email address and truly consents, unlike opt-out methods which are often considered spam.
Branding Your Design System for Adoption
Treat your design system as an internal product. Give it a brand—a mission, vision, and narrative—to drive adoption and ensure consistency. This aligns teams on the 'why' behind the components, not just the visual rules.
Email Marketing: A Conversation, Not a Megaphone
Email marketing uses email to nurture customer relationships, not just to send ads. It aims to build loyalty, acquire new customers, and drive sales by sending targeted commercial messages. The footgun is treating every email as a hard sales pitch.
HMW Questions: From Research Insights to Design Ideas
HMW questions turn research insights into open design challenges that keep ideation focused on real user problems. Teams use them after discovery to prevent pet solutions.
Drip Campaigns: Automated, Triggered Conversations
A drip campaign is an automated conversation, sending pre-written messages over time based on user actions. It's used for onboarding new users or re-engaging inactive ones.
UX Highlight Reels: Show, Don't Tell
A highlight reel is a shortcut to empathy: short clips that make stakeholders feel the problem. Use them to win executive buy-in when charts fail to stick. The footgun is curating only positive clips; without struggle it reads as marketing, not research.
Welcome Email Series: Turn Signups into Customers
A welcome series is an automated email sequence that acts as a guided tour for new subscribers. It's used by e-commerce and SaaS to build trust and drive initial sales or activation. The biggest footgun is sending a single, generic email and stopping there.
Exposure Hours
Exposure hours measure the time each team member spends directly observing real users. Research by UIE found teams that watch users at least two hours every six weeks make markedly better design decisions, because firsthand empathy beats secondhand reports.
Abandoned Cart Sequence: Recovering Lost Sales
An abandoned cart sequence isn't just one email; it's a timed, multi-step campaign addressing different reasons for leaving. It's the highest-converting automation for e-commerce, moving from a simple reminder to reassurance, and finally, an incentive.
Figma Dev Mode: From Design to Code Snippets
Figma's Dev Mode translates designs into code snippets, not just redlines. Select an element to get CSS, Swift, or Android XML with layout and style properties. The footgun is relying on this starter code; use Code Connect to link to your real design system.
Email Personalization: Beyond the First Name
Email personalization uses automation to send the right message to the right user. By segmenting your audience based on behavior or data, you can target them with relevant content, like abandoned cart reminders.
Figma's Handoff Status: A Traffic Light for Devs
Think of Figma's handoff status as a traffic light for your designs, signaling what's safe to build. Designers mark sections Ready for dev, and Figma automatically flags them as Changed if modified.
Component Coverage: The 80/20 Rule for Design Systems
Component coverage applies the 80/20 rule to your UI, measuring what's built from a design system versus custom code. It helps track adoption and justify freeing up dev time for unique features.
Figma for VS Code: Designs Inside Your Editor
Embed a live Figma inspector in your IDE to stop switching contexts. Use it to grab code snippets, check measurements, or reply to comments without leaving VS Code. The footgun: it's for inspection, not editing—you can't change the design itself.
How Design Systems Lower Your UI Bug Rate
A design system is a factory for pre-tested UI parts. By using standardized components instead of hand-crafting them each time, you reduce one-off bugs. This is a key metric for proving a design system's ROI, but teams often fail to track it.
Component Detachment Rate: A Design System Health Metric
Component Detachment Rate is a design system health metric, like customer churn. It tracks how often designers must break a component's link to its source to make custom changes, signaling that the component is too rigid or lacks needed variants.
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