Passion Fuels Purpose!

The more you sweat in preparation, the less you bleed in execution.

I provide expert guidance in the implementation of configuration management solutions. My methodology is not simply implementing a solution, as there are no “One Size Fits All” solutions to every entity in their market. Every organization should first understand the current operational state of the business and its anatomy. This is accomplished by properly identifying and understanding all the stakeholders as well as their needs, wants and interdependencies. Armed with this knowledge an organization can then strategically architect a roadmap that brings immediate value to the business, while providing a blueprint for successful growth of a Configuration Management solution.

Time and time again the traditional attempts on implementation of configuration management systems have produced failed attempts and discouraged further attempts due to a system that goes live without governance surrounding its core intent. This leads to an overwhelming amount of information that clouds the data, making that data harder to decipher and providing its consumers with added frustration when the intent of the CMS is to provide its customers with a clear understanding of a specific case at hand. The data should have the consistency, meaning, purpose and clarity to drive reports, harness impact simulations, identify criticality and gaps.

Adopting the ideology of establishing clear objectives upfront will pay in dividends at implementation time as it will reduce the cost, and raise the effectiveness, of an implementation team’s ability to focus on a set of predefined requirements, lowering the implementation time from months to just weeks. Allocating several weeks of workshops and knowledge transfers educating the organization, post implementation, of how their system operates becomes a thing of the past as the act of requirements gathering itself becomes the knowledge transfer.

This is an agnostic business, no matter the product, the core ideology remains the same. One should pursue progress over perfection. After all what once was a perfectly authored process that met all of the business requirements of the time, may in todays changing world, not carry the same perfection it once did. Audit verbiage changes; in some cases as fast as the technology it's meant govern. In other's it's simply a concatenation of processes that has tried to keep up with those changes to stay in compliance without re-examining the core requirements. So why carry these dated process over to a fresh start?