LM: The term “Evergreen” is a pillar of IFS Cloud, meaning the system is constantly updated. However, for many organizations used to “freezing” their system for years, this sounds exhausting. Klas, how do you manage this organizational shift?
KK: You’ve hit the nail on the head. Historically, an ERP upgrade was a “big bang” event every 5 to 7 years. You did the project, then you forgot about it for half a decade. With Evergreen, that cycle is broken. You now receive updates twice a year.
The challenge is organizational: you need a permanent “Release Management” mindset. This means your Super Users can’t just go back to their daily jobs and forget the ERP. They need to proactively review change logs and test new features in a sandbox environment regularly. It sounds like more work, but it’s actually about “small steps” instead of “giant leaps.” It prevents your business from ever becoming obsolete again, but it requires a culture that values continuous improvement over static stability.
LM: Does this mean companies need to change their internal support structures to keep up with these updates?
KK: Absolutely. You need a dedicated rhythm. We recommend setting up a permanent “IFS Cloud Steering Committee” that meets not just during the project, but throughout the year. Their job is to look at the upcoming IFS roadmap and decide which new features will actually drive value for the business, rather than just reacting to technical updates.
December 28, 2024 
5 min to read 
