Compile an archive of student work from and for the BFA Design and Technology (DT) department at Parsons School of Design, and set up a manageable system to maintain and grow the archive without external, tenuous intervention.
The Team + My Role
For this project, I worked with another student and a faculty member to complete the project. I took lead on creating the archive submission form and translating the gathered information into our visual, interactive archive.
Our very lovely users, and those interacting with both the archive and its submission method are BFA DT students, each of whom is required to take 1-3 spefically DT classes each semester, depending on their year. In these classes, each student will create a number of projects which they will be encouraged to submit to the archive.
BFA DT students however, after the first version of this form was sent out were hesitant to share their work, or give permissions to the school to do as they please with it. In order to convince them to add their work to our internal archive so that it can be learned from and used as reference of resource for other students that come after them, it is important to earn their trust through transparency, and to ensure that they know this is an optional thing.
The first step in this project was to circulate and compile the work from a first form given to us pre-written by the department and school.
With this initial feedback and what we saw in the first pass at organizing the results, we started with prioritizing our users and how they might respond to and use this archive. Step two involved thinking ahead to how this might be implemented, and step three was to choose the best tools for our newly specified needs.
Some of our takeaways and priorities became:
Our results were the following form, and archive. We wanted to keep the question, "What is the minimum effort we can ask for from the students that will give us the highest value for the archive?" in mind.
From the form to the archive, the content filters as follows:
While not a UX project specifically, the systems thinking happening with this project was a good way to apply elements of UX flows, user stories, and translating action into a front end that filters certain content out that is not necessary in different views, or for varying purposes.