Versions Compared

Version Old Version 2 New Version 3
Changes made by

Joy He (Deactivated)

Joy He (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 a laptop

  • Our task is 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

...

To-dos for all of you (try to do by [date])

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

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

    • Paste them into . Underneath, write a short summary (half a page total, not for each) of good points for each source you find

    • If you have questions, write them down too! Others (or me) can research/look into them and write more info on the doc

  • Telemetry dashboard – 0.5 to 1 hour

  • Everything I’m making y’all do

  • Put together list of technical requirements for telemetry

    • Read Telemetry Server

    • Read Telemetry Software

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

      • Write notes/questions here [background research link]questions/comments in May 31st meeting notes so we can start with those at next week’s meeting

      • Exploratory research/UX in general is all about asking questions so we can ~understand the problem space~

      • I will be funneling questions to firmware and/or strategy (who can be hard to reach) other people as needed, so ask early!

      • I’ll try to be checking in on this doc regularly, so I’ll be able to answer questions directly

      • Make your own private notes about those two docs (optional, but recommended).

To-dos for me (try to do by [date])

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

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

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.

...