The 5 Dysfunctions of an IT Infrastructure

Having just re-read The Five Dysfunctions of a Team, by Patrick Lencioni (and highly recommending that you read it, too), we were inspired to share these thoughts with you based on what we are seeing in our work with various clients across the US.  These items are critical to every organization, regardless of what platforms have been adopted, and are only just starting to get the attention they deserve.  Have a look at our list and see what you think.

1. Inattention to the directory structure - the most frequently ignored yet easily the most critical part of any network infrastructure. Symptoms to watch for: cobbled together, out-of-control, too many administrators, inconsistent application of policies, inconsistent information, old user accounts, no group policies, too many group policies, slow user logins.
2. Inability to effectively and efficiently deploy system updates, new software, software upgrades, new images, etc.  - too many images, too much traffic to the update site versus an update service, have to physically touch every machine to do an upgrade
3. Unmanageable assets - what we have and what is being used, what is capable of supporting new software and what will need upgrading or retiring, no understanding of how assets inter-relate, network diagrams that are outdated as soon as they are created, or network diagrams that are not updated at all, software we bought but can't find, buying too much software
4. Inefficient help desks with poorly defined SLAs, process challenges, or SLAs that are frequently broken, management systems that have not adapted to new technology, or are difficult to customize, or systems that have dictated how our help desk should operate
5. Siloed thinking - not taking into account how systems, processes, software, and people need to integrate together to form a unified infrastructure,

What dysfunctions would you add to or subtract from this list?