|By Stewart McKie||
|April 16, 2012 11:30 AM EDT||
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)
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.
JFrog has announced a powerful technology for managing software packages from development into production. JFrog Artifactory 4 represents disruptive innovation in its groundbreaking ability to help development and DevOps teams deliver increasingly complex solutions on ever-shorter deadlines across multiple platforms JFrog Artifactory 4 establishes a new category – the Universal Artifact Repository – that reflects JFrog's unique commitment to enable faster software releases through the first pla...
Oct. 7, 2015 03:00 PM EDT Reads: 553
Saviynt Inc. has announced the availability of the next release of Saviynt for AWS. The comprehensive security and compliance solution provides a Command-and-Control center to gain visibility into risks in AWS, enforce real-time protection of critical workloads as well as data and automate access life-cycle governance. The solution enables AWS customers to meet their compliance mandates such as ITAR, SOX, PCI, etc. by including an extensive risk and controls library to detect known threats and b...
Oct. 7, 2015 03:00 PM EDT Reads: 101
Ten years ago, there may have been only a single application that talked directly to the database and spit out HTML; customer service, sales - most of the organizations I work with have been moving toward a design philosophy more like unix, where each application consists of a series of small tools stitched together. In web example above, that likely means a login service combines with webpages that call other services - like enter and update record. That allows the customer service team to writ...
Oct. 7, 2015 02:45 PM EDT Reads: 335
Several years ago, I was a developer in a travel reservation aggregator. Our mission was to pull flight and hotel data from a bunch of cryptic reservation platforms, and provide it to other companies via an API library - for a fee. That was before companies like Expedia standardized such things. We started with simple methods like getFlightLeg() or addPassengerName(), each performing a small, well-understood function. But our customers wanted bigger, more encompassing services that would "do ...
Oct. 7, 2015 02:30 PM EDT Reads: 539
Clearly the way forward is to move to cloud be it bare metal, VMs or containers. One aspect of the current public clouds that is slowing this cloud migration is cloud lock-in. Every cloud vendor is trying to make it very difficult to move out once a customer has chosen their cloud. In his session at 17th Cloud Expo, Naveen Nimmu, CEO of Clouber, Inc., will advocate that making the inter-cloud migration as simple as changing airlines would help the entire industry to quickly adopt the cloud wit...
Oct. 7, 2015 01:30 PM EDT Reads: 605
The APN DevOps Competency highlights APN Partners who demonstrate deep capabilities delivering continuous integration, continuous delivery, and configuration management. They help customers transform their business to be more efficient and agile by leveraging the AWS platform and DevOps principles.
Oct. 7, 2015 01:15 PM EDT Reads: 116
Our guest on the podcast this week is Jason Bloomberg, President at Intellyx. When we build services we want them to be lightweight, stateless and scalable while doing one thing really well. In today's cloud world, we're revisiting what to takes to make a good service in the first place. Listen in to learn why following "the book" doesn't necessarily mean that you're solving key business problems.
Oct. 7, 2015 12:00 PM EDT Reads: 2,195
Apps and devices shouldn't stop working when there's limited or no network connectivity. Learn how to bring data stored in a cloud database to the edge of the network (and back again) whenever an Internet connection is available. In his session at 17th Cloud Expo, Bradley Holt, Developer Advocate at IBM Cloud Data Services, will demonstrate techniques for replicating cloud databases with devices in order to build offline-first mobile or Internet of Things (IoT) apps that can provide a better, ...
Oct. 7, 2015 11:45 AM EDT Reads: 486
Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership ab...
Oct. 7, 2015 11:00 AM EDT Reads: 857
Despite all the talk about public cloud services and DevOps, you would think the move to cloud for enterprises is clear and simple. But in a survey of almost 1,600 IT decision makers across the USA and Europe, the state of the cloud in enterprise today is still fraught with considerable frustration. The business case for apps in the real world cloud is hybrid, bimodal, multi-platform, and difficult. Download this report commissioned by NTT Communications to see the insightful findings – registra...
Oct. 7, 2015 11:00 AM EDT Reads: 222
Application availability is not just the measure of “being up”. Many apps can claim that status. Technically they are running and responding to requests, but at a rate which users would certainly interpret as being down. That’s because excessive load times can (and will be) interpreted as “not available.” That’s why it’s important to view ensuring application availability as requiring attention to all its composite parts: scalability, performance, and security.
Oct. 7, 2015 11:00 AM EDT Reads: 371
“All our customers are looking at the cloud ecosystem as an important part of their overall product strategy. Some see it evolve as a multi-cloud / hybrid cloud strategy, while others are embracing all forms of cloud offerings like PaaS, IaaS and SaaS in their solutions,” noted Suhas Joshi, Vice President – Technology, at Harbinger Group, in this exclusive Q&A with Cloud Expo Conference Chair Roger Strukhoff.
Oct. 7, 2015 10:00 AM EDT Reads: 376
As we increasingly rely on technology to improve the quality and efficiency of our personal and professional lives, software has become the key business differentiator. Organizations must release software faster, as well as ensure the safety, security, and reliability of their applications. The option to make trade-offs between time and quality no longer exists—software teams must deliver quality and speed. To meet these expectations, businesses have shifted from more traditional approaches of d...
Oct. 7, 2015 08:45 AM EDT Reads: 162
As the world moves towards more DevOps and microservices, application deployment to the cloud ought to become a lot simpler. The microservices architecture, which is the basis of many new age distributed systems such as OpenStack, NetFlix and so on, is at the heart of Cloud Foundry - a complete developer-oriented Platform as a Service (PaaS) that is IaaS agnostic and supports vCloud, OpenStack and AWS. In his session at 17th Cloud Expo, Raghavan "Rags" Srinivas, an Architect/Developer Evangeli...
Oct. 7, 2015 08:00 AM EDT Reads: 133
What Is Emergent About Emergent Architecture? By @TheEbizWizard | @DevOpsSummit #DevOps #BigData #API
All we need to do is have our teams self-organize, and behold! Emergent design and/or architecture springs up out of the nothingness! If only it were that easy, right? I follow in the footsteps of so many people who have long wondered at the meanings of such simple words, as though they were dogma from on high. Emerge? Self-organizing? Profound, to be sure. But what do we really make of this sentence?
Oct. 7, 2015 08:00 AM EDT Reads: 381
Last month, my partners in crime – Carmen DeArdo from Nationwide, Lee Reid, my colleague from IBM and I wrote a 3-part series of blog posts on DevOps.com. We titled our posts the Simple Math, Calculus and Art of DevOps. I would venture to say these are must-reads for any organization adopting DevOps. We examined all three ascpects – the Cultural, Automation and Process improvement side of DevOps. One of the key underlying themes of the three posts was the need for Cultural change – things like t...
Oct. 7, 2015 05:00 AM EDT Reads: 314
There once was a time when testers operated on their own, in isolation. They’d huddle as a group around the harsh glow of dozens of CRT monitors, clicking through GUIs and recording results. Anxiously, they’d wait for the developers in the other room to fix the bugs they found, yet they’d frequently leave the office disappointed as issues were filed away as non-critical. These teams would rarely interact, save for those scarce moments when a coder would wander in needing to reproduce a particula...
Oct. 7, 2015 05:00 AM EDT Reads: 277
In today's digital world, change is the one constant. Disruptive innovations like cloud, mobility, social media, and the Internet of Things have reshaped the market and set new standards in customer expectations. To remain competitive, businesses must tap the potential of emerging technologies and markets through the rapid release of new products and services. However, the rigid and siloed structures of traditional IT platforms and processes are slowing them down – resulting in lengthy delivery ...
Oct. 7, 2015 05:00 AM EDT Reads: 989
In a report titled “Forecast Analysis: Enterprise Application Software, Worldwide, 2Q15 Update,” Gartner analysts highlighted the increasing trend of application modernization among enterprises. According to a recent survey, 45% of respondents stated that modernization of installed on-premises core enterprise applications is one of the top five priorities. Gartner also predicted that by 2020, 75% of
Oct. 7, 2015 04:00 AM EDT Reads: 274
It is with great pleasure that I am able to announce that Jesse Proudman, Blue Box CTO, has been appointed to the position of IBM Distinguished Engineer. Jesse is the first employee at Blue Box to receive this honor, and I’m quite confident there will be more to follow given the amazing talent at Blue Box with whom I have had the pleasure to collaborate. I’d like to provide an overview of what it means to become an IBM Distinguished Engineer.
Oct. 7, 2015 04:00 AM EDT Reads: 174