Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

31 May 2021

Questions/Comments/Concerns!

Onboarding - (24 May 2021)

Welcome to telemetry!

What is Telemetry?

  • There’s a bunch of instruments/sensors/fancy things in the car

  • They measure like 500 different things

  • Telemetry: this data is recorded and transmitted to the user (on a laptop)

  • The purpose of the telemetry dashboard is to allows us to view historical car data and create new graphs or visualizations as necessary.

  • We need to display all this data in a coherent, legible, usable way

    • [insert screenshot of a line graph with >20 lines that firmware absolutely insisted had to be displayed like that so they could compare everything]

FSGP 2019 Telemetry dashboard

Onboarding To-dos for all of you (try to do by [May 31st])

1. Book 1-1s https://calendly.com/joyhe1-1/15min?month=2021-05 – they’re optional, but also highly encouraged: they help me.

  • What do you want to gain from this experience/what are your goals learning/career-wise?

  • What past experience do you have with UX and/or front-end?

  • How many hours do you think you can do each week?

  • What do you need from me?

2. Figure out what’s going on (and do some writing…sorry)

  • Data visualization and UX best practices – 1 to 2 hours Resources/Best Practices

    • Google! Find 3 good sources/articles/guides (that other people haven’t found yet).

    • Paste them into the doc and write a short summary of good points for each source you find

    • If you have questions, write them down too! We can research/look into them and write more info on the doc – you can also write them in the May 31st meeting notes

  • Telemetry dashboard – 30 min

    • Read Telemetry Server

    • Read Telemetry Software

    • Come up with at least 1 (non-googleable) question about things you’re confused about/you or the team needs clarification on/resources you want.

      • Write questions/comments in May 31st meeting notes so we can start with those at next week’s meeting

      • I will be funneling questions to other people as needed, so ask early!

Individual Tasks (2 people on each) – how long do we need?

Tasks

People

Compile list of technical requirements in Technical Requirements -- Telemetry Dashboard

  • Start with Telemetry Server and Telemetry Software

  • What needs to be displayed on the dashboard? Not worried about the “how” yet

    • Don’t start solutioning yet!!

    • Technical requirements is more about “we must have voltage, speed, PWM”.

  • What info do you need, and from who?

    • Have a list of questions so we (you?) can starting planning exploratory interviews

    • Look into UX interview/exploratory research techniques

Competitive analysis in Competitive Analysis -- Telemetry Dashboard

  • Telemetry Server is a start

  • Telemetry dashboards for other applications (drones? robots? trucking?)

  • Non-telemetry dashboards/data visualization

    • finance/stocks? not sure what else. You look into it!

  • How do other people visualize large amounts of complex data?

  • Look into competitive analysis techniques/templates

Riishi Jeevakumar

Catherine Burns

Upcoming Tasks

People

Start looking at user needs – we know nothing about this right now

  • User needs is about why do you need voltage? what are you doing with this info? what needs to be more prominent?

  • Think about exploratory interviews

    • What kind of people do you need? – come up with proto-personas, or different roles within the team who need different things from the dashboard

    • What information do you need from each type of person?

  • Come up with more questions! Start organizing them into themes

  • We want to be able to generate jobs to be done, use cases, flows, etc

Digging deeper into pain points with existing data visualization solutions

  • Planning for interviews with people who were on MSXII (past dashboard)

    • What kind of people do you need? – come up with proto-personas, or different roles within the team who need different things from the dashboard

    • What information do you need from each type of person?

    • List of questions.

  • Think of other ways to figure out issues with past or existing data visualization/dashboards so we don’t repeat the same mistakes

    • Could get files of the MSXII dashboard, get your peers to look at it and do user testing??? idk

      • Also could do with existing products that you found earlier

To-Dos for me Joy He (Deactivated)

  • Do the To-dos for all of you

  • Bug people about getting access to the actual FSGP2019 dashboard so y’all can poke around

  • Write up summaries of data visualization best practices resources I got from co-op

If you have questions/concerns about anything, message the Telemetry Dashboard channel. Your questions will likely help the entire team. You can also DM me!

  • No labels