<\/p>\n\n
<\/p>\n\n
How do you shorten the path from deciding on a new business system to realizing business value\u2014without building in new constraints? That\u2019s a question Implema has worked on for more than 25 years. On October 15, Patrik Sundeborn, Head of Sales SAP at Implema, brings those lessons to the SAP Roadshow in Gothenburg to talk about what it takes to run a successful Cloud ERP project\u2014and why faster implementation is, above all, about starting to create value sooner. <\/strong><\/p>\n\n \u201cThe goal isn\u2019t to implement a business system as fast as possible. The goal is to get something in place sooner that creates value for the business\u2014and at the same time provides a foundation to keep building on,\u201d says Patrik Sundeborn. <\/p>\n\n Shortening the time from decision to a working solution is not a new ambition for Implema. For more than 25 years, the company has worked with standardized processes and its own methodology to reduce complexity in ERP projects and reach a working solution faster. <\/p>\n\n One key principle is not trying to solve everything at once.<\/p>\n\n \u201cIt\u2019s easy to think you should include every wish when you\u2019re changing business systems anyway. But every customization and special solution also creates complexity that the customer then has to live with and manage. We believe more in putting a stable foundation in place, starting to use it, and then continuing to develop based on the business\u2019s actual needs.\u201d <\/p>\n\n It\u2019s also about not locking the customer into a large project where the benefits are far off in the future.<\/p>\n\n \u201cThe longer it takes before the business starts using the solution, the longer it takes before the investment starts paying back. That\u2019s why we try to break the journey down and create value step by step.\u201d <\/p>\n\n For Patrik, a successful Cloud ERP project is therefore not about squeezing a traditional ERP project into a shorter timeframe. The key is instead to reduce unnecessary complexity from the start. <\/p>\n\n With modern cloud-based business systems, companies also don\u2019t need to start from a blank sheet of paper. Standardized processes, best practices, and ready-made ways of working provide a clearer starting point. <\/p>\n\n \u201cThat\u2019s very close to how we at Implema have always wanted to work. Start with standard, challenge requests for customizations, and focus effort on what is truly business-critical. With today\u2019s cloud solutions, the conditions for working that way are even better.\u201d <\/p>\n\n But \u201cfast track\u201d doesn\u2019t mean skipping important questions.<\/p>\n\n \u201cA fast project isn\u2019t one where everyone runs faster. It\u2019s about removing what doesn\u2019t create value and making the right decisions in the right order. That\u2019s where experience can make a very big difference.\u201d <\/p>\n\n A common objection to standardized implementations is that the business risks having to adapt to the system. Patrik argues that the question is really about where<\/em> a company actually needs to be unique. <\/p>\n\n \u201cNot all processes are competitive advantages. If there are established standard processes for things that don\u2019t differentiate the business, there\u2019s rarely any inherent value in building something of your own. Then the time and money can be used where they actually make a difference.\u201d <\/p>\n\n It also delivers an important long-term effect. Fewer customizations make it easier to upgrade, take advantage of new functionality, and continue developing the solution after the initial implementation. <\/p>\n\n \u201cThat\u2019s at least as important as the project timeline itself. The customer shouldn\u2019t just get into their new business system quickly. You should be able to keep moving forward without being stuck with the decisions and customizations made during the project.\u201d <\/p>\n\n This becomes even more important as AI is increasingly built directly into business systems and business processes.<\/p>\n\n \u201cIn the past, you could think of innovation as something you added later. Now, much of the development comes continuously in the platform. That makes it a major advantage to have a solution where you can actually adopt new features as they arrive.\u201d <\/p>\n\n For Patrik, it also changes the perspective on what an ERP implementation is really meant to achieve.<\/p>\n\n \u201cGo-live isn\u2019t the end goal. It\u2019s the starting point. What matters is how quickly you can start creating value and how strong your conditions are for continuing to develop the business after that.\u201d <\/p>\n\n An afternoon at Implema in Gothenburg on Cloud ERP, AI, and the path from business system projects to business value\u2014with perspectives from SAP, Emballator, and Implema.<\/p>\n\n 3:00 PM \u2013 Registration and coffee<\/strong> 3:15 PM \u2013 Welcome and introduction<\/strong> 3:30 PM \u2013 The latest trends in cloud-based business systems<\/strong> 3:50 PM \u2013 Customer case: Transformation with Cloud ERP<\/strong> 4:10 PM \u2013 The foundation for a successful Cloud ERP project<\/strong> 4:40 PM \u2013 Panel discussion and Q&A<\/strong>Fast implementations aren\u2019t new<\/strong><\/h2>\n\n
What does it take for a \u201cfast track\u201d to business value?<\/strong><\/h2>\n\n
Standard doesn\u2019t mean all companies should become the same<\/strong><\/h2>\n\n
AI increases the value of a solution that can evolve over time<\/strong><\/h2>\n\n