Back to resources

Combining User Research with Testing to Build a Successful Product

Innovation / Experiment
Product
Conflict Solving
Feedback
Users

20 April, 2022

Waldo Vanderhaeghen
Waldo Vanderhaeghen

VP Product at 3YOURMIND

Waldo Vanderhaeghen, VP of Product at 3YOURMIND, details an experience in product discovery, analyzing user research, and testing.

Building a Booking Funnel

After joining a company, I was assigned to build a funnel that would obtain customers digitally rather than through traditional offline channels. The challenge with building a booking funnel was that the direct customers were not familiar with digital media; think senior citizens and elderly people. However, these individuals had children or families that could help them use the services.

The product itself enabled senior citizens to find caregivers that matched their needs. During the discovery phase, many of our users mentioned how important a personal connection with their caregiver was to them. Based on that insight and other competitor information, our company knew that we needed to integrate profiles for each caregiver. We wanted the users to be booking people rather than a service.

Working Through The Discovery Process

Testing our Product:

We built and designed a prototype of our idea: incorporating profiles for each of our caregivers. However, when we began testing it, we encountered some friction. Rather than feeling that personal connection with caregivers, our users were apprehensive to book services with them based on their profiles. Users started to question:

  • Was the caregiver too young?
  • Where was the caregiver from?
  • Did they speak the user’s native language?
  • Does the caregiver have enough experience?

We quickly realized that having profiles on our service might not be conducive to those in need but rather act as a distraction. On the other hand, profiles may have been convincing to some users when they found that personal connection. The duality between distracting and convincing profiles stayed with our team for almost the entire product’s lifecycle.

Decision Making:

Based on the user research, including entire team discussions, we decided to pivot. It was difficult, as I felt personally a bit attached to the product in its previous form, but nevertheless, I was happy we pivoted.

Our product changed models where users reserved services based on their specifications. These were anything from gender, age, and responsibilities. After moving to this model, we gained initial traction and eventually success.

What to Consider During Discovery

  • It’s essential to be flexible throughout discovery. Even with large amounts of pressure to start developing a product, without nailing the exact product during discovery, the product may not be successful as it could.
  • Keep the key focus on the needs of the customers over everything else. Without that, your product may not be targeted to the correct audience.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

Streamlining Product Processes After a Reorganization

16 May

Snehal Shaha, Lead Technical Program Manager at Momentive (fka SurveyMonkey), details her short-term technical strategy to unify processes among teams following an acquisition.

Acquisition / Integration
Product Team
Product
Building A Team
Leadership
Internal Communication
Collaboration
Reorganization
Strategy
Team Processes
Cross-Functional Collaboration
Snehal Shaha

Snehal Shaha

Senior EPM/TPM at Apple Inc.

How Less Viable Solutions Solve Common Architectural Challenges

13 May

Tom Hill, Engineering Manager at Globality, Inc., describes his decision-making practices when making architectural decisions.

Architecture
Different Skillsets
Conflict Solving
Collaboration
Tom Hill

Tom Hill

Engineering Manager at Torii

Navigating Disagreements When It Comes to Priorities

9 May

Pavel Safarik, Head of Product at ROI Hunter, shares his insights on how to deal with disagreements about prioritization when building a product.

Innovation / Experiment
Product Team
Product
Dev Processes
Conflict Solving
Internal Communication
Collaboration
Convincing
Strategy
Prioritization
Pavel Safarik

Pavel Safarik

Head of Product at ROI Hunter

Leading Your Team in Stressful Situations

27 April

David Kormushoff, Director at Koho, recalls how he galvanized his team to tackle a time-sensitive problem, sharing his tips on how to shift chaos into calm.

Goal Setting
Leadership
Conflict Solving
Deadlines
Collaboration
Motivation
Strategy
Health / Stress / Burn-Out
David Kormushoff

David Kormushoff

Director at Koho

Why You Should Take Technology Risks in Product Development

25 April

Matias Pizarro, CTO and VP of Residents at ComunidadFeliz, recalls a time in his early career when he took a technology risk that had wide-ranging benefits to his product's user experience.

Innovation / Experiment
Product
Scaling Team
Dev Processes
Matias Pizarro

Matias Pizarro

CTO and VP of Residents at ComunidadFeliz

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.