# data[].attributes.body
It was a bit awkward to have to track students down during lunch (disorganized) and find students who speak English.

# data[].attributes.body
As soon as your problem is defined, allow time for independent and individualized brainstorming before sharing ideas to the group so that all ideas can be heard before jumping to select one.

# data[].attributes.body
Consider using same students for both interviews and user testing so they can see the shifts in design based on their feedback.

# data[].attributes.body
Connecting the topic (new city experience) to the users (students) was challenging because many students not have relevant experience; we need to select more relevant topics (maybe redesigning the school).

# data[].attributes.body
Message upfront that prototyping is to learn what works and what does not (not to create a MVP or synthesize all of the ideas) because there usually isn't enough time. This can help alleviate anxiety.

# data[].attributes.body
Ask groups to craft ~3 careful questions to ask users before testing.

# data[].attributes.body
Next time: identify users ahead of time and bring them into the classroom (similar to the user testing process).

# data[].attributes.body
Give more prep and structure for interviewers can be helpful so it is more comfortable.

# data[].attributes.body
It's important to carefully tailor questions to the users/interviewee.

# data[].attributes.body
This process is important but was a bit awkward. The two lines of communication activity didn't work to build empathy --> find a replacement activity?

# data[].attributes.body
Worksheets in CSD Unit 4 Chapter 1 work really well!

# data[].attributes.body
Use index cards to mock up apps, to better understand linking screens. Big papers with many screens are fun to work on but make linking screens more challenging later on.

# data[].attributes.body
Linking screens in CSD: Copy and paste code into shared Google Doc to make this easier. Just remixing projects doesn't work well because images don't transfer with code.

# data[].attributes.body
Be flexible with how things turn out. Different groups will have different things. If things don't work well, run with it. For example, groups that don't link screens in CSD should present screens separately and pretend they link to one another.

# data[].attributes.body
It's important to scaffold the process for market researching. Go to the app store, type in your topic, etc. Model explicitly.

# data[].attributes.body
Use a template to make assignments for team members, what they create, and when they will accomplish this.

# data[].attributes.body
Stress the idea of creating an MVP (minimally viable product) from the very beginning because they won't be able to create something very complex.

# data[].attributes.body
CSD: Students create images with other tools and import these to make MVP.

# data[].attributes.body
Students switch up group members to learn about the projects and add "hacks" (to add how functionality they would want) to a remixed project. Then, they go back to original groups.