How to de-risk the change?
Changing how creators get paid was high-risk with the potential to create serious negative user sentiment (don’t mess with my $$), lose loyal customers, decrease in-app usage and user engagement. Obviously the goal was to avoid (or reduce) the risk that any of this would happen. First step — dig into the ongoing UX research to see how we might design the new flow while minimizing any unnecessary friction. AKA — what do we already know?
Artifact Library
I joined this product team in Fall 2022 after a year working on a similar but different platform. While the target audience was essentially the same, the product was materially different. However, there was a lot of overlap specifically within my domain, so the first thing I did was to create an artifact library for the team to access, along with a wayfinding document for quick access to: personas, user journeys, UX research, sticker sheets with content for UI elements, composable content strings that had already been localized as well as direct source links in the codebase.
By creating an UX artifact library, we were able to be even more agile because we knew before kick-off where we needed to design new and where we could evolve the current state. We could make a more conscious decision about where to put team resources and created a more lightweight approach to customization.
Content Taxonomy
With such high-level of complexity, changing this monetization program in a material way required the early application of a clear content taxonomy. With the user data we created a content taxonomy based on the current ecosystem to ensure cohesion across the UI.
-
A content taxonomy is a mini-site map for a user interface. It’s a way to organize content (words) by category and it’s a way to apply object-oriented development to content design.
-
A content taxonomy improves user experience, site performance, scalability, and can reduce design debt.