Reverse brainstorming is a way to solve problems by thinking about what could go wrong with a certain issue, goal, or product, instead of trying to find immediate solutions. It's about figuring out how something could fail or what challenges it could face, and then coming up with ideas to stop those failures or solve those challenges. This method can be especially helpful for making existing products or systems better, and for spotting weak spots in new projects.
Reverse Brainstorming: the Key to Better Problem Solving? | Ideanote Blog
Here's how I understood the article about reverse brainstorming and how it could be a game-changer for my Apollo project:
This technique could be useful for my project when traditional methods are ineffective or when innovative and creative approaches are needed.
Before beginning this project I want to explore what could go wrong before its been created. Creating a brainstorming mindmap I went ahead and asked the question “what if my idea won’t work effectively?” Branching off this question I came up with 4 main areas of interest:
I wanted to then see how I could overcome these keypoints. By using a colour passing tool for colour this can help the accessibility of my final design. Making sure each image is HR is going to be very important in my project as i am focusing on images. Testing my prototype on normal users to see if they are able to work it is key. It needs to be easy to use for everyone therefore I can take notes if a certain user struggles. Lastly creating style tiles before going forward with the development area of my project will guarantee a theme that resinates with the Apollo project.