|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.
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of...
Jul. 1, 2015 05:00 PM EDT Reads: 2,181
Conferences agendas. Event navigation. Specific tasks, like buying a house or getting a car loan. If you've installed an app for any of these things you've installed what's known as a "disposable mobile app" or DMA. Apps designed for a single use-case and with the expectation they'll be "thrown away" like brochures. Deleted until needed again. These apps are necessarily small, agile and highly volatile. Sometimes existing only for a short time - say to support an event like an election, the Wor...
Jul. 1, 2015 05:00 PM EDT Reads: 1,599
The cloud has transformed how we think about software quality. Instead of preventing failures, we must focus on automatic recovery from failure. In other words, resilience trumps traditional quality measures. Continuous delivery models further squeeze traditional notions of quality. Remember the venerable project management Iron Triangle? Among time, scope, and cost, you can only fix two or quality will suffer. Only in today's DevOps world, continuous testing, integration, and deployment upend...
Jul. 1, 2015 03:00 PM EDT Reads: 1,906
Discussions about cloud computing are evolving into discussions about enterprise IT in general. As enterprises increasingly migrate toward their own unique clouds, new issues such as the use of containers and microservices emerge to keep things interesting. In this Power Panel at 16th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the state of cloud computing today, and what enterprise IT professionals need to know about how the latest topics and trends affect t...
Jul. 1, 2015 02:30 PM EDT Reads: 1,160
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Arch...
Jul. 1, 2015 02:21 PM EDT Reads: 470
Summer is finally here and it’s time for a DevOps summer vacation. From San Francisco to New York City, our top summer conferences list is going to continuously deliver you to the summer destinations of your dreams. These DevOps parties are hitting all the hottest summer trends with Microservices, Agile, Continuous Delivery, DevSecOps, and even Continuous Testing. Move over Kanye. These are the top 5 Summer DevOps Conferences of 2015.
Jul. 1, 2015 01:00 PM EDT Reads: 843
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
Jul. 1, 2015 12:00 PM EDT Reads: 1,702
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
Jul. 1, 2015 11:45 AM EDT Reads: 1,004
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at DevOps Summit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.
Jul. 1, 2015 10:30 AM EDT Reads: 784
Cloud Migration Management (CMM) refers to the best practices for planning and managing migration of IT systems from a legacy platform to a Cloud Provider through a combination professional services consulting and software tools. A Cloud migration project can be a relatively simple exercise, where applications are migrated ‘as is’, to gain benefits such as elastic capacity and utility pricing, but without making any changes to the application architecture, software development methods or busine...
Jul. 1, 2015 10:00 AM EDT Reads: 1,914
Data center models are changing. A variety of technical trends and business demands are forcing that change, most of them centered on the explosive growth of applications. That means, in turn, that the requirements for application delivery are changing. Certainly application delivery needs to be agile, not waterfall. It needs to deliver services in hours, not weeks or months. It needs to be more cost efficient. And more than anything else, it needs to be really, dc infra axisreally, super focus...
Jul. 1, 2015 10:00 AM EDT Reads: 1,972
The most often asked question post-DevOps introduction is: “How do I get started?” There’s plenty of information on why DevOps is valid and important, but many managers still struggle with simple basics for how to initiate a DevOps program in their business. They struggle with issues related to current organizational inertia, the lack of experience on Continuous Integration/Delivery, understanding where DevOps will affect revenue and budget, etc. In their session at DevOps Summit, JP Morgenthal...
Jul. 1, 2015 09:32 AM EDT Reads: 570
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction. ...
Jul. 1, 2015 09:00 AM EDT Reads: 852
DevOps tends to focus on the relationship between Dev and Ops, putting an emphasis on the ops and application infrastructure. But that’s changing with microservices architectures. In her session at DevOps Summit, Lori MacVittie, Evangelist for F5 Networks, will focus on how microservices are changing the underlying architectures needed to scale, secure and deliver applications based on highly distributed (micro) services and why that means an expansion into “the network” for DevOps.
Jun. 30, 2015 08:30 AM EDT Reads: 2,429
Many people recognize DevOps as an enormous benefit – faster application deployment, automated toolchains, support of more granular updates, better cooperation across groups. However, less appreciated is the journey enterprise IT groups need to make to achieve this outcome. The plain fact is that established IT processes reflect a very different set of goals: stability, infrequent change, hands-on administration, and alignment with ITIL. So how does an enterprise IT organization implement change...
Jun. 29, 2015 12:45 PM EDT Reads: 2,807
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations migh...
Jun. 28, 2015 05:00 PM EDT Reads: 2,044
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
Jun. 28, 2015 01:00 PM EDT Reads: 1,908
Mashape is bringing real-time analytics to microservices with the release of Mashape Analytics. First built internally to analyze the performance of more than 13,000 APIs served by the mashape.com marketplace, this new tool provides developers with robust visibility into their APIs and how they function within microservices. A purpose-built, open analytics platform designed specifically for APIs and microservices architectures, Mashape Analytics also lets developers and DevOps teams understand w...
Jun. 27, 2015 11:00 AM EDT Reads: 1,944
Buzzword alert: Microservices and IoT at a DevOps conference? What could possibly go wrong? In this Power Panel at DevOps Summit, moderated by Jason Bloomberg, the leading expert on architecting agility for the enterprise and president of Intellyx, panelists peeled away the buzz and discuss the important architectural principles behind implementing IoT solutions for the enterprise. As remote IoT devices and sensors become increasingly intelligent, they become part of our distributed cloud envir...
Jun. 26, 2015 12:00 PM EDT Reads: 2,243
Sumo Logic has announced comprehensive analytics capabilities for organizations embracing DevOps practices, microservices architectures and containers to build applications. As application architectures evolve toward microservices, containers continue to gain traction for providing the ideal environment to build, deploy and operate these applications across distributed systems. The volume and complexity of data generated by these environments make monitoring and troubleshooting an enormous chall...
Jun. 26, 2015 12:00 PM EDT Reads: 1,550