Download the WFM Implementation Strategy White Paper
Musician & Yin Style Bagua practitioner. Over twenty years of software implementations and upgrades, project management, systems and applications development experience with a current focus on ADP eTime & Kronos Timekeeper/HR systems implementation.
Current Articles | RSS Feed
Welcome to the second in the series of the Kronos WFC Upgrade Studio Change Management Toolkit. Remember, no psycho-babble. No discussion of checkpoints, Change Control Review Boards or big flowcharts. We're going to focus on the stuff that matters.
So let's cut to the chase. How does an implementation team decide just how much Change Management (next blog I'll clearly define my use of the terms) is required for the organization? One has to carefully analyze both the functional and technical impact of the changes that will be promoted into Production.
The Technical concerns are usually just "Make sure the change does what it appears it's supposed to do. Don't let it break Production."
The Functional concerns are simply, well, often ignored except for development requested by a particular person/dept/location. The scary part here is that it's the functional areas for which ALL this is done? Why do anything if it doesn't improve Operations, ROI, User Experience, etc.
With this in mind one should ask serious questions about the way we manage change.
Allowed tags: <a> link, <b> bold, <i> italics