|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.
When building DevOps or continuous delivery practices you can learn a great deal from others. What choices did they make, what practices did they put in place, and how did they connect the dots? At Sonatype, we pulled together a set of 21 reference architectures for folks building continuous delivery and DevOps practices using Docker. Why? After 3,000 DevOps professionals attended our webinar on "Continuous Integration using Docker" discussing just one reference architecture example, we recogn...
Feb. 23, 2017 04:00 AM EST Reads: 2,548
Thanks to Docker and the DevOps revolution, microservices have emerged as the new way to build and deploy applications — and there are plenty of great reasons to embrace the microservices trend. If you are going to adopt microservices, you also have to understand that microservice architectures have many moving parts. When it comes to incident management, this presents an important difference between microservices and monolithic architectures. More moving parts mean more complexity to monitor an...
Feb. 23, 2017 01:30 AM EST Reads: 1,394
Feb. 22, 2017 11:30 PM EST Reads: 6,679
All clouds are not equal. To succeed in a DevOps context, organizations should plan to develop/deploy apps across a choice of on-premise and public clouds simultaneously depending on the business needs. This is where the concept of the Lean Cloud comes in - resting on the idea that you often need to relocate your app modules over their life cycles for both innovation and operational efficiency in the cloud. In his session at @DevOpsSummit at19th Cloud Expo, Valentin (Val) Bercovici, CTO of Soli...
Feb. 22, 2017 10:45 PM EST Reads: 663
"We're bringing out a new application monitoring system to the DevOps space. It manages large enterprise applications that are distributed throughout a node in many enterprises and we manage them as one collective," explained Kevin Barnes, President of eCube Systems, in this SYS-CON.tv interview at DevOps at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
Feb. 22, 2017 09:45 PM EST Reads: 6,707
The rise of containers and microservices has skyrocketed the rate at which new applications are moved into production environments today. While developers have been deploying containers to speed up the development processes for some time, there still remain challenges with running microservices efficiently. Most existing IT monitoring tools don’t actually maintain visibility into the containers that make up microservices. As those container applications move into production, some IT operations t...
Feb. 22, 2017 09:15 PM EST Reads: 807
Docker containers have brought great opportunities to shorten the deployment process through continuous integration and the delivery of applications and microservices. This applies equally to enterprise data centers as well as the cloud. In his session at 20th Cloud Expo, Jari Kolehmainen, founder and CTO of Kontena, will discuss solutions and benefits of a deeply integrated deployment pipeline using technologies such as container management platforms, Docker containers, and the drone.io Cl tool...
Feb. 22, 2017 06:30 PM EST Reads: 2,057
For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.
Feb. 22, 2017 04:45 PM EST Reads: 995
SYS-CON Events announced today that CA Technologies has been named “Platinum Sponsor” of SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY, and the 21st International Cloud Expo®, which will take place October 31-November 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA. CA Technologies helps customers succeed in a future where every business – from apparel to energy – is being rewritten by software. From ...
Feb. 22, 2017 02:45 PM EST Reads: 1,637
SYS-CON Events announced today that Outlyer, a monitoring service for DevOps and operations teams, has been named “Bronze Sponsor” of SYS-CON's 20th International Cloud Expo®, which will take place on June 6-8, 2017, at the Javits Center in New York City, NY. Outlyer is a monitoring service for DevOps and Operations teams running Cloud, SaaS, Microservices and IoT deployments. Designed for today's dynamic environments that need beyond cloud-scale monitoring, we make monitoring effortless so you...
Feb. 22, 2017 02:30 PM EST Reads: 1,547
DevOps is being widely accepted (if not fully adopted) as essential in enterprise IT. But as Enterprise DevOps gains maturity, expands scope, and increases velocity, the need for data-driven decisions across teams becomes more acute. DevOps teams in any modern business must wrangle the ‘digital exhaust’ from the delivery toolchain, "pervasive" and "cognitive" computing, APIs and services, mobile devices and applications, the Internet of Things, and now even blockchain. In this power panel at @...
Feb. 22, 2017 02:30 PM EST Reads: 4,780
Cloud Expo, Inc. has announced today that Andi Mann and Aruna Ravichandran have been named Co-Chairs of @DevOpsSummit at Cloud Expo 2017. The @DevOpsSummit at Cloud Expo New York will take place on June 6-8, 2017, at the Javits Center in New York City, New York, and @DevOpsSummit at Cloud Expo Silicon Valley will take place Oct. 31-Nov. 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Feb. 22, 2017 02:15 PM EST Reads: 1,516
With 10 simultaneous tracks, keynotes, general sessions and targeted breakout classes, Cloud Expo and @ThingsExpo are two of the most important technology events of the year. Since its launch over eight years ago, Cloud Expo and @ThingsExpo have presented a rock star faculty as well as showcased hundreds of sponsors and exhibitors! In this blog post, I provide 7 tips on how, as part of our world-class faculty, you can deliver one of the most popular sessions at our events. But before reading the...
Feb. 22, 2017 01:45 PM EST Reads: 8,267
TechTarget storage websites are the best online information resource for news, tips and expert advice for the storage, backup and disaster recovery markets. By creating abundant, high-quality editorial content across more than 140 highly targeted technology-specific websites, TechTarget attracts and nurtures communities of technology buyers researching their companies' information technology needs. By understanding these buyers' content consumption behaviors, TechTarget creates the purchase inte...
Feb. 22, 2017 12:45 PM EST Reads: 1,411
@DevOpsSummit at Cloud taking place June 6-8, 2017, at Javits Center, New York City, is co-located with the 20th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long developm...
Feb. 22, 2017 11:30 AM EST Reads: 1,250
Microservices (μServices) are a fascinating evolution of the Distributed Object Computing (DOC) paradigm. Initial design of DOC attempted to solve the problem of simplifying developing complex distributed applications by applying object-oriented design principles to disparate components operating across networked infrastructure. In this model, DOC “hid” the complexity of making this work from the developer regardless of the deployment architecture through the use of complex frameworks, such as C...
Feb. 22, 2017 11:15 AM EST Reads: 995
DevOps and microservices are permeating software engineering teams broadly, whether these teams are in pure software shops but happen to run a business, such Uber and Airbnb, or in companies that rely heavily on software to run more traditional business, such as financial firms or high-end manufacturers. Microservices and DevOps have created software development and therefore business speed and agility benefits, but they have also created problems; specifically, they have created software securi...
Feb. 22, 2017 11:00 AM EST Reads: 3,386
Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem" ...
Feb. 22, 2017 06:00 AM EST Reads: 5,411
Both SaaS vendors and SaaS buyers are going “all-in” to hyperscale IaaS platforms such as AWS, which is disrupting the SaaS value proposition. Why should the enterprise SaaS consumer pay for the SaaS service if their data is resident in adjacent AWS S3 buckets? If both SaaS sellers and buyers are using the same cloud tools, automation and pay-per-transaction model offered by IaaS platforms, then why not host the “shrink-wrapped” software in the customers’ cloud? Further, serverless computing, cl...
Feb. 22, 2017 06:00 AM EST Reads: 1,897
Hardware virtualization and cloud computing allowed us to increase resource utilization and increase our flexibility to respond to business demand. Docker Containers are the next quantum leap - Are they?! Databases always represented an additional set of challenges unique to running workloads requiring a maximum of I/O, network, CPU resources combined with data locality.
Feb. 22, 2017 02:45 AM EST Reads: 2,100