Finity

Finity

Business Banking

Business Banking

A banking platform designed for the specific needs and requirements of business owners within the recruitment space.

A banking platform designed for the specific needs and requirements of business owners within the recruitment space.

Q1 2024

Background

Background

Background

Finity is a software eco-system specifically designed and tailored to meet the needs of the temporary recruitment industry; offering back office, payroll, banking and rewards solutions. The temporary recruitment market abides by different regulations when it comes to payroll and banking and Finity aims to bridge the gap experienced by professionals in this space. Crafting a better journey for a fast growing group within the UK, Finity aims to solve a problem for a work force that is often neglected by current solutions.

Finity is a software eco-system specifically designed and tailored to meet the needs of the temporary recruitment industry; offering back office, payroll, banking and rewards solutions. The temporary recruitment market abides by different regulations when it comes to payroll and banking and Finity aims to bridge the gap experienced by professionals in this space. Crafting a better journey for a fast growing group within the UK, Finity aims to solve a problem for a work force that is often neglected by current solutions.

Finity is a software eco-system specifically designed and tailored to meet the needs of the temporary recruitment industry; offering back office, payroll, banking and rewards solutions. The temporary recruitment market abides by different regulations when it comes to payroll and banking and Finity aims to bridge the gap experienced by professionals in this space. Crafting a better journey for a fast growing group within the UK, Finity aims to solve a problem for a work force that is often neglected by current solutions.

Problem

Problem

Problem

High street banks do not cater for the specific needs of the temporary recruitment market when it comes to banking. A gap is left by modern banks lack of an effective approach to approving batch payments. Business owners may be managing multiple businesses’s payrolls under their umbrella and require a streamlined solution to approving batch payments so that their customers are paid efficiently with as little burden on their administrative duties as possible.

High street banks do not cater for the specific needs of the temporary recruitment market when it comes to banking. A gap is left by modern banks lack of an effective approach to approving batch payments. Business owners may be managing multiple businesses’s payrolls under their umbrella and require a streamlined solution to approving batch payments so that their customers are paid efficiently with as little burden on their administrative duties as possible.

High street banks do not cater for the specific needs of the temporary recruitment market when it comes to banking. A gap is left by modern banks lack of an effective approach to approving batch payments. Business owners may be managing multiple businesses’s payrolls under their umbrella and require a streamlined solution to approving batch payments so that their customers are paid efficiently with as little burden on their administrative duties as possible.

Goal

Goal

Goal

"Design a user friendly and intuitive interface for a business banking platform that is familiar yet also caters to the niche necessity of approving batch payments sent out to multiple different businesses. This payment will be sent out from another piece of software within the eco-system."

"Design a user friendly and intuitive interface for a business banking platform that is familiar yet also caters to the niche necessity of approving batch payments sent out to multiple different businesses. This payment will be sent out from another piece of software within the eco-system."

"Design a user friendly and intuitive interface for a business banking platform that is familiar yet also caters to the niche necessity of approving batch payments sent out to multiple different businesses. This payment will be sent out from another piece of software within the eco-system."

Map of ecosystem flow

Map of ecosystem flow

Map of ecosystem flow

Understanding the user: Product History

Understanding the user: Product History

Understanding the user: Product History

Our team was in an unusual situation, having built a product to meet this niche requirement for a client before realising the potential and looking to expand. The current product we had in our wheelhouse held a lot of the required functionality needed, but was built on old technology with a clunky user experience, having had no designer on the team at the time of the project initially running many years ago. This meant we already had a list of features and a couple of expert users in our pockets who fit the persona perfectly.

Our team was in an unusual situation, having built a product to meet this niche requirement for a client before realising the potential and looking to expand. The current product we had in our wheelhouse held a lot of the required functionality needed, but was built on old technology with a clunky user experience, having had no designer on the team at the time of the project initially running many years ago. This meant we already had a list of features and a couple of expert users in our pockets who fit the persona perfectly.

Our team was in an unusual situation, having built a product to meet this niche requirement for a client before realising the potential and looking to expand. The current product we had in our wheelhouse held a lot of the required functionality needed, but was built on old technology with a clunky user experience, having had no designer on the team at the time of the project initially running many years ago. This meant we already had a list of features and a couple of expert users in our pockets who fit the persona perfectly.

Understanding the user: The Expert

Understanding the user: The Expert

Interviews with these expert users revealed a deeper understanding of the key feature requirement that would differentiate our product from typical business banking apps: bulk authorisations. Our user persona required the ability to bulk authorise batch payments from their phone easily yet with the flexibility and familiarity that other banking apps offer.

Interviews with these expert users revealed a deeper understanding of the key feature requirement that would differentiate our product from typical business banking apps: bulk authorisations. Our user persona required the ability to bulk authorise batch payments from their phone easily yet with the flexibility and familiarity that other banking apps offer.

Understanding the user: The Expert

Interviews with these expert users revealed a deeper understanding of the key feature requirement that would differentiate our product from typical business banking apps: bulk authorisations. Our user persona required the ability to bulk authorise batch payments from their phone easily yet with the flexibility and familiarity that other banking apps offer.

"I need to be able to authorise payments quickly. I'm worried if I miss a notification I'll miss the cut off for getting these payments out."

"Sometimes I need to authorise multiple batches from different businesses. How easy will it be to see between the groups?"

“I love [other banking app]. It’s super easy to use but it doesn’t quite meet the needs I have for it.”

Features and themes

Interviews with our expert users and stakeholders as well as running a competitor analysis helped reveal features to include in our MVP product that users would typically expect from a banking app outside of our spotlight feature. We drew together themes to help put forward a suggested site map before doing some rapid wireframing based off of our findings.

Features and themes

Features and themes

Interviews with our expert users and stakeholders as well as running a competitor analysis helped reveal features to include in our MVP product that users would typically expect from a banking app outside of our spotlight feature. We drew together themes to help put forward a suggested site map before doing some rapid wireframing based off of our findings.

Interviews with our expert users and stakeholders as well as running a competitor analysis helped reveal features to include in our MVP product that users would typically expect from a banking app outside of our spotlight feature. We drew together themes to help put forward a suggested site map before doing some rapid wireframing based off of our findings.

Feature spotlight: Bulk authorisations

Feature spotlight: Bulk authorisations

Feature spotlight: Bulk authorisations

Users need the ability to bulk authorise batch payments. This must give them the flexibility to do it quickly as well as review some finer details should they wish. Users need to be able to come back to it if they choose not to carry out the payment at the immediate time. It must be easy to do, trustworthy and have minimal margin for user error. It must also be displayed clearly within the app in the case a user happens to miss their push notification.

Users need the ability to bulk authorise batch payments. This must give them the flexibility to do it quickly as well as review some finer details should they wish. Users need to be able to come back to it if they choose not to carry out the payment at the immediate time. It must be easy to do, trustworthy and have minimal margin for user error. It must also be displayed clearly within the app in the case a user happens to miss their push notification.

Users need the ability to bulk authorise batch payments. This must give them the flexibility to do it quickly as well as review some finer details should they wish. Users need to be able to come back to it if they choose not to carry out the payment at the immediate time. It must be easy to do, trustworthy and have minimal margin for user error. It must also be displayed clearly within the app in the case a user happens to miss their push notification.

Spotlight: UI explorations

Spotlight: UI explorations

Spotlight: UI explorations

As Rewards is going to be the first live project with our new branding, we took some time to explore how we wanted the look and feel of the UI to be.

As Rewards is going to be the first live project with our new branding, we took some time to explore how we wanted the look and feel of the UI to be.

As Rewards is going to be the first live project with our new branding, we took some time to explore how we wanted the look and feel of the UI to be.

What could have been better

What could have been better

What could have been better

  • More research and competitor analysis. This is one of the first projects I worked on with business analysts and I was often a bit confused about their role. Not wanting to step on toes as it was their jurisdiction, I did not feel like I spent enough time on competitor analysis. This prevented me from immersing myself in the business banking mindset rather than a personal banking one, which led to some biases in UI during the design phase.

  • Digging deeper with user interviews. With in-house experts at the ready, it is easy for stakeholders to forget the nuances of a specific problem space they are trying to solve. In the end, I understood their bulk authorisation problems. But my understanding of the issue would have been better served with some extra interviews to really understand the niche issue users are facing.

  • More research and competitor analysis. This is one of the first projects I worked on with business analysts and I was often a bit confused about their role. Not wanting to step on toes as it was their jurisdiction, I did not feel like I spent enough time on competitor analysis. This prevented me from immersing myself in the business banking mindset rather than a personal banking one, which led to some biases in UI during the design phase.

  • Digging deeper with user interviews. With in-house experts at the ready, it is easy for stakeholders to forget the nuances of a specific problem space they are trying to solve. In the end, I understood their bulk authorisation problems. But my understanding of the issue would have been better served with some extra interviews to really understand the niche issue users are facing.

  • More research and competitor analysis. This is one of the first projects I worked on with business analysts and I was often a bit confused about their role. Not wanting to step on toes as it was their jurisdiction, I did not feel like I spent enough time on competitor analysis. This prevented me from immersing myself in the business banking mindset rather than a personal banking one, which led to some biases in UI during the design phase.

  • Digging deeper with user interviews. With in-house experts at the ready, it is easy for stakeholders to forget the nuances of a specific problem space they are trying to solve. In the end, I understood their bulk authorisation problems. But my understanding of the issue would have been better served with some extra interviews to really understand the niche issue users are facing.

What's next

What's next

What's next

  • This project has been paused until early 2025 whilst we progress with another project that has taken priority (see Finity: Rewards).

  • When the project restarts, usability testing will be high on the list to ensure the priority feature does what it's intending to do.

  • We will iterate based on internal and external stakeholder feedback and ideate towards some new solutions as we will have more capacity, and then run a/b testing to ensure we are delivering a high quality experience.

  • As we will have a more developed component library we will also audit the UI and make sure it aligns with our status.

  • This project has been paused until early 2025 whilst we progress with another project that has taken priority (see Finity: Rewards).

  • When the project restarts, usability testing will be high on the list to ensure the priority feature does what it's intending to do.

  • We will iterate based on internal and external stakeholder feedback and ideate towards some new solutions as we will have more capacity, and then run a/b testing to ensure we are delivering a high quality experience.

  • As we will have a more developed component library we will also audit the UI and make sure it aligns with our status.

  • This project has been paused until early 2025 whilst we progress with another project that has taken priority (see Finity: Rewards).

  • When the project restarts, usability testing will be high on the list to ensure the priority feature does what it's intending to do.

  • We will iterate based on internal and external stakeholder feedback and ideate towards some new solutions as we will have more capacity, and then run a/b testing to ensure we are delivering a high quality experience.

  • As we will have a more developed component library we will also audit the UI and make sure it aligns with our status.

Thanks for checking out my work 👀