ADS 560 Kirkland Syllabus v2.0 20180106

ADS 560, Interaction Design, Spring 2018
Monday / Wednesday @ 6:00-9:00pm
Matt Kirkland / mattk@ku.edu / Slack @matt

Desk Reservations

In this project, we will design a tool for on-demand desk assignments at a large company. Your solution will need to accomodate desk reservations, travel, in-person searches, and other user requests. The solution will have two user levels with different functional requirements. Your design will need to complement a large existing brand.

We will follow a similar process as the Inventory project, but this time you'll know what you're doing.

Your Client

Your client is a Fortune 500 company: you'll get to pick one. Choose one that you want to design for: either because they have something interesting going on with their brand, or compelling design assets to work with, or maybe you have some personal affinity for a specific corporation, weirdo.

Here's a list of the Fortune 500 to choose from.

The Problem

Your client (Fortune 500 Company X) is moving to a new seating system: staff will not have assigned desks, but instead can reserve a desk at any location the company has. This allows more staff to telecommute and work from home, encourages collaboration and cross-pollination of ideas, and gives the staff freedom to work from different locations around the globe without needing a formal transfer. Plus it saves money on real estate.

Your task is to design a Desk Reservation system. Design a new system that allows staff to book their desk location for one or more days, let staff find each other. Who knows what else? We'll talk about the problem and propose a set of solutions.

Requirements

  • You are designing for at least 20 office locations, spread across at least 4 countries. You don't have to reference the actual locations of your client company unless you choose to.
  • Your offices have many floors!
  • Use these floor plans for reference: One, Two, Three
  • Your design should work for mobile, tablet, and mobile devices. Start thinking in systems, not instances. Remember an 'edgeless surface of unknown proportions', as ol' Frank says.
  • Your design should include access control for staff: login/ logout/ forgot password, etc
  • Your design should accomodate guests in some fashion. What happens if a vendor / client / partner / pizza dude comes to visit the office? How do they find staff if they move around all the time?

Deliverables

We'll go step-by-step through specific design deliverables that get us closer to an interactive system to solve our client's problem. We'll discuss each deliverable before we start, but this will include:

  • Problem Discovery, User Stories, Concepts
  • Loose Wireframes (Hand-drawn)
  • Loose Wireframe Prototype (Created and shared in Invision)
  • Guerilla User Testing
  • Tight Wireframes
  • Wireframe Prototype
  • Guerilla User Testing
  • Mockups (Designed in Sketch)
  • Mockup Prototype