Design requirements detail what our users need to accomplish their goals. By closely looking at our personas and our user journey map for touchpoints that custodians encounter on an average day, our group came up with a list of ten requirements that our design must meet.

Five of our design requirements were broken down according to action, object, and context, while the other five were broken down according to data, functional, and contextual. The action, object, and context breakdown referred to the physical functionality of the design, whereas the data, functional, and contextual breakdown referred to the information our design dealt with. By breaking down our design requirements in these ways, our group was able to form a clear idea of what our design needed to encompass.

​

Once we had our first draft of the design requirements, our group moved forward with our project. It was not until completing our storyboards that we realized some of our design requirements were not appropriate for our design vision. We found that many of the requirements we came up with moved into a gray area of replacing the custodians instead of supporting them. Because that was not our original goal, we went back to change our design requirements to better reflect the idea of supporting the custodians instead of replacing them. Here is a list of a few of the key design requirements we made:

​

• Assist custodians in taking out trash

• Assist custodians in vacuuming the floor

• Assist custodians in viewing their tasks

Design Requirements