TA02+Formative+Research+and+Proposal

= TA02: Formative Research & Project Proposal =

** Due: **** Tuesday, March 4th (before classtime) ** = = toc =Assignment Overview=

Your assignment is to extend and refine the existing one paragraph “elevator pitch” for your project into a longer, more comprehensive 5 - 6 page project proposal based on formative user research and competitive landscape analysis. Note: images, figures, and tables are free and do not contribute to the page count. The appendix (required) and reference list (also required) do not contribute to the page count either. You will work on this assignment with your project team. =A Brief Timeline= On Thursday, February 20th, we will conduct in-class brainstorms. Specifically, we will break out into our teams and brainstorm/iterate on the original project pitches with a particular focus on //who// are the target users, //how// can interactive technology play a role in solving our proposed problem, and //what// particular aspects are you, as a team, going to solve this semester. On Tuesday, March 4th, you will submit a final draft by posting it to your team wiki. On Tuesday, March 11th, you will present your proposal to the class. The entire class session will be dedicated to your in-class presentations. =What to Do= Note: if a password is required to get to any of the source links, use CMSC434 (username) and HCI4Good! (password) > > > > >
 * 1) **Brainstorm. Ideate. Generate** as many ideas as you can about the trajectory of your project this semester. Brainstorm together. Follow Kelley's recommendations for a "perfect brainstorm" ([|source link]) as well as the strategies we discussed in class. You will submit your brainstorm notes (//e.g.,//scans/sketches of your notebook, pictures of whiteboard) with your report.
 * 1) **Perform a competitive analysis.** This is extremely important and will contribute to your brainstorming sessions. You must understand how your ideas relate to other similar technologies/applications that are out there (and believe me, they exist). Your report must include an analysis of at least six specific commercial products or academic projects along with statements about expected differentiation. Use these investigations to //fuel// your brainstorms--remix from the masters.
 * 1) **Identify your primary target user groups.** These should be justified in your report. For example, if you are making a new on-campus map application, you might identify four classes of users: (i) tech savvy students, faculty, and staff who are already familiar with the campus; (ii) one-time visitors to campus with SmartPhones; (iii) new students, faculty, staff trying to learn the campus and the buildings necessary to their education/work; (iv) people with impairments (//e.g.,// persons with low-vision or mobility impairments).
 * 1) **Narrow down on one or two classes of target users.** In this class, we don't have time to design for all primary users groups, so just focus on one or two. Your report must include //why// you made the selections that you did.
 * 1) **Select two formative user research methods** and conduct your formative research using these methods. One of these methods must interface directly with your target users (//e.g.,// either via interviews, surveys, observation, etc.). Again, as with all design decisions in this class, you must justify which methods you selected. For guidance, see the IDEO Method Cards ([|source link]), //An Ethnographic Approach to Design//by Blomberg and Burrell ([|source link]), and //Contextual Design// by Beyer and Holtzblatt ([|source link]). Record your notes, interview responses, survey results, etc. You must include these in your report (in the Appendix).
 * 1) **Analyze your collected data.** What did you learn? How might this affect your design?

=The Report=

**Section 1: Title and Abstract**
This may be an update of the “elevator pitch” based on your new brainstorming/ideation sessions and the input of all team members. However, the **abstract must be no longer than six sentences and include the following features:** Your abstract must address each of these points, regardless of whether they are currently in the elevator pitch.
 * a motivating sentence about the problem and why it’s important
 * a sentence on past solutions along with their limitations
 * a sentence on your proposed solution and how it is unique from past approaches
 * a sentence on how you plan to evaluate the effectiveness of your proposed solution
 * a sentence on who this will benefit and why.

Section 2: Introduction
The introduction should clearly articulate the problem and why it is important. It should also include specific high-level goals for the project (//i.e.,// what does a “win” look like for this project and what metrics are you going to use to know that you got there). You should be sure to describe how your proposed solution is novel or, at the very least, how it may extend existing solutions. The introduction should be two to four paragraphs. If your project has changed substantially from the original pitch because of your competitive analysis and formative user research, then one of these paragraphs should explain these changes.

Section 3: Background / Review of Past Work
This section should provide a background context on the problem (//e.g.,// its history) as well as a review of past work (//i.e.,// competitive landscape analysis). I expect at least six specific references to either related commercial products or research papers. When relevant, you should include a figure of the related application, tool, product, or webpage with a numbered figure caption below. When referring to past work it’s important to include a description of the past work, why it’s relevant and significant to the proposal at hand, and how your proposed solution is different.

When citing work, each reference is assigned a unique number and referenced like this [id]. At the end of the proposal, the last section will be a “References” list that maps the unique id to the reference. See the example in “IA02 Project Pitch”.

Note: If you are having trouble with this, post a question to Piazza or email me or Meethu. It’s absolutely essential that you understand the current solutions within your problem space so that you (1) don’t reinvent the wheel; (2) can fully differentiate your solution; (3) can extend and build upon good ideas from past work and avoid the bad ideas from past work.

Section 4: Target Users
In this section, you should describe your list of primary target users as well as your //narrowed// list of the one or two you selected for this semester's project. Your should enumerate their needs, and why your proposed solution benefits them. Most, if not all, of the project proposals should have more than one user group. Don’t believe me? Think about the IDEO shopping cart redesign. You may think that “shoppers” are the only users of the carts, but we know better. Shoppers may be the primary users—perhaps the most important users—but others include the employees who must clean and collect the carts from the parking lot, the mechanics who must fix the carts, and even the homeless who might want to use the cart for their own reasons. All of these user groups (with the exception of the last group) must be able to effectively use the cart or the cart design fails. Even further, the primary user group—shoppers—can be further categorized into subgroups: power shoppers, shoppers with children, shoppers with disabilities, shoppers in a hurry, very tall shoppers, etc.

If you decide to develop personas for the one or two selected target users, include them in your appendix. I encourage but don't require you to use the persona format to help your team focus on your target users.

Section 5: Formative User Research
In this section, you will introduce and describe your two formative user research methods. For those methods that interface directly with your target user group (whether it was via observation, interviews, surveys, or some other method), you must have the following subsections (recall that you were to select at least one method that interfaced directly with your target user group). > > >
 * **Intro to method and why you selected it.** This should be one paragraph and provides a nice overview of the method you employed and why you selected it.
 * **Participants:** This should be one or two paragraphs describing your participants (//e.g.,// their demographics) and how they were recruited. You should also justify why these participants were selected and how they relate to your project. Please include a participant table where each row is a participant and the columns describe attributes of that participant related to your project (//e.g.,// gender, age, etc.). See below for an example from Dr. Froehlich's [|dissertation] (double-click to open image directly, full-size):
 * **Procedure:** This should be one paragraph and describe how you executed the formative research (//e.g.,// where did you conduct the interview, how long did it take, what are some example questions you asked). Include any materials you prepared for the interview (//e.g//. a protocol for structured or semi-structured interviews) in your appendix.
 * **Data and Analytical Method:** This should be 1-2 paragraphs and describes the data you collected and how you analyzed this data. For example, for data collection did you record the interviews, did you take notes, etc. For the analytical method, how did you synthesize the data? Did you discuss it as a team and organize your notes into higher level themes/concepts?

If both of your formative user research methods involved users, repeat the above structure for both. If not--for example, you used Informance or Role Playing (see IDEO Method Cards, [|source link])--then your structure should be: (i) Intro; (ii) Procedure; (iii) and Data and Analytical Method. Adapt them accordingly.

Section 6: Formative User Research Results
This section should have two subsection headings: //Results from // and //Results from .// Organize your results into themes/categories. Emphasize why they are relevant to your project and discuss their significance.

Section 7: Conclusion
Conclude with one or two paragraphs on your main findings and your planned work going forward.

Section 8: References
A list of references formatted according to the ACM Style guide ([|link]), Chicago Manual of Style guide ([|link]), or the APA Style guide ([|link]). You might use [|Mendeley], [|Zotero], [|Papers], or [|EndNote] for this, or you can also keep them organized by hand. You must include at least six related work references--you are welcome to have more. You can also use references in other places in the report (//e.g.,// if you utilized a specific method, you can cite that method in the literature).

Section 9: Appendix
The appendix should include:
 * A copy of the original elevator pitch (in its unmodified form) followed by a brief paragraph describing how the proposal has evolved since its initial composition.
 * Your brainstorming notes (//e.g.,// scans of your notebook, pictures of whiteboards, pictures of zaniness).
 * Personas or scenarios is you have developed them (even partially).
 * Any materials that you used in your formative research (//e.g//., survey form, interview protocol)
 * Your raw data collected from your formative research (//e.g.,// notes, interview responses, survey results)

Additional Requirements
You must include several visual elements that **complement your submission**; again, these elements will not count towards your total page count. Images, graphs, or tables should all have captions that explain them. Please inline these visual elements into the report itself rather than placing them in the Appendix (I like seeing the figure/table close to the associated text). Remember to cite any sources used in your references. Please email me or post to Piazza if there are questions or concerns about this requirement. =Grading= You will be graded on how well you execute on each of the above seven sections. You will be additionally graded on creativity and writing quality across the entire proposal. Please follow the directions carefully. If you completely miss a section, I can't give points for it. Finally, I will be factoring in peer review to help assess the quality of the work and the output from each team member. This proposal is worth about 10% of your project grade in the class.

Specifically, Meethu and I will be using the following guidelines in evaluating your reports:
 * 05 points | Section 1: Title and Abstract
 * 05 points | Section 2: Introduction
 * 20 points | Section 3: Background / Review of Past Work
 * 15 points | Section 4: Target Users
 * 25 points | Section 5: Formative User Research
 * 20 points | Section 6: Formative User Research Results
 * 05 points | Section 7: Conclusion
 * 2.5 points | Section 8: References
 * 2.5 points | Section 9: Appendix
 * 100 points
 * 100 points

=Submission= You will not be emailing this submission. Instead, post a PDF directly on the CMSC434 class wiki. Each team must make a wiki for their project. You will use this to post deliverables the rest of the semester. Please make sure to convert your report to PDF format so that it will look the way you intended for it to when I look at it. =Common Mistakes= > > > >
 * **Including figures but without captions:** Each figure should have a caption that looks like: "Figure X: " where X is the figure number.
 * **Not referencing figures in prose:** Each figure must be referenced in your prose. If you have difficulty figuring out how to refer to the figure in your text, it's likely that the figure is tangential/irrelevant and can be removed.
 * **Enumerating related work but not differentiating:** A very common mistake--even amongst graduate students--is to simply enumerate work related to your proposal rather than explicitly describing how your proposed project is similar/different. The "Background / Review of Past Work" section should be seen as a form of //rhetoric// (of argument) articulating how your proposed solution is informed by past work but sufficiently different from it. You should never simply list a product or past piece of research without differentiating your solution.
 * **Enumerating related work but not synthesizing:** An acceptable "Background / Review of Past Work" simply lists and differentiates past work and directly links it to the proposal at hand (by drawing similarities/differences). A better approach is to offer high level synthesis and categorization of past work. Think about the higher level relationships between previous work and how they fit together. Use this to provide sub-sections in this section (//e.g.,// related to specific features, techniques, etc.).
 * **Not justifying recruitment method.** It's not enough to simply tell me how you recruited participants for your formative studies, you must also provide a rationale.