Today I’m sharing a custom UI audit report for BuzzSumo — a popular analytics tool for content marketers. I’ve always admired their product success story, and did a little dance when they asked me for UI/UX help.
There’s one question I get more often than others: “Jane, do you have an example audit report you created for one of your clients?” I’ve always been sharing examples in a private conversation, but publishing one to a wide audience seemed uncomfortable. But finally I mustered up my courage — and also received a permission from several clients.
BuzzSumo audit is a great example when some hands-on work explains the improvements better than any words. Please read on for the tools and the method, the actual PDF download, and the tips for running a UI audit for your own clients.
I’ve tried a few methods of delivering UI audit reports. Each of them has its own cons and pros — maybe one day I’ll write a detailed overview of them. Long story short: these days I’m either shipping an illustrated PDF report (written in Markdown first), or writing directly in Dropbox Paper. I’m starting to like Paper more, because it’s beautiful and allows to exchange in-place comments with the client.
For the hands-on design part, I’m using Sketch — it’s been my tool of choice for the last two years.
I’m following my own method described in The UI Audit book. This method focuses on key tasks and calls-to-action in each screen. However, custom audits are called “custom” for a reason — I’m also commenting on dozens of other things.
For each area of the app, I’m including an original screenshot of the app and pointing out potential problems. Then (if it’s a premium package) I’m including my own redesigned screen, and commenting on the improvements.
Download the Report
Please click here to download the full audit report (PDF, 23 pages).
If you decided to do a UI/UX audit for your own client, here’s a sequence of steps to follow. Hope this helps to bring more value to your clients!
- Pick a tool for documenting the audit (but don’t think too hard).
- Explore the web application and decide which screens deserve the most attention.
- Take screenshots for these screens. Multiple free browser add-ons are available for that.
- Follow the process with key tasks and calls-to-action — I’ve described it in the bookand in the free course (attention existing subscribers: you won’t be able to join the course again, so email me if you want access).
- Document any other problems you see with each screen. Strive for maximum clarity.
- End the document with a friendly overview, and a brief high-level roadmap for future work.