Versions Compared

Old Version 49

changes.mady.by.user Unknown User (mwchen@mit.edu)

Saved on

compared with

New Version 50

changes.mady.by.user Unknown User (mwchen@mit.edu)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Sketch

Design Description


Design 1:
Top: The first design was a stretch to an extreme focusing on the illiterate audience. This design was eventually adopted into the third storyboard. The purpose is to eliminate most of the words on the screen. In the left panel, there is a diagram for each floor in a stacked formation that opens up in an accordion fashion. The right panel just shows the particular job with a list of the mechanics whom the house manager can select. Prioritization happens by selecting the drop down in the top left of the pane.

Bottom: After all of the tasks are prioritized, the house manager can see a list of the tasks and the corresponding mechanic for the task. The completed tasks are located at the bottom with check marks next to them.


Design 2:
Top: The second design is focused on dragging and dropping tasks. The existing queue of tasks are located on the left while the right list indicates what are the new tasks. The house manager can then drag and drop the new tasks directly into the existing task list.

Bottom: From there, the mechanic can see an tabulated list of jobs and update the status of each job.

Design 3:
Top: This design is focused on splitting up the tasks into relative prioritization rather than absolute prioritization by flagging the important tasks. The first screen simply has a list of the tasks with a few additional buttons. The House manager can then designate if the task is important, not as important or require additional info (e.g. order more parts).

Bottom: The following screen will showcase the tasks being split into the three lists (important, do later and parts to purchase) so that the mechanic can easily see the three sections and decide what to start with.

Design 4:
The premise of this design is to sketch out something for a small screen such as a mobile device. Behind this model is the thought that the mechanic might not be able to constantly check his/her phone throughout the day and this would help him/her to check the latest requests that need to be fixed. The left image shows all of the tasks that the mechanic might need to see and queue throughout the day. When the mechanic is done with a task, he/she will just need to click on the checkbox on the right. By double clicking on a particular task, there will be a separate card that gives more details and allows the users to enter in additional information that would be useful for fixing the repair.

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.

...