<span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">!http://knowledgeinfusion.typepad.com/knowlege_infusion_blog/images/ki53.jpg![http://knowledgeinfusion.typepad.com/.shared/image.html?/photos/uncategorized/ki53.jpg]Now that youâ??ll be sleeping well due to the go-live of your HR, Talent Management, HCM project, itâ??s time for a phase of the project that you will not see addressed in any project methodology.  I like to call this the â??Vigilanceâ?? phase.  Dictionary.com defines vigilance as simply â??alert watchfulness.â??  I think this definition suits this phase well.  The vigilance phase canâ??t be planned â?? itâ??s almost all reaction mode.</span>

<span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Although itâ??s important to celebrate the important gains made thus far in your project journey, itâ??s even more important to remain vigilant.  It is at this point in many projects where previously unknown issues are discovered as more and more users begin to use the technology.  These problems can snowball and negatively impact the perception of the user community toward the system.   The Vigilance Phase is much more than â??Production Supportâ??, itâ??s an attitude.  In this post go-live phase, user perception is the key to your success.  Here are some suggestions on how to be vigilant:</span>

1. <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"># Donâ??t discount any reports of problems or functionality glitches â?? not matter how seemingly minor.  Investigate everything!  Most issues will not turn out to be major problems.  If you can solve a problem early, you just might be preserving a positive view of the system by the user community â?? which will keep user adoption high.</span>#

1. <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"># There will be some flame-ups (itâ??s inevitable).  These flame-ups may be technical issues, functionality issues, or expectation management/communication issues.  Have a SWAT team identified and ready to be called upon to stamp out flame-ups.  Address flame-ups quickly and communicate with confidence about solutions.</span>#

1. <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"># Itâ??s not a failure when issues arise - Itâ??s a normal part of technology implementations.  Addressing these post go-live issues is just another part of the final phase of your implementation.  Be prepared to react quickly and decisively. </span>#

1. <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"># Stay vigilant for a month (at least) after go-live.  Often problems donâ??t become clear until a large number of users exercise the application.</span>#

<span face="Times New Roman">

<span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">By recognizing the importance of the Vigilance Phase, you will be taking a major step toward insuring the success of your HCM project.  If you would like to discuss further; mailto:andrew.gebavi@knowledge-infusion.com.</span>