4-14-2023 General Meeting notes

User testing

• Very insightful

• Helpful in seeing patterns of user actions

• Observations

  • Lead people a bit more to what they should be entering

    • People enter a number and don’t have any indication that this is wrong

  • Too many tabs

  • Change colors

    • Color palette changes for professor card

  • Graphs need to be straightforward, don’t intimate the user

    • Explanations for what stuff means?

  • What really matters to them?

    • grade distribution

    • recommendation from friends

    • past syllabi

Product Survey

• 79 responses so far

• Looking for around 100

Product planning documents

• Templates added to Confluence

  • User testing

  • Feature Specification

  • Product Requirements

• Priority of features

Design plans

• Be involved in user testing, but from a design perspective

• Lots of communication between divisions at a low-fidelity level

  • designs are ensured to be feasible from engineers

  • designs are actually what users want

• Create low-fidelity prototypes to provide in product user testing

Confluence

• General structure of each division

• Now we fill it in!

Integration with Planner

• We want to stay on as few tabs as possible

• Providing data with a few jumps as possible

• We need to refine Trends as a product first before integrating with other products

Another round of User Testing

19 Apr 2023 at 11:00am at JSOM

• We want some more data

• Get 5 more people tested per group

• Aim to get a more diverse group of testers (majors, graduate)

• Analyze current test results before user testing

  • Build a few low-fidelity models to show testers