The Kronos Guy Blog

A Kronos Implementation: Planning for Complexity Part 3

Jenna Ryckman — May 2015

Over the last two weeks we have been discussing the inherent complexity in a Kronos implementation. In the part one of our planning for complexity series, we reviewed how to properly assess your project team’s mix of resources and skills by performing a current state analysis and how to create a resource inventory using that information. In part two of our Kronos Implementation series, we discussed how to start with the end in mind and how to successfully complete a state comparison and analysis for your organization. In the final blog of our three-part series, we are going to discuss the last simplification process: the Post-Project Support Model. 

Read More

A Kronos Implementation: Planning for Complexity Part 2

Jenna Ryckman — May 2015

Last week we discussed the inherent complexity in a Kronos implementation: part one of our three-part series about simplifying a complex enterprise Kronos implementation or project. We reviewed how to properly assess your project team’s mix of resources and skills by performing a current state analysis and how to create a resource inventory using that information. In part two of our Kronos Implementation series, we will discuss the next step of the simplification process: starting with the end in mind.

Read More

A Kronos Implementation Guide: Planning for Complexity

Jenna Ryckman — May 2015

Complexity is inherent in any enterprise Kronos implementation. Failing to fully account and plan for all variables in the total Kronos equation guarantees an overbudget and under-delivered project. Failing to plan for the inherent complexity in an IT project results in:

  • Incomplete Planning

  • Disjointed Execution

  • An end product that is a support nightmare, negating any planned ROI

"Most people don't plan to fail; they simply fail to plan."

Read More

Subscribe to Email Updates


Posts by Month

see all