Welcome!

Microservices Expo Authors: John Katrick, Elizabeth White, Liz McMillan, Derek Weeks, Pat Romanski

Related Topics: Java IoT, Industrial IoT, Microservices Expo, Microsoft Cloud

Java IoT: Article

ERP and the Art of Action

The importance of knowledge transfer and alignment in ERP implementations

In his book The Art of Action (2011), Stephen Bungay identifies three gaps that frustrate the ability of organizations to translate plans into actions that lead to desired outcomes. He calls them the knowledge, alignment and effects gaps. Here, I wish to reflect on Bungay’s perspective by reviewing these gaps in terms of the selection and implementation of enterprise resource planning (ERP) software.

ERP software exerts a significant influence over the way an organization manages and monitors its performance. In large organizations, ERP software can touch hundreds, even thousands of people given that today’s ERP software may have a significant organizational footprint encompassing accounting, supply-chain, manufacturing, human resources (HR), customer relationship management (CRM), environmental, social and governance (ESG) and performance management activities. ERP software is at the heart of organizational management in the world’s leading businesses.

However, most organizations approach the selection and implementation of ERP software with some trepidation. The stories of failure are legion. There are well- documented examples of businesses brought to their knees by poor selections and out- of-control implementations. Spiraling budgets, burnt-out implementation teams and legal actions between buyers and sellers are a fact of life in the world of ERP.

Often, much of this spiralling cost, team stress and organizational risk is a direct result of the uncertainty and friction generated from Bungay’s three gaps. I’ll begin by introducing a typical ERP selection and implementation process and then discuss Bungay’s gaps in the context of ERP selection and implementation

The ERP Selection and Implementation Process
Figure 1 outlines a typical ERP software selection process. At the end of this process, buyers know very little about exactly how the ERP solution they are buying will meet their business needs, because the knowledge transfer from vendor to customer is of the order of just a few days of demos and customer reference checks. Therefore it’s hardly surprising that significant knowledge and alignment gaps exist even before any implementation process begins.

Fig. 1 – Typical ERP Software Selection Process (condensed)

Selection process

Figure 2 outlines a typical ERP ‘pre go-live’ implementation process. Knowledge and alignment gaps can surface at any stage of this process. And these gaps may be wide enough to have the potential to derail the project timeline or cost or cause some customers to consider switching their implementation partner. The Effects gap generally comes into play after implementation and during the initial pre go-live phase.

Fig. 2 – Typical ERP Implementation Process (condensed)

Consequently most ERP implementation projects, especially those informed by project management methodologies such as PRINCE2, are particularly concerned with managing risk. Unfortunately many project managers are not focused on actively mitigating risks caused by knowledge and alignment gaps and this is because many project managers either don’t recognise these gaps or don’t know how to mitigate them if they do. So let’s examine Bungay’s three gaps in more detail.

The Knowledge Gap
Bungay defines the Knowledge gap (p.45) as, ‘the difference between what we would like to know and what we actually know’ and a situation that prompts the ‘collection of more data’. In this context, the knowledge gap frustrates the ability of organizations to plan for an on-time, on-budget and on-benefit ERP implementation project.

Today’s ERP systems from market leaders such as SAP, Oracle and Microsoft (AX) are both broad and deep in terms of their functions and features. Much of the challenge in implementing these systems lies in figuring out how to configure the system to get the functionality you want with the minimum impact on operational (in- use) complexity. Gaining the knowledge required to design and build a fit-for-purpose solution is the key challenge for implementation partner, while communicating the information needed to enable this is the key challenge for an implementation customer.

Fig. 3 - The ERP Knowledge Gap

 

The ERP knowledge gap involves both parties, and has a significant role to play as a key project risk. Your implementation partner knows about the software and the best practices for configuring and using it. You know about your business processes and operational roles and responsibilities. Clearly, this is a gap that exists and needs to be crossed in every implementation. But at the same time, both parties are subject to what they mutually don’t know.

Implementation partners may have never configured the package to suit a specific business process or may uncover hidden software bugs in doing so. You may have never thought about managing a business process in the way that the system enforces or about adapting roles and responsibilities to suit new ways of doing things. So what neither of you know is an ever-present wild-card that can widen the knowledge gap, and in reality there’s no quick fix to this gap.

The Alignment Gap
Bungay defines the Alignment gap as, ‘the difference between what we want people to do and what they actually do’ and a situation that is indicated by ‘top-level frustration and lower-level confusion’. The Alignment gap also frustrates the ability of organizations to execute an on-time, on-budget and on-benefit ERP implementation.

In an ERP implementation, the alignment gap is all about methodology and expectations. If the implementation partner’s implementation methodology is not clearly communicated to and understood by the customer, alignment will suffer. Equally, if the customer’s implementation constraints are not clearly communicated and understood by the partner, alignment is impacted.

As Figure 4 shows, the ERP alignment gap is another key project risk that is created by misguided expectations created by poor communication and understanding between the two parties. Vendor methodologies must be adaptable to suit the organization size, operational style (e.g. methodical vs. agile) and team-resources of the customer. Otherwise an alignment gap will exist from the start and is likely to grow over time. And like the knowledge gap, there is a further ‘gotcha’ that may come into play in the form of unexpected events triggering timeline/people constraints (among others) that inevitably occur in implementation projects that can take many months or even years.

Fig. 4 – The ERP Alignment Gap

The Effects Gap
Bungay defines the Effects gap as, ‘the difference between what we expect our actions to achieve and what they actually achieve’ and a situation that is responded to by ‘an increase in control’ typically via the collection of more metrics. Here, the Effects gap frustrates the ability of organizations to fully realize the benefits from their ERP investment.

The total cost of ownership (TCO) of ERP solutions can easily run into millions of dollars of licensing and implementation fees, plus on-going maintenance and upgrade costs. So naturally the company boards or investors that authorize this level of expenditure expect significant benefit realization from their investment. Realization of these benefits depends on is a clear understanding of exactly what benefits are expected, communication of those expectations internally, and regular check-pointing of progress towards those benefits.

Implementation project managers are rightly focused on delivering projects on-time and on-budget. But the third deliverable, on-benefit, is often neglected or forgotten entirely. The reason is usually that benefits were never clearly defined and communicated in the first place and even if they are, it’s all too easy to forget the destination whilst dealing with the hazards of the journey.

As Figure 5 shows, unlike the previous gaps, the effects gaps is less about distance between the implementation partner and the customer and more about distance between an organization’s internal executive and operational management and the impact of ‘change strain’ on the ability of the organization to realize the expected benefits.

Fig. 5 – The Effects Gap

Closing the Gaps
Bungay claims (p.47) that the usual reactions to these three gaps are:

  • Knowledge: more detailed information
  • Alignment: more detailed instructions
  • Effects: more detailed controls

In other words, many project managers' dream: More complexity.

In terms of ERP selection and implementation, I believe one way of tackling the gaps that threaten to derail implementation projects specifically is to do more due diligence at the selection stage: that is to do more and take more time about doing it.

Many selections are hasty, with companies rushing headlong into implementation like a train that is already in danger of running off the tracks. The selection is considered a necessary evil and an unwanted cost. But money spent here will almost always lead to money being saved during the implementation process, where mistakes can be so much more costly. So here are some recommendations:

  • Start the selection with a clear definition and communication to the project team of executive management's expected benefits so that these can be revisited and adjusted regularly during selection, pre go-live implementation and post go-live operations. Formally build-in the checkpoint and review meetings, especially in the first year after go-live.
  • Consider sending your key functional ‘leads' (e.g. finance, supply chain and manufacturing) on a training course in your preferred ERP system BEFORE you decide to buy, rather than leave this until after the pilot phase of the implementation. These people should be smart enough to figure out if the package is likely to be a good fit from this ‘early-visibility' training and act as an early warning system for potential issues and problems to come.
  • Pay attention to both the functional and technical complexity of the solution you propose to buy. Businesses with limited resources or who have outsourced key IT infrastructure and lack available internal IT resources will inevitably struggle with ERP solutions that have complex technical requirements to setup and maintain. And unless you are buying a solution specifically designed to operate in a hosted environment, implementing ERP as a hosted application may introduce it's own challenges as many leading ERP solutions were simply not designed to be run in a hosted environment and in practice, many hosting companies have limited experience running ERP in software-as-a-service (SaaS) mode.
  • Make sure that you fully understand your implementation partner's methodology before you choose them. These methodologies can be complex - whole books have been written about Microsoft's Sure Step methodology for example - so spend the time to understand how the methodology works or put your team on a methodology training course well before any implementation process is started.
  • Try to achieve a close-fit alignment between you and your needs and your implementation partner's capabilities and resource constraints early on otherwise this will come back to haunt you time and again later in the implementation process.
  • Front-load the project with analysis activities that aim to close the knowledge gap well before any design/delivery/deploy activities (to use Microsoft Sure Step terms) take place. You simply can't paper over knowledge gaps. Lack of knowledge will always cause issues later - especially with today's ERP systems that depend on significant configuration effort that is costly to ‘roll- back' if you get it wrong due to inadequate knowledge of your business processes.
  • Focus your implementation project on meaningful rather than more data. So that as well as regular management of implementation tasks/actions, change requests and risks, make sure you also log and monitor business process and product configuration decisions made, and questions/issues/suggestions raised, as these are useful to refer back to when someone asks the inevitable question: ‘so why did we do it that way?'

Achieving outcomes effectively is always as much an art as a science. And it's impossible to expect that you can fully close these gaps and remove all uncertainty and friction from a project such as an ERP implementation. But there are ways to narrow the gaps and mitigate the risks they pose to give your plans and actions the best chance to deliver the outcomes you want to achieve.

More Stories By Stewart McKie

Stewart McKie has 25 years of IT industry experience. His education includes a MSc in Organization Consulting and a MA in Screenwriting. I was the Technology Editor of Business Finance magazine during 1995-2000 and also wrote regular features for Intelligent Enterprise magazine. I am the author of six books on accounting software and over 50 technology white papers. My current focus is my screenwriting 2.0 app called Scenepad and my supply-chain auditing app. I have managed many ERP selections and implementations of SunSystems all over the world. Currently I am engaged as the Implementation Oversight consultant for a global AX2009 rollout for a manufacturing client and as the selection consultant for pan-European ERP solution.

@MicroservicesExpo Stories
Gaining visibility in today’s sprawling cloud infrastructure is complex and laborious, involving drilling down into tools offered by various cloud services providers. Enterprise IT organizations need smarter and effective tools at their disposal in order to address this pertinent problem. Gaining a 360 - degree view of the cloud costs requires collection and analysis of the cost data across all cloud infrastructures used inside an enterprise.
The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
Admiral Calcote - also known as Lee Calcote (@lcalcote) or the Ginger Geek to his friends - gave a presentation entitled Characterizing and Contrasting Container Orchestrators at the 2016 All Day DevOps conference. Okay, he isn't really an admiral - nor does anyone call him that - but he used the title admiral to describe what container orchestrators do, relating it to an admiral directing a fleet of container ships. You could also say that they are like the conductor of an orchestra, directing...
The past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the business impact of software failures. How can software testing professionals keep pace with modern application delivery, given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery)? This is where continuous testing comes in. D
SYS-CON Events announced today that Synametrics Technologies will exhibit at SYS-CON's 22nd International Cloud Expo®, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. Synametrics Technologies is a privately held company based in Plainsboro, New Jersey that has been providing solutions for the developer community since 1997. Based on the success of its initial product offerings such as WinSQL, Xeams, SynaMan and Syncrify, Synametrics continues to create and hone in...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
The notion of improving operational efficiency is conspicuously absent from the healthcare debate - neither Obamacare nor the newly proposed GOP plan discusses the impact that a step-function improvement in efficiency could have on access to healthcare (through more capacity), quality of healthcare services (through reduced wait times for patients) or cost (through better utilization of scarce, expensive assets).
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task...
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
Many IT organizations have come to learn that leveraging cloud infrastructure is not just unavoidable, it’s one of the most effective paths for IT organizations to become more responsive to business needs. Yet with the cloud comes new challenges, including minimizing downtime, decreasing the cost of operations, and preventing employee burnout to name a few. As companies migrate their processes and procedures to their new reality of a cloud-based infrastructure, an incident management solution...
Our work, both with clients and with tools, has lead us to wonder how it is that organizations are handling compliance issues in the cloud. The big cloud vendors offer compliance for their infrastructure, but the shared responsibility model requires that you take certain steps to meet compliance requirements. Which lead us to start poking around a little more. We wanted to get a picture of what was available, and how it was being used. There is a lot of fluidity in this space, as in all things ...
Cloud Governance means many things to many people. Heck, just the word cloud means different things depending on who you are talking to. While definitions can vary, controlling access to cloud resources is invariably a central piece of any governance program. Enterprise cloud computing has transformed IT. Cloud computing decreases time-to-market, improves agility by allowing businesses to adapt quickly to changing market demands, and, ultimately, drives down costs.
Recent survey done across top 500 fortune companies shows almost 70% of the CIO have either heard about IAC from their infrastructure head or they are on their way to implement IAC. Yet if you look under the hood while some level of automation has been done, most of the infrastructure is still managed in much tradition/legacy way. So, what is Infrastructure as Code? how do you determine if your IT infrastructure is truly automated?
Every few years, a disruptive force comes along that prompts us to reframe our understanding of what something means, or how it works. For years, the notion of what a computer is and how you make one went pretty much unchallenged. Then virtualization came along, followed by cloud computing, and most recently containers. Suddenly the old rules no longer seemed to apply, or at least they didn’t always apply. These disruptors made us reconsider our IT worldview.