Review progress

• Product

  • Need to sync with design team

  • Discussed design for search bar

  • Possibly do A/B testing in November

  • Additional specs completed

    • Search bar feature spec

  • Collected info for user personas

• Design

  • Had sync meeting

  • Skedge - dark mode design

  • Consolidating wireframes

• Engineering

  • Continuing to review PR’s

  • Continuing to familiarize with the tech stack

Design and Product collaborative efforts

• Design

  • Need to sync!

  • Wireframes

    • Sally Qalawi (Unlicensed) 's work on new wireframes

      • Sorting professors - highest rating first?

      • Graphs can expand to be larger

      • Could have a page control on the graph to switch to reviews/evals

      • What if student selects only a professor name

        • Would show the left-aligned professor card

        • Every class is listed out on the main content of the page

      • For a large number of courses, the design supports infinite scrolling

      • professor card is sticky but scrollable

      • Can click on professor card to go to profile page

        • Could have link to the official UTD profile for the professor

    • Need to get a new doc with user flow and new features from Product

  • Information architecture

  • Analytics

    • Product needs to make a list of everything that should be tracked

    • Required for MVP?

    • Want the live website to track some metrics

    • Can track complete journey that the user took

    • Will be a trial to gather this data and work on it

  • Advertising Skedge within Trends (and vice-versa)

    • We should do skedge-> trends, but not the other way around

    • Trends should be a more detailed version of Skedge

  • A/B Testing

    • On homepage design

    • Would like to target new design launched in Spring

    • Want to get this info (for things like search bar) in next registration period

    • Need designs → Figma interactive prototype → A/B Testing

    • Designers need to be designing two designs, engineering needs to implement both, then we do testing

  • User personas

    • Product has their idea of user personas, but need to understand Designers' ideas of user personas

    • Don’t need a bunch personas for each feature, they represent a person and their goals and wants, and inform all features