Versions Compared

Key

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

...

...

5 October 2021

23 August 2021

...

  • 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]

Tasks

People

Prepare interview guide for users who will be using the MSXIV telemetry dashboard that we design

Riishi Jeevakumar

Joy He (Deactivated)

Prepare interview guide for past users of the MSXII dashboard

  • Joy He (Deactivated) Get everyone Github access to the MSXII dashboard

  • [insert link to confluence page for MSXII interview guide]

Cheryl Li

Catherine Burns

MSXII - Cheryl Li

New/Current one - Riishi Jeevakumar

...

31 May 2021

Questions/Comments/Concerns!

  • Explanation of battery pack layout/architecture would really help

    • What’s a battery pack module?

    • Their pack layout is split into a master/slave box. They want a graphical representation of that

    • They also want physical layout visualization

Tasks

People

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

  • Went over Telemetry Software/Server, got preliminary list of things they want to have displayed

  • Need to come up with list of questions

  • Fleshing out definitions of technical terms/acronyms

    • create glossary/summary of what each thing means?

    • Create running list of stuff we’re still confused about and need to bug firmware about

Begin thinking about user needs

  • Why do they need x feature? What are they using it for?

  • Expanding on the table notes we have right now for each technical feature

Joy He (Deactivated)

Cheryl Li

Competitive analysis in Competitive Analysis -- Telemetry Dashboard

  • Any updates?

  • Continue working on – try to finish this week

  • Focus on other team’s telemetry dashboards if you don’t know where to start

    • How do they organize tabs? Their “overview/summary” page? “Car view”? Ways to create graphs? Ways to visualize battery pack?

  • Take screenshots of other products, and take notes on them

  • UX is all about “taking inspiration” so we’ll likely be looking up other work throughout the design process to see how people visualize x thing

Riishi Jeevakumar

Catherine Burns

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?

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

Joy He (Deactivated)

Cheryl Li

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 and manipulate 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)

...