...

...

5 October 2021

• CAN messages: CAN Message Definitions MSXIV

23 August 2021

• Strategy will likely be using the Dash framework (Python), which is built on top of Plot.ly

  • https://dash.plotly.com/

  • https://dash.plotly.com/dash-core-components/graph

  • https://dash.plotly.com/dash-core-components

• Because we’re using the Dash framework, it has ~40 types of graphs built in already, so we don’t need to design the actual graphs

  • see all of them here: https://plotly.com/python/

    • https://plotly.com/python/line-charts/

  • they already have a bunch of nice features built in like “hover to see values” and zoom/pan

• Now the focus is: how do we arrange these graphs in an effective way?

• https://www.figma.com/file/sHEI3MdvAfuLyjyo8XZvxX/Telemetry-Dashboard?node-id=0%3A1

• Think about everything in cards

• https://docs.google.com/spreadsheets/d/1ejOK4Xj4pYAV-a-VKjRtYI9etoIzy69uUqa943JjWJg/edit?usp=sharing

• https://www.figma.com/community/plugin/731451122947612104/Charts – Figma plugin: use this for your chart placeholders when you’re mocking things up!

26 July 2021

Updates

• Wrote up user stories in User Stories

• As team, went over insights from interviews and brainstormed big-picture potential dashboard organization/features in FigJam

• Pulled out and assigned 4 of the most complex/important user stories

  • Finding/searching for data/filtering – Riishi Jeevakumar

  • Displaying values vs booleans vs enums & comparing data – Catherine Burns

  • Displaying Faults – Cheryl Li

  • Historical data – Joy He (Deactivated)

Deliverables for next week:

• Brainstorm as many concepts as you’d like

  • Recommended: diagram out the user flow. This is a sample one I did for a hackathon (a slightly shitty app for crowdsourced leftovers) https://drive.google.com/file/d/19wIMkiZAql_yDnEB4oYsX-W2dzRsfihV/view?usp=sharing – yours will likely be much simpler (only 1 flow for each concept, no subflows)

  • Sketches (can be pen and paper) or wireframes (figma) of 2-3 concepts

    • Remember storyboarding? Ideally the sketches/wireframes would be in some kind of storyboard form, and follow the user flow

    • If you’re strapped for time, a simple sketch communicating each of your concepts will do

Misc

• I forgot to mention this, but if you see any random stuff in the wild that looks aesthetic, throw it in here 🤷‍♀️ https://www.figma.com/file/7an6eJ4dgmSnQP0P3TFxds/Telemetry-Dash-Moodboard?node-id=0%3A1

• Any random stuff (like Stats Canada) that you think would be good inspo for someone else/the rest of the team, share it over Slack!

...

19 July 2021

General Updates/what we’ve been up to

• Wrapping up interviews

  • [list of people we interviewed]

  • Ryan Dancy – Firmware

  • Emma Wai – Strategy

  • Michael Shiozaki – MSXII, Strategy

  • Avery Chiu – Firmware + our main point of contact

  • Aashmika Mali - Hardware, MSXII

  • James Lin – Hardware

  • Hewitt – Firmware

  • Micah Black – Hardware; upcoming

What to do this week

• POST/SHARE ON CONFLUENCE:

  • your notes

  • link to the cardsorts that you have access to

  • https://drive.google.com/file/d/1rRaQj6PiY_Yw-c7wpVUwlNMvqkTihZBt/view?usp=sharing – Firmware

  • https://drive.google.com/file/d/17n6PGQ5VoHAkqF0M-GYx1rX_Le_Ee3dR/view?usp=sharing – Hardware

  • https://drive.google.com/file/d/1UnQTMgNIpVUl1WBEOoWPL-f1ktRXbT3g/view?usp=sharing – Firmware

  • https://drive.google.com/file/d/1WCn8ml2O2V6nKDeSbTZwVHCmwQpjqPO8/view?usp=sharing – Hardware

  • https://drive.google.com/file/d/1qyHk3GtLf3RpG1S_G2ByevmMRzbijaNY/view?usp=sharing – Hardware

  • https://drive.google.com/file/d/1Z4FXWx_JVjtZYsPyVMM8EfJHS6YDLmDF/view – Strategy

• https://www.figma.com/file/9H2vLH5BcZYCq1SUbvP9wC/Telemetry-Dash-Figjam?node-id=0%3A1

  • Fill this out with

    • important/relevant points from the notes that you’ve been assigned to look over

    • observations from the card sorts that you’ve been assigned to look over

Coming up

• Interview with Micah Black (hardware lead) at some point this week

• Next check-in we’ll discuss what we found and begin thinking about how to approach the design

  • ticket-by-ticket approach? how to divide up tickets?

  • subteam-by-subteam approach?

  • other approaches?

• Iron out timelines some more. Bug Kristen about what she expects us to have done this term.

• Start ✨ moodboarding ✨

...

5 July 2021

Interview Guides

• Went over interview guides for firmware and software and gave feedback

• Iterate on them throughout this week

• Joy He (Deactivated) will do interview with Ryan Dancy (firmware lead) this Thursday at 7:00pm

  • Cannibalize questions from other interview guides for this one

  • Rest of us will sit in, take notes, observe

• Interview scheduled for Sunday July 11 at 1pm with Emma Wai (strategy lead)

  • Riishi Jeevakumar will run this one, rest of us take notes

Interview Guides Feedback

• Don’t make assumptions about the current state/usage of the system

  • You don’t know if they’re currently using telemetry, if they’ve done stuff in the past, etc

  • Lead with an open-ended question such as “tell me about your experiences with [thing you want to ask about]” then go into the specific thing you want to investigate

  • Or you’ll get a blank look and “we don’t use this” or “what thing?”

• When trying to suss out usage patterns, lead with a “scenario-setting” question

  • “What current tasks within MidSun involve data visualization? Tell me about them?”

  • Then go into trying to suss out usage patterns, design patterns, current solutions

  • Forcing people to think of specific scenarios/examples give you richer, more accurate, less speculative answers

• Pay attention to wording: will the other person know what you’re trying to ask them about? Keep your wording specific.

• Essentially, ask open-ended (“vague”) questions to find and establish specific tasks/situations/scenarios that are relevant to what you want to know about, then you can drill down

Card Sorting

• May be done in FigJam, Joy He (Deactivated) needs to investigate + set up

• Will be done for all interviews

• Based off of technical reqs and all data points outlined here https://uwmidsun.atlassian.net/wiki/spaces/S/pages/2760245765/can+dbc+Breakdown

Technical Req’s

https://uwmidsun.atlassian.net/wiki/spaces/S/pages/2760245765/can+dbc+Breakdown

• Some stuff still needs to be clarified (tagged in red) ideally by this week

• Give it a read to give you an idea of the data we’re dealing with, but no need to spend time on it

...

30 June 2021 (not a meeting)

...

• One person acts as the “main interviewer” – they will be asking most of the questions and directing the interview

• The rest of the people listen in on the interview (cameras off) and act as notetakers

  • They are also expected to step in with any questions that they have, and help prompt the interviewer if they’re having trouble

  • It’s good practice to record interviews and go over recordings after the fact. However, it’s very time-consuming and we have multiple people able to take notes – so I don’t want to do it.

    • I will save transcripts/recordings for reference, but we don’t want to fully go over all of them

    • Take good, detailed notes during the interview

    • Don’t do schoolwork/other stuff during the interviews lmao

• It would be Very Cool if y’all were able to act as the “main interviewer” at least once

  • Really good experience and helps differentiate you as a UX applicant, since most people never get the chance to do research with actual users

  • HOWEVER, the interview guide must be well prepared/fully fleshed out (or I won’t let you do it :P)

Interview Guides

• I will screenshare one of the interview guides I created for co-op during Monday’s meeting (June 14).

...

• Notice that the sample has 5 main research questions/themes. These are your guiding questions that you are seeking to answer. They are BIG and ambiguous.

• This weekend (June 12/13), try to come up with 5 big questions EACH that you want answered

  • 5*4 = 20 questions total

  • 10 for MSXIV dash (Rishii and Joy), 10 for MSXII dash (Cheryl and Catherine)

  • As a team, we will discuss what questions we want to prioritize (ie if all of us came up with the same question, we likely want to include that question)

• Next week, flesh out the sub-questions for the big questions/themes we agree on

  • I will try to provide guidance on this if needed, or prompts to help you brainstorm

  • I will also be re-splitting up the interview guides, because I feel that we may need different ones for each subteam using telemetry – let’s discuss Monday

...

[link to resources/example]

MSXII - Cheryl Li

New/Current one - Riishi Jeevakumar

...

31 May 2021

Timeline stuff???

• When are midterms? When does the term end for everyone?

• Midterms are scattered all throughout June

• July slightly lighter

...

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

To-Dos for me Joy He (Deactivated)

...