Intermediate concepts in Design & UX, page 15
Hiring Writers: Freelance vs. In-House
Choosing between freelance and in-house writers is a strategic trade-off. Freelancers offer cost-effective, specialized talent on demand, while in-house writers provide deep brand knowledge and consistent availability.
Screen Reader Testing: Navigate UI Without Sight
Screen reader testing reveals gaps visual checks miss by turning your UI into audio. Run real tasks with only a keyboard and screen reader, checking headings and focus order. The footgun is treating axe passes as equivalent to a human listening through a flow.
Handoff Plugins Bridge Figma to Code
Handoff plugins are automated translators between Figma and code, turning visual specs into tokens or components. They speed up design systems where manual inspection is a bottleneck. The footgun is treating generated output as production-ready without review.
Hybrid Model: Core Team Plus Federated Contributors
A hybrid design system team pairs a central group owning primitives with product squads shipping patterns. Large orgs use it when one team cannot cover every surface. It fails when contribution rules are vague and the core becomes a bottleneck not an enabler.
Beyond Per-Word: A Framework for Setting Freelance Rates
Price your work based on value, not just word count. Rates vary widely by service (editing vs. consulting), genre, and your expertise. This applies when quoting any project.
Strategic Foresight in UX
UX foresight is a telescope: it maps where behavior is heading so you avoid building winners that soon become obsolete. Deploy it when roadmapping multi-year platforms. The trap is treating scenarios as predictions rather than assumption stress-tests.
Figma File Covers as Status Billboards
A Figma cover page turns your file thumbnail into a status billboard, showing if a design is draft or ready for dev without opening it. Teams with many files use covers as scannable dashboards. Outdated badges send developers hunting for nonexistent specs.
Component Definition of Done: The Shipping Checklist
Component Definition of Done is the checklist that turns UI code into a team dependency. It covers a11y, tokens, tests, and docs so teams can adopt without asking questions. Stopping at code-complete is the footgun; orphans silently fracture systems.
Statement of Work (SOW): Defining 'Done' for a Project
An SOW is the project's blueprint, translating a goal into a concrete plan of activities, deliverables, and timelines. It's used when engaging vendors to ensure both sides agree on the scope. The footgun: a vague SOW invites scope creep and disputes.
Research Office Hours: A Drop-In Clinic
Research office hours are a drop-in clinic for product questions, offering expertise without a project brief. Teams use them to gut-check methods or interpret data fast. The trap is drop-ins replacing prioritization and making researchers reactive support.
Figma Branch Reviews: Merge Gates for Design
A Figma branch review is a merge gate: reviewers diff changes against main and approve before merge. Use it when designers share a system or a lead must sign off. The footgun is rubber-stamping and missing broken component links that corrupt the main file.
ADR: Capture Context, Not Just Conclusions
An Architecture Decision Record captures why a significant technical choice was made, so teams understand trade-offs without relitigating them. Use it when a decision is costly to reverse or crosses team boundaries.
Ghostwriting Agreement: Who Owns the Words?
A ghostwriting agreement legally transfers authorship from the writer to a credited person. It's used when an expert has ideas but not the time or skill to write, ensuring the final work is legally theirs.
Dynamic Counter: State in Figma
A dynamic counter wires a number variable to a text layer, letting taps change the value. Use it for quantity steppers or pagination in prototypes. The footgun is skipping the text-to-variable binding, so clicks fire but the on-screen number never updates.
Release Cadence: The Design System Heartbeat
Release cadence is the heartbeat of a design system: a fixed shipping rhythm that lets teams plan upgrades instead of absorbing random change. It is vital when many squads share a library.
Figma Boolean Variables: State Without Variant Sprawl
A boolean variable is a light switch for your component: one true/false value reveals badges or loaders instantly. Use it for binary states like visibility across a system. The trap is wiring too many switches into one component, making debugging a hunt.
Design System Roadshow: The Internal Campaign
A design system roadshow treats adoption as a political campaign, not a product launch. You visit every squad to demo components, surface fears, and co-build trust.
Figma Variable Modes for Multi-Context Theming
Variable modes let a single token hold different values for different contexts, like light and dark themes. Apply a mode to a frame and every token inside swaps instantly. The footgun is treating modes as component states, which creates a combinatorial mess.
Pair Programming Drives Design System Adoption
Pair programming with the system team embeds design system knowledge directly into product code. Use it when a squad ships their first feature with new tokens or components. The footgun is treating the session as code review rather than knowledge transfer.
Simulate Form Validation in Figma
A form prototype is an interactive script, not a picture. You pre-build every state — empty, typing, error, success — and link them so stakeholders feel validation timing before engineers code it. The trap is logic you cannot maintain across design changes.
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