Originally Posted by riley.jean23
I was just wondering how teams documented their work, if they need better solutions, if they do at all, if they need improvements, etc.
One thing I've found absolutely essential is documenting the "Why" of every build season decision you make. Sometimes, later in the season, somebody goes to change something on the robot and nobody can remember why the robot is the way it is, so you change it, only to have it bite you in the back at the worst time.
5254 uses Google Drive to store our documentation, largely with Google Docs and Sheets. These include screenshots of CAD sketches and models and updates whenever possible, as well as links to GrabCAD models, drawings and Bills of Materials.
20 has an internal "build blog" where we keep members, mentors, and alumni up to date on what is happening during build season. People go around taking pictures of prototypes and talking to team leads at the end of every meeting.