After building the low-fidelity prototype for HayDay, the next logical, and essential, step was clear: it was time to put it in front of real users.
Prototype testing is the bridge between our assumptions and reality. It’s one thing to imagine how a user might move through booking a trail ride or proposing to their partner on horseback. It’s another thing entirely to watch them do it, narrating their thought process as they go. And that’s precisely the point of user prototype testing: uncover friction points, hidden confusion, unexpected behaviors, and little moments of delight all before a single line of code gets written.
Setting Up the Test
User testing for HayDay followed a straightforward but carefully considered process. Two users were selected for remote testing using a clickable POP (Prototyping on Paper) prototype:
- Cynthia DeRose, 57, retired, tech-comfortable but not tech-fluent.
- Olivia DeRose, 17, assistant manager at Red Buffalo Ranch, is highly familiar with the ranch but new to the app.
Testing was conducted over Zoom, using screen sharing and audio recording to capture real-time reactions. Each participant was given a script and asked to complete four core tasks without guidance:
- Book a trail ride for a future date and time.
- Modify an existing reservation.
- Plan a special event, such as a proposal ride.
- Complete payment and add the ride to a calendar.
The testers were encouraged to “think aloud,” narrating their experience, frustrations, surprises, and thoughts freely. This setup mirrors methods used in earlier UX studies, where low-fidelity prototypes were tested in small-scale, real-world settings to collect qualitative feedback.
What I Wanted to Learn
The goals for this round of prototype testing were simple:
- Navigation: Could users intuitively find their way around the app?
- Task Completion: Could they efficiently perform core actions like booking a ride or editing a reservation?
- Pain Points: Where did confusion, hesitation, or backtracking occur?
- Expectations vs. Reality: Did the app meet the users’ mental model of how a booking app should work?
This wasn’t just about testing “if it worked,” it was about listening for nuance, about spotting the nearly invisible hurdles that often turn good apps into great ones when fixed early.
What I Learned
During usability testing, several consistent patterns and points of feedback emerged across both participants. These themes helped validate areas of strength in the app while highlighting opportunities for improvement that will guide the next iteration.
| Theme | Findings |
| Navigation Clarity | Users found the app generally intuitive but suggested that modifying existing reservations could be made more seamless. |
| Content Expectations | First-time users expected more information about the ranch, services, and ride options to be available before booking. |
| Special Events Booking | Booking a proposal ride felt too complex to complete independently through the app; a personal support option would better meet user expectations. |
| Labeling Improvements | Certain sections, like “Events,” were unclear and should be renamed to more accurately reflect their content (e.g., “Special Cases”). |
| Payments & Policies | Users preferred having flexible payment options, such as Venmo, and requested clearer communication regarding policies, including helmet requirements and weather alerts. |
Expanded Key Insights
First-Time User Content Needs: Cynthia repeatedly asked, “What should I wear?” and “What happens if it rains?” This revealed a strong need for a richer “Explore the Ranch” section, complete with FAQs, photos, and clear guidelines on gear and policies. By answering these questions upfront, we can build user confidence and reduce the number of support inquiries.
Special Event Booking Friction: Both testers found the proposal planning form too generic. They recommended pivoting that flow into a “Request a Callback” option, allowing a ranch representative to add the personal touch these events require. Renaming “Events” to “Special Experiences” or “Packages” would also clarify the section’s purpose.
Streamlined Reservation Edits: When modifying a reservation, users should see available time slots immediately. By surfacing openings in real-time, we can eliminate unnecessary navigation steps and make schedule changes quickly and frustration-free.
Login & Guest Checkout Confusion: Cynthia was prompted for a password without clear guidance on account creation. A simple inline note, such as “Don’t have an account? Create one here,” will help orient guest users and prevent dead ends during the booking process.
Flexible Payment Options: Olivia suggested adding Venmo for group deposits to avoid credit card fees. Offering multiple payment methods not only modernizes the experience but also supports the diverse needs of ranch visitors.
Next Steps
After digging through all the feedback from user testing, I’m excited to share what’s next for HayDay! The next phase focuses on refining and enhancing the prototype to make it feel more natural and intuitive for all users.
One of the first things we’re tackling is the “Explore” section. I’m adding more helpful content, such as FAQs, photos, dress code tips, and information about their weather policies, all things that should make it much easier for first-time visitors to feel prepared.
I’m also streamlining the process for booking special events. Instead of requiring guests to fill out a complete online form, they’ll be able to “Request a Callback.” I’m also considering renaming that section to something clearer, such as “Special Experiences” or “Packages,” to make it easier to find.
Rescheduling is about to get a lot easier, too. I’ll be showing real-time availability, which should make picking a new time way faster and less frustrating. Since the users were confused at checkout about whether they needed an account, we’re adding clearer messaging to guide them through the process if they need to create one.
Another thing I’m excited about is exploring the option to add Venmo as a payment method, instead of credit cards, since they don’t accept credit cards due to the high fees associated with them. That should give guests (especially groups) more flexibility when it’s time to settle the bill.
If you’re interested in diving deeper into everything we learned, I put together a complete Prototype Testing PDF. It includes scripts, participant info, task flows, and a summary of the big takeaways. Feel free to check it out or download it below for a closer look at how this feedback is shaping the next version of HayDay!