Saving pots.
Research and
benchmarking
There were significant constraints, including limited time and resources for implementation.
To address this, I collaborated closely with the research team. Together, we conducted diary studies, competitive analysis, and unmoderated testing. These efforts helped us uncover the diverse needs associated with this feature and identify users' favorite potential add-ons.
Designing
I explored numerous design options, starting with the most ideal version and iterating from there. Once we reached a version that satisfied all stakeholders, a change in the tech provider extended the estimated timeline from 3 months to at least 6.
To adapt, I pivoted to designing an MVP that could be implemented within the new constraints. This approach allowed us to launch a functional version quickly, with plans to iterate and enhance it over time.
Prototype
I created a quick prototype to evaluate the flow and ensure a seamless user experience. Once the flow was validated, I gradually increased the fidelity of the design before proceeding with more in-depth testing.
Results
This version was initially rolled out to staff for live testing to ensure the design was clear and the user experience was seamless.
After a few weeks and some adjustments, the feature was implemented globally. While the overall impact fell short of expectations, we observed that 5% of users began creating pots, providing valuable insights for further iterations.
What I learned / What I would do differently
I learned a lot about how users manage their savings and saving pots.
How much we needed to understand before designing.
How many different blockers we have, mainly from providers and third parties.
I was told this was needed in 2 weeks (in december) and couldn’t run a workshop.