SAP ROI — Enterprise Architecture & Business Solutions

Strategic SAP & IT Program Development for Measurable Business Value

Leading Change (and Change Management)

May 17th, 2010

Leading Change


“Leading Change” is clearly more difficult than arriving at the realization that change is needed…If you want to validate the prior statement reflect back on all of the “change agents” that have crossed your path over the years and ask yourself the following question: How many of them have truly succeeded? While we’ve heard a lot about change of late as it relates to our current political landscape, the power of real change is trivialized when it becomes little more than a political sound-bite. Whether in business or in life in general, I have found that change can either be your best friend or your worst nightmare – which is it for you? Nobody ever said change was easy, but it’s critical that you understand that change is essential. In today’s blog post I’ll discuss why CEO’s and entrepreneurs (and not just politicians) need to become masters at catalyzing and leading change.

Why is Change (and Change Management) Important in Today’s Business?

While there is little debate that the successful implementation of change can create an extreme competitive advantage, it is not well understood that the lack of doing so can send a company (or an individual’s career) into a death spiral. Companies that seek out and embrace change are healthy, growing, and dynamic organizations, while companies that fear change are stagnant entities on their way to a slow and painful death. 

Agility, innovation, disruption, fluidity, decisiveness, commitment, and above all else a bias toward action will lead to the creation of change. It is the implementation of change which results in evolving, growing and thriving companies. Much has been written about the importance of change, but there is very little information in circulation about how to actually create it. While most executives and entrepreneurs have come to accept the concept of change management as a legitimate business practice, and change leadership as a legitimate executive priority in theory, I have found very few organizations that have effectively integrated change as a core discipline and focus area in reality.   

Consider the modern workplace…In executive circles, leaders often talk about employees who are not on-board, resist change, and are reluctant to try new things.  And among the ranks of employees, conversations that take place in the hallways and break rooms often center around whether or not executives really know what they’re doing, and whether the newest change initiative is just a passing fad.  Actually, these reactions are reasonable, given the pace that change is occurring in most of organizations.

Leading change is certainly not without risk, but if implemented properly it can breathe life back into the most tired business. The most successful companies incorporate disruptive thinking into all of their business and management practices to gain distinctive competitive value propositions. “Me Too” companies fight to eek out market share in an attempt to survive while disruptive companies become category dominant brands insuring sustainability. So why do so many established and often well managed companies struggle with disruptive innovation? Many times it is simply because companies have been doing the same things, in the same ways, and for the same reasons for so long that they struggle with the concept of change.

Change as a Critical Success Factor for Innovation

As a CEO Coach many of my engagements with chief executives focus on helping them to embrace change through disruptive innovation. Why didn’t the railroads innovate? Why didn’t Folgers recognize the retail consumer demand for coffee and develop a “Starbucks” type business model? Why didn’t IBM see Dell and Gateway coming? Why didn’t more established social networks see Twitter coming? How did the brick and mortar book stores let Amazon get the jump on them? I could go on-and-on with more examples, but the answer to these questions are quite simple…The established companies become focused on making incremental gains through process improvements and were satisfied with their business models and didn’t even see the innovators coming until it was too late. Their focus shifted from managing opportunities to managing risk, which in turn allowed them to manage themselves into brand decline…

At one end of the spectrum take a look at the companies receiving investment from venture capital and private equity firms, and on the other end of the spectrum observe virtually any category dominant brand and you’ll find companies with a disruptive focus putting the proverbial squeeze on the “me too” firms occupying space in the middle of the spectrum. The continued rapid development of technology is taking the concept of globalization and turning it into hard reality facing businesses of all sizes, it is time for executives and entrepreneurs to examine their current business models from a disruptive perspective.

Why the Pursuit of Perfection is the Enemy of Change and Change Management

One of my contentions about why change is difficult to implement is that too many executives want perfection to precede action, and the truth is that the pursuit of perfection is one of the great adversaries of speed. In fact, at the risk of being controversial I’m going to take the position that perfection does not exist. I hate to break it to you, but those of you who regard yourselves as perfectionists simply exhibit perfectionistic tendencies in an unrealistic attempt to achieve what cannot be had. The pursuit of perfectionism might lead to small, incremental increases in quality, but at what cost? What the pursuit of perfectionism will cause is time delays, cost overruns, missed deadlines and unkept commitments. I would suggest that rather than seeking what cannot in most cases ever be achieved, that it makes more sense to seek the highest standard of quality that makes economic sense relative to the constraints of an ever shifting marketplace.

Change, Change Management, Agility, Speed, and Reducing Cycle Times

One of the key considerations that must be understood when implementing change is the necessity of moving quickly. There are those that would argue that speed in synonymous with undisciplined decisioning, but I would caution you against confusing speed with reckless abandon I’m a big proponent of planning, assessment, analysis and strategy, but only if it is concluded in a timely fashion. “Analysis Paralysis” leads to missed opportunities and failed initiatives.

Earlier in my career I served as Director of Internet Strategy for what was at that time the world’s largest web-enablement firm. While serving in that position I coined the term e-velocity which we trademarked and used to describe the influence that technology was having on the pace at which business had to be conducted in order to remain competitive. It used to be acceptable to take 12 to 18 months to roll-out an initiative, but in today’s world you better be able to do it in 90 days or it will be obsolete before it gets to market.

When I first started in business it was usual and customary to produce 5 and 10 year business plans and today I work off of rolling 90 day tactical business plans. The latest advances in Business Process Management (BPM) have seen a reduction in the planning and budgeting cycle from 120 and 90 days to 45 days. But, is 45 days good enough? How many days constitute a responsive cycle time? Many believe the right number is between 5 and 10 days. Why is cycle time reduction important? Because shorter planning and budgeting processes facilitate greater flexibility and responsiveness.

In today’s competitive business environment you must quickly be able to assess risk and make timely decisions. You cannot be successful being guided by fear and hesitation. When in doubt, remember that “Speed Kills” and that “he who hesitates is lost.” Don’t fear change…embrace it. I think General George S. Patton said it best: “A good plan violently executed today is far and away better than a perfect plan tomorrow.”

====================

The original source for this post can be found here: http://www.n2growth.com/blog/leading-change/

====================

Leading Change Isn’t Hard

Is leading change difficult? Only if you don’t know what you’re doing. As much as some people want to create complexity around the topic of leading change for personal gain, the reality is that creating, managing and leading change is really quite simple. In fact, catalyzing and leading change isn’t very daunting at all if you understand the 3 pillars of change. To prove my point, I’ll not only explain the entire change life-cycle using the 3 pillars of change in three short paragraphs, but I’ll do it in simple terms that anyone can understand…

Identifying the Need for Change:

The need for change exists in every organization. Other than irrational change solely for the sake of change, every corporation must change to survive. If your entity doesn’t innovate and change with market driven needs and demands it will fail…it’s just that simple. The most complex area surrounding change is focusing your efforts in the right areas, for the right reasons, and at the right times. The ambiguity and risk can be taken out of the change agenda by simply focusing on three areas: 1) your current customers…what needs to change to better serve your customers? 2) potential customers…what needs to change to profitably create new customers? and; 3) your talent and resources…what changes need to occur to better leverage existing talent and resources? 

Leading Change:

You cannot effectively lead change without understanding the landscape of change. There are four typical responses to change: The Victim…those that view change as a personal attack on their persona, their role, their job, or their area of responsibility. They view everything at an atomic level based upon how they perceive change will directly and indirectly impact them. The Neutral Bystander…This group is neither for nor against change. They will not directly or vocally oppose change, but neither will they proactively get behind change. The Neutral Bystander will just go with the flow not wanting to make any waves hoping to perpetually fly under the radar. The Critic…The Critic opposes any and all change. Keep in mind that not all critics are overt in their resistance. Many critics remain in stealth mode trying to derail change behind the scenes by using their influence on others. Whether overt or covert, you must identify critics of change early in the process if you hope to succeed. The Advocate…The Advocate not only embraces change, they will evangelize the change initiative. Like The Critics, it is important to identify The Advocates early in the process to not only build the power base for change, but to give momentum and enthusiasm to the change initiative. Once you’ve identified these change constituencies you must involve all of them, message properly to each of them, and don’t let up. With the proper messaging and involvement even adversaries can be converted into allies.

Managing Change:

Managing change requires that key players have control over 4 critical elements: 1) Vision Alignment…those that understand and agree with your vision must be leveraged in the change process. Those that disagree must be converted or have their influence neutralized; 2) Responsibility…your change agents must have a sufficient level of responsibility to achieve the necessary results; 3) Accountability…your change agents must be accountable for reaching their objectives, and; 4) Authority…if the first three items are in place, yet your change agents have not been given the needed authority to get the job done the first three items won’t mean much…you must set your change agents up for success and not failure by giving them the proper tools, talent, resources, responsibility and authority necessary for finishing the race.

====================

The original source for this post can be found here: http://www.n2growth.com/blog/leading-change-isnt-hard/

Re-posted with author Mike Myatt’s permission, he runs a great blog at http://www.n2growth.com/blog/

Related Posts:

Process Execution of Business and IT Innovation

May 3rd, 2010

Innovation

The idea of innovation in business or IT is generally an aspiration to most.  Leaders and managers occasionally mention the need to innovate but when they stop to consider what that means many of them abandon it as an impossible dream.  They wait for some strange spark, some odd occurrence to somehow spark the flame of new beginnings.

Execution of the Innovation Process

Inspiration for innovation or creativity can come from anywhere.  Frequently the innovation problem isn’t a lack of good ideas, or even innovative solutions–, too often it is a lack of execution.  Even though I’ve laid out a proposed business model for an innovation process in the post From Collaboration to Innovation to Market – Toward a Working Model too often the champions, or the owners for the process are missing from the major stages of execution.  There must be an “owner” or a “champion” at each stage, they might be the same person, or it might be a different person, but each stage needs someone to champion the new innovation to maturity and then to completion or it will die in the process.

The three stages I have defined are concieve, develop, and market.  For example, the conceive stage might have a marketing or sales person “own” that process to its development handoff.  That does not mean that engineering or some other key person from the development area should not be active in the early conception stages, only that the stakeholder(s) with the most influence at that stage should own that portion of the process.  At the develop stage it might be key product or service leaders who then move the idea from infancy and from concept to tangible product or service offering.  And then finally the market stage must have a champion from sales or marketing (or both) to ensure that it is properly positioned and prepared for market trials and finally the sales launch.

Without that critical leader at each stage of the process there is little chance of many successful innovations in products or services.  Your innovation engine will quickly run out of gas and go nowhere.  If you pursue any kind of innovation initiative without these key champions any “innovation” that survives will likely be more like minor tweaks or changes, more like continuous improvement than real innovation.  Those small incremental changes are the only things that might survive the process without strong leaders moving them forward.

Business Product, Service, and IT Innovation Series

A structured approach to innovation, to creating new products or services is possible, but it takes a deliberate, concerted and focused effort.  I’ve laid out the various posts on this site that explore how to create a business-centered innovation process:

 

From Collaboration to Innovation to Market – Toward a Working Model
http://www.r3now.com/from-collaboration-to-innovation-to-market-toward-a-working-model

A process oriented approach toward a process model for moving from collaboration to innovation to market. A first pass at integrating collaboration with a structured creative process and moving from idea (conceive) to design (develop) to market (sell).

=========================

Business Strategy and IT Strategy to Reproduce Apple Innovation
http://www.r3now.com/business-strategy-and-it-strategy-to-reproduce-apple-innovation

Overview of Apple Innovation and the focus on Jobs as the head of Apple. The apple innovation secret (if it can be called that at all) is about relentlessly pursuing the customer experience at the point of customer frustration. Where there is customer frustration or customer dissatisfaction there is opportunity for gaining market share for the company who is able to address that point of frustration.

=========================

Striving for a Customer Focused Approach to Innovation 1 of 3
http://www.r3now.com/striving-for-a-customer-focused-approach-to-innovation-1-of-3

Categorizing and Defining the 3 primary types of corporate innovation. I’ve dubbed these as “Stoic” (minimalist or continuous improvement); the “Stretch” (striving for a known future state); and the “Maelstrom” (directionless chaotic storm of ideas). The names you use really don’t matter, but these are the 3 types of what companies call “innovation” that I have seen.

=========================

Striving for a Customer Focused Approach to Innovation 2 of 3
http://www.r3now.com/striving-for-a-customer-focused-approach-to-innovation-2-of-3

Explaining the use of an “innovation narrative” in the “Stretch” type of innovation. This method produces a future state narrative which may not be achievable but provides a customer and market focused direction to aspire to for new products or services. That narrative acts as a future state blueprint for product or service development to move toward.

=========================

Striving for a Customer Focused Approach to Innovation 3 of 3
http://www.r3now.com/striving-for-a-customer-focused-approach-to-innovation-3-of-3

Practical ideas and practical application of some methods of moving toward an innovation culture. Some specific examples around how SAP (the big ERP vendor) has been very successful at integrating their customers, vendors, and their internal organization into an extended development dialog are explored. Includes an overview of how this all ties into the collaboration model I started in a post entitled “From Collaboration to Innovation to Market – Toward a Working Model”.

Good luck on your innovation journey!

Related Posts:

Aligning SAP Scope to Meaningful Business Requirements

April 13th, 2010

ERP or SAP Business Case, CRM, ERP, BI, and IT investment, where is the business benefit?I’m always amazed at how many projects miss one of the most important (and relatively simple) scoping requirements.  The worst part is that projects don’t just miss it but they get it completely backward!

After doing SAP projects since 1994, I still can’t believe SAP’s customers don’t use the old “Seven Habits” step of starting with the end in mind.  What do I mean by that? 

Start your SAP project with REPORTS and BUSINESS requirements! 

Come on now, WHY do so many projects wait until they are live with some new system to figure out what the reporting requirements are?  Reporting requirements must become part of the initial SAP scoping exercise.  Even if it is not spoken, every business that undertakes a massive ERP or IT project like SAP wants actionable information from the system after it is installed.  You want critical information that can enable you to:

  • Make better management decisions
  • Make better financial decisions
  • Determine what products or services have good margins (and which ones don’t)
  • How different product lines or geographies are performing
  • What future business directions you should take based on ACTIONABLE information
  • What competitive pressures in the marketplace to focus on
  • Etc.

Aside from the operational automation and getting business processes defined, reporting is the key for :

  • compliance,
  • operations decisions,
  • sales and product (or service) decisions,
  • and for every part of the business. 

Reporting is so critical to a business yet on almost every project it is treated as an afterthought.  Too often “reporting projects” start after the system is in place and people start working in it.  From a budget and cost perspective you don’t need all of your reports done as soon as the system is installed, but the system must be designed from the beginning to support all of the data needed for those reports.  It must be designed from the start to produce actionable information after the operational and automation components are implemented. 

If you start from the beginning with your reporting requirements you can ensure that the system design addresses any reporting gaps.  By doing this from the beginning you will not have the system installed and then be disappointed that it does not provide you with the key actionable information you need for your business.

Using Reports for Driving Meaningful Business to IT Alignment

Without knowing in advance what the final actionable reporting requirements are you will not be able to take advantage of some of the really great information that a system like SAP can offer.  When an SAP system is properly implemented and constructed SAP provides mountains of data and field options.  There is the ability to add custom fields, re-purpose existing fields [FN1], and add other data dimensions so that you can track and report on any piece of information in any way you can imagine.  However, if this is not planned for in the beginning, and then set up and trained so that you can maintain that data, then after you go live you may be disappointed. 

If you do not do this up front exercise you may discover that you need certain key data requiring expensive rework, expensive customization, and additional time budgeted.  And in the worst case, depending on the system design, you may end up creating a design dilemma causing even more trouble down the road.  Worse still you may discover that the way the system was designed and implemented may prevent you from ever realizing key decision-making information.

There is one other benefit from this approach as well.  By defining end-state reporting needs and end-state actionable information needs you can use this during vendor selection to separate the capable from the incompetent.  The ideal situation would go so far as to provide actual desired end-state reporting examples (field names, field values, etc.).

By doing this exercise you also have the additional benefit of focusing the entire project, right from the beginning, on the end-state goal.  This will help to distill the project down into actual business needs and business requirements for success.

Where to Begin with SAP Scoping and Reporting

Every customer considering an SAP implementation should carefully read through the article on developing an SAP business case (ERP and SAP Business Case for ROI, Business Benefit, and Success, PDF version attached here). 

The key steps to getting the most from your SAP implementation or your SAP scoping exercise is to start with the tools and resources SAP provides free of charge to their customers (and prospects).  There are a couple of tools in particular that every customer, or prospective customer should insist on working with before doing their SAP implementation.  The first is the SAP Solution Composer [FN2], it is a free download and it is a great tool for understanding how to scope your SAP implementation.  As mentioned in the article linked above on developing the SAP business case, it is a great tool for:

  • Developing an initial scope
  • Creating process lists for starting some of the critical change management discussions
  • Communicating in a “new” but common language about the processes.

The next tool available for a high quality project is the ASAP methodology.  It is an active HTML and Java script based repository which contains templates, resources, materials, and a project plan for ensuring you have a successful implementation or upgrade. 

Take Inventory of Your Existing Reporting Landscape and Define Desired Metrics

After your initial SAP scoping exercise it will be important to take an inventory of all of the spreadsheets, databases, and system reports that exist.  From these you can get a good idea of what will need to be accommodated in the system.  And from these existing reports the master data requirements that are required can also be derived.

After gathering the existing reports, begin short duration management workshops to define desired reports.  In other words what has been lacking from the business decision-making process that would provide strategic or tactical insight going forward.  For more information on one reporting and metrics strategy see the posts related to defining and understanding real Key Performance Indicators for business performance (see Why Indexed KPIs are Critical for Business Performance and Success, and Using Key Performance Indicators for Building a Strategy Focused Organization).

Once the initial operational requirements, existing reporting requirements, and desired reporting requirements are defined a final scope and blueprint can then be determined which will propel the business forward strategically into the future.

Conclusion / Summary on

Early Reporting Requirements in SAP Scoping and Blueprinting

In the end I’m still suprirsed at how many organizations finally get around to SAP reporting requirements after the system is already implemented an in place.  Just because you consider and plan for them from the beginning does not mean that you have to complete them by the time the system is in.  On the other hand, you will need them at some point so having the key data and understanding the business drivers for key information is crucial in your SAP implementation.

Too often the reporting metrics, goals, and drivers for business decision-making are treated as an afterthought.  Those reporting metrics and the business goals, key performance indicators, or business direction they represent are generally the reason for the huge investment in new systems to begin with. 

Stop and think about it, how will you ever know if any of the business-centered success criteria was delivered if you don’t have a clear direction in advance?  Those reporting requirements must include current and desired actionable data requirements in some measure of detail.  Certainly as a company and then during the sales cycles the buzz words and generalities of the information end-state are discussed;

  • during the early research,
  • during RFP preparation, and then 
  • during the vendor sales cycles when all of those promises are made about a “future state” for your business. 

Some of the actionable data requirements, or efficiency improvements, or competitive improvements, or other business drivers are also explored during this period.  If they are not captured and distilled into some detail, and then included in your RFP and project charter how will you know if they were ever delivered without defining these critical business justifications for the system to begin with?

One other thing to keep in mind is that no system, no matter how good or how well implemented will change a business by itself, but properly implemented it will provide the actionable information to make sound business decisions for marketplace success (see also SAP as a Change Enabler, Using SAP to Improve Revenue and Profitability, and Change How You Look at SAP to Create ROI).

[FN1] SAP provides a huge number of fields that are never used on most projects.  Some of them are directly tied to application functions and can not be used, still others are not and without doing any custom coding or application changes you can use some of these fields for other purposes.  This “re-purposing” of some fields is a very easy, cost-effective way to solve a number of issues.

[FN2] Go to http://www.sap.com and search for “Solution Composer” (or use this link http://www.sap.com/solutions/businessmaps/composer - retrieved 4/13/2010).

Additional SAP Project Success Reading:

ERP and SAP Business Case for ROI, Business Benefit, and Success

Why SAP Projects Fail to Deliver ROI (and How to Change IT)


Related Posts: