While there are many out there that will feel quite comfortable using Skore to drive a UX workshop it’s more common to see it used alongside the whiteboard and sticky notes. Where Skore really makes a difference, in this use case, is in providing an online, interactive set of documentation as the output of the workshop. Here’s how.
The problem : workshop documentation & post-workshop confusion
One of the common challenges I’ve come across is post-workshop confusion. There are always a lot of very useful and insightful discussions that take place in the heat of the moment, yet in the days and weeks afterward it can be hard to remember the details. Most people take photos of the whiteboard and document discussion items and actions for reference later.
“Transition from free-form to sequential documentation”
The problem with this approach is in the translation from the free form nature of the workshop into the sequential and flat nature of traditional documentation. When a question arises later about why a specific decision was made, or what is the impact of changing something we discussed in the workshop, it can be difficult to draw that out of the documentation. One UX consultant I spoke to recently told me that most of their customers never read the documentation and just call them directly with questions. Even they have trouble remembering exactly what was said and what it referred to so they waste a lot of time discussing and reviewing the documentation on behalf of the client.
A typical UX workshop
Most UX workshops we see are looking at how to improve the user experience of existing products and sites. In the workshop you bring together the research (interviews, observations, eye tracking etc) in the context of the steps the user takes. Then the team discuss the issues, identify opportunities for improvement, define goals and assign actions for the next steps.
The user’s steps are often represented by screenshots and stuck on the whiteboard. Known issues and feedback are highlighted through sticky notes and marker pens. The remaining space on the whiteboard is used to sketch out improvements and ideas.
Creating interactive documentation with Skore
Before the workshop define the steps of the user’s journey using What and Why boxes in Skore. Attach any screenshots to each step for quick reference. Add notes to the steps to highlight important feedback items and findings. This should be roughly the same as what you start with on the whiteboard in the workshop.
During the workshop capture additional notes, create detail views where necessary and attach photos of the whiteboard to the relevant steps. Before everyone leaves the room walk them through what you’ve captured in Skore so they are familiar with it and then send them a link using the Just Skore it export feature. Simple as that.
Instead of traditional boring documents in pdf, the customer will have an interactive set of documentation, built around the user journey, describing the problems and the suggested improvements. And of course these can be updated as you go. This will save you a lot of time and clarify things for the customer.