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 at any time, please know that this page is 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. You should include all the information below in some order and format that makes sense for you:
Approach? Lean UX, including a very brief explanation of what Lean UX is (not more than a sentence or so).
Duration? How long did you work on this project?
Links? Include links to all important files and/or other relevant information.
Recap of project? Include a bullet pointed discussion of goals for the project, challenges tackled during this project, results (i.e., what happened?) and/or lessons learned.
Role? What was your specific role?
Team size? How many people were on your team?
Tools? What tools did you use to complete this project?
What? What is your app idea? Explain it in brief. Introduce your idea in a pithy, engaging way.
In this section, you will lay out what the reader will experience on this page in more detail.
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.
The conclusion can be formatted many different ways. In short, it needs to summarize the page. It also include lessons your learned from the process. What challenges did you faced? What would you have done differently if given another chance or more time? Employers understand that not everything works out perfectly all the time; how you deal with adversity and how you can reflect on past projects shows your ability to grow.