Wiki
User Experience Engineering

2017 Jan 2-6: Augmented Reality
Page last edited by Per Bækgaard (pgba) 28/12-2017

Week 1 project

Augmented Reality systems like the Microsoft HoloLens are examples of Mixed Reality: blending the virtual and real worlds. This offers new and exiting opportunities for systems design, but also poses a whole new set of challenges when designing solid User Experiences.

The first weeks project will focus on re-enginering existing ideas and apps to work in an augmented reality setting.

Notice: This page will be updated throughout the week with additional information and material.

Learning objectives

  • Map out user needs, existing alternatives, market segments, unique value propositions and solutions provided by your augmented reality app using a lean business model canvas
  • Create user story maps for your augmented reality app in order to hierarchically model high level goals, activities and tasks as basis for scoping the prototype
  • Prioritize what slices of the user story map tasks you would translate into the wireframes and storyboard that would make up a first teration for your augmented reality app prototype
  • Define how your augmented reality app prototype will enable you to validate whether it solves a user "problem" for a specific market "segment" and to what degree that is reflected in your MVP minimum viable product "solution" 

Monday January 2nd

8:00: Short introduction and lecture followed by group work on the assignment : 1) Re-engineer an existing idea or app (your own choice which) in order to understand and describe the underlying elements of the lean business model canvas (problem, costumer segment, solution and unique value proposition). 2) Incorporate elements of augmented reality into the app. 3) Describe your key idea in a one-page landing page that clearly communicates the unique value proposition.

12:00 Upload your one-page landing page as a pdf file to the campusnet assignment area. Only one-page pdf files that are named "Group_NN.pdf" are considered as handed in (where NN is your group number, i.e. "01", "23", etc).

13.00: Brief presentation of selected landing pages and feedback,  followed by continued group work finalising 1) your landing page and 2) lean business model canvas.

16.00: Upload your group work (landing page and lean business model canvas) as one PDF file containing exactly two pages: your landing page and your lean business model canvas to peergrade.io. Subsequently review the projects you have been assigned.

Monday morning slides: Intro, Landing Page, Lean Canvas and HoloLens

Tuesday January 3rd

8:00: Short feedback and lecture followed by group work on the assignment : Continue working on your idea, creating a user story map of high level goals/desired outcomes, sequential activities and priorities tasks. You may use any tool of your choice, including storiesonboard.com or realtimeboard.com.

12:00 Upload your user story map as a pdf file to the campusnet assignment area. Only one-page pdf files that are named "Group_NN.pdf" are considered as handed in (where NN is your group number, i.e. "01", "23", etc).

13.00: Brief presentation of selected user story maps and feedback,  followed by continued group work finalising your user story map while -- as time allows -- adding your storyboard with linked wireframes that reflects at least key prioritised parts of your user story map.

16.00: Upload your group work (user story map and possibly storyboard with wireframes) as one PDF file containing exactly four pages: your user story map, your (optional) storyboard of linked wireframes as well as your revised landing page and your revised lean business model canvas to peergrade.io. Subsequently review the projects you have been assigned.

Tuesday morning slides: USM and Wireframes in Storyboard

Wednesday January 4th

8:00: Short feedback and lecture followed by group work on the assignment : Continue working on your idea, creating a storyboard of wireframes, annotated with microinteractions (triggers, rules, feedback, modes/loops). 

12:00 Upload your storyboard as a pdf file to the campusnet assignment area. Only one-page pdf files that are named "Group_NN.pdf" are considered as handed in (where NN is your group number, i.e. "01", "23", etc).

13.00: Brief presentation of selected storyboards and feedback,  followed by continued group work finalising your storyboard while updating your user story map.

16.00: Upload your group work (storyboard with wireframes and updated user story map) as one PDF file containing exactly four pages:  your storyboard of linked wireframes and  your user story map, as well as your revised landing page and your revised lean business model canvas to  peergrade.io . Subsequently review the projects you have been assigned.

Wednesday morning slides: Microinteractions

Thursday January 5th

8:00: Short feedback and lecture followed by group work on the assignment : Perform at least two “prototype tests” of your design with other groups,
 using your sketched wireframes/prototypes, 
validating your design and asking open questions,
 and finally incorporate feedback to improve your design.

12:00 Upload lessons from (at least one) “prototype test”
 and a summary of what you intend to change as a pdf file to the campusnet assignment area. Only pdf files that are named "Group_NN.pdf" are considered as handed in (where NN is your group number, i.e. "01", "23", etc).

13.00: Brief discussion of lessons learned / feedback, followed by continued group work finalising your landing page, lean canvas, user story map and annotated storyboard, preparing for the friday morning presentations, plus working on your weekly project report.

16.00: Upload your group work (landing page, lean canvas, updated user story map and annotated story board) as one PDF file to  peergrade.io. Subsequently review the projects you have been assigned.

 

Thursday morning slides: Minimum Viable Product and Validation

Friday January 6th

08:00: Project presentations (3 min for each project) with online feedback. Group order decided at the start of the session. For feedback, please use this google forms. Results will be available when forms are (temporarily) saved.

11:00: Continued group work incorporating the feedback and writing of the weekly project report.

17:00: Upload of your weekly project report with appendices (landing page, lean canvas, updated user story map and annotated story board). Please use the 2-column ACM_SigConf template (part of ACM Master Article Template) 
to generate and hand in one single pdf file. The template exists in both Word and LaTex formats, but only the reulting pdf file should be uploaded. Only pdf files that are named "Group_NN.pdf" are considered as handed in (where NN is your group number, i.e. "01", "23", etc). NOTE: make sure you mark who takes responsility for each section of the report.

Video lectures/background material

Lean methods related to UX design prototyping, business modeling and user story mapping:

UX design prototyping

Lean business model canvas

User story mapping

UX design for qualitative and quantitive prototyping

UX design microinteractions: triggers, rules & feedback

UX design microinteractions: loops & modes

UX design turning shapes into gestalts

UX design translating gestalts into design patterns

Microinteractions Keynote

Literature

Microsoft: HoloLens website with Introduction Videos

Jon Kolko:  "Design thinking comes of age" (Harvard Business Review, 2015)

Ash Maura:  "Running Lean", Chapter 1  Meta-principles (free sample)

Jeff Patton:   "User Story Mapping", Chapter 1   The big picture" (free sample)

Laura Klein: "UX for lean startups"  Chapter 1    Early validation (free sample)

Dan Saffer: "Microinteractions" Chapter 1   "Designing microinteractions"    (free sample)

Inspiration

Image search for "hololens field of view" to see what is visible with the HoloLens. This can help you create a realistic storyboard.

Report template

For those who had hard time finding the right template, it was uploaded in the file sharing. Or you can download the template by googling 'ACM template word' - the first result  ('proceedings template - WORD - ACM').

Support: +45 45 25 74 43