Understand how the initial phase of product design can be driven by testable hypotheses, rather than guesswork. The goal is to define the big picture for your product, starting with assumptions, then hypotheses, and finally a concept story.
NOTE: we will follow the process from LeanUX, modified to be suitable for a course project. This unit includes: 1) preliminary work done by each team member, 2) a team meeting, 3) time to polish and submit your work.
Read:
Pages 23-29 of LeanUX
Create an assumptions worksheet, as displayed on page 29 of the LeanUX textbook. Skip questions 7-11 under Business Assumptions.
Each team member should fill out an assumptions worksheet, and also a hypothesis statement (next section), ahead of time. These will be submitted.
During the team meeting, you will discuss and agree on the assumptions for your team product.
NOTE: figure 3-3 shows problem statement template for new products and services. Market research to learn about competing products is a critical (and too often overlooked!) step. Alas, due to time constraints, we need to skip this step.
Pages 30-35 of LeanUX
For simplicity, just one testable hypothesis for your product is required (but it's fine if you have more). The format of your hypothesis should be similar to figure 3-4, but instead of a business outcome, create a hypothesis related to a user problem.
Example: we believe the user goal of achieving life/work balance goal is possible if users who begin our "How to Balance It All" mini-course actually complete all segments.
During the team meeting, review the hypotheses generated by each team member and select one or more (or make up a new one) for the team.
NOTE 1: The customer lifecycle funnel (figure 3-6) is good for you to know, but not relevant for our class exercise. The distinction between output, outcome and impact is also good to consider.
NOTE 2: It seems to me that the hypothesis should be done along with the feature brainstorm. We'll discuss on piazza.
Review User's Journey chapter 3
Create a concept story for your product. Following the text, your story should have Exposition, Inciting Incident/Problem, Rising Action, Crisis, Climax/Resolution, Falling Action and End.
NOTE: creating a compelling concept story is more difficult than just brainstorming a list of features. You may want to have each team member create a draft ahead of time, or you might want to brainstorm during the team meeting then finalize the story via email (e.g., have one person create a draft, then send to other members to edit/improve).
Create ONE ZIP for the team which includes:
You will submit one zip for all team assignments. In Canvas, all team members will generally receive the same grade, unless I can detect or am informed of significant differences in participation (e.g., this assignment includes "pre-work" done by each individual).
There are no "right" answers for this assignment, so your work will be evaluated based on whether the effort appears to be sufficiently broad and your assumptions/hypothesis/concept story seem plausible.
Separate grades for individual assumptions, team assumptions, and concept story.