UX Research Skill #4: Synthesizing Findings vs. Translating Them Into Business Value
Synthesis tells you what’s true. Translation tells you why it matters to this team, this product, this decision. Most researchers are good at one but not both.
Synthesis tells you what’s true. Translation tells you why it matters to this team, this product, this decision. Most researchers are good at one but not both.
Running a clean usability test is teachable. Knowing what to do when the data is contradictory, incomplete, or just weird — that’s the skill that takes years to develop.
The interview guide is a starting point. What separates good interviewers from great ones is how they respond when the conversation goes somewhere unexpected.
Writing a research plan is easy. Getting the people who need to act on the findings to care before the study even starts — that’s the harder skill.
Courses teach frameworks. Real research teaches you what frameworks miss. The most important skills I’ve developed as a researcher didn’t come from any curriculum.
Being the only researcher in an organization is both liberating and exhausting. Practical strategies for managing scope, stakeholders, and sanity when you’re a team of one.
Kids don’t read instructions — they just try things. What watching my children interact with products revealed about assumptions we bake into design.
Most UX teams focus on what users can’t do. The question that unlocks the most insight is something else entirely — and almost no one asks it.
Demographic personas tell you who someone is. Spiritual personas tell you where they are on their journey — and what they actually need from your ministry right now.
Churches measure attendance and giving — but rarely the things that actually indicate spiritual growth. What discipleship metrics most churches are missing and why it matters.