Tunnel visioning is one of the challenges and problems that most of us students face whenever we are solving a homework, working on a project or performing a simulation. The main issue with tunnel visioning is that we usually don’t know whether we are falling for it or not whenever we are performing a simulation. I think brainstorming scenarios, approaches and solutions in any project or simulation is the main key that helps a lot in avoiding tunnel vision. That’s why I normally start my simulation with brainstorming to consider multiple scenarios and then try to find multiple solutions and approaches for each specific scenario. Also, I tries to do multiple brainstorming with each step or progress I have in my projects and simulations in order to avoid focusing on one approach. Also, I think that working in a team to accomplish any task minimizes tunnel visioning since there are many ideas shared by each member in the group i.e., brainstorming is more efficient in a team. Moreover, tunnel visioning happens more with topics and projects where students don’t have much experience with. That’s why reading and having much experience with different topics can be helpful to avoid tunnel visions. In the end, I know for a fact that I will still have tunnel visions in some projects; however, by performing brainstorming on every step and by building more experience I could avoid falling in tunnel visions.

Having tunnel vision can be detrimental in situations in which the root cause of a problem must be found, like in the simulations. With tunnel vision, someone does not consider all aspects of a problem, and instead focuses on one “path” to a solution. This has happened to me on multiple occasions on a variety of tasks and problems, and with the simulations, there was one tactic that I employed to prevent this from happening. With each simulation, I made a list of ideas to test, try, or consider immediately after understanding the prompts. Even if I strongly believed that I knew the solution, I made sure to write down all potential ideas because this forced me to think about the bigger picture. More than this, having a team also helps in that ideas can be brainstormed together, and team members can help other members who may have tunnel vision. Overall, tunnel vision can be terrible when it comes to brainstorming and problem solving, but there are a variety of tactics that can be used to prevent it from occurring.

From what I seen thus far, having tunnel vision has never resulted in any success especially when it comes to project management perspective. It is important have tunnel vision for yourself, like "I am trying to improve myself and myself only", however having tunnel vision regarding your vision for the project or your solution for any problem is counter intuitive in some cases as you may be wrong and might have to extend the over project. Additionally, by having tunnel vision you tend to miss out on what others have to offer. Hence the importance of communication during each step of the project. 

From what I seen thus far, having tunnel vision has never resulted in any success especially when it comes to project management perspective. It is important have tunnel vision for yourself, like "I am trying to improve myself and myself only", however having tunnel vision regarding your vision for the project or your solution for any problem is counter intuitive in some cases as you may be wrong and might have to extend the over project. Additionally, by having tunnel vision you tend to miss out on what others have to offer. Hence the importance of communication during each step of the project. 

From the four simulations in this class, I have learned that the occurrence of tunnel vision can lead a group to not complete a simulation in time. The reason for this is that the group will continue to propose tests surrounding one idea that can ultimately lead them to a failed proposal for resolving the conflict at hand. While working in my group for the initial simulations this was something I encountered as we proposed tests around one potential idea that was brainstormed as the potential root cause. As a result, a method to prevent the occurrence of tunnel vision is to challenge the team to brainstorm more than one potential path that could be followed. For instance, my group for this final simulation was able to avoid the negative effects of tunnel vision by proposing tests for multiple potential root causes in our first round of proposals. The results from this proposal were then assessed by the team to determine which potential paths should continue being tested. 

I've had to catch myself multiple times this semester to stop myself from tunnel vision. Especially, when you think you have a great idea that could be the solution. I think open communication with my group members helped prevent this. I think it is important to frequently take a step back and see how each step or part of a project relates back to the original goal of the project. In relation to the simulations, it is important to come up with a ton of ideas and generate experiments which will help you confirm or refute your hypothesis. However, especially in the second simulation, it is important to keep your options open since there could be multiple root causes and solutions to the problem. Throughout my job experiences I've also found it helpful to understand product testing time & resources - which has helped me improve planning experiments and strategizing design verification and root cause activities.

Having tunnel visions with these simulations, I believe, is unavoidable. The fact that you would like your current thought process to work out and try your best to do so is what anyone would want. Unfortunately, it could lead to realizing that another way of solving the problem would have been more beneficial. Fortunately, in these simulations, you get to work with others who bring in different ways and mindsets to solve these situations. Hopefully, through this, you could learn how to approach these situations better for faster results.