ALAMO CONSERVATION WESBITE

Currently all information about the Alamo in regards to conservation is recorded in field notes or various online documents. None of the information can be found in a single place. The Alamo Conservation team asked for a group of students to help create a website that would allow researchers to input their information about the Alamo in a single place and that would help create visibility to the public about the changing state of the Alamo. As a team our goal was to create a friendly website for data conservation and allow researchers and the general public to see how the Alamo is changing. 

Project Duration: 3 Months
Project For: Alamo Conversation Team
Project Type: Website Design
My Role: UX Researcher & Designer
Platform: Desktop
Tools: Sketch & Invision
Project Overview
Process
Requirements
Research
Sketches
Prototyping
  • Create a log-in for researchers

  • Allow researchers to input their necessary data

  • Help non-researchers explore the Alamo walls

  • Present the information in easily digestible manner. 

As with any new project, my first step is to do my best to understand or discover the problem at hand. In order to better grasp the issue of accessibility I read articles online of blind individuals who have struggled with ride sharing, I talked with students at the School for the Blind in Austin, and became better acquainted with the rules and regulations surrounding individuals with disabilities. Additionally I researched how other ride sharing companies are dealing with this issue. The main findings of this research - the unpreparedness of drivers for their passengers and the unfriendliness of the existing interface for the blind - helped me hone in on which part of the problem I wanted to tackle in our two week sprint. 

Any project that I start begins with sketches, quick user testing sessions and many iterations.

In just under a week, I realized a first iteration of the sketches above. My goals were to:

 

  • Portray a new workflow, one without a map, for those who are visually impaired

  • Offer drivers a way to indicate their ability and willingness to drive accessibility passengers

  • Offer passengers a way to indicate their disabilities upon creation of account

  • Create an unspoken dialogue between driver and passenger

  • Begin the exploration of expanding Fare beyond passenger ride-sharing

Outcomes

In culmination of this project, I presented this redesign to the Fare team. The following is feedback received from the team:

Juliette 10/10

  1.  Was the first to use the Digits sign up process, easy and simple.  Well done.

  2. Permanent Wheelchair, great idea – she seemed to do some good research on her ideas and how to implement them correctly.

  3. List/Map View – really smart way of making Blind Passengers able to use the app.

  4. Driver Walkthrough for ADA was great.  Again, seemed to of all cases and how to make them easier.

  5. Think about how to reduce amount of text on screen for text-to-speech.

Lessons Learned

There's always something to learn!

  1. It is difficult to understand requirements without users to talk to and requires extra diligence and research.

  2. Dates are hard! Designing effective date pickers and selecting the proper language to ensure clarity requires time and thought.

  3. Iteration is key and working closely with the developers on a project create for greater collaboration and a better product.