Sunday, January 20, 2008
Enterprise Architecture and the communications problem...
Have you ever heard an IT executive discuss how the enterprise has a problem communicating. Here is my latest perspective on this topic...
Gaining consensus, buy-in or whatever phrase you happen to prefer is important. Minimally, it is vital that everyone knows everything they need to or at least how to find it out. The thing that most folks forget is that communication has a cost. The cost of communication is at least linear to the number of people who need to receive it.
James Tarbell and I frequently acknowledge that a simple conversation in the hallway may end up having to be put on slides to be presented to IT executives and therefore enterprise architects should carefully choose what to communicate and to whom.
What is the lost ROI when folks always CC an executive on project communications? Does the entire world need to be invited to participate in every decision?
| | View blog reactionsGaining consensus, buy-in or whatever phrase you happen to prefer is important. Minimally, it is vital that everyone knows everything they need to or at least how to find it out. The thing that most folks forget is that communication has a cost. The cost of communication is at least linear to the number of people who need to receive it.
James Tarbell and I frequently acknowledge that a simple conversation in the hallway may end up having to be put on slides to be presented to IT executives and therefore enterprise architects should carefully choose what to communicate and to whom.
What is the lost ROI when folks always CC an executive on project communications? Does the entire world need to be invited to participate in every decision?
