Show which entity the customer is acting for.
I moved entity selection into the main account context instead of leaving it buried in settings.
PRODUCT DESIGN CASE STUDY

MY ROLE · Corporate and retail UX/UI, design system and front-end review
At ITSS, I worked on Vista’s digital banking experience across four West African subsidiaries. I designed for people handling different accounts, currencies and approval responsibilities without losing track of the context.
A corporate customer may act for several legal entities, while a payment may need another person’s approval. I worked across onboarding, dashboards, transfers and approvals, with local language and market requirements.
I moved entity selection into the main account context instead of leaving it buried in settings.
I brought pending payment requests above the fold, with separate counts so the blocking task is visible.
I built shared patterns with room for local currencies, language and regulatory copy, and reviewed front-end builds in HTML/CSS.
The screens below show how those decisions came together.
Entity context stays visible when a finance manager moves between companies.

Approvals are work to complete, not just notification dots.


Evidence available. My ITSS award letter names the Vista UI/UX project. It supports my contribution; I did not have post-launch task-completion data.
Next validation. I would test entity selection and approval comprehension with corporate customers, particularly before they initiate a transfer.
My ITSS award letter names the Vista UI/UX work. The case study records requirements and design reasoning; I did not have post-launch task-completion data. I would test entity selection and approval comprehension with corporate users.