Discovery
Background
When looking at the numbers, it was clear our onboarding wasn’t driving results. Out of 600+ signups to Subkit, only 52 creators (internally referred to as "providers") launched plans that were making money. Additionally, most creators with successfully launched plans required a lot of support from our community team to get from account creation to their first dollar. Though we had our educated guesses (internally) about what could be improved, we wanted creators to walk us through plan creation and understand where they were hitting a wall and why before we tried to revamp the entire experience.
Usability testing
We conducted usability tests, having users create an account on Subkit and walk us through how they would go about creating a subscription plan. Afterwards, we were able to define addressable pain points that creators experienced.
Defining user pain points
A major pain point in subscription plan creation stemmed from users' fundamental mental model: they understood subscription plans as a way to offer goods or services on a recurring basis. However, the subscription plan creation form failed to align with this understanding. Users struggled to identify where to input these goods or services, as the label "Features" wasn't immediately recognizable as the place for products.
The confusion went beyond mere semantics. Users expected more comprehensive input options for each good or service, rather than just a single text field. While the plan preview card eventually helped users realize that "Features" meant products within the plan, they were left wondering why there wasn't more space to properly describe or showcase these products.
This misalignment became even more apparent for users who approached subscriptions with a tiered model in mind. They found it unintuitive to specify product quantities in a way that would allow our backend to effectively compare and highlight the different value propositions across their plan tiers.
Mapping creator & subscriber mental models
Going back to mental models, I wanted to start from a subscriber's point of view to consider what information would be compelling to drive sales. Since each subscriber-facing output would be displayed as an input to creators, I mapped out how stores, subscription plans, and products related to one another.
The store information was to let subscribers know why they should buy from a certain creator– whether that meant expertise or seller ethos, this gave creators a chance to sell themselves. Next was the subscription plan– this was an opportunity for creators to showcase the bundled recurring value held within their plans. One store could offer many subscription plans, but since our goal was to help users get from 0-1, we built infrastructure to support tiered plans in the future, but didn't go into details with creating that for this iteration. Lastly, we got to the most nested component of a plan which was the product. Products were what customers sought most from plans, aside from discounted value they would get on a recurring basis. We wanted to make products stand out and allow creators to market the value contained in their subscription plans in the most effective way.