No. The title is not a typo.
Have you ever heard the phrase that you aren't focusing enough? In management and, indeed, all kinds of complex development environments (of which I assume game development is one) we actually err the other way. This is the problem referred to as "Bounded Awareness" and it's a serious problem in development. The video above is an ad for SAP software claiming it can get around this problem; good marketing strategy, but I question it. The original study was done by Ulric Neisser back in 1979 and he used a slightly more obscuring video. In his studies he found that only 21% of viewers saw the gorilla dancing within the basketball players.
To contrast the silly gorilla video, we have the more serious Challenger explosion. This occurred because of an O-ring failure brought on by low temperatures. Before the launch there was a meeting about the O-rings in low temperature, but an analysiss of the last seven launches with O-ring failure revealed no correlation between temperature and failure. When expanding the analysis to all of the last 24 launches, the correlation becomes very obvious. Unfortunately that analysis was done after the explosion. Thus, by focusing on specific cases of O-ring failure, the gorilla (bad O-ring) became invisible and the space shuttle exploded, killing those on board. I don't want to trivialize NASA's job or claim that they didn't "see the obvious." There are thousands of things that can go wrong in a complex system and it's easy to pick on something like this. It's precisely because there are so many details that our minds become ignorant of the incredibly obvious.
It is important that managers know this. On many occasions I have seem brilliant programmers become obsessed with a particular problem and spin on it for days, weeks, and even months. Many times they have focused themselves on some minor detail which is not really all that important for the game. A great way to find these is to identify someone who has been working on something for "a long time" and have them walk you through what they are doing and why they are doing it. Even if you don't understand the problem yourself, forcing someone to explain it to you may let them see the gorilla. Don't focus on the details of what task they are doing, or how long it will take then - as managers often do. Instead, put yourself in their mind, look at the world through their eyes and see if it makes sense. This simultaneously forces them to step back for a second and make sure there aren't any kung-fu gorillas in the code.
Ironically, this same problem applies to playing games. Adventure games are notorious in this way. It's so easy to use details to cause focus on small things such that people miss the big things. My favorite example of this is the movie "The Sixth Sense." *SPOILER ALERT*
While watching it, it is almost impossible to recognize that Bruce Willis' character never interacts with physical objects, doesn't have meaningful conversations (except with the kid) and so on. The movie is bounding you to assume that he is a real person so your mind is unable to consider that this assumption is incorrect. If you know he's the ghost the movie looks VERY different, just like the silly basketball video and the challenger explosion.
Unlike other human rationality problems bounded awareness is something that can usually be avoided by simply reminding yourself that you will be doing it. Bringing in people outside the project, the proverbial "fresh set of eyes" will also do the trick. If you watch the video without the bounded condition of "count the passes" it's almost impossible not to see the gorilla.