Dear Reader,
These are famous last words for a UX researcher.
When I said them, I was pretty new to doing research at companies, and I had just shared an academic-looking document with my product team.
I thought I was clever for using a Google Doc so I could gather comments on my report.
The only thing I got was a few pity comments from my boss.
I should have known better.
That same boss used to print out research reports she wanted me to read. She would leave them on my desk because she knew that was the only thing that worked.
When it came to reports, she understood what I didn't.
Ironically, I was a designer doing research, and my research report was completely undesigned.
I turned off my design brain and sent out a barely-formatted report.
Why do we put important things above the fold on websites?
Why do we add bullets, drop-downs, images, and clear navigation?
We do that because we know the truth…nobody reads.
At best, people skim tell you they read (try using a PDF heatmap if you don't believe me).
Consider your front-end developer. Consider your UI designer. Do they want to read your 72-page report?
We don't expect this much from users, and we probably don't even follow this unrealistic behavior ourselves.
Your research report is like any piece of content. If it's too hard to consume, people won't. Think highlights reel or movie trailer...not early draft of the script.
Try formatting it like a newspaper article with the most important thing first. Use the Minto Pyramid if you need some guidance.
As for the report format, maybe it's time you let go of those PDFs and Google Docs.
UX Research, meet Content Design...🤝
Here are 10 ways to go beyond the Google Doc with your Research Reports.
(ordered from easy to difficult)
Learn how to move beyond research reports in this talk from UX researcher, Basim Al-Baker
It takes work to help people understand.
Of course, you could go beyond deliverables and involve the team instead. It's also a great way to get the whole team to research every week.
It's easy to complain that nobody does research, but it's hard to do something about it.
This video is how you can do something about the lack of research at your company.
Bonus: if you're bringing the team into research activities, you don't have to make a research report ever again.
Watch the video here:
| Get Instant Access to the Masterclass |
Until next week, stop reporting and start inspiring!
Jeff Humble
Designer & Co-Founder
The Fountain Institute
The Fountain Institute is an independent online school that teaches advanced UX & product skills.
5 More Signals about the Future of AI Interactions by Jeff Humble Dear Reader, The way we interact with AI is changing, and it fascinates me. How will we interact with AI in 2035? Signals give us a hint. What are signals? Signals = surprising examples from today that suggest where the future might end up. Last year, I did part 1, and now I want to share 5 more. Signal #1: Google built an AI-enabled mouse pointer from Google DeepMind This is a signal that I think will catch on fast. The Google...
Which parts of your work do you actually want to keep? By Hannah Baker This one's a few days late; life got in the way. Back to our regular scheduled broadcast next week. For a long time, I was using Claude the same way most people do. As a chat function. A thinking partner. Something to help me get things done. But I kept running into the same problem. Every new conversation, I'd have to re-explain everything, my tone, my formatting, what I needed the output to look like. So I'd stay in the...
7 Tells that a UI is AI-Generated by Jeff Humble Dear Reader, You can see a vibe-coded app from a mile away, if you know what to look for. Here are seven design patterns that scream amateur vibe coder. Learn them, avoid them, and stay above the rising tide of slop, my friends. 1. Neon color palette from IceWhistle If it's vibe-coded, it's gotta be neon. To slop this one up to the max, use 5+ neon colors and never pick a single one to focus. Why AI loves it: Neon-on-dark is overrepresented in...