Process is a big deal
In order to understand the system myself and the rest of the UX design team started with current user interviews and workshops.
So what did we get out of the interviews?
The interviews allowed us to understand what features in V4 the users wanted and which ones they didn’t want. It also helped us understand the user’s goals irrespective of the software they were using. We let those goals act as a guide that helped us decide what features to keep and which ones to throw away.
I then visualised all our findings into a readable graph for later reference. I find visualising finding at this stage really helpful as a way to declutter the vast amount of information gained from workshops and interviews.
At this stage I also made an initial audit of the current system.
This helped me figure out if any features were repeated or redundant.
I used this information to analyse the UX wins and the fails.
Each persona had a set of real world goals and what the users would like to achieve with Tag CMD
TAG CMD is Tag’s enterprise-level Marketing Resource Management (MRM) solution. The brief require the redesign of the then current TAG CMD v.4. The most challenging thing about the work was understanding the many faceted parts that belonged to the MRM system and the need to deliver a wide range of complex features for a specific user group.