Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Possible people to interview

  • Michael Hanley (from a hardware/aerobody standpoint)

  • Yanshen Zhou

  • ?

Resources:

Interview Guides

https://www.figma.com/file/TccjbqECefrFEdgQD0b4sq/Dashboard?type=design&node-id=0-1&mode=design

ChatGPT for questions

Introduction

  • Role

  • Background (familiarity) with the race, what their role is with the race

Possible questions

  • Can you describe the main tasks or goals you're trying to accomplish with our dashboard?

  • Looking at our current dashboard prototype, what are some pieces of data we can include/omit?

  • What are specific pieces of data that would be helpful while you complete your task? (ie. driving the car → what are things that would be good to know, etc.)

  • How would you describe the overall user interface and design of our dashboard?

Michael Hanley

Introduction

  • Role: Operations manager, mech project manager, aerobody manager, business lead.

  • Very familiar with how the race works → coordinating logistics (who is going, how are we getting there)

  • Going into the race in the mech team, fixing the car and reporting to organizers about any questions the team might have during the race

General

  • Car vitals page needed (telemetry), monitoring speed, power consumption, how much charge we have left

  • Race strategy page needed

Route model

  • Any type of map would be good

    • Directions need to be there

  • Upcoming landmarks sections is very good → would be a good feature to show if we’re on track

  • Summary of current position → Good, MUST BE HERE

    • Distance from checkpoints would be better

  • Looking at our current dashboard prototype, what are some pieces of data we can include/omit?

    • Upcoming landmarks can be omitted if it’s too much

  • No labels