The Issue
Why it Matters
Barricades at Entrances
The path entrances are barricaded without effective signage regarding closures and detours.
The Bayview Detour
Though an alternative route is available, poor signage results in low usage.
Proximity to Downtown
The trail is just minutes from downtown and high-density residential areas.
Green Space
The trail offers Toronto residents an essential escape into nature.
Problem Statement
Objectives
Highly scannable information – Create a solution that is easily understood and used by trail users.
Maintain a sense of discovery – Enhance the experience without removing the sense of exploration.
My Role
I was responsible for the entire end-to-end process of this project, from research and data collection to UX design, prototyping, and testing. This case study was developed as part of the Graphic Design 2 course at OCAD University, where I applied UX research, data visualization, and interaction design principles to solve a real-world navigation challenge.
Meeting Users' Needs
Through data analysis and user interviews users expressed a need for a better understanding of trail detours but only at a high level. Their primary concerns were:
Basic information on the landscape, entry points, and detours
Minimal interaction with screens, limiting time spent not experiencing the environment
Maintain a sense of discovery while navigating the trail
To accommodate this, information was designed to be quickly digestible at a glance while remaining non-intrusive.
Data Collection
To address the problem, I gathered data on the trail closure from government sources and social media posts to understand the situation. This information was compiled into a report to identify trends and gauge user sentiments. Additionally, I conducted interviews with trail users to understand their needs and how they navigated the closures.
Analysis
Key Takeaways
Why Bridges?
User-uploaded images on Strava revealed that bridges along the trail were the most commonly photographed landmarks. This indicated that users were already familiar with them. Leveraging this, the trail was divided into sections based on bridges, which also aligned with major entry points.
Why No Traditional Maps?
Given the highly linear nature of the trail, user testing revealed that maps were unnecessary for navigation. Instead it was revealed that with few other significant landmarks, users oriented themselves by proximity to the next bridge rather than needing a full trail map. Although counterintuitive, usability tests conducted on-site validated this hypothesis.
Why Mobile?
A mobile solution was chosen because users already carry their phones, eliminating the need for extra materials like printed maps. Physical signage is frequently vandalized or removed, making it unreliable, whereas a mobile-based approach ensures users always have up-to-date detour information.
Testing Approach
The designs went through multiple testing stages, including:
Moderated usability studies
A/B testing
User interviews
Insights gained led to refinements such as:
Keeping information architecture shallow and minimizing screen complexity.
Simplifying visuals to reduce cognitive load.
Separating the "Images" screen from the "Trail Map" screen for clarity.
Ensuring the visualization matched real-world trail bifurcations at detours.
An Iterative Approach
Through rounds of user testing, it was determined that a consistent structure was effective for both landscape and access information (trail map) as well as image information. However, users preferred standard chart formats for summary information.
Early Explorations
Sketches & Icons
Various icons were tested to ensure reduced cognitive load, and scanability.
Chart Comparisons
Different layouts were tested to optimize readability.
Standard Charts
Users found them easier to interpret than image-heavy designs in the summary.
Images within Charts
While engaging, they reduced quick information retrieval.
Results
Through A/B testing and user research, the prototype demonstrated significant improvements in information retrieval and user experience. Previously, trail users had to search across 3–5 different websites and spend several minutes gathering closure and detour details. With the prototype, they could access all necessary information in a single location within seconds.
Learning
Faster Information Access – The prototype eliminated the need for scattered online searches, drastically reducing the time needed to find trail updates.
Reduced Frustration & Cognitive Load – A/B testing confirmed that users struggled to retrieve critical closure information without the app, while the prototype provided a clear, streamlined solution.
Potential for Increased Trail Usage – While live implementation data isn’t available, improving accessibility to closure and detour information could encourage more users to continue using the trail rather than abandoning it.
Hypothetical Success Metrics (If Implemented)
50%+ reduction in time spent searching for closure and detour information.
Higher adoption of designated detour routes due to clearer navigation cues.
Improved user engagement, measured through app interactions or feedback on usability.
By eliminating uncertainty and centralizing trail information, this prototype offers a scalable solution that aligns with user needs while preserving the trail experience.
Next Steps
Further refine the prototype based on additional user feedback.
Explore ways to integrate real-time detour updates while maintaining minimal phone reliance.
Consider expanding the approach to other urban trails with similar closure issues.