Visual App Design

Designing the layout for an App to Match Riders with Horses

Role: UX Researcher
Intent: Thought Exercise
Client: The Wranglers
Timeline: Summer 2019

Quick Backstory

One summer I decided to work as a horse wrangler at a kids camp in Colorado. I’ve been riding since I was young and love horses, so I figured it would be a perfect summer job. In the end, it turned out to be a less than ideal situation with staffing issues and a herd of horses that did not match up with a kids camp. In the end, I managed to scrape together a program for the summer that avoided safety hazards and harm to the children. Emerging on the other side of this experience, the problem-solving tendency in me struggled with how this could’ve been prevented and what I could do to fix it for the next person. This piece reflects how I think the major problem with the horse program in specific at this camp could be solved or at least improved upon.  

Step 1: Identifying the Problem

Since this was a summer job, that meant little consistency in roles. New horse wranglers would come every summer and the most recent existing wrangler guide was full of outdated information. Additionally, the camp rented 20 horses to fill out their herd in the summers. These horses came with no information and the new wranglers had to quickly determine which horses were best for younger children. Having ridden horses for over 10 years and helped out at riding programs for five, if I know anything, it’s that you need to be sure your horses temperament is well suited for the chaos of little kids. If not, then there’s going to be a lot of problems, and with a thousand pound animal, you really don’t want to have problems. So the question is: how do I make sure what I had to go through doesn’t happen with the next wranglers? How do I pass down all the useful information on horses? Well, I thought an app might do the trick. A horse-child matching app.

Step 2: Collect all Relevant Information

So the next step is what information do I need to collect to input into this app to get a desired outcome? Well, turns out, there’s a lot.

For Horses:

Each horse would get their own profile with a picture and their name and the wranglers would be asked to fill out a form with questions based on the Criteria below and the option to rate the horse in each category on a scale from 1 to 5.

Criteria 1 5
Temperament Easygoing Wrangler Only
Trail-ride usability Good on all trails Spooks on some/all trails
Spookiness level Bombproof Any loud noise will set them off
Scared of Pigs (don’t ask) No Yes
Laziness Very slow Practicing for the Kentucky Derby
Can canter No Yes
Ability to leave the field/follow the leader A good follower Will turn back to paddock, or refuse to leave
Injuries/sores No Yes
Lead ability (for Wranglers Only) Not a Leader Great Leader

For the Children:

Each child would also get their own profile with their name and answers to the following criteria on a scale from 1 to 5 similarly to the horses. The Wranglers would probably need to get most of this information from the counselors beforehand.

Criteria 1 5
Temperament Rambunctious Calm
Scared of horses? Yes No
Experience None A lot
Ability to follow directions Not great Listens well

Extraneous Factors

  1. Weather for the day

  2. Total number of children for program

  3. Type of ride planned

After completing these forms, the algorithm will assign the horse a number based on overall usability in the program. The children will similarly be assigned a number based on the difficulty they might pose in the program.

Step 3: Rules for Matching Horses and Children

Overall: The calmer, better beginner horses, should have low scores, while the high-strung and dangerous horses should have higher scores. Ideally, horses with too high of a score would get returned or replaced in the program. For the kids, the lower the score, the worse rider the kid is probably going to be. The higher the score, the better rider. Thus, the horses with low scores should be ideally placed with the low score children and vice a versa. We want the kids who are likely to not listen or are nervous riders to be on the bomb-proof horses that aren’t likely to do much more than follow the trail.

Step 4: The Algorithm

This is where the magical algorithm will come into play; i.e. time to hand this information over to a developer. Here is where all the above information is inputted and produces the desired outcome; a horse to child match. Ideally, each child for the program would be matched with a suitable horse(s).

Step 4(b) : Additional Features

The main part of this app would be the horse-child matching system. However, there would be some other important features that I wish I had been given. These fall under nice-to-have features category on the app.

  • One subsection of this app would be a bridle-saddle-horse matching system, where all the tack would be labeled based on size and then matched to horses that they fit on. This wouldn’t have to be a one-to-one match, but rather a list of compatible horses for each saddle.

  • Another subsection would be a map feature with all the trails clearly marked from start to finish with the difficulty level. I’d rather not get lost in the woods on a horse again thank you very much.

  • Pictures of Horses and Children

  • Finally, sort of an addition to the main matching algorithm, a cumulative, historical database of horses and children would be helpful. There would be an option to select the “herd” for the summer and save it as a subsection of all of the horses and only run the algorithm through that. This would allow information to be passed along from summer to summer as horses may come back for another summer and the information will already be there. Same with children, though both may need to be updated.

Step 5: Implementation

This would all be put into an app that could be easily accessed on cellphones as there were no laptops available by the horses. At the beginning of the summer, the wranglers would spend most of the time imputing information on the herd, figuring out which horses were usable, and which were not. The app would then build profiles for each horse with a number based on difficulty. Ideally, during this time, horses with high numbers would be returned to the rental place and replaced. Each horse will also be able to be listed as Active or Inactive depending on injuries or sores. Then, when the kids arrive, the wranglers would input all the information available about each kid for that day (or week). Then, poof, magic! The app would match the best horse to each child from the whole herd. If there are enough horses to choose from, the app would even give multiple options of horses for each kid. The wrangler can then hand pick from their own personal experience and produce a list of horses to use for each section of the program.

Designing an App to Display Maps for a Client

Coming Soon!

Role: UX Lead & Researcher
Team: 4 UX Designers (Master's Program at the University of St Andrews)
Client: Doctor M. from the University of St Andrews
Timeline: September 2022 - December 2022
Tools: Figma, Miro, Balsamiq

1. Project Overview

Between 2009 and 2011, Dr. M conducted research on political motivations and violence, collecting data through surveys that combined questionnaires with participant-drawn maps. These maps offered unique insights into individuals' “psycho-geographies”—how different groups perceive and navigate shared physical spaces based on political or social affiliations.

While the research culminated in a published paper, all the data existed only on paper maps, making it difficult to compare, analyze, or build upon. Dr. M approached our team to help digitize this data and create a system for visualizing and comparing the maps more interactively.

Concept Statement:
- No existing system currently allows for qualitative map comparison tied to participant affiliations. Our solution explores how digital tools can reveal patterns in how different groups perceive space.

Goal Statement:
- Design a system that allows Dr. M to digitize and compare participant-generated maps, visualize affiliation-based patterns, and provide contextual background on the original research—enabling deeper, more scalable analysis.

2. Challenges

Going into this project, we recognized that there would be certain areas of concern that we needed to keep in mind throughout the design process. As we continued to gather information and shape our final prototypes, we made sure we continued to address the following areas that presented more unique challenges:

  • Data Complexity:

    • The research involved nuanced, qualitative data such as personal interviews, narratives, and hand-drawn maps—rich in meaning but difficult to visualize or compare systematically.

    • Digitizing this data was going to present a rather large issue with this project

  • Geospatial Context:

    • All responses were tied to specific geographic areas, meaning the system needed to incorporate spatial visualization in a way that preserved the context of place.

    • Maps are complex and choosing how to display a variety of information on one map would become a constant problem we work workshop through; how much is too much information? How much is too little? What becomes cluttered? What colors are associated with certain geographical features?

  • Audience Diversity:

    • The client’s end goal was to allow this map not only to be an aid for fellow academic researchers and graduate students but also to the general public. The interface needed to accommodate varying levels of technical and subject-matter expertise.

    • This tool needed to convey a lot of complex information, but also be user-friendly; this introduces the idea of ‘hiding’ features to allow users to build their own experience on the platform. We would continue to build on this throughout the project

  • Neutral Presentation:

    • Given the politically sensitive nature of the research, it was critical that the system present data impartially and avoid reinforcing biases or overgeneralizing individual responses. We designed with transparency and neutrality in mind to respect the integrity of both the research and the participants.

3. My Role: Team Leader

As the team leader, I took on a central role in coordinating and driving the project forward. With the strongest English skills in the group and a naturally organized approach, I was responsible for managing internal communication, delegating tasks, and ensuring our team met deadlines—despite the added complexity of balancing this work alongside a full semester of graduate coursework.

I helped coordinate the project, by assigning and tracking tasks across team members, adjusting for schedule conflicts, and keeping the project on track through weekly planning. We had several papers to turn in throughout the course of this project to track our progress and I ensured these were completed on time.

I was also in charge of communicating with both the client and the interview candidates. I was the main point of contact with our client and provided regular updates via email and occasionally video call.

4. Research and Interviews

To ground our design decisions in real user needs, we conducted qualitative interviews with individuals who were representative of our target user base: fellow researchers and academics who regularly work with complex qualitative data.

We interviewed a total of 7 individuals who were all colleagues and professional contacts of Dr. Murer:

  • 3 Master's students

  • 2 PhD candidates

  • 2 Professors from different universities

To prepare for the interviews, we began by crafting a thoughtful interview guide, reviewing best practices in interview etiquette to ensure we created a respectful and productive space for open-ended responses. Our questions focused on:

  • How researchers currently analyze qualitative and geospatial data

  • What tools or methods they use

  • Ideal features in a digital visualization tool

Brainstorming Interview Questions and Topics

I took the lead as primary interviewer while my group mates took notes. The conversations provided rich, firsthand insights into the workflows, frustrations, and aspirations of our end users.

From our research, we were able to begin crafting user stories for two key personas:

  • The Doctoral Researcher: Needs a way to explore participant narratives by theme and affiliation, ideally overlaid onto a map to observe spatial patterns.

  • The Fellow Academic: Wants to explore and compare findings from related research but requires sufficient background information to understand the context of each map entry.

These findings shaped how we structured the interface, prioritized features (like filtering by theme or affiliation), and thought about the data display hierarchy.

5. Synthesis & Insights

WAAD Diagram

Miro for organizing data points from interview

user personas/stories created

6. Ideation & Design

Sketch-a-thon : basically we met for two hours and just sketched different ideas and parts of the app and potential needs for it etc.

Design critique with another group

7. Prototyping & Testing

Balsamiq and then Figma: In the end we had two main prototypes with certain parts of the groups specializing on one or the other

8. Outcome & Reflection

Presentation with teachers and client. Client was happy wiht the ideas and prototypes and the team was able to answer questions raised. a solid design was presented at the end. No build stage