Versions Compared

Version Old Version 8 New Version 9
Changes made by

Joy He (Deactivated)

Joy He (Deactivated)

Saved on

Key

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

...

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.

...

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

Former user (Deleted) Ammar Faridi (Deactivated)

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

...