User Experience/Stories Interviews

Owned by Stephanie Li
Last updated: Jul 29, 2023
3 min read

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

 

Yanshen Zhou

  • Look at Jira board and ask him about what types of modules does he want to see on the dashboard, and what specific pieces of data he wants to see on modules

Introduction

  • Role: Project manager, business team lead (operations manager, sponsorships, proposals, monetary, finance), overseeing electrical - hardware

    • Help at weekly leads meetings to facilitate cross-functional discussions regarding system integrations

    • Making sure hardware is on track to meeting their manufacturing goals

  • No firsthand knowledge, lots of secondhand knowledge of how the race is from past leads

    • Competition happens in the States, scrutineering process to ensure vehicle passes all safety checks

    • 1-2 day race around a racetrack, vehicle qualifies if it does a fast enough lap or enough laps

    • If qualifies → Drives the American Solar Challenge where they drive across the US on highways

    • Distance-based race

  • Actual role within the race is not finalized yet

    • Planned to be the driver of the competing car

  • Logistics-wise, listed as the team lead (designated point of contact) for the competition organizers

    • Other positions that need to be listed for contacts: Safety people, leads for each system (technical, mechanical), drivers

General

What other pages would we require?

  • Battery → State of charge

  • Telemetry → Speed, braking (regen braking), temperature of car parts (battery pack, occupancy cells)

    • How often are signals being sent?

  • Race strategy → Yanshen says it’s up to us on how to determine KPI/Performance factors

    • Aggressive vs conservative?

Route Model

  • Look into “Loops”?

    • Might be built into route model

    • Loops → Once we reach checkpoint for the day, we have the option of doing loops around to add extra distance

      • Strategy says: Loops will be integrated into route model, need to decide how to visualize it

  • Elevation gains (very important)

Weather

  • Include more “niche” weather components

    • Cloud coverage: Affects solar power

      • From testing, Yanshen said some cloud coverage can decrease solar power by 50%

      • Satellite coverage of the cloud coverage would be useful (maybe snapshots every few minutes)

        • Strategy says: Cloud coverage will be provided, will look into more about what type of data we are getting (ie. percentage of cloud coverage, etc.) so we can visualize it

Telemetry

  • More firmware project?

  • Make sure that there are more strategy/firmware meetings so that we’re all on the same page regarding data

  • Speed, temperatures (of car parts), if car parts are working properly

  • May want to reach out to Mitchell Ostler or Jarvis to discuss which members are in charge of telemetry

    • See if they want to join strategy meetings

Other

  • The race will be travelling across timezones (Kansas to Oregon) so it would be great if the dashboard could adjust for timezones and keep track of time