Managing the cost of complexity
Robert L. Bogue
Published: 06 Jun 2005 11:45 BST
Controlling the cost of complexity
The simple answer to constraining training costs is to find something similar to existing pieces of the system. This can mean a different model of the same brand, or a model of a brand that is familiar to most of the people working on the system. Ultimately the goal is to minimise the amount of difference from one part of the solution to the other. For instance, if you typically buy NetGear switches and routers, try to add/replace NetGear switches and routers, if possible. If that’s not possible, look for a solution such as LinkSys which has a high penetration in the consumer market. Most IT professionals are bound to have run into these solutions before.
The next step in controlling costs is to document how the tool is used and what it is expected to do in the environment. If you clearly define the component's role, the less confusion there will be about how it’s being used. Documentation doesn’t have to be fancy, and shouldn’t be long. It should be the information someone needs to support and troubleshoot. The basic architecture of every solution should be documented.
Finally, good documentation can be a great help particularly in saving support costs when it’s unclear what pieces of the environment may be involved. Solid documentation should include product names, versions, firmware, serial numbers, support accounts, etc. It can be essential in reducing the amount of time necessary to resolve problems when they arise.
Key learning
Managing complexity in the environment is key to maintaining low costs. Managing complexity requires an honest evaluation of not only the acquisition cost but the costs associated with the long term impact of the solution.
Previous
Did you find this article useful?
174 out of 337 people found this useful
Digg
Slashdot
Del.ici.ous
Stumble
Reddit
