Intermediate concepts in Design & UX, page 14
Components: One Master, Many Instances
A component is a master spawning linked copies; edit it and all copies update instantly. Use them for buttons and cards that repeat so one edit flows everywhere. Detach instances or override everything and you kill reusability, forcing manual fixes.
Federated Docs: One Hub, Many Authors
A federated documentation strategy treats your design system docs like a network, not a monolith. Each team maintains docs in their own repo, and a central hub aggregates them.
Automated Release Pipeline
An automated release pipeline turns merged design-system changes into published, versioned packages without manual steps, using semantic versioning and changelogs so consumers can upgrade safely and the team ships small changes frequently and reliably.
The 8 Pillars of ResearchOps
ResearchOps is the operating system behind scalable user research, not just scheduling. The 8 pillars map ops gaps like governance or tools. The footgun is treating it as a checklist to implement all at once rather than a diagnostic for triaging pain.
Masking: Hide Pixels Without Deleting Them
A mask is a stencil that hides everything outside its shape without destroying the original image. Use it for circular avatars and rounded photo crops. The hidden portion still exists, so exporting without flattening may bloat the file with invisible pixels.
Research Financial Operations: The Business of Research
Research financial operations funds and justifies research spend. You use it when negotiating tool contracts, setting incentive budgets, or defending headcount. The footgun is tracking costs per study while ignoring how a fragmented stack bleeds budget.
Component Properties: Levers Without Variants
Component properties are levers that let you swap text, toggle layers, or change icons without detaching. They shine in buttons with optional icons. The footgun is adding so many toggles that the panel becomes harder to use than a tidy variant grid.
Changesets: PR Receipts for Monorepo Releases
A changeset is a receipt stapled to each PR that records what changed and how it bumps versions. It lets CI batch monorepo releases and generate changelogs automatically. The footgun is forgetting to add one, leaving unreleased code silently unpublishable.
Research Governance Model
A research governance model is the operating system for scaling insights, trading autonomy for coordination so studies do not collide. It matters when teams share users and budgets.
Text Resizing in Figma Auto Layout
Text in Auto Layout does not wrap by default. A label set to Auto Width grows forever, while a parent set to Hug follows it. The footgun is leaving text on Auto Width inside a responsive card and expecting it to behave like a paragraph.
Semantic HTML: Structure as Accessibility Infrastructure
Semantic HTML assigns real roles to page elements so screen readers can navigate them. Use buttons for actions, headings for outline, and tables for data. The footgun is using divs with click handlers as buttons; they are invisible to keyboard and screen…
Research Spike: Fast Reconnaissance Before Commitment
A research spike is a time-boxed scout mission to answer one blocking question before the team commits. Use it when requirements are fuzzy. The footgun is letting the spike balloon into a full research project instead of a sharp go or no-go call.
Boolean Component Properties in Figma
Boolean properties in Figma are light switches for layers inside a component. They let you toggle an icon or badge on and off without spawning extra variants. The catch is that hiding a layer can break auto-layout if that layer was anchoring spacing.
Centralized Design System Team Model
A centralized design system team acts as a central kitchen: one dedicated group owns the components and standards that every product team consumes. It guarantees consistency but becomes a bottleneck if the team loses touch with shipping product teams.
Experience-Based Roadmap: Triage for Product Teams
An experience-based roadmap prioritizes user pain over feature deadlines. It sequences work by the severity of friction users actually encounter, not internal priorities. Teams often confuse it with a feature wishlist and skip validation.
Prototype Overlays: Layer Without Duplication
Overlays layer modals and menus above your current screen like a transparency sheet, so you never duplicate frames. Use them for dropdowns, dialogs, and toasts. The footgun is fixing them to the screen edge instead of the trigger, which breaks on resize.
Design System Roadmap: A Prioritization Contract
A design system roadmap is a contract with product teams, not a release calendar. It balances platform health against consumer demand so the system stays relevant. The footgun is letting roadmaps dictate every sprint, reducing the team to a service desk.
Accessibility Heuristic Evaluation
Accessibility heuristics spot keyboard traps and missing labels like a code audit for access. Use them in early reviews if disabled users are weeks away. The footgun is treating a clean score as proof, since only real users validate true usability.
Conditional Logic in Figma Prototypes
Conditional logic turns static click-throughs into state-aware flows. Use it to unlock a button only after form fields are valid, or to branch checkout based on payment method. The footgun is building a brittle fake app instead of a focused testable flow.
Federated Design System Team Model
Federated ownership spreads design system control across teams, not a silo. A lean core owns standards while contributors ship components from the field. The footgun is treating federation as zero governance, splintering the system into forks.
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