Scenario:
Michael McIntyre, Housing Manager of McCormick Hall, walks into his office on a Monday morning. He logs onto his computer and navigates to our web application, `appname`, where he views the current repair jobs, along with the new repair jobs which have come in and are already heuristically prioritized. However, Michael decides to move the broken printer repair job to the top of the list because it’s finals week and because many students will be wanting to print out practice exams. He then assigns the new repair jobs to the dorm mechanic, Jenks.
Jenks walks into his office and checks the list of jobs assigned to him. He notes down the jobs he’s been assigned to do as well as their priorities. He begins working on the different jobs and writes down parts that he might need to order. In particular, he needs new fluorescent light bulbs to replace the lighting in the McCormick Date Room. At lunchtime, he logs back into `appname`, closes the tasks he’s completed, and notes that he needs new fluorescent light bulbs.
Michael returns from his lunch break and logs on to `appname` to check up on his active repair jobs. He sees that he’s received a notification from Jenks informing him that Jenks needs fluorescent light bulbs for him to replace the lighting in the McCormick Date Room. Michael uses `appname`’s address book feature to find Home Depot’s phone number and then place a bulk order for replacement light bulbs. He then updates the light bulb task on `appname` to indicate he’s placed an order for the needed light bulbs and that the task should be ready to proceed tomorrow morning. While he’s on `appname`, Michael also goes ahead and processes the new repair jobs that have come in since the morning.
Storyboards:
Storyboard #1 (Gmail-esque):
TEXT
Storyboard #2 (Drag and Drop):
Sketch |
Design Description |
|---|---|
|
|
|
|
|
|
Storyboard #3 (Illiterate/Graphically intensive):
Text
Additional Design (Mobile version):
Text
Individual Designs:
1. Michelle's Designs
Sketch |
Design Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
Jeffrey
Sketch |
Design Description |
|---|---|
|
This is the first mobile design. The focus is to present the user with the information they need and allow them to easily take action. |
|
This was the second mobile design which focuses on efficiency. Items can be marked and then action can be taken (shown: `mark complete`, but other actions may be available. |
|
This design was focusing on showing the user everything they might need. This is done in a table format. The table headers may be used to filter by priority/assignee/etc. Moreover, filters are available to the user on the site and action items on top. |
|
This was a run at showing jobs in a nicer maner. Jobs can be filtered then selected, information about the job is shown on the right. This allows the user to quickly drill into a specific problem they're having and filter out any noise. The view of the task could include things such as a notes/comment section, activity, etc. |
|
This design is similar to the above design except that it takes on priority sections in the middle panel. The view also has more focus on "activity" and notes/comments than the previous. The focus here was layout over specific details. There may be more actions or details noted on a specific task, but those might have been omitted here. |
|
This was a unique design that listed all the tasks. The tasks may have some indication of priority when they come in, or may be dragged/dropped into place. When the manager wants to assign a job to a worker, he may drag/drop it into place. The focus here is to allow the manager to do what he needs to do and be done with it. He can view incoming/existing jobs and then view the jobs per worker as well. |
|
This was an alternate for a closeup of an individual task. Again, the focus is on another design layout opposed to complete functionality. There may be more to this design such as `location`, `description`, `time`, etc. |
