Lean UX: Process Page

last update: May 2024

Included on this page are instructions for what should go into a Lean UX-based Process Page. If you have questions, please contact Prof. Lahey via Teams or email.

Goal?

Executive Summary

This section acts as a summary of your entire page. 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. (Also, consider steering away from templates with huge hero-style image sections at top because it pushes your content down too far.) You should consider all the information below in order at works for your page:

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 or tasks?

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.

Introduction

In this section, you should lay out what the reader will experience in more detail. In short, you are elaborating on the Executive Summary. Consider:

  • Name and explain your prototype.
  • Storytelling is impactful. Consider starting with a short story related to your prototype or domain. This story explains the reason why you wanted to build this prototype, i.e., the problem your prototype addresses.
  • Briefly 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, measuring, and testing.
  • Be clear that this was a class project and that Lean UX was adapted for this class. This helps set expectations for the reader.
  • Briefly explain how the rest of the page is set up, i.e. signpost.
An image of a cat walking app.

Sprint 1

Each sprint section should have a brief introduction and conclusion to help out the reader. You should explain what happened, focusing on the important parts of Lean UX like assumptions, the Lean UX canvas, and your process for creating and testing MVPs.

Design Week Zero

  • Focus on explaining the Lean UX canvas. What is it? What did using it teach your team? How did it help you either formulate or test assumptions? What were the results (i.e., the Sprint Backlog)?

Sprint Week 1

  • Explain the concept of the 2-day Stand-up, how you created MVPs, and tested assumptionsWhat did you learn?
  • There are no definitive rules in Lean UX for how you shift from Design Week Zero to creating MVPs. Explain how your team tackled this transition.
  • Explain your user research/usability sessions. What type of questions did you ask? Who and how many people 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.
An image of sticky notes.An image of wireframes.

Sprint 2

Information here is similar to Sprint 1 -- you should not feel the need to define terms you've already defined above. Sprint 2 should show growth, especially with how your assumptions changed based on evidence.

Design Week Zero

  • You need to explain what revalidation is, why you revalidate, 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 from Sprint 1.

Sprint Week 1

  • Explain the MVPs you built and how you tested them.
  • Once again, explain, in some detail, your user research/testing sessions.

Sprint Week 2

  • How did this week grow out of the results of Week 1?
  • Explain your 3rd Proto-persona(s). How did they change? What did you learn?
An image of someone workin on a design workflow.An image of someone working on a design problem.

Conclusion

The most important thing to do in the Conclusion is to recap lessons you learned from the process. (Note: How you dealt with challenges during this process should be mentioned above.) 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 rethink your MVPs based on 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.