Along with Roger’s needs, it is also imperative that I consider the goals of Capital One. In lieu of speaking directly with the Capital One team, I relied on their brand mission and positioning to offer perspective into the company's values. While Capital One’s goals does center around monetizing of the app, there are still overlaps between user and business.
POV & HMW Questions
Following the exercise of aligning business and user goals, I revisited my insights. From there, I attempted to narrow the focus and pinpoint user problems: 4 POV statements were developed that directly corresponded to Roger’s use case. We than re-framed them into “How Might We Questions,” which ultimately opens up to ideation sessions.
To guide my brainstorming and feature prioritization, I mapped my HMW's on digitized whiteboard and tossed around ideas ranging in scope, size, and feasibility.
To synthesize and refine solutions, I considered each alongside Capital One’s existing positioning and goals as well as the user’s. This meant abandoning some solutions for the sake of brand continuity and ensuring solutions aligned with the company’s self-identified values about its product.
Noting the shared user and business goals, I looked back at ideas generated during brainstorming and determined which ones could be further developed into a money management feature that would respond to the needs of both parties. I then outlined specific details for each and prioritized them.
Informed by the features and priorities outlined in my product roadmap, I created an app map for Capital One, showing how the new “MoneyWise” feature would integrate within the existing architecture.
Highlighting two distinct paths, I wanted to understand how users would navigate through the app with the goal of 1. categorizing and rating transaction and 2. creating budget and savings goals.
A user flow helped to capture multiple user paths and decisions points in completing the task of categorization and of creating budgeting / savings goals. It also helped to inform all the screen states that would need to be designed for.