Brainstorming

Now that you've interviewed your co-designer and gathered some user needs, it's time to figure out what you're going to do about them - which one(s) will you tackle, and how will you try to meet those needs?

Brainstorming is a process by which people work together to come up with ways to approach a problem. The goal of brainstorming is not to arrive at a final answer, but to generate as many possibilities as you can. It is perfectly okay at this stage if some of your ideas are wild, and a little (or very) unrealistic. Brainstorming can sometimes just be unstructured discussion in your group, but there are many different ways to do it in a structured format as well. 

A couple rules about brainstorming:

• You can choose a method below, or find your own method, but we ask that you try at least one structured brainstorming approach. If you do find your own method, we will ask you to describe it.

• If they are available and interested, consider including your co-designer and parents/caretakers/etc in your brainstorming.

• Assign a facilitator, a person in your group who is responsible for moving the discussion along, and making sure everyone's voices are heard.

• Assign a scribe, a person in your group who is responsible for writing down the group's ideas.

• No bad ideas (yet). We'll discuss project scoping next, when you may consider what ideas are more or less realistic for your team, but for now, there are no bad ideas - please refrain from criticizing or dwelling on the limitations of any particular idea.

------

Warning: It is sometimes tempting to skip this step and just run with a single idea. There have even been teams in the Challenge that have come up with a specific idea for a product before finding a co-designer for it. Please do not do this. Following the brainstorming step of the product design cycle can help you come up with more and better combinations of ideas, get you unstuck faster, and help meet your co-designer's needs better.

------

Brainstorming Method: The Five Whys

This method tries to get at the root causes of a problem, and is great for "out of the box" thinking, particularly when you don't have an existing solution. Take one of your user needs, and ask "why" that need is present. Take the answer to that question, and ask "why" again. Continue doing this five times, or until you cannot answer the "why" anymore. If there are multiple reasons that come up at some point, you can "branch" your "why" questions to come up with multiple causes.

Brainstorming Method: SCAMPER

The SCAMPER approach is a brainstorming method used when you have a process or product that you want to improve (less so when you're starting completely from scratch). SCAMPER is an acronym that walks you through seven different ways of thinking about the process or product. You'll find that some of these lenses overlap - that is okay!

• Substitute - Is there a component that you can substitute? When thinking about "components," you might consider physical parts, but also things like procedures, people, locations, or other elements of the thing you are considering.

• Combine - Are there components that you can combine together?

• Adapt - What existing solutions can you adapt? This is often a particularly useful lens to view assistive technology, as relatively small modifications of existing products or processes can sometimes have big impacts. Don't be afraid to adapt an existing solution. You do not lose (metaphorical) points for not building a solution from scratch. You do lose (metaphorical) points for building something from scratch unnecessarily.

• Magnify/Minify - Are there components that you might emphasize or de-emphasize? Make bigger or smaller? Make faster or slower? Process to streamline or add friction to?

• Put to another use - Is there something else that your process or product might be used for? (In our context, this lens is typically less directed at the product or process that is driving a user need, and more at other processes that may be adjacent.)

• Eliminate - Are there components that you can eliminate? This lens applies to both an existing product/process that your co-designer has, and also to any idea that you develop later. Are there things that you can remove without affecting functionality (but may save time, money, or complexity)?

• Rearrange - Can you change the way something is laid out - either spatially or temporally?

Since SCAMPER works on an existing product or process, it can be useful to apply it a few times, at various stages of your product design process. In fact, one way to use SCAMPER is to apply it after each design review or product iteration.

Brainstorming Method: Add Constraints

This approach is useful when you have one or more ideas/directions that you're considering. Take one of the things that your product idea depends on, and pretend that you can't use it anymore. How does that affect your solution?

For example, if you were considering a Arduino-based internet-connected camera approach, what happens if you take away web access? Or electricity? Or light (for the camera)? If you were considering 3D printing an enclosure, what happens if you took away the ability to 3D print?

Write down what your alternatives would be - sometimes they can be relatively straightforward component substitutions (e.g. "instead of 3D printing, we will make an enclosure out of wood"), but other times, they can force you to think of entirely different solutions (e.g. "instead of a reminder system based on web services, we will implement it using colored index cards"). Remember, the key is to think about how you might solve the same problem(s) that your original idea was trying to tackle, under new constraints.

Modification: Individual Brainstorming

Group brainstorming is great, but it can also be helpful for team members to work through ideas on their own before coming back together. This modification to any brainstorming method is particularly helpful to make sure that people who may not speak up as much in a group setting to get some ideas down. You can combine this with any of the methods above, or unstructured brainstorming, but decide roughly on some minimum measure of "quantity of ideas" for each person to come up with, as a guideline before coming back together. You can also do this as an "assignment" to your team between meetings.

Assignment: Evidence of Brainstorming

Each team should submit a document with the following information:

• Who contributed to brainstorming?

• What user need(s) was/were under consideration?

• What brainstorming method(s) did you use?

• What ideas did you have?

The "document" doesn't have to be purely text - it can be text, images, photos of whiteboards, Jamboards, drawings, pictures of your teammates making gestures and shapes with their hands, whatever helps you capture your ideas. The last bullet also does not need to be terribly organized, though it may help you to organize your ideas at some point towards the end of your brainstorming.

It may be appropriate to do this for more than one user need.

Remember, the more ideas you have at this point, the better.

This assignment should be submitted to LINK TBD FOR 2024-2025 SEASON.