tdm-calculator
tdm-calculator copied to clipboard
Create Detailed/In-depth video for users
Dependency
- [ ] When the application is ready for people to start using it (has a solution for what happens on the last page/submission, etc. which is going to a form. See all issues using label: p-feature - Submit Snapshot)
- [ ] My projects updates are all in prod
- [x] #875
- [x] ~#874~ David said that they anticipate significant changes to the strategies based on the feedback they are getting. So we will hold off on this video until we get the changes.
Overview
We need to add a detailed/in-depth video that helps the user understand how to navigate the web pages and also how to access tooltips.
Action Items
- [ ] Define ideal length of video
- [ ] Define what features and functions of the app will be covered in the video
- [ ] see the comment below for some notes about what people were confused about early in testing https://github.com/hackforla/tdm-calculator/issues/866#issuecomment-1304592072
- [ ] Define where the tags will go (so that the video can play on specific pages the user is on by the time stamp).
- [ ] LADOT to review script
- [ ] Make an in-depth/detailed video
- [ ] Add tags to the video
- [ ] review with stakeholder
David said that they anticipate significant changes to the strategies based on the feedback they are getting. So we will hold off on this video until we get the changes.
Emily and Alexander are we ready to make this or should we hold off until approval from Planning Commission
Emily says 'Keep on hold till after the subsequent User testing and after the City-Attorney has spent some time with the ordinance, which might be at the end of the year'
At one point we thought the video would address these issues. We hope that we have addressed these issue in the app itself. But its a good list to reference when making a script for the video.
Notes
The video should be able to address the below issues from the usability testing https://docs.google.com/spreadsheets/d/1SEd8uPOwOmEMdsDR_pylZ2tiByopzPrmlqB5Y4Ka4xc/edit?usp=sharing
- [ ] Bonus package information is confusing, not sure what it applies to and how it fits into the flow of everything.
- [x] Users were unsure of what to do at this step as it is informative rather actionable.
- [ ] People do not know there is a tool tip for every single row on this page. They are missing the disclaimer at the very top of the page.
- [x] Bonus package information is lost and hard to find
- [x] People are not quite sure what the point of this page is. Not sure that one can use this page to see the different options they may take to meet the TDM requirements.
- [x] General confusion on what information is actually required (e.g., how much detail is needed for project description).
- [x] Users are confused about what to do with the information presented on this page.
- [x] User is unsure where these numbers came from, especially the Target Points.
- [x] Tooltip information is lengthy and confusing
- [x] Users unclear what to do if they did not succeed, as this is not displayed
Here are some thoughts I have on length, content, and placement.
Length: -This video should not be very long if its purpose is to explain tooltip visibility and function
- Few seconds max since there are 2 types of tooltips (hover over, and clickable)
Content: -Check common areas of difficulty in tooltip visibility -Research study where we ask one group to go thru the site and another to go thru site with the video
Location: -A/B test design preferences in which we show users images of the site with varying placements of the video.
Clarifying question: are we aiming to 1) have a whole run down video that walk through a test case project and tour the site, or 2) short videos that focus on particular pain points - a video version of FAQ page (I think that the FAQ page covered everything that i can think of at the moment)?
@Jane4925 @pmeda12 The intent of the video is to have a complete run through of the site features using a test case to tour the site.
@pmeda12 will start making a rough draft for outline
-Checklist -Explanation of visual design --When hovering over clickable item, it changes visually from x to y -How to use the following functions: --Reset page / reset project --Top menu bar --Save project -Pain points to clarify --Purpose of bonus package --How strategy selection factors into sidebar
https://docs.google.com/document/d/1fu1RidWoyNoHK_2HR4dapVPAEQvKB_fB0BiGTvz_Lks/edit
@Biuwa https://docs.google.com/document/d/1fu1RidWoyNoHK_2HR4dapVPAEQvKB_fB0BiGTvz_Lks/edit
Here is the link to the checklist with some updates.
Moving up to Priority: Should Have because of the problem with users not seeing tooltips even though we have tried
- bolding on hover
- changing color on hover
- adding a box on page 1 that explains how to get more information
Per notes from [04/05/2023 team meeting] (https://github.com/hackforla/tdm-calculator/issues/1311#issuecomment-1498346806), here are some current thoughts and questions:
- "Where would this video be viewable?": thinking that Youtube is a suitable media if LADOT has an official channel and agrees to create a designated playlist. We can also link the tutorial videos on the TDM Calculator site under the FAQ page or inside specific tooltip or page.
- "break it down, so it's easy to implement": can we be a bit more specific on how to further break it down?
If we still want to do a complete run-down tutorial video using test cases, then Youtube might be the most suitable media. We can set up the "chapter" inside the complete video, or have a playlist including shorter videos breaking down very page.
If we want to do short video clips, we can still post on the Youtube and link/embed those videos on the FAQ page along side the specific question, or inside tooltips, or somewhere on each page within TDM Calculator site. If we don't want to post the short video clips on Youtube, I don't know how feasible it is to embed them on the website... probably a question for Dev team.
A question though, when do we expect making videos need to get started?
This issue is in ice box until we finish implementing solutions for the tooltips