Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Misrepresentation of the cost of Transit Passes #1135

Closed
2 tasks
Biuwa opened this issue May 2, 2022 · 2 comments
Closed
2 tasks

Misrepresentation of the cost of Transit Passes #1135

Biuwa opened this issue May 2, 2022 · 2 comments
Labels
level: missing p-feature: strategy costs We don't have plans to implement this, but users wanted to know what the average costs are priority: missing role: missing User Test #2

Comments

@Biuwa
Copy link
Member

Biuwa commented May 2, 2022

Overview

Users are worried broad ranges of percentages misrepresent the cost of Transit Passes

Action Items

  • Reduce the range sizes and increase the number of range selections to fairly adjust earned points. These ranges must align with Metro's guidelines. Waiting on stakeholder
  • Add a tooltip that explains how each gradiation was selected.

Resources/Instructions

5/3/2022 Slide deck, slide no.5:
https://docs.google.com/presentation/d/1L-jjtspbw7Re_rNgncN0QRciu7iyxFicbGCSoMLzNbk/edit#slide=id.g126b7371ae7_1_8

slide 5 ss

Zoom Recording Timestamp:

00:00:10 - 00:02:15
https://drive.google.com/file/d/1eTkhtTLAsi5fJPOqUSCOB0k78pg-06oq/view

@ExperimentsInHonesty
Copy link
Member

Summary of meeting with stakeholder (when original recording was made) was that they would pass on the concern from users and that this could change in the future, but they had no guidance to change it now.

A later meeting (before city council meetings) and they said it had not changed and was not going to currently.

@Biuwa
Copy link
Member Author

Biuwa commented Nov 16, 2022

The tooltip will not be updated by LADOT or LACP at this time. If it comes up in future testing, we can revisit it.
Add a note to our testing, directing the user to discuss the issue directly with LADOT.

@Jane4925 In future user testing, please keep an eye out for this issue. If anyone is willing to discuss it further, HFLA will schedule a meeting with LADOT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level: missing p-feature: strategy costs We don't have plans to implement this, but users wanted to know what the average costs are priority: missing role: missing User Test #2
Projects
Archived in project
Development

No branches or pull requests

4 participants