Product Roadmap | Chase Mobile Banking App
Previously, I went through a product sizing exercise where it is identified how long it will take to bring a product to market. During this process, everything that is unnecessary or isn’t critical to the users experience is removed and reimplemented at a later version if added back into the product at all. During this process, I removed the spending habits portion of the application because it added almost an entire month. Additionally, it is not critical for this banking app to be successful.
The next step is to identify exactly when specific components and parts of the app were going to get built. As a primarily right brained person, creating a roadmap doesn’t exactly have me jumping up and down. However, as I approached creating the roadmap, I understand how critical it is for me as a designer to comprehend this part of the process. A roadmap essentially dictates how much of your design gets built, when, and the quality of the product. It breaks down the stages in which a user gets to experience your design since an app is typically released in parts.
The process I used was to go through each screen and enter into a spreadsheet how long each component or feature would take.
Then I took small sticky notes (3 colors for 3 versions) and had each sticky note represent a day. During this process, it’s important to keep in mind what needs to get built first before the other parts. Since two developers are working at the same time, it’s best to keep one person on one flow or the other on a separate flow. An example would be for the same person to add in the selection of transfer to account and confirm transfer pages. This will keep the confusion and need for translation of thought processes to a minimum.
After putting it up, I took a step back with Jon and had him take a look. He asked me a series of questions such as why locations was in the first version or why my first version was so much smaller than my second. He suggested the transfer function up to the first version and notifications to be in the second version. I also put up screens for referencing next to each part represented in sticky notes.
From the wall, I created a simple, readable version in illustrator. If I were working with a team, this is what would be passed along to them so that everyone would be on the same page with expectations and delivery.
Click here to see it in a larger view.
Right now, the app is planned to be completed by May 3rd with two developers working 40 hour weeks. Which in my opinion isn’t so bad but as with anything in design and production, it always takes longer than you think. This is a great starting point to at least know what to do next. The design team has to be a couple steps ahead of the developers so they aren’t wasting time and waiting for designs to implement.