Telemetry Dashboard

Kristen S Joy He (Deactivated)

01 May 2021

NOT STARTED

Figma, Confluence

Background Research

Goals of this phase:

1. Have a rough idea of and document here

   • https://uwmidsun.atlassian.net/wiki/spaces/S/pages/edit-v2/2522480716?draftShareId=d7ab5cd5-3f50-431f-a348-79f0190ee4e3

     • what needs to be on the dashboard

     • issues/pain points with existing dashboards

     Send this document over to strategy so that they can validate/add to it before we jump into user interviews.

     I’m not sure how much of this we can do without user interviews, but I don’t want the interviews to just be each person dumping a list of 50 requirements/stuff they personally want on the dashboard over a video call.

2. Learn about and collect resources on data visualization best practices here

   https://uwmidsun.atlassian.net/wiki/spaces/S/pages/edit-v2/2522480716?draftShareId=d7ab5cd5-3f50-431f-a348-79f0190ee4e3

How do we achieve this?

• Review Telemetry Server findings from FSGP2019 and identify takeaways that would be suitable for MS XIV

• Create a preliminary list of requirements/things that need to be on the dashboard, again refer to Telemetry Server

  • There’s a table at the bottom (“Desktop Telemetry Client Requirements”) with a list of things they want for telemetry.

  • I’m not sure if this is up-to-date. Would be nice to ask if there’s a document that outlines the stuff they want on the dashboard more clearly, or if one could be created for us in writing.

  • “GUI” (graphical UI) means they want it displayed. We’ll need to sort through the table to figure out what they want displayed.

• Collect and review data visualization best practices

Finish research/ documentation: 2 weeks?

Wait for strategy to get back to us: ?

Exploratory interviews

• Goal of this phase: validate and expand on Background Research

  • Pain points with the FSGP 2019 telemetry dashboard

  • What else needs to be on the dashboard

  • What we don’t need on the dashboard

  • Non-issues/things we don’t need to worry about

  • Other insights into the dashboard

How do we achieve this?

• From the Background Research, try to isolate 2-4 big themes that we want to ask about.

• Create a list of questions for each theme

  • Having a few themes helps organize your inquiries instead of having 50 random questions that are all over the place

  • Ensures that you cover all the general things you wanted to cover during the interview without going off track

• Recruit around three to five FSGP 2019 attendees → create a list of people to reach out to

• Speak with them (~30 min to 1 hour interviews)

  • Record Zoom sessions, go through them after to take notes or have a dedicated third person act as notetaker

2 weeks?

Planning

• Understand pain points of users and identify goal of project

• Information Architecture mapping + grouping

Design

• Visual Design Guidelines

  • Colours

  • Typography

• Low-fi mockups

• High-fi mockups

Handoff

• Final style