Internet banking system adapted to meet the needs of MSMEs
The brief
GoBusiness is an Omni channel Internet Banking Service for MSMEs. This service should allow the basic functions of an internet banking system adapted to meet the needs of MSMEs accessible on a PC/Laptop and Mobile phone.
Role
Product Designer
Tools
Sketch, Whimsical, Sketch cloud, Notion, Zoom, Slack
Stakeholders
GoBusiness has a couple of Stakeholders who will be interfacing with the Application. These Include:
Challenge
Designing for critical information and functionality at a glance
The main UX hurdle was to determine what information is most vital for business owners to access, as well as what controls. I aimed to design for the stakeholder above the fold, further facilitating quick action, as well as adding to the design constraints I worked under.
Functional Requirements
This section captures the list of all in scope functional Requirements and the different business rules governing them. The Functional requirements are grouped by the user-type.
The two user types for this scope include:

Research + Planning
I worked with directly with a project manager and two other designers. The product manager created the PRD and we highlighted the different modules we had to create prototypes for to arrive at a successful product. We worked in 2-week sprints, with a sprint planning meeting at he beginning of each sprint and a sprint retrospective at the end; to double back and see what we have achieved during the sprint. The different modules we highlighted include:
I took over 3 of the modules; Beneficiary Management, Reports and Analytics & Audit Log. I processed, ideated and created user stories and high-fidelity prototypes for them.
Design System
With the ethos of the product already outlined and in order to achieve intuitive and consistent design, I was tasked with creating a design system that didn't diviate too much from the already existing product.

User stories
I created user stories for the modules I took on. I created a table and organised the user stories by "Story Name", "Story Narrative" and most importantly; "Acceptance Criteria".



Prototype
With the user stories completed, the design equation was already close to being solved.
Now I sketched out my low fidelity solutions and converted them into high fidelity prototypes wiith the user stories as the main guide.



Uploaded the sketch file to figma for sharing purposes. Here's a link to the figma file.