Nine practical ways to make research reports easier to read and harder to ignore: clearer structure, stronger hierarchy, better contrast, more whitespace, consistent charts, and reusable templates. The authors make a very UX-ish point — a research report is itself an interface with two users: the researcher creating it and the stakeholder reading it. MeasuringU even usability-tested its own report template and went through four iterations before settling on the current version

When everyone on a product team “owns the user”, responsibility for actually understanding them can disappear. The author shows how overlapping research by UX and Product can turn into a data-quality problem when interview framing and methods aren’t shared. His practical fix is surprisingly small: agree upfront who researches, who is consulted, and who makes the call

NN/g’s practical map of where AI already fits into UX work — from research planning and analysis to prototyping, writing, service design, and workshops. The guide is less about “AI will replace UX” and more about choosing specific tasks where it can genuinely help without outsourcing judgment. The research section alone covers synthetic users, AI-moderated interviews, survey writing, digital twins, and why analysis still shouldn’t be handed over completely to AI

A two-week experiment in designing tiny experiences around emotions like restlessness, adventure, and optimism — often with just a day to research, prototype, and test. The projects range from an endless staircase timer to chocolate as a trigger for hope and motion-activated “fireflies”. The best lesson comes at the end: even a handful of people was enough to break assumptions and reshape almost every prototype

AI makes features dramatically cheaper to build, but implementation is only a fraction of their real cost. Every new feature adds maintenance, support, friction, complexity, and eventually makes removing it a product decision of its own. The uncomfortable takeaway: when almost anything can be built, deciding what not to build becomes the harder skill

What first dates can teach researchers about rapport, awkward silences, knowing when to end a conversation, and trusting your instincts. The authors connect familiar dating situations with practical research skills — from making interviews feel less like a checklist to planning fieldwork with exits, check-ins, and even a code word. A useful reminder that researcher safety deserves as much preparation as participant safety

A persona is useful only when it helps a team make product decisions, not when it simply describes age, job title, and favourite apps. The author suggests building personas around context, goals, pain points, behaviour, motivation, and decision drivers — then using them to prioritise features and UI choices. A good test is simple: can your persona help explain what you should avoid building?