Finity
Finity
Rewards
Rewards
The first rewards platform for professionals in the recruitment fintech space.
The first rewards platform for professionals in the recruitment fintech space.
Q2 2024
Q2 2024
Finity
Rewards
The first rewards platform for professionals in the recruitment fintech space.
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 and create a better journey for such a fast growing group within the UK work force that is often neglected and forgotten about 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 and create a better journey for such a fast growing group within the UK work force that is often neglected and forgotten about 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 and create a better journey for such a fast growing group within the UK work force that is often neglected and forgotten about by current solutions.
Problem
Problem
Problem
It is typical for many back office, HR and payroll services to offer rewards and incentives for using their software. Few services offer software that specifically caters to the unique needs of the recruitment fintech market. Finity aims to be the first eco-system within this industry to offer rewards to the businesses that they serve, allowing points to be accrued for various usages across their platforms - beginning with payroll.
It is typical for many back office, HR and payroll services to offer rewards and incentives for using their software. Few services offer software that specifically caters to the unique needs of the recruitment fintech market. Finity aims to be the first eco-system within this industry to offer rewards to the businesses that they serve, allowing points to be accrued for various usages across their platforms - beginning with payroll.
It is typical for many back office, HR and payroll services to offer rewards and incentives for using their software. Few services offer software that specifically caters to the unique needs of the recruitment fintech market. Finity aims to be the first eco-system within this industry to offer rewards to the businesses that they serve, allowing points to be accrued for various usages across their platforms - beginning with payroll.
Goal
Goal
Goal
"Design a rewards platform that allows users to manage their accrual of points across the Finity ecosystem of products. Users will be able to convert points into pounds and load them onto a card to then be treated as any other regular prepaid card.
The platform will be web based and mobile friendly with the stretch goal of also delivering a complimentary mobile app."
"Design a rewards platform that allows users to manage their accrual of points across the Finity ecosystem of products. Users will be able to convert points into pounds and load them onto a card to then be treated as any other regular prepaid card.
The platform will be web based and mobile friendly with the stretch goal of also delivering a complimentary mobile app."
"Design a rewards platform that allows users to manage their accrual of points across the Finity ecosystem of products. Users will be able to convert points into pounds and load them onto a card to then be treated as any other regular prepaid card.
The platform will be web based and mobile friendly with the stretch goal of also delivering a complimentary mobile app."
"Design a rewards platform that allows users to manage their accrual of points across the Finity ecosystem "of products. Users will be able to convert points into pounds and load them onto a card to then be treated as any other regular prepaid card.
The platform will be web based and mobile friendly with the stretch goal of also delivering a complimentary mobile app."
Business flow
Business flow
Business flow
Understanding the user: History
Understanding the user: History
Understanding the user: History
Finity already has loyal customers of their services, and was looking to reward these customers with this new offering. It involved us as a team taking a step back to understand the business proposition. The users and earners of rewards points were not the people using the platforms the most, but rather the people who own the businesses that utilise the software on a daily business. Due to the industry niche, our stakeholders know a lot of the target users personally, and were able to filter the information we needed to start building the platform down to the team.
Finity already has loyal customers of their services, and was looking to reward these customers with this new offering. It involved us as a team taking a step back to understand the business proposition. The users and earners of rewards points were not the people using the platforms the most, but rather the people who own the businesses that utilise the software on a daily business. Due to the industry niche, our stakeholders know a lot of the target users personally, and were able to filter the information we needed to start building the platform down to the team.
Finity already has loyal customers of their services, and was looking to reward these customers with this new offering. It involved us as a team taking a step back to understand the business proposition. The users and earners of rewards points were not the people using the platforms the most, but rather the people who own the businesses that utilise the software on a daily business. Due to the industry niche, our stakeholders know a lot of the target users personally, and were able to filter the information we needed to start building the platform down to the team.
Some project specifics: Risks and challenges
Some project specifics: Risks and challenges
Some project specifics: Risks and challenges
Some of our direct stakeholders were the archetype of the user we were designing for. This can be both a positive and negative in projects, with a higher likelihood of the project inheriting some bias as well as more access to a deep understanding of the needs of the user. We were also presented with a design that had never gone live from the first time this project was scoped.
At the time, I was onboarding a new designer. I chose to not show her these old designs until we had scoped the problem later, as to make the most use of fresh eyes and not pass on any bias of our architecture.
Some of our direct stakeholders were the archetype of the user we were designing for. This can be both a positive and negative in projects, with a higher likelihood of the project inheriting some bias as well as more access to a deep understanding of the needs of the user. We were also presented with a design that had never gone live from the first time this project was scoped.
At the time, I was onboarding a new designer. I chose to not show her these old designs until we had scoped the problem later, as to make the most use of fresh eyes and not pass on any bias of our architecture.
Some of our direct stakeholders were the archetype of the user we were designing for. This can be both a positive and negative in projects, with a higher likelihood of the project inheriting some bias as well as more access to a deep understanding of the needs of the user. We were also presented with a design that had never gone live from the first time this project was scoped.
At the time, I was onboarding a new designer. I chose to not show her these old designs until we had scoped the problem later, as to make the most use of fresh eyes and not pass on any bias of our architecture.
"I've used a rewards platform before that was way too complicated. I just needed a way of managing my points."
"I have a business partner who owns 50% of my business. How will this work with points accrual and accounts?"
“It needs to be easy to manage points. I'm busy and bad at using apps…will it be easy to load points onto my card?”
Legacy
Legacy
Legacy
The old designs and architecture that was suggested to me involved the separation within the platform of card and points management. However, no stakeholder conversation or user interview suggested that these were mentally separated in the instance of a rewards platform. As quite a light platform, we wanted to test a design that combined the card and points features.
The design on the right shows the original suggested architecture from a previous team. You can see that to manage a card or manage points, the user must go to separate locations despite these two elements being interlinked.
The old designs and architecture that was suggested to me involved the separation within the platform of card and points management. However, no stakeholder conversation or user interview suggested that these were mentally separated in the instance of a rewards platform. As quite a light platform, we wanted to test a design that combined the card and points features.
The design on the right shows the original suggested architecture from a previous team. You can see that to manage a card or manage points, the user must go to separate locations despite these two elements being interlinked.
The old designs and architecture that was suggested to me involved the separation within the platform of card and points management. However, no stakeholder conversation or user interview suggested that these were mentally separated in the instance of a rewards platform. As quite a light platform, we wanted to test a design that combined the card and points features.
The design on the right shows the original suggested architecture from a previous team. You can see that to manage a card or manage points, the user must go to separate locations despite these two elements being interlinked.
The old designs and architecture that was suggested to me involved the separation within the platform of card and points management. However, no stakeholder conversation or user interview suggested that these were mentally separated in the instance of a rewards platform. As quite a light platform, we wanted to test a design that combined the card and points features.
The wireframe on the right shows the original suggested architecture from a previous team. You can see that to manage a card or manage points, the user must go to separate locations despite these two elements being interlinked.
Findings
Findings
The second design was much preferred from both a cognitive and visual stand point during some light a/b testing. We showed users and stakeholders the different designs and questioned what they would do if presented with these screens. We found some users initially could be a little confused in their understanding of sending points to the card before being able to use it, and that their understanding of the process was much better once those actions all happened on the same screen. In the initial design, users would either remain on a screen that didn't show them the results of an action or would have to relocate them, causing confusion. This was eliminated with the new design. We proceeded with the second design to develop in the hi-fi phase (see below).
The second design was much preferred from both a cognitive and visual stand point during some light a/b testing. We showed users and stakeholders the different designs and questioned what they would do if presented with these screens. We found some users initially could be a little confused in their understanding of sending points to the card before being able to use it, and that their understanding of the process was much better once those actions all happened on the same screen. In the initial design, users would either remain on a screen that didn't show them the results of an action or would have to relocate them, causing confusion. This was eliminated with the new design. We proceeded with the second design to develop in the hi-fi phase (see below).
The second design was much preferred from both a cognitive and visual stand point during some light a/b testing. We showed users and stakeholders the different designs and questioned what they would do if presented with these screens. We found some users initially could be a little confused in their understanding of sending points to the card before being able to use it, and that their understanding of the process was much better once those actions all happened on the same screen. In the initial design, users would either remain on a screen that didn't show them the results of an action or would have to relocate them, causing confusion. This was eliminated with the new design. We proceeded with the second design to develop in the hi-fi phase (see below).
Component library
Component library
Component library
Once the primary UI designs were done we started to think about our wider Finity component library, with the plans of it evolving into a design system project. This is an important part of our overall process right now as whilst we are working closely with innovation projects, we have large uphaul projects of our current product offerings to complete in order to fully transition the brand. Currently for the legacy platforms there is no centralised design system, so we are starting from scratch.
Once the primary UI designs were done we started to think about our wider Finity component library, with the plans of it evolving into a design system project. This is an important part of our overall process right now as whilst we are working closely with innovation projects, we have large uphaul projects of our current product offerings to complete in order to fully transition the brand. Currently for the legacy platforms there is no centralised design system, so we are starting from scratch.
What I would have done differently
What I would have done differently
What I would have done differently
Having to quickly pivot onto this project proved a little tricky for the process and good communication between cross-functional teams was key. Had things been a little different we would have had more time to work on testing before the build and questioning certain features that perhaps were added in at request for the sake of trying out new tech rather than it serving the user, but we didn't have the capacity to put this to the test.
Due to the sudden pickup in speed, our plan for organisation fell apart a little bit and we will have to come back to make sure our designs are all as consistent as we want them to be before live.
It would have been good to a/b test the designs a little more, including the visual design due to it being the first go-live product of a new brand image.
Having to quickly pivot onto this project proved a little tricky for the process and good communication between cross-functional teams was key. Had things been a little different we would have had more time to work on testing before the build and questioning certain features that perhaps were added in at request for the sake of trying out new tech rather than it serving the user, but we didn't have the capacity to put this to the test.
Due to the sudden pickup in speed, our plan for organisation fell apart a little bit and we will have to come back to make sure our designs are all as consistent as we want them to be before live.
It would have been good to a/b test the designs a little more, including the visual design due to it being the first go-live product of a new brand image.
Having to quickly pivot onto this project proved a little tricky for the process and good communication between cross-functional teams was key. Had things been a little different we would have had more time to work on testing before the build and questioning certain features that perhaps were added in at request for the sake of trying out new tech rather than it serving the user, but we didn't have the capacity to put this to the test.
Due to the sudden pickup in speed, our plan for organisation fell apart a little bit and we will have to come back to make sure our designs are all as consistent as we want them to be before live.
It would have been good to a/b test the designs a little more, including the visual design due to it being the first go-live product of a new brand image.
What's next
What's next
What's next
This project is due to go live at the start of 2025.
A mobile app will be designed with the same feature set as the web based version minus the users ability to manage cardholders.
We are currently in the hi-fi design phase of the project and are delivering features one step ahead of the ones the developers are working on.
We are using this project as an opportunity to start building out the Finity component library. As we iterate through each feature we are pulling reusable components out with the goal of coming back and developing them into a reusable component library.
When the hi-fi designs have been created as a first iteration we will prototype and test the designs and collate feedback for further work.
This project is due to go live at the start of 2025.
A mobile app will be designed with the same feature set as the web based version minus the users ability to manage cardholders.
We are currently in the hi-fi design phase of the project and are delivering features one step ahead of the ones the developers are working on.
We are using this project as an opportunity to start building out the Finity component library. As we iterate through each feature we are pulling reusable components out with the goal of coming back and developing them into a reusable component library.
When the hi-fi designs have been created as a first iteration we will prototype and test the designs and collate feedback for further work.
This project is due to go live at the start of 2025.
A mobile app will be designed with the same feature set as the web based version minus the users ability to manage cardholders.
We are currently in the hi-fi design phase of the project and are delivering features one step ahead of the ones the developers are working on.
We are using this project as an opportunity to start building out the Finity component library. As we iterate through each feature we are pulling reusable components out with the goal of coming back and developing them into a reusable component library.
When the hi-fi designs have been created as a first iteration we will prototype and test the designs and collate feedback for further work.
Thanks for checking out my work 👀