1 of 16

Vehicle Feedback Summary

Feedback Collected: February 14, 2024

2 of 16

Q1: Overall Experience

  • Average score: 4.36

3 of 16

Q2-3: Meeting Structure

  • General idea seems good
  • Execution is lacking - say good execution
  • Common Feedback:
    • Slides are too long
    • More delegation and independence

4 of 16

Q4-5: Enjoyment and Management Ratings

  • Least Enjoyed: Document Writing
  • Most Enjoyed: Rocket Building
  • Worst Managed: PDR Presentation
  • Best Managed: CDR and Full-Scale

5 of 16

Q8: Working On Your Own

  • 60% Yes, Everyone else some form of “yes, but”
  • Impression: Lack of trust of certain team members and topics

6 of 16

Q9: Subteam on Track

  • Most agree that the subteam has been on track so far, however…
    • 1 observation that I get off track a lot
    • Several observations that we push to the last minute on most things

7 of 16

Q10: Effective Mentor

  • Nobody hates me, but people want to see more trust in them from me

8 of 16

Additional Remarks

  • The management is a significant step up from high school teams
  • More Chava’s apparently

9 of 16

Common Themes in Feedback

  • Lack of trust: This was mentioned several times. Near-constant hovering, not letting a task progress until checked, and similar activity plays into this.
  • Planning or lack thereof: It is pretty much a direct relationship between how enjoyable and well-managed something is perceived to be and how much of a plan we went into it with. Despite it being the least enjoyable, the CDR has the highest ratio of best to worst managed.
  • Taking too much time: Feedback on the raw amount of time is mixed, some say meetings should be shorter and some say they should be longer. The general theme here is that I need to ramble less and redirect that time to getting important points across in a clear and concise manner.
  • Not giving good information: There are several complaints about me not communicating specific resources or techniques on how to do certain things, ranging from technical documentation to flight simulation to construction to recovery to… you get the idea.
  • ​

10 of 16

Improvement Plan: Meeting Structure

  • Slides will be updates, action items, and necessary introductions or recaps. -> Keep team up to date but don’t take more than 5-10 minutes at most

11 of 16

Improvement Plan: Assigning Tasks

  • Action Items Spreadsheet
  • Tasks will be refreshed within a week if not in progress
  • I will try to assign tasks as soon as possible
  • Plan spreadsheet for you to find your own tasks and keep track of progress

12 of 16

Improvement Plan: Team Trust

  • That system “belongs” to you
  • I am a reviewer -> Point out anything missing or sketchy, but will trust your judgement

13 of 16

Improvement Plan: Staying on Track

  • Tracking spreadsheets for all major milestones
  • Timelines developed and target one week before deadline (post-FRR implementation)
  • ​

14 of 16

Improvement Plan: Team Communications

  • Weekly email and discord ping
  • Discord pings for quick announcements (“30 minutes to meeting” etc.)
  • USLI leadership is developing proper team hub - more info soon

15 of 16

Improvement Plan: Giving Help

  • Will check in regularly to ensure a) you are doing alright and b) task is being completed
  • Will try to balance between my help and your work - the more team members the harder this inevitably becomes

16 of 16

Caveats

  • I don’t know everything, despite my reputation
  • Some information is mandatory, and will add time to meetings
  • Some things are out of my control, like the weather and NASA’s timeline