Intermediate everything in Design & UX, page 9
How do you validate UX within hard technical constraints?
Tests evaluative research design for constrained, buildable prototypes rather than ideal mocks. Strong answers scope to feasible layers, use Wizard of Oz or stubs, and benchmark against current state. Red flag: testing fantasy UI that ignores API limits.
Design a centralized consent platform: core components and database schema
Separate CMF from CMP; build an append-only ledger with versioned wording, per-activity granularity, and real-time revocation.
How do you fulfill a GDPR erasure request across data stores?
This tests cross-system deletion under GDPR's 30-day SLA. A strong answer maps PII lineage across S3, databases, and analytics; uses soft deletes for backups; and handles dashboards via reprocessing.
Generative versus evaluative research: when to use each
Generative precedes design to find needs; evaluative follows a build to test it.
How does UX research integrate into a two-week agile sprint?
This tests if you see research as ongoing discovery, not a predev phase. A good answer covers backlog work across sprints, outcome-based prioritization, and engineer touchpoints in refinement. Red flag: saying research happens only before coding starts.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Atomic Research: Reusable Insight Nuggets
Atomic research treats insights as reusable nuggets rather than trapping them in static reports. It shines when teams build living repositories for continuous discovery. The footgun is dumping raw quotes without synthesis, which buries signal under noise.
Research Playback: The Researcher's Closing Argument
A research playback is your closing argument, not a filing cabinet. It forces stakeholders to confront user evidence when a strategic decision is stuck. The fatal error is narrating methodology instead of insight, which bores the room and kills momentum.
UX Data Storytelling That Drives Decisions
Raw metrics fail to move teams; stakeholders cannot feel user pain. Storytelling with data weaves findings into a narrative arc exposing friction and driving action. The footgun is cherry-picking to fit a preset conclusion instead of letting data lead.
UX Research Report: Decisions, Not Deliverables
A UX research report is a decision tool, not a data dump; it turns observations into product direction. Teams use it after usability tests to align stakeholders on what to build. The biggest mistake is writing for your ego instead of the reader's next move.
Framework Analysis for UX Research
Framework analysis overlays a proven lens onto raw UX data instead of mining themes from scratch. Reach for it when testing against heuristics, TAM, or accessibility standards.
Saturation: When to Stop Interviewing
Saturation is when new interviews stop yielding fresh themes, like wringing a dry towel. It gives UX researchers a data-driven stopping rule instead of an arbitrary quota. The footgun is claiming it after only talking to lookalikes who share the same context.
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