Discovery Research for Profi.io

A user-centric approach to shaping the future of coaching and consulting on Profi.io

This case study highlights how user research shaped an all-in-one solution for coaches and consultants, streamlining administrative tasks to let pros focus on their clients.

  • The Problem:
  • Profi.io lacked clarity in its unique value proposition (UVP), target audience (TA), and strategic differentiation. Its features also failed to address the diverse needs of all users effectively.

  • The Goal:
  • Understand and map practitioners' service delivery processes while identifying the pain points encountered by coaches, trainers, and consultants during their interaction with clients. Leverage findings to define UVP.
  • The Hypothesis:
    The current platform functionality limits coaches, trainers, and consultants from building flexible services due to package and program restrictions.
  • My Role:
  • UX Researcher

The Tools Used:
Notion.io,
Miro.com,
Productboard.com,
Respondent.io,
LinkedIn,
Hubspot.com,
Zoom,
Fathom AI,
Google Workspace.

The Team Involved:
UX Researcher,
Product Manager,
Product Designer,
Customer Success Team.


Duration
6 weeks
(December 2022-January 2023).

Research Impact

Skip to My Research Process

Clickable arrow icon leading back to the stages of My Design Process
Infographic for Research Impact

Refining the Ideal Customer Profile (ICP)

Insight:  
Trainers primarily need LMS (Learning Management System) functionality, which the platform cannot effectively provide.

🎯 Decision:
Exclude trainers from the target audience, avoid marketing to them, and deprioritize product changes requested by trainers. This allowed the team to focus efforts on segments that align with the platform’s core value proposition.


Identifying Product Gaps and Shaping Decisions

 Insight 1:  
Coaches and consultants need the ability to create flexible client engagements with organized materials.

🎯 Decision:
Consolidate the Programs and Packages features to create a new Engagement feature. This functionality enables professionals to organize materials and sessions in a chronological flow and track progress for both themselves and their clients.

Insight 2:  
Scheduling is cumbersome and represents the platform’s primary use case.

🎯 Decision:
Prioritize upgrading the scheduling experience to make it seamless and efficient for both roles.

Insight 3:  
Both coaches and clients need visibility into service delivery progress (e.g., sessions remaining, material covered, or time left).

🎯 Decision:
Introduce progress visualization for both professionals and their clients.

Insight 4:  
Many coaches and consultants want quantifiable insights into their performance.

🎯 Decision:
Develop an intuitive reporting feature to help professionals track and analyze their results.

Strategic Product Roadmap Adjustments

Research informed the design of the new features

The design team used research insights to begin developing functionality tailored to the needs of coaches and consultants. The goal was to ensure a seamless flow of service delivery that directly addressed the core requirements of the refined ICP.

My Research Process

Below, I highlight the key questions addressed during this project and how I tackled them to achieve the research goal.

1. What are the research goals?
2. Which method to choose?
3. Who to speak to?
4. How to prepare for and conduct the interviews?
5. How to make sense of data?
5. How to share the insights with the team?
7. How to make insights accessible for all team members?
8. What challenges did I face during this project?

What are the research goals?

Initially, this project aimed to uncover potential unique value propositions for our customers, but we needed to specify the goal of the project and understand the research questions we needed to answer to accomplish this goal.

The process of defining the research goal

Firstly, I discussed the purpose of the research with both the Product Manager and the Customer Success (CS) team to gain insights into customer challenges. After that, I developed an initial hypothesis:

"Coaches, trainers, and consultants struggle to solve all their problems using the current functionality of Profi.io, as the platform doesn’t provide a flexible way to build services."

Through further collaboration with the Product Manager, we refined the hypothesis to:

Refined hypothesis:
"The current platform functionality limits coaches, trainers, and consultants from building flexible services due to package and program restrictions."

Secondly, In close partnership with the Product Manager and CS team, I outlined the research goals and formulated key research questions. After preparing and sharing an initial list with the Product Manager, we collaboratively refined and finalized it to ensure all perspectives were considered before moving forward with the research.

Goal:
This project aims to map the service delivery process for coaches, trainers, and consultants, and validate our assumptions about core narratives: target audience (TA), value proposition, strategic differentiation, the problem we are solving, and the business model.

Research Questions:
- What is the main pain point we’re solving for our market?
- What is the value proposition we’re offering our market?
- What can be our strategic differentiation?
- What is the native service delivery process for coaches? What are their biggest pain points?
- What is the native service delivery process for consultants? What are their biggest pain points?
- What is the native service delivery process for trainers? What are their biggest pain points?‍

Which method to choose?

When I joined the team, a competitive audit had already been conducted, revealing a diverse landscape of platforms, each with its unique strengths. Despite their advantages, we noticed that many customers were transitioning from these competitors to Profi in search of something different. So, what were our customers truly seeking?

To navigate this uncertainty and uncover our Unique Value Proposition, I realized we needed to maximize our limited resources. In close collaboration with the Product Manager, I selected three key research methods to gain comprehensive insights into the user experience:

Through this methodical approach, we gained the clarity we needed to refine the understanding of our users and, ultimately, to shape the future of our platform.

Who to speak to?

Defining the target audience for the research

It was crucial for us to determine our Ideal Customer Persona to be more focused on whom we can bring the most value.
That's why we needed to carefully select the research participants to ensure the results of the study are as representative as possible.

The primary users of the Profi platform at the time were mostly coaches, consultants, and occasionally trainers. To gain a comprehensive understanding of their native processes, I chose to interview:

Interesting fact:  
The users of Profi platform are not only our direct customers. They are also clients of our customers. So my goal was to get the information from both sides to understand the issue from different perspectives.

Other criteria for research participants

  • Team Collaboration: Participants had to work in a team of at least two professionals. This would allow us to understand not only the challenges they face with their clients but also the pain points in team collaboration and how Profi can support them.
  • Client Load: Participants needed to have more than five clients. This ensured participants had systemized their processes, offering deeper insights into daily challenges.
  • Tech Savviness: We recruited participants with varying levels of technological proficiency, ensuring that our findings were inclusive of different user experiences.
  • Diversity: We made sure to recruit participants of different ages, genders, and levels of tech savviness to ensure a broad and inclusive perspective.Accessibility: We also included participants with disabilities to ensure that the platform could better serve professionals with varying needs and abilities

Recruiting research participants

I utilized the following platforms as our main sources for respondents and for each platform, I slightly adjusted the recruitment strategy based on its unique characteristics:

To acknowledge their time and contributions, each participant was offered an incentive for their involvement in the study.

This is a gif showing the Screener Survey contents

Screener survey

To recruit professionals who met the established criteria, I created a screener survey to identify suitable participants.

I used Google forms for respondents from Linkedin, Facebook groups and my personal network. On Respondent.io, I utilized their native tool for creating the screener survey.  

How to prepare for and conduct the interviews?

Before the interviews

To ensure our interviews were structured and effective, I embarked on a thorough preparation process that involved several key steps. Below, there are slides presenting all the documentation I prepared prior to conducting the interviews.

A screenshot of the Research Plan
A screenshot of the SOP document
A screenshot of the SOP document
 A screenshot of the Interview Protocol
 A screenshot of the Interview Protocol
 A screenshot of the Raw Data Spreadsheet
 A screenshot of the Conversation Guide
 A screenshot of the Thank you email template
Picture representing collaboration with the team

Conducting the interviews

These are the main rules I followed to make sure the interviews run smoothly

  • 1. Invite team members
    Each interview was recorded, and either I or the UX Research intern took detailed notes using the Interview Guide spreadsheet. This dual approach ensured we didn't miss any crucial insights while maintaining the flow of a dialogue.
  • 2. Record and take notes
    Each interview was recorded to capture the conversations accurately, and either I or the UX Research intern would take detailed notes using the Interview Guide spreadsheet. This dual approach ensured we didn't miss any crucial insights while maintaining the flow of a dialogue.
  • 3. Debrief with the team
    After each interview, we held a 15-minute debrief session to review our notes and discuss key findings. This reflection allowed us to identify immediate action items and determine the next steps based on participants' feedback.
  • 4. Send a thank you email
    Following each session, I would send a thank you email to the participants, expressing our gratitude for their time and insights. If time permitted, I would also update the Raw Data spreadsheet with all the collected information, ensuring our data remained organized and accessible for analysis.

How to make sense of data?

Creating Affinity diagram

To uncover patterns and commonalities, I created an affinity map by visually grouping pain points of coaches, trainers and consultants as well as observations into themed categories. This approach helped me identify the most pressing and recurring issues faced by these professionals.

Thematic analysis of pain points

I conducted a thematic analysis of pain points, identifying patterns for coaches, trainers, and consultants.
Thematic analysis of pain points

I also analyzed and grouped pain points of their clients.
Thematic analysis of pain points

In partnership with CS team, I analyzed our current customer’s pain points.
High and critical feature requests
 I also analyzed feature requests from existing customers. This helped in understanding their unmet needs and provided a holistic view of pain points across user groups.

Process mapping

By analyzing the workflows of coaches, trainers, and consultants, I mapped out the typical service delivery processes for each role in the form of diagrams. These visualizations provided a clear understanding of how these professionals operate. I then integrated the pain points identified in the affinity diagram into these processes, creating a cohesive view of challenges within their workflows.

Raw native process diagram

During the interviews, I captured the native service delivery process of each participant to understand their unique workflows.
‍
Refined native process diagram

After the interviews, I refined each process diagram to make them more readable for team members and to simplify the analysis. 
‍
Common patterns

By analyzing the refined diagrams, I identified common service delivery processes for coaches, trainers, and consultants.
Here is an example of the common coaching service process.

Master process map construction

In collaboration with the Product Manager, we developed a comprehensive master process map. This map consolidated all service delivery steps, user actions, and the corresponding pain points into a single, unified view. We enriched this map with user stories covering every step of the process.

Complete process map

Profi functionality mapping

Finally, we overlaid the master process map onto Profi.io’s current functionality. This exercise allowed us to pinpoint gaps and strengths in the platform’s features, highlighting areas for improvement and potential opportunities to enhance the user experience.

How to share insights?

Effective communication is key to ensuring research insights drive impactful decisions. I utilized multiple strategies to share findings with cross-functional teams, tailored to their specific needs.

Going through the process map with the team

I organized collaborative sessions to walk the team through the comprehensive service delivery process map.

These sessions focused on:

  • Explaining the pain points and user stories tied to each step.
  • Aligning on how these insights impact product priorities.
  • Encouraging team members to ask questions and contribute their perspectives.

Presenting insights to stakeholders

When presenting insights to stakeholders, I adhered to a few key principles to ensure clarity and engagement

  • Tailored Communication: I adjusted the presentation style based on the audience's familiarity with UX research.
  • Actionable Outcomes: Insights were tied directly to business goals and included actionable recommendations.
  • Concise Storytelling: I emphasized storytelling with real user quotes, visuals, and prioritized findings to keep the presentation compelling.

Presenting insights to development team

For the development team, I focused on translating insights into actionable steps by:

  • Breaking down technical pain points and user challenges.
  • Highlighting opportunities for quick wins and iterative improvements.
  • Maintaining open communication to address feasibility and constraints.

Co-design sessions

Sharing insights didn’t stop at presentations. I immersed myself in co-design sessions, championing the user’s voice at every stage of the process. I provided evidence from user interviews to support design decisions and worked closely with designers and product managers to craft thoughtful, user-centered solutions. My focus was always on keeping the user at the heart of every discussion, guiding the team toward decisions that directly addressed pain points and elevated the overall experience.

How to make insights accessible to all team members?

Sharing research insights through a presentation is a great first step, but it doesn’t guarantee everyone on the team will retain the details or fully grasp the findings. Ensuring easy and ongoing access to research data is essential to keeping the team aligned and informed. Here are the key principles I follow to achieve this:

What challenges did I face?

THis project required a lot of problem solving on the go and here are some of the challenges I and the team overcame to achieve exceptional results.

Recruiting phase

Challenge:  
While using Respondent.io, I encountered a challenge with the accuracy of the screener survey responses. Some participants overstated their qualifications, particularly regarding the number of clients they managed (e.g., claiming to have more than 5 clients when they only had 1 or were still in the early stages of client acquisition).

🎯 To address this, I conducted a brief pre-interview chat with each potential respondent to verify their qualifications before officially inviting them to participate in the study. This extra step ensured that we recruited participants who truly met the criteria, providing more reliable and valuable insights for the project.

I knew that another option was to adjust the screener survey questions, but since this issue occurred only on Respondent.io, and I wanted to maintain consistency across all platforms, I opted for this additional step specifically for Respondent.io.

Interviewing users

Challenge 1:  
Not everyone on the team was fully aware of the fundamental principles researchers should follow during interviews. This resulted in a few issues in maintaining the conversation flow.

🎯 To address this, I organized a brief 10-minute prep session before each interview. During these sessions, we reviewed the main questions, discussed any relevant background information about the participant, and aligned on our common objectives.

🎯 I also took the time to remind the team of essential interviewing rules: avoiding product promotion, steering clear of leading questions, asking open-ended questions whenever possible, and encouraging observation over speaking.

Challenge 2:  
Participants faced difficulty explaining all the steps of their service delivery process without losing focus on the sequence of steps. Often, they would recall specific challenges unrelated to the overall process, which risked derailing the conversation. With only 60 minutes for the interview, maintaining focus was critical.

🎯 To assist the conversation and to help us all stay focused on the goal of the interview, I prepared a Miro board which i used during the interview to illustrate the process they were describing. (I would share the screen and draw the schema of their process delivery as they spoke)  THis insured that all the steps were mentioned and put in the correct order. It was then also easier to map the pain points to each step illustrated on the schema.

Next Case Study:

Clickable arrow up to get to the top of the page

Back to top