<aside> 👨🔧 Currently involved helping people find flexible works by choosing where and when they want to work. Assessing and validating new concepts, prototypes and products to build the new age of staffing platforms.
Product Design Lead (UX & UI)
Coople started as Staff Finder a few years back, and their mission has always been to revolutionise the way gig economy is setup and runs based on the concept of the traditional staffing agency where companies request a set amount of workers to fill in their shifts based on placing order in a very traditional way.
They changed that by giving the power to workers to apply to as many jobs and shifts they wanted, making it then easier for them to plan their work around their life and not the other way around.
On paper this idea seems brilliant and easy to execute, but the deeper you dig into the flows and how everything is interconnected; the experience of the workers, the employers and some magic force in between still needed to do some manual work to ensure all shifts are staffed and workers know where and how to go to their jobs, currently done by Coople.
The model is clear, and the vision aligned, towards a more automated and user-friendly set of platforms that allow both workers and employers to manage their jobs in a very flexible way, but given the amount of work, different typologies of jobs and how every company runs in a slightly different way, the challenge here is to build a platform that fulfils the needs of as many people as project, and building a one size to fit them all is a monumental task.
As part of my day-to-day tasks at Coople as Senior Product Design within an agile feature team, I have to lead the design and implementation of new features as well as improvements across all the products in Coople that cover multiple platforms and verticals.
The teams are usually shaped by a Product Owner, multiple developers and a sole designer in charge of executing the designs as well as research and testing and gathering feedback to continue with further improvements.
In order to maximise the resources and the impact of our work we applied the user-centric design process where we gather feedback and requirements at an initial stage, we conduct research on the topics that related to the pain points that we want to solve and work on a backlog around those in the most concise and precise way without loosing track of the global OKRs of the company and how we can influence those.
Within the internal flow of the company and how the product development has their own workflows setup, as a senior product designer involved in the implementation of new features and improvements, my process was as follow:
Research at Coople happens in different phases and levels of complexity, depending on the nature of the things that need research of how much effort would require to implement and test, but one of the highlights of how the company is setup is that feedback and the voice of the users come from different fronts: from our internal users, the customer care team, for who we build internal products always providing feedback and keen on testing new prototypes and answering our questions, to arranging interviews or a constant flow of emails from our employers to who we interview regularly and put in front of prototypes for them to test them. And finally with our bigger user base, our workers, for who we set up jobs in the platform for them to be testers and object of research in either usability testing or user interviews.
We are quite lucky as the different ways our users have of providing feedback, is up to us to make sure it's aligned with the things we are working on and can generate more impact and be of significant influence based on the research.