Friday, February 9, 2018

9A - Testing the Hypothesis, Part 2

In this entry, I will continue assessing the issues with the RTS bus app and my hypothesis.
The people I will interview are students who use the RTS app, but who have not experienced the problems that I have.

Summary of interviews:

E: Interviewee E said that he uses the bus frequently, to get to work. He is right in the middle of a route and lives/works on campus, so he usually has wifi. He doesn't experience any problems with the app because he isn't near the ends of any routes (where drives take breaks), and he doesn't experience issues with loading the app since he always has wifi when he uses the app. For him, the app is able to accurately predict when the bus will come.
B: Interviewee B said that she experiences no issues with the RTS app, but misses the bus sometimes anyway because she just doesn't leave her house early enough, then has to call an uber. She lives off campus, has an unlimited data plan, and doesn't live near the ends of any routes.
A: Interviewee A said that he hardly uses the buses, but when he does it's during high-traffic times. His problem is not with the RTS app itself, but with buses getting too full to accept more passengers at the Reitz and then having to wait for the next bus. However, he has never had issues with the app because when he is at the Reitz he has UF wifi, and he lives on campus so he bikes or walks more often than takes the bus.
N: Interviewee N said that she only really takes the bus at night when she doesn't want to walk in the dark, so she doesn't use the RTS bus app very often. When she has used it in the past, it has worked. She does not have unlimited data, but said she hardly uses data anyway and doesn't use her phone much outside of texting. She lives off campus.
M: Interviewee M said that he uses the RTS bus app almost every day (mostly on weekdays), but he always gets on the bus at high traffic times so he hardly ever even has to check the RTS bus app because his bus comes so frequently.

WHO: People who fall outside the boundary of the problem I'm addressing (but who are very similar to my audience) are people who use the RTS bus system but who have consistent access to high-speed LTE or wifi, who only take the bus during high traffic times when there are more buses and stop more frequently, and who live closer to the middle of the routes than the ends (closer to campus). The person can be inside my boundary if one or more of those three factors is not true.

WHAT: The need is for the app to account for bus drivers' breaks and become more reliable in tracking the buses. The need is not as prevalent during high traffic times when buses come more frequently and towards the middle of routes where drivers don't take breaks.

WHY: The need exists when the tracking on the app is sporadic and inaccurate, and when the ETA of the bus at a bus stop doesn't account for the time that the bus is off on break at the end of a route. An alternate explanation is that someone's LTE or wifi connection is weak or nonexistent at the bus stop.


1 comment:

  1. Hi Kyleigh,

    You did a very good job at identifying RTS users who don't have the need for your product. You've narrowed down the problem and figured out who will primarily be using the product. Even though not every RTS user will have timing problems, I think that there are people who could use a better tracking system. Accounting for breaks, traffic, and departing times could help more people catch the bus on time.

    ReplyDelete