User testing reports are often pages long, lets face it how often do clients actually read this. What interesting ways can you share the results of user testing?
Reports are fine, I do it for myself at least, so I keep my thoughts consistent.
But for clients, you have to do presentations.
It doesn't matter what your presentation medium is, powerpoint, prezi or an infographic. Or perhaps you just dance with a marker in your hand in front of a whiteboard or a big ol' sheet of paper. In lieu of a whiteboard, just bluetack some paper on a wall (yeah, I did this a few times, esp. when I was in my first startup, in a university dormitory).
A presentation is a kind of a performance, hence the rules of performance apply: you can act, or be honest, you could be funny or dramatic, but in general, you're doing a performance and you have to keep up the interest of your audience.
Tell stories. It doesn't matter if the stories are fictional or non-fictional.
Stories are what keep people's interest up. It's pretty likely that they had a children's room, with a mother or granny or whoever who read stories to them. It's pretty likely that they have best friends who they tell stories to. It's pretty likely that they read newssites which tell stories to them.
Good stories are always about people. You're a UX designer. Your stories have to be about users.
It doesn't matter if you say: "Listen, I have to tell you something about users. " or "Listen, I have a story for you. Take Alice and Bob, two youngsters in their 20s with a mobile phone". Or you say: "Listen, we had this user testing, and one of the participants.."
It doesn't matter if it's the general case, it's about fictional characters, or an actual person. Keep telling stories, set contexts.
Have the reports to back you up. You need that data. But don't present just the data, it's not interesting.
Of course, sometimes you have to do "offline presentations", that is, you have to provide documents which will be read by people in their "spare time" and it's obvious they don't have spare time for you to say a few things in twenty minutes. It's likely they have about 5 minutes for your whole project per week or even per month.
It usually has a great negative effect for the project as a whole, but still, you have to keep them engaged, you have to create a reading material which makes them interested even when they're just skimming through, as that's what they'll do.
You need reports here because they'll prone to make some pretty stupid consequences as they don't invest the time to actually understand the things you say. Here, reports help to keep your back, "yes, but did you read my report as well? on page 22, it says that...".
There's a science on how to make reading materials which keeps people engaged, it's called literature: you have to understand your readers however, to achieve that: you have to understand their context, and more importantly, their interests.
Perhaps they're not that much interested in UX anyway, and they trust you in general that you do this job just fine, just prove them that you'll bring the profits they need, or you're at least worth the money.
At the end of the day,it's the customer who pays you, but the user is your stakeholder anyway. You have to create a customer experience to keep you employed, but you have to create a user experience to make the world a better place.
Don't do a report.
Tomer Sharon (Google), Jeff Gothelf (New Context) and many others have recently been talking about the ineffectiveness of reports and other deliverables. Involving stakeholders in every step of user research, including analysis, will improve buy-in and the overall results.
Clients should be watching the usability testing study and taking notes. Provide all clients and other team members with the same notetaking spreadsheet that has a row for each usability problem with a column to mark each participant that encountered the problem. Also, have a column for potential solutions to each problem. Hold regular debrief sessions to talk about the problems that were found.
At the end of the study, hold another debrief session to talk about solutions. Consider using a technique like the KJ Method (aka affinity diagramming) to organize findings and solutions. The end output of the study will be a recording of the meeting (video and audio) and photos.
I like to do a 'show reel' of clips of the screen recording which illustrate the points made in the report.
If you embed them in say powerpoint you can give a brief text description of what's going on.