Before (above): Overdraft Protection before rethinking the experience and re-evaluating design. The design was overly simple to the point users were getting confused with what the feature did and what it offered.
Below: The basic IA outlining some changes on what screens were going to be visible and determining how the user would navigate. I ended up bringing in more information and transparency into the ODP (Overdraft Protection) landing screen and throughout the opt-in process.

Methods/Process: Our process began with user interviews, during which we identified the primary pain points and issues. Through walkthroughs and discussions with our active users, we pinpointed that the main issue revolved around the "HOW". Once that was determined, we met with cross-functional teams (dev and PMs) to map out our plan and define requirements. We then quickly went into mapping out a flow, further research (competitor and UX/UI research), jumped into discovery, and finished off with validation before shipping out our update.
Validation: Following multiple rounds of critiques, we conducted several rounds of light user testing throughout the process to ensure that we were moving in the right direction, aligned with the preferences and needs of our users.
Wrapping it up: After weeks of iterations and meeting with devs and our PM, we were able to better fine tune requirements and conclude our newly improved ODP. We ran 2 sets of user testing/interviews to make sure our product was not in any way confusing, misleading, and did not discourage our users from utilizing a useful and potentially money saving tool.
Results: We saw a dramatic increase in users signing up for our ODP feature and more positive feedback overall. However, as a designer, this does not mean this is where my work stops. I found that there may be TOO MUCH text and have been revising this feature to include less text overall and breaking things down better for our users.