/
Product Division Meeting #1

Product Division Meeting #1

Owned by David Launikitis
Jan 31, 2024
3 min read

 NEBULA

PRODUCT MEETING 

08 February 2022 / 11:30 AM / BLDG ROOM#

ATTENDEES

Eric

Caleb

Harsha

AGENDA

 

NOTES

Want to be a standard process for Product team to follow for the future

  • Harsha

    • Want better understanding of Nebula Lab’s Products

  • Eric

    • Planner - degree plan tool

    • Jupiter - help students find clubs

    • Survival Guide - helpful articles for new UTD students

    • Trends - extension on UTD grades

      • Trends desktop

      • Sk.edge - chrome extension for schedule planner

    • API - provides data

  • Harsha

    • Been using UTD grades

    • Where is the data being posted? Is it live data?

  • Eric: yes; live data

    • Get grades via FOIA request 

    • Get course & professor reviews data via coursebook

    • Trends is UTD analytics platform

  • Harsha: Trends going live this semester?

  • Eric: yes; March 24th

  • Harsha: how recognizable is Nebula Labs?

    • Within ECS decently

    • Widely, not really

    • Trying to increase visibility through marketing team

  • Harsha: how are we  coming up with current products?

  • Eric: partially brainstorming but comes from experience of ourselves & peers

    • Planner: motivation was bc advising bad

    • Trends: motivations comes from professor complaints that people prioritizing classes w/ best grades

      • Doesn’t fully capture the quality of the class

    • Sk.edge: Won HackUTD; was really popular among students; brought onto Nebula

    • Jupiter: school doesn’t have an organization portal

      • Used to use Presence but contract expired

      • Now using Microsoft Sharepoint site; it’s pretty bad

    • Guide: students’ questions are repetitive

      • Want 1 central place to answer FAQ

  • Harsha: what do you want me to do?

  • Eric: left for what you think we need to succeed

    • Division heads’ job is to set standards

    • Key: give standards and direction

    • Monthly or bimonthly meetings?

  • Harsha: Are feature development finalized atm?

  • Eric: yes but we use agile to readjust engineering backlog

    • Release cycle is during class registrations

    • Feedback cycle

      • Do user testing

      • Adjust feature set

      • Rinse and repeat

    • 4 month release cycle

  • Harsha: need to create product management processes

    • Would be good to automate or make it better

    • Increase efficiency

    • Problems

      • Customer interviews

      • Do surveys

    • Personas?

      • Eric: aiming to build personas and user journeys

    • Will look through all the products

    • Come up w/ strategy for each product

    • Best to create a general product framework & let each product team operate

    • “Act as a bridge between all Product teams”

    • Eric: Goal for Head of Product to set standards

  • Harsha:

    • Want to meet w/ each product lead to figure out problems

    • Use insights to come up w/ strategies for each team

  • Eric:

    • Can reserve a room for brainstorming session

      • Need 1 week notice

  • Harsha:

    • Can look through each Product over the weekend

    • Next week can schedule a call

  • Eric: train all project leads how to use Product people on their team

  • Caleb:

    • Concerned w/ project lead’s ability to utilize product personnel 

    • Most of our product people are new

    • Might be best to train our product people

  • Harsha

    • Set up a call next week to talk to all Product people to gauge experience

    • Approach semester training product people

      • 1 week teach customer interviews then go do customer interviews

  • Eric

    • Send out when2meet to get people’s availability

  • Harsha

    • Going to learn about projects

    • Need to talk to undergrads to better understand what students want

  • Eric

    • Change stuff plz if you think it could be better 🥺

    •  

ACTION ITEMS