About Me

My photo
Scott Arnett is an Information Technology & Security Professional Executive with over 30 years experience in IT. Scott has worked in various industries such as health care, insurance, manufacturing, broadcast, printing, and consulting and in enterprises ranging in size from $50M to $20B in revenue. Scott’s experience encompasses the following areas of specialization: Leadership, Strategy, Architecture, Business Partnership & Acumen, Process Management, Infrastructure and Security. With his broad understanding of technology and his ability to communicate successfully with both Executives and Technical Specialists, Scott has been consistently recognized as someone who not only can "Connect the Dots", but who can also create a workable solution. Scott is equally comfortable playing technical, project management/leadership and organizational leadership roles through experience gained throughout his career. Scott has previously acted in the role of CIO, CTO, and VP of IT, successfully built 9 data centers across the country, and is expert in understanding ITIL, PCI Compliance, SOX, HIPAA, FERPA, FRCP and COBIT.

Tuesday, October 19, 2010

Change Management

I read an interesting article this past week on how some of the IT "Leaders" are saying ITIL has seen the prime is on a dowward spiral.  Really?  The organizations that have embraced ITIL and found value - probably would not agree.  Yes, there are those organizations that took on ITIL and failed - but that was the approach, not the methodology nor the value it brings when done properly. 

I have talked a few times on my blog about Change Management.  If you do any ITIL - start and maintain Change Management. If you don't track your changes, then your incident response has to include finding out what changed - right?  Having a managed and structure environment really ensures your environment can quickly respond in the event something happens.  Planned or unplanned - have documentation. 

Change Management:
  • Want to manage risks to the organization
  • Reduce risk to a level acceptable to management
  • Need to also enable the organization by quickly responding to changes
  • Need to design the process accordingly
  • Have a solid process
Have a great change advisory board, have full participation and do it right!  Check back again this week for my thoughts on Emergency Change.

Scott Arnett
scott.arnett@charter.net


 

No comments:

Post a Comment