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 11 Next »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

  • Review progress

  • Cover Design and Product collaboration

\uD83D\uDDE3 Discussion topics

Item

Notes

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 (if possible, otherwise live implementation) → 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

✅ Action items

  • Engineering: Review Skedge repo
  • Engineering: By next meeting run the website, demonstrate any change made. Could be as simple as the color/position of something
  • Design, Product: need to sync this week, designers who are available attend the product meeting on from 12pm to 1pm and product managers who are available attend the design meeting on [TBD Monday or Tuesday]
  • Product: By add user personas document to Confluence and share with designers to get their feedback and help them create wireframes in line with product’s idea
  • Product: By need to provide designers with user flow, which will clearly mark out the two different version we need for A/B Testing
  • Design: By next meeting have the two wireframe designs based on the user flow from product
  • No labels