Included on this page are instructions for what should go into a Lean UX-based Process Page. While anyone in IAD can view this page, please know that it's specifically set up for an assignment that occurs at the end of IAD4000 (Interaction Design II). If you have questions, please contact Prof. Lahey via Discord or email.
This section acts as a summary of your entire page. Or, put differently, what are the important things someone might want to know at a glance? This is an important section for job recruiters and the early stages of the interview process. Keep it short so that it exists totally (or mostly) over the scrolling break -- you'll elaborate on all this information below in other sections. (Also, steer away from templates with huge hero-style image sections at top because it pushes your content down too far.) You should include all the information below in this order-ish:
Approach. Lean UX (you'll elaborate below)
App Idea. Distill it down to a sentence.
Objectives. What did you set out to achieve?
Role. What was your specific role?
Team size. How many?
Duration. How long did you work on this project?
Tools. What tools did you use to complete this project?
Links. Include links to all important files and/or other relevant information.
In this section, you will lay out what the reader will experience in more detail. In short, you are elaborating on the Executive Summary. The goal of an introduction is to set the scene for the reader and explain to them what will happen on this page.
Please note that there are two different ways you can set up the sections that cover sprints (Either way is fine -- it depends on your template and personal preferences.):
Each sprint section, no matter how you set it up, should have a short introduction and conclusion to help out the reader. Additionally, as with all design terms, you need to explain your terms -- sprint, design week, etc. You should explain what happened each week, focusing on the important parts of Lean UX like assumptions, the Lean UX canvas, and your process for user research and prototyping (depending on what week you are discussing).
Information here is very similar to Sprint 1. You should not feel the need to define terms you've already defined above. Be mindful that Sprint 2 should show growth, especially with how your assumptions changed based on evidence.
You need to accomplish two things in the conclusion. First, you need to summarize your experience in a concise manner. Second, you need to explain discuss lessons you learned from the process. What would you have done differently if given another chance or more time? Did you have any issues during your Sprints? Did you have to change anything because of user feedback? Employers understand that not everything works out perfectly; how you deal with adversity and how you can reflect on past projects shows your ability to grow.