Easy concepts in UX Research, page 2
Build-Measure-Learn Loop: Experiment Over Intuition
Ship a small test, watch real reactions, and steer the next version by data instead of gut instinct. Use it when you must know fast if a business model is viable. The footgun is calling the first release a product instead of an experiment.
Proto-Persona: Sketch Users from Team Assumptions
A proto-persona sketches your team's user assumptions in a quick workshop, creating shared targets without new research. It aligns Lean teams, but the footgun is treating these guessed profiles as facts rather than hypotheses.
Aesthetics-Usability Effect
The aesthetics-usability effect is the tendency for users to perceive attractive designs as easier to use and to be more tolerant of minor usability problems in them, which can mask real issues during testing.
UX Competitive Analysis: Benchmark to Outperform
UX competitive analysis treats rivals as free design research: reverse-engineer what works and where the market is underserved. Run it before redesigns and repeat quarterly. The footgun is copying visuals instead of analyzing underlying flows and task success.
Critical Incident Technique: Story Mining
Skip asking what users want; ask for the exact moment something went great or terribly wrong. Researchers use this to pinpoint interactions that make or break an experience. Teams collect vague feedback instead of concrete stories with clear context.
Team Charter: Shared Agreements for Collaboration
A team charter is the operating agreement that keeps collaboration aligned, distinct from the design rules the team produces. Teams use it to establish shared norms alongside principles and heuristics.
Research Advocacy in UX Design
Research advocacy means suspending your own priorities to speak with the user's voice in product decisions. It matters when teams must translate raw user frustration into concrete design changes. The footgun is letting personal opinion masquerade as user need.
UX Research Staffing: The 1:5:50 Ratio
A 2020 industry survey found the most common UX team structure is one researcher for every five designers and fifty developers. These ratios signal staffing norms but should never replace measuring actual research impact or team maturity.
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