The "Kronos Guy" Blog
WFC is moving to the Cloud. In fact, 83% of net new additions of Workforce Central are now in the Cloud. Cloud-based workforce management applications create easier access and management of real-time employee data, while providing enterprise class HR, time, and attendance platforms. It seems like everywhere you look technical blogs and IT consultants are encouraging small and mid-size businesses to consider moving to the Cloud. However, a migration to the Cloud can be costly, time consuming, and disappointing if not executed properly. With the release of Kronos Version 8.0, many organizations are considering, not just an on-premise upgrade, but upgrading into the Kronos Cloud. How can you determine if it will be beneficial to your organization to move to the cloud?
Here are some key questions to consider before deciding if moving to the Kronos Cloud is a wise investment for your company.
The moment we've all been waiting for: Kronos recently debuted Workforce Central Version 8 with a webinar entitled, “Workforce Central 8: Managing without Limits.” The new and improved platform boasts optimized user experience, enhanced industry capabilities and Global Deployments, as well as intuitive and accessible reporting and analytics. Kronos introduced over 500 new features between versions 7.0 and 7.07 and Version 8.0 contains all those and many more.
In this blog post, we are highlighting the top eight new Version 8.0 features that we are most excited about. Which new features will have the biggest positive affect on your company?Read More
I just returned from the Kronos Partnership Summit. Yes, I got to see Kronos version 8! (How jealous are you, dear readers?)
Kronos is referring to the release of version 8 as a Product Event - a release of a product that is so special it has the potential to become a game-changer for its users. In this case, I think the hype is true. Just about everyone is excited, but in all the excitement, I'm consistently hearing a few themes and some questions. We're even seeing questions and discussions over on Kronos-fans! I'd love to get a conversation started - won't you join me?
Tags: Kronos Version 8.0
Companies invest substantial labor and financial resources to
deploy workforce management software.
Why do so many projects fail?
Although each Workforce Management implementation has its own unique needs and requirements, WFM projects share certain commonalities: they are complex, require detailed strategy and thoughtful change management. Failure can have catastrophic consequences across an organization. With Kronos Version 8.0 being released, it is time for many organizations to start considering an implementation or upgrade strategy. Strategic planning at the outset of the implementation saves time and money while increasing the likelihood that expected benefits will be delivered on time and on budget.
Software implementation and upgrade projects are prone to failure. Overall, an estimated 74% of IT (Information Technology) projects fail in delivering “the promised functionality on time and on budget.” An average 66% of software projects experience a cost overrun, 33% experience a schedule overrun and 17% fail so badly they can threaten the very existence of the company. In fact, 50% of businesses had an IT project fail in the last 12 months. Workforce Management Software (including Kronos®) implementations face similar threats.
Kronos® implementations can be particularly challenging and complex.
Depending on the business needs of an organization, a Kronos deployment can touch every facet of the company, including employee timekeeping, payroll, benefits and HR administration. From a technical side, HR, Payroll and Accounting systems may be affected through single and dual-feed data interfaces. Not only are employees and systems affected, but compliance with legislative mandates and union agreements can also be major concerns for a Kronos implementation. An organization implementing any Kronos version across multiple locations must also contend with a variety of local, state, federal (and in the case of an international deployment, country) regulations. Failure to adequately meet these requirements can be costly. Intangible aspects of a difficult or failed implementation impact an organization as well - no employee is happy to have their paycheck or benefits miscalculated.
Failure is not an option; strategy is the solution. [Tweet This]
Too often, organizations will begin an IT project with no clear direction on where they currently are or where they are going. The pressure of a necessary Kronos upgrade can cause decisions without direction. The literature agrees: software project failures are often the result of inconsistent stakeholder involvement and commitment, fuzzy business objectives or a failure to align project requirements with business needs.
Strategic implementation planning must identify an organization’s Critical Success Factors (CSFs). These factors will vary by organization size, location(s) and industry. To avoid costly overruns or inadequate delivery, a successful implementation plan will include:
- Strategic Alignment
- Strategic Reconciliation
- Gap Analysis
- Project Charter
- Change Management
To continue reading click below to download our new whitepaper: Successful Implementation Strategies.
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 successfullly 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
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
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."
When writing about The Law of Competition, Andrew Carnegie said “…while the law may be sometimes hard for the individual, it is best for the race, because it insures the survival of the fittest in every department”.
Gamification has become a large topic of conversation in recent months, specifically in the fields of healthcare and retail. In fact, technology research and advisory company, Gartner, Inc. predicted that by 2016, businesses will spend a total of $2.6 billion on this technology. Although the projected numbers seem hopeful, industry thought-leaders disagree on whether or not the technology will be effective.Read More
Faced with the dilemma of keeping up with service packs, advisories, and upgrades, Prince Hamlet of Kronosland despondently asked, "To upgrade or not to upgrade, that is the question ---." Painful reference to Shakespeare aside, should your organization upgrade now? Should you wait for the java-free Kronos version 8.0? The Kronos Upgrade conversation often centers on the decision to upgrade, without focusing on “why” the decision to upgrade is necessary. Strategically planning if, when, and how to upgrade entails understanding the reasons why a Kronos upgrade would be beneficial for your organization (or why it might be time to wait).
Here are some of the most important reasons to upgrade:Read More