At the beginning of my journey, I had very little experience when it came to conducting my own primary research. When going over my notes as I interviewed my classmate, I realized that problems run much deeper than the surface-level assumptions we initially think of. From then on, I learned that issues rarely have simple, surface-level causes and often stem from more complex, underlying factors. This experience taught me the importance of asking more thoughtful questions and not settling for the most obvious explanations, as well as conducting my own primary research. It also made me more aware of my own biases and the need to approach research with an open and curious mindset. As I continued conducting my own primary research, I became more confident in analyzing responses critically and identifying patterns that may not be immediately apparent.
Moving onto the second activity, I learned about the differences between primary and secondary research and the importance of each of them. Before knowing about the two types of research, I misjudged the importance of gathering real-life, personal research via interviews, surveys, or simply talking to anyone who could have valuable insights on the topic at hand. Through this experience, I came to understand that primary research offers firsthand, specific, and potentially more nuanced information that secondary sources may overlook. It provides direct perspectives and real-world experiences that can challenge or expand upon existing data. I also gained a greater appreciation for secondary research, as it allows for a broader context by building on existing knowledge and identifying trends or gaps. Learning to combine both types of research effectively strengthened my research skills, making my analyses more comprehensive, well-rounded, and credible.
The third activity, which I completed in a group setting, was the first time I had to collaborate with others during my research journey. I found this to be a challenge, mainly because it was difficult for me to share my own ideas while others were voicing theirs. However, the experience taught me the value of active listening and the importance of building on others' ideas rather than competing with them. It also helped me become more comfortable with sharing imperfect or unrefined thoughts. I realized that even ideas that initially seem absurd can spark creative discussions and potentially evolve into something innovative. Also, working in a group had the benefits of multiple perspectives, as each person brought their own unique insights and experiences, which strengthened the overall quality of our work. This activity ultimately helped me become more open-minded and collaborative in my approach to problem-solving.
The fourth activity, which felt like the opposite of what I was doing in the previous activity, required my group to narrow down our previously generated ideas. We did this by grouping similar ideas together, which helped me realize that even ideas that seem bad at first can often be rethought and transformed into something valuable. This was an important takeaway, as it taught me that no idea should be dismissed too quickly, as it may hold potential with a little tweaking or a change in perspective. Much like the prior activity, the group setting posed a similar challenge, with our focus often shifting away from the initial How Might We statement we had chosen. It was difficult to stay on track because we kept picking ideas that sounded good overall, rather than ideas that aligned specifically with the problem at hand. This experience made me realize the importance of staying focused on the core problem during brainstorming or ideation.
The fifth and final activity, in which we created a rapid prototype, felt like the final step in what a realistic creative problem-solving methodology would look like, before moving on to creating the actual product. Using just a short pitch to come up with an idea was a great exercise, as it pushed me and my group to think outside the box and revisit our divergent and convergent thinking methods to develop something that truly addressed the problem at hand. Although it was just a small, rapid prototype, it provided a strong sense of what a real-world scenario might entail, where time and access to resources are often constrained, but the ability to make prototypes and test them quickly is essential for success. This activity reinforced the importance of being agile in the creative process and taught me that even rough, early prototypes can serve as valuable learning tools, guiding further development and refinement.