Part one: Quick wins
Before diving into the weeds and conducting more thorough UX research, I implemented some 'quick wins', leveraging both my UI & UX experience over the years. This meant, amongst other optimisations, improving the legibility, information available and its hierarchy, accessibility and simply making the checkout process much more professional and consistent.
Part two: Discovery / UX Research
With the low-hanging fruit plucked, it was now time to perform a more detailed analysis of our users, what their various needs are and we could best accomidate those. In order to get these insights, we used several methods & disciplines.
As the startup had ventured into a particular direction quite quickly, I realised it would be important to take a step back in order to determine if we were heading in the right direction. Hence, together with the PO, we started with conducting many user interviews, to get a better understanding of why they were using our product, but more importantly, which problems they were trying to solve. The best products & services usually start with the 'why' -- it isn't until you understand the core of the issue, that you can truly, effectively, solve these problems.
While in-depth, user interviews can provide a lot of detailed insight, it's also important to keep the bigger picture in mind. Hence we worked together with a data-scientist to see if what users were telling us was reflected in the data. After all, it would be a shame to dedicate a substantial amount of work to a feature only 10% would actually use.
Lastly, to further supplement our sights, we also used tools like Hotjar to get a better sense of how users were using our platform on a larger scale, along with issues they were running into. We combined these insights with user surveys, including trying to measure an NPS score, so we had a better grip on how users were experiencing the platform.
Clustering user-types into personas
The marketing department already had a good sense of customer profiles and relevant sectors, and the sales team already spent a lot of time talking to (potential) clients, it would be shame to not make use of these insights! Therefore, I facilitated several workshops to combine these insights, where we actually discovered there was significant overlap between users from different domains, this helped define the personas that were most relevant to the product's offering.
Companies/designers often include a lot of generic information about personas, e.g. their technical expertise, or even (random) details like if they have a pet or not. This in my experience, can often add a lot of noise and makes focussing on the right features harder. In this case, we stuck to specific needs various users had, and how they differ, so we could be more effective in prioritising. Moreover, the core values of the company included accessibility and making every feature easy to understand & use, do we could cut through the noise.
Competitive analysis
Building a great product or service isn't done in a bubble. One might understand problems users are facing exactly, and come up with perfect solutions, but what if someone else has done that already? What if the market is saturated in a particular country, domain, or target group already? Enter the competitive analysis!
Not only did we complete the competitive analysis from a product perspective, but also integrated it with company-wide insights, including marketing, sales, business development and customer care, to ensure our tragedy was sound going forward and that it was also good for business!
Take-aways of research
Combining the various research insights, here are some general takeaways:
- Customers & freelancers were spending too much time fixing grammar & spelling mistakes and even copy & pasting text back and forth into other tools like Word & Grammarly. Could we integrate some of these features into our own editor?
- Customers & freelancers constnatly had to fix the same nouns over and over again. Would it be possible to fix them all at once, or even prevent these issues?
- The sequence of steps in the upload/checkout flow were confusing to users and required lots of going back and forth, especially with all the conditional logic. What would be the most seamless flow?
- Specific audio segments are hard to understand and require a lot of click to rewind and reply these segments over and over again. Could this be streamlined?
- Especially for European clients, supporting more than one language in the subtitle editor is essential. Translations are also important. Could we automate this right into the subtitle editor?
- GDPR & Data-security are essential in many markets, but for DACH especially
- The transcript & subtitle editors were increasingly getting bloated by constantly adding new features. Can we streamline the interface and priotise features when necessary?
- Don't judge a book by its cover: many users across different segments actually had the same needs
Step 3: Ideation & Validation
Now that we had a better understanding of our users and the issues they were facing, it was time to ideate on solutions and to validate them with real users!
Workshops
Great solutions are hardly ever conceived by one person. When coming up with solutions, it often very useful to immediately make use of various resources within companies. Hence ideation workshops are often done with POs, PMs and solution architects included, so that ideas can be validated with business and technical validity right away.
Moreover, it's important to make clear what current assumptions are, and the metrics could be of how to prove if an experiment is a hit or miss, otherwise you're shooting in the dark.
Sample discovery workshop
Courtesy of my friend & former colleague:
Prototyping
Luckily prototyping has become significantly easier over the years. Nowadays, built-in prototyping tools, like in Figma after often enough to validate basic and initial experiments/hypothesis. For more tailored prototypes, we used ProtoPie, it's amazing to see how far these tools have come, where they can include detailed animations or even use input from device sensors to create high-end experiences to properly validate any concept as if it were actually built!
Moreover, we have also used tools like Lookback to facilitate remote prototyping while still getting detailed feedback on the user's experience with the prototype.