Back to Projects
CONCEPT PROJECT · ACCESSIBLE TRANSIT
Transit you can predict
I turned expert interviews and community research into prioritized requirements for a transit app concept for autistic travelers.

My role

Research synthesis & requirements prioritization

Context

Team of 5 · 100+ community discussions

Project status

Tested prototype · real journeys untested

Accessible Design
Requirements
User Research
Prototyping
01
Plan for unexpected changes
Our team of five investigated what could make public transit difficult for autistic travelers. We interviewed two autism-research specialists and reviewed more than 100 community posts across Reddit, YouTube, and Facebook. Unexpected route changes emerged as an important concern, alongside sensory overload and the coping strategies people already used.
02
Prioritize recovery over speed
I synthesized the research into a ranked set of product requirements. We prioritized predictability and recovery over finding the fastest route. The concept needed to explain what would happen next and give a traveler a clear option when the plan changed.
A route change needed an understandable next step.
Our persona was a UF student who wanted to travel to class independently. That kept the requirements focused on a specific journey. Route previews and quieter alternatives addressed the uncertainty we had seen in the research, while breathing exercises offered an optional coping aid.
03
Feedback changed the navigation
The team built a high-fidelity prototype with route previews and sensory information about upcoming stops. It also included hazard reporting, quieter-route alternatives, and coping activities. These were proposed features in a prototype, not a live transit service.
Focus-group feedback led us to simplify the navigation and make quieter-place rerouting easier to reach. We then used Maze for task-based testing, including finding the hazard-reporting control and starting a breathing exercise.
Participants also wanted the community section in the main navigation. We had given it lower priority, but the feedback prompted us to move it up. My requirements work had to leave room for that change.

Requirements and revisions

Make route changes easier to handle

Before disruption

01

Preview the route

02

See sensory notes ahead

03

Know where to recover

Proposed features for a more predictable journey.

What testing changed

01

Simpler, fixed navigation

02

Immediate quieter-place rerouting

03

Community moved into main navigation

Participant feedback changed the feature hierarchy.

Summary of the concept and revisions following focus-group feedback.

04
A prototype for further testing
The project produced a tested prototype and a set of requirements grounded in expert interviews and community research:
100+
Community posts analyzed
across Reddit, YouTube, Facebook
5
Person team
I owned requirements and prioritization
2
Autism-research experts
interviewed to ground the work
The remaining question is whether the concept helps during an actual journey. I would next test route changes with autistic travelers in real transit settings, with appropriate support, to understand where the guidance helps and where it adds work.
Hiring for your product team?
Get in touch →