Intro
Many fitness entrepreneurs face a critical problem when trying to strike it out on their own: they know how to operate the fitness side of things, but aren't good enough with entrepreneurship to become profitable. The Privato platform, part of the wider EmpirePreneur brand, looks to close the gap for trainers moving from purely training to fitness entrepreneurship.
Privato Fitness solves the problem of trainers connecting with with compatible clients and operating their fitness brand.
My Role
As a UX Designer, my role on the Privato Fitness Project was to implement the entire User Centered Design proecess end to end with a team of 3 other UX designers.
Our process followed the below methodology:
Because this was my clients' first phase of working with designers, I wanted to align on what his business goals were
His ultimate goal was to:
After understanding his business needs and vision, I learned that our final deliverable would be the beginnings of a technical solution for fitness experts and clients.
To better understand the fitness space, my client asked me to review four fitness platforms that he wanted to use as inspiration for the Privato Platform
Here were my insights:
I originally hoped to conduct user interviews, but do to time constraints I was only able to conduct my initial user research via a Qualtrics survey with 8 participants.
Define
I used an affinity map to better find the overarching themes from my data in order to better understand where my users' needs were centered. I gained the following insights:
Since this design effort could span multiple teams, I wanted to make sure my designs were focused on people, so I created a persona to reflect my findings from my research and also to help guide my design efforts for this project.
Because I'd yet to truly define my research as problems to solve, I created HMW questions to focus my design efforts on problems to solve.

After creating HMW questions to focus on problems to solve, I needed to further break these down into actionable pieces for this specific sprint I was conducting with my client. To do this I made user stories around my original HMW questions.
I identified that the following functionalities/features were critical and therefore would be a possible design focus during the project:
After creating all of my user stories, I started creating user flows for some of the critical paths the target user would be pursuing when trying to accomplish their goals.
After reviewing these paths with my client, I realized that creating designs for these red routes would be much too much for the scope of this project. For this reason I revised the red routes from 4 (image on the left) to 2 (image on the right):
Design
The client originally outlined that this solution should be a desktop application with the possibility of being on mobile further down the road. For that reason I focused on sketching solutions for a desktop solution, focused on onboarding and accepting new clients as outlined in previusly in my red routes.
Due to time constraints and client availability, I moved onto creating low fidelity options for our designs without validating anything with potential users.
Using Figma, I created some low fidelity designs based on my sketches. After showing these to the client, I didn't get any pushback or concerns before moving to more high fidelity designs, so I moved forward in making these wireframes more high fidelity.
My client already had initial branding and typography to start from on our style guide, so I began creating system-specific buttons, icons, and interactions to use during the entire development of the Privato platform. I used my clients' ask to evoke trust and industry-leading brand recognition when designing the symbols and buttons, which resulted in using lighter tones and more rounded shapes.
I moved to creating high fidelity designs with the following assumptions and input from the client:
Deliver
When creating my research plan, I wanted to focus on several key goals:
The full test plan can be viewed here and script can be viewed here.
Due to time and availability constraints I was only able to conduct usability testing with 3 participants. The feedback I got can be viewed in a usability report here.
The main insights from the first round of testing were the following:
If I had continued the design process with my client I would have done the following as my next steps:
Learning & Limitations
Below are my thoughts on what I learned during this client project:
Every project has its limitations, and this one is no different. I've identified some of those limitations below:
Projects
Privato FitnessDiscovery research, visual design, design systems, user flows, user stories, data synthesis, how might we questions, usability testing
Omadi Torch-Problem Sync & performance issues, painful usability, high task completion time -Solution Only sync information drivers need, all towing types in one list, geo-tagging, consistent workflow for all jobs, interactive photos & damage reporting, mobile payments, eliminate time consuming inventory. -Role My role was as Jr. UX designer on the project. As Jr. UX designer, I owned the workflow of conducting field research with current users of the Omadi mobile platform, as well as assisted with the redesign process (visual design, user journeys, user flows, etc).
Ballot BuddyProject type
TinyTales Design SprintSpringboard
Metaverse UX ResearchProject type
Ticket Admin ResearchProject type