Process Page Example (Lean UX)

Assignment

The goal of this assignment is to set up a Process Page for IAD4000 (Interaction Design II). In doing so, you'll show clearly that you understood the material learned from Lean UX (3rd Edition) and explain how you applied that material to your team project.
A Process Page shows the project, all the work the team did, and a special focus on your contribution to the project. (That means each Process Page for team members should be somewhat different because each member did different things.)
The central goal of this page is to clearly explain why you made the decisions you made. Thus, detail is important.
In the process of explaining how your team's project came together, you must also explain Lean UX. What is it? What does its jargon mean? How did you apply it to your project?
Why is this important? You’re writing this for people who might have never used an approach like Lean UX. A recruiter might have little to no experience and a designer may have been trained using different methods. Don't assume that your reader has total familiarity. Finally, this page gives you a chance to show that you can fully explain an interaction design process.
The page should target at two audiences -- recruiters who may not want to read deeply (thus the inclusion of an Executive Summary) and decision makers who are more likely to read your page deeply during later stages of an interview.

Grading

You'll be graded on content and design:
Content will be graded on your ability to convince the reader of your familiarity with Lean UX as well as your ability to explain your work to someone not familiar with Lean UX. This also means that part of the grade will reflect the quality and clarity of your writing, so please proofread, revise, and edit your work.
Design will be graded on how your Process Page looks. Much in the same way that you’ll be judged by your work on the job market, you’ll also be judged by the design of your Process Pages. Use that feeling as a guide for how much care and attention you should put into the details (i.e., margins, padding, spacing, alignment, visual rhythm, information hierarchy, etc.).
You're required to have a minimum of two meaningful citations from Gothelf & Seiden's Lean UX (3rd edition). These citations should include specific page numbers and be formatted as such, e.g., (Gothelf & Seiden, 199) or (199) if the author names are mentioned in the sentence. These citations should be placed at the end of a sentence.

Executive Summary

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.

Introduction

In this section, you will lay out what the reader will experience on this page in more detail.

Name and explain your prototype.
Storytelling is impactful. Consider starting with a short story about something related to your product domain. This story also serves the purpose of explaining the reason why you wanted to build this prototype.
Introduce Lean UX. What is it? Where does it come from? What is it meant to do? Any discussion should be built around the concept of the assumption and an overview of the genesis of Lean UX (UX + Lean + Scrum). You need to define each of these terms in your own words.
Be clear that this was a class project and how Lean UX was adapted for this class. This helps set expectations for the reader.
You should consider including the names and images of people on the team, including a link to their Portfolios.)
Explain how the rest of the page is set up.

Sprint 1

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.):

You can do separate sections for Sprints 1 and 2. This would create two sections which would be longer.
Or you can break it down by Weeks: Sprints 1 & 2 -- Design Weeks 0, Weeks 1, Weeks 2. This would create 6 separate sections which would each be shorter.

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).

Design Week Zero

Explain what happened during your meetings this week, including focusing on explaining terms related to the Lean UX canvas. How did we modify Lean UX for this class?
Each of the terms related to the Lean UX canvas and what you did this week need to be explained. Why did you do them? What did they help you learn? How did they help you either formulate or test assumptions?

Sprint Week 1

Explain the concept of the 2-day Stand-up and how you utilized affinity maps. Explain how you tested assumptions and created MVPs.
There are no definitive rules in Lean UX for wireframing or how you shift from Design Week Zero toward creating your MVP. Thus, you need to explain how your team tackled this transition.
Explain, in some detail, your user research/testing sessions. What type of questions did you ask? Who did you talk to and why? What did you learn? How did this knowledge shape your assumptions? Remember, Weeks 1 and 2 are about testing your assumptions and pivoting if need be.

Sprint Week 2

Explain the concept of the Retrospective.
Explain how the things you learned in Week 1 shaped what you did in Week 2.

Sprint 2

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.

Design Week Zero

You need to explain what revalidation is, which things you revalidated, and what you learned from this process.
Because Lean UX utilizes Proto-Persona(s), you need to explain how (or if) your personas changed.

Sprint Week 1

Explain how the processes you followed this week were different from Sprint 1. Remember to focus on testing assumptions and MVPs.
Once again, explain, in some detail, your user research/testing sessions.

Sprint Week 2

Explain how the processes you followed this week were different from Sprint 1. Remember to focus on testing assumptions and MVPs.
Once again, explain, in some detail, your user research/testing sessions.
Explain your 3rd Proto-persona(s). This would be a good time for a deeper dive into the evolution of the persona(s) over the course of your sprints. How did they change? What did you learn?

Lean UX: Process Page

last update: August 2022

Assignment

Grading

Executive Summary

Introduction

Sprint 1

Design Week Zero

Sprint Week 1

Sprint Week 2

Sprint 2

Design Week Zero

Sprint Week 1

Sprint Week 2

Conclusion