Monese webapp updates: Account overview 2.0 + Transaction details + Cards controls
Wunder Mobility Subscription Plans
Subscriptions are usually an arrangement between a company and end-users, where the company offers a set of goodies/services in exchange for a regular recurring payment.
Context
Wunder Mobility is a company providing clients with a flexible white-label product so the clients can offer mobility services to end-users (B2B2C).
One of the recurring requests from clients is the “Subscription Plans” feature, where Wunder’s clients believe they would be able to become more profitable by offering this business approach to their end-users. After validating this hypothesis with client calls and market evaluations, we decided to build this feature.
My team & my role
Working in a cross-functional mobile team, my role as a product designer was to be responsible for the end-to-end development of this topic, which means, discovery sessions, research & exploration, prototyping, testing, validation, and following up code development (Design QA).
Discovery & Exploration
To kick off this project I first started with competitors analysis to understand how this feature was being offered by other companies and then be able to collect some initial insights.
One important insight collected at this moment is that even though we needed to offer the subscription plans to multiple vehicle models, most of the time, the benefits were the same.
The next step was to jump into sessions with multiple clients, that had previously flagged to us the need for this feature, with the goal to validate assumptions and establish a common ground solution that could for all of them.
Important note here: As a product team developing a white-label product, we don’t want to become an agency developing a feature that works specifically for one client, so this type of alignment is crucial to our process.
After this, the next step was to pair it up with the PO and engineers to understand the technical constraints and viability in order to enable us to develop the feature in a scalable way.
The next step then was to define a scope together with the team based on the information collected for the MVP of this feature.
For the MVP we decided to provide end-users with a list of subscriptions that could be configured by clients. Clients would be able to:
- Provide riding credits and discounts as perks of the plans
- Configure if the credits would work on a “refill” basis or “stack” one.
- Define titles, short descriptions & long description
There were other ideas for the MVP, that due time of development was postponed to future iterations. For example, offer a free or specific number of free vehicle unlocks, discounts on unlocking fees, etc.
Prototyping & Testing
Following up with the design process, I started working on initial designs and prototypes so I could prepare user testing sessions to validate our assumptions and ideas so far.
Coming up with the prototype was quite fast due to the usage of our Design System, which enables us to quickly prototype and validate ideas.
When jumping into user testing sessions, we prepare a script where they had 3 main tasks:
- Subscribe to a subscription plan
- Replace the subscription with another one
- Cancel a subscription
The testing sessions provided us with learnings that reflected small changes in the designs but in general, the core flow was clear and aligned with the proposal of the MVP for this feature.
After development and Design QA, these are some of the outcome of the designs:
Related posts
