On December 25, 2009, a Nigerian man traveling to
After meeting with his National Security team, the President said, “It was a failure to integrate and understand the intelligence that we already had.” The President also said that the government had collected sufficient information to uncover the terror plot in advance but that intelligence officials had, “failed to connect those dots.”
The phrase “connecting the dots” has been often repeated to describe the circumstances which allowed for this situation to present itself. This incident has captured our attention because it is disturbing at a number of levels. The fact a person could get on an airplane with an explosive device reminds us all of how vulnerable we are. The fact this person was not stopped, despite the billions of dollars invested in intelligence services, is perplexing. The fact this person was known to some within the intelligence community but that knowledge did not result in action, is inexcusable.
In our organizational and community life, we often find situations which reflect a “failure to connect the dots.” While it is rare these situations present themselves as dramatically as a terrorist threat, we often find situations where the answer we seek is within our reach but seemingly unavailable to us.
Lessons Learned:
The incident of December 25th allows us to witness an examination of a very large system and how it failed to achieve its most basic goal. Describing the problem as a failure to connect the dots leads us to some basic questions:
- Which are the dots?
- What are the connections?
- What does it mean to connect the dots?
The phrase “connect the dots” suggests a model including resources, data and relationships. The “dots” can be seen as the agencies and resources which collect, catalogue and interpret data. The “connections” are the pieces of data/information flowing to and from the various agencies and resources (dots). Under this model, data flows to the dots for interpretation and collection and flows from the dots as refined information to be used elsewhere in the system.
In the system described above, information flows can be either directed (pushed) out from one agency/resource to another or can be provided in response to a request for information (pull). Regardless of whether data is pushed to or pulled from another agency/resource, it only becomes useful to the receiving organization after it is processed by the new owner of the data.
It seems an inevitable part of organizational life to find we continually have either too much or too little information to work with. The challenge is to find just the right mix of routinely provided information and information available on demand.
Applying the Lessons:
The following steps will help sort out the “connecting the dots” challenge:
- Identify the dots: Make a list of the organizations and resources which provide you with information.
- Identify the connections: What information is provided by each resource? Note whether the information provided is generated by the organization or passed along from another source.
- Note gaps and overloads: As you make an inventory of the information you receive you are likely to find there are things you need but don’t receive. You may also find data you receive but have no use for.
- Depending on what you find you will likely want to adjust the information flows connecting you to other organizations and resources.
The steps above are an informal process for reviewing the information flowing into an organization. There are more formal processes for reviewing how the dots connect and organizations should perform a formal data flow review on a regular basis. Another approach to the problem of connecting the dots is to forget about the dots and focus on the people within the dots.
_____________________
<http://www.AffinityByDesign.com/>