← back TO WORK
Enterprise banking platform

Bank Cache

Creating a modern online banking platform across every major device.

Jumping into the project

After joining my new company, Cognizant Softvision, I was quickly onboarded and added to the Oyko Bank team. The existing group of designers when I first joined added up to 4 total. Over the course of the project, that number would grow to 8 total and then gradually back down to 3 near the ending of the client initiative.

The project itself was divided into 3 segments: Round 1, Round 2, and — you guessed it — Round 3. Initially, most of the wireframes for Round 1 were already completed, which is the point where I was added. However, the workflow hit a snag when it came to development as the client moved their platform to use an existing third-party banking platform as the basis for their new company. This third-party platform came from India-based developers and we learned the app's ability to conform to our designs were limited, so much research needed to take place in order to determine how our existing wireframes would need to be altered to fit into this new third-party development model.

The product started off as Oyko and rebranded near the end of the project

My immediate contributions to the Round 1 platform feature-set were final designs for Transfers, Wire Transfers, Add Recipient, Personal Details, Application Settings, Notification Settings, and Account Closure.

The project was highly managed mostly by the designers, relying on high-quality communication loops to maintain up-to-date progress on the various areas of the platform feature-set and to capture future roadmap insights.

Our Design Process workflow required up-front research about the third-party application being used to develop the platform as well as constant feedback loops through management, fellow designers, third-party developers, and final client approval.

Rebranding to Cache

After many months of working on the Oyko Bank project there was some movement on the business end that resulted in a full rename and complete rebrand of the entire product. Included in that was a new logo, colors, and fonts. Luckily, the initial design team that lead the product look-and-feel for the project before I joined chose a very clean direction that easily lent itself to a company rebranding, but significant work still needed to be done.

Since there was a team of 6-8 designers, the work distribution was broken out so that about 2 designers would focus on upcoming product features, another 2-3 would focus on cross-platform implementation for tablets and phones, and another 2-3 would focus on the rebrand. With those groups established, I assisted the team as a sort of flex designer, going between all 3 areas of need.

Moving from the Oyko designs to the new Cache rebrand required that every screen needed to be re-built and cross-referenced with existing screens to make sure copy, logos, colors, fonts, and design components were all properly updated.

The internal design guides built by lead designer, Jaimy Stewart, also included advanced naming conventions for screens and file names to ensure nothing was ever duplicated in the hand-off step to the developers.

Facilitating designs for all devices

After the rebrand was finished, the team was nearing the end of the Round 2 roadmap and needed to switch gears to focus primarily on cross-platform implementation. Near this time the design team transitioned down into 4 and then 3 members to help meet client budget but the team still needed to meet deadlines and maintain substantial progress.

The team was again separated to hone in on different areas of the design, with designers being designated to either desktop, tablet, iOS, or android. Once each of these areas of the platform were validated, they needed to be grouped holistically into their feature-areas so that the hand-off into Zeplin for the developers would be as seamless as possible and also ensured that the client could easily track our progress via what was uploaded and checked-off in Zeplin's project listing. All-in-all this averaged out to about 60 screens per product feature that included all 4 device sizes. Which means, with about 44 total features identified for the first major version of the product, the design team had created and updated a total of 2,200 hi-fi screens during the seven months that I was embedded on the team.

← back TO WORK