Business Process Reengineering

Organizational change

Perhaps the most asked but least answered question in business today is “What can we do to make our business survive and grow?” The world is rapidly changing into something too hard to easily predict, with a hundred opportunities and pitfalls passing by every moment.
To add to this confusion, there are hundreds, if not thousands of techniques, solutions and methods that claim to help business improve productivity, quality and customer satisfaction. A company President, CEO or business owner has so many choices in these buzzwords, whether they be called Total Quality Management, Customer Satisfaction, Re-engineering or Teambuilding. They are like new shoppers in a giant grocery store: They are hungry, but there are so many brands, sizes and varieties you don’t know what to buy.
In response to this confusion, many do nothing, often afraid of making the wrong choices. Others change the techniques they use every few months, using the “program du’jeur” method of organizational change, otherwise known as MBS (Management by Best Seller). Neither of these responses help the organization in the long run. Changing nothing will produce nothing. Implementing a different buzzword (Total Quality, Just in Time, Re-engineering, etc.) every few months often creates a “whipsaw” effect that causes mass confusion among your employees. These buzzwords are often a hammer in search of a nail, techniques applied with no clear focus as to the why, expected results or return on investment.
One of the organizations we consulted with started on this path. Senior management proclaimed in a memo that Total Quality should be a way of life. One senior vice president declared that he wanted 25% of his organization using Total Quality tools within a year. This caused tremendous excitement in the organization, However, the follow-through was delayed, occasionally inappropriate and sometimes not there. Many employee became discouraged with the process and considered it just another management fad. With the next business downturn, virtually all training had stopped and little enthusiasm was left.
Other organizations clearly focus on technical problems and on improving what they had. They are initially successful, but become victims of their own success. I call this an improved, planned incremental approach. Their initial quality improvement teams may be so successful they rapidly create more teams, without the qualitative organization-wide changes (re-engineering) necessary to sustain a permanent effort.
One organization we worked with had over 70 quality improvement teams in a plan with only 300 employees. They had shown little results after their first successes, and asked us what their next steps should be. We suggested the union’s leadership in their efforts, look at restructuring their organization along more product-focused lines, and possibly start profit sharing. They were not interested in taking any of these actions. A few months later, its parent company shut down the site, partly because of its poor productivity.
Organizations need to move beyond the buzzwords into deciding what actions they need to perform that will help them grow and develop. In response to this problem, this article will provide you a framework for coping with organizational change independent of buzzwords or the latest management fad. Organizations must first decide on the framework their organizational change long before they choose a buzzword to implement.
The major decisions
Instead of grasping for the latest technique, I suggest instead that organizations should go through a formal decision-making process that has four major components:
Levels, goals and strategies
Measurement system
Sequence of steps
Implementation and organizational change

The levels of organizational change
Perhaps the most difficult decision to make is at what "level" to start. There are four levels of organizational change:
shaping and anticipating the future (level 1)
defining what business(es) to be in and their "core competencies” (level 2)
reengineering processes (level 3)
incrementally improving processes (level 4)

First let's describe these levels, and then under what circumstances a business should use them.
Level 1- shaping and anticipating the future
At this level, organizations start out with few assumptions about the business itself, what it is "good" at, and what the future will be like.
Management generates alternate "scenarios" of the future, defines opportunities based on these possible futures, assesses its strengths and weaknesses in these scenarios changes its mission, measurement system etc. More information on this is in the next article, "Moving from the Future to your Strategy."
Level 2 - defining what business(es) to be in and their "Core Competencies
Many attempts at strategic planning start at this level, either assuming that 1) the future will be like the past or at least predictable; 2) the future is embodied in the CEO's "vision for the future"; or 3) management doesn't know where else to start; 4) management is too afraid to start at level 1 because of the changes needed to really meet future requirements; or 5) the only mandate they have is to refine what mission already exists.
After a mission has been defined and a SWOT (strengths, weaknesses, opportunities and threats) analysis is completed, an organization can then define its measures, goals, strategies, etc. More information on this is in the next article, "Moving from the Future to your Strategy."
Level 3 - Reengineering (Structurally Changing) Your Processes
Either as an aftermath or consequence of level one or two work or as an independent action, level three work focuses on fundamentally changing how work is accomplished. Rather than focus on modest improvements, reengineering focuses on making major structural changes to everyday with the goal of substantially improving productivity, efficiency, quality or customer satisfaction. To read more about level 3 organizational changes, please see "A Tale of Three Villages."
Level 4 - Incrementally Changing your Processes
Level 4 organizational changes are focusing in making many small changes to existing work processes. Oftentimes organizations put in considerable effort into getting every employee focused on making these small changes, often with considerable effect. Unfortunately, making improvements on how a buggy whip for horse-drawn carriages is made will rarely come up with the idea that buggy whips are no longer necessary because cars have been invented. To read more about level 4 organizational changes and how it compares to level 3, please see "A Tale of Three Villages."

One organization we consulted with has had a more positive experience with the incremental approach. We trained an internal facilitator, helped them deliver training in a just-in-time fashion, and had them focus on specific technical problems. The teams management formed reduced initial quality defects by 48%.
The disadvantages of such an incremental approach include avoiding structural, system-wide problems, and assumes existing processes need modest improvement. In addition, using incremental approaches can be frustrating to employees and management if (pick a buzzword) does not catch on in the organization. As a result of these disadvantages, many organizations experience a high risk of failure in the long run.
What level do I choose?
These levels have much of the same goals: increasing customer satisfaction, doing things right the first time, greater employee productivity, etc. Despite these similarities, they differ substantially in the methods they use to achieve these goals.
Levels one through three, on one hand, focuses on "big picture" elements such as analysis of the marketplace, out-sourcing, purchase/sale of subsidiaries, truly out-of-the box" thinking and substantial change in the management and support systems of the company . In my experience, companies that use these methods tend to have a high need for change, risk-tolerant management, relatively few constraints and have substantial consensus among its management on what to do. Types of industries include those whose environment requires rapid adaptation to fast-moving events: electronics, information systems and telecommunication industries, for example.
Companies using mostly incremental tools (level 4) have management that perceives only a modest need for change, is relatively risk-avoidant, has many constraints on its actions and only has a modest consensus among themselves on what to do. Instead of focusing on new opportunities, they wish to hone and clarify what they already do. Types of industries that often use these methods include the military, aerospace, and until recently, health care organizations. Those organizations whose strategic planning solely focuses on refining an existing mission statement and communicating the paragraph also fall into using incremental (level 4) methods.
When discussing the continuum of structural vs. incremental change, its important to realize that what labels companies use are not important here. One must carefully observe their actions. Many companies have slogans, "glitter" recognition programs and large budgets to provide "awareness" training in the buzzword they are attempting to implement. The key, however, is to note what changes they are really making. If management is mostly filling training slots with disinterested workers and forming a few process improvement teams, they are using level three methods. If they are considering changes in business lines, re-organizing by customer instead of by function, or making major changes in how the everyday employee is being paid, they are using level 3 methods.
Unfortunately, all of this discussion hinges in management's belief about how much change is necessary. This belief often hinges on their often unassessed beliefs of 1) how well the organization performs compared to other organizations (a lack of benchmarking); and 2) what the future will be.
As a result, my recommendation is that organizations conduct scenario/strategic planning exercises (level 1) anyway, even if they have already decided that level 4 (incremental) methods will suffice to solve their problems. This way management can be aware of the limitations of the lower-level methods they are using and realize when it is best to abandon these lower-level methods for something more substantive.
Based on this exercise, comparison of existing internal processes with world-class examples (benchmarking) and market analysis, management may come to realize how much change is necessary. The greater the gap between what the organization needs to be and how it currently operations and what businesses it is in, the more it suggests that greater change is necessary, and greater restructuring is necessary.
This decision is very important. IBM in the mid 1980’s felt that the future would be much like the past and a result didn't have to change much. They did not realize how much microcomputers would replace the functions of their bread-and-butter business, the mainframe. The net result was tens of thousands of people were laid off, with the company suffering the first losses in its history.
Goals
Based on whatever level work you are doing, the opportunities that are found need to be evaluated to determine which of them best suit the existing and future capabilities of the organization and provide the most "bang for the buck" in terms of improvement in your measures of success. In addition, goals need to have the resources and management determination to see to their success.
Goals also need to be SMART, that is:
Specific - concrete action, step-by-step actions needed to make the goal succeed
Measurable - observable results from the goal's accomplishment
Attainable - The goal is both possible and is done at the right time with sufficient attention and resources
Realistic- The probability of success is good, given the resources and attention given it.
Time-bound- The goal is achieved within a specified period of time in a way that takes advantage of the opportunity before it passes you by.

Some examples include:
“We will expand into the polystyrene market within the next five years and achieve 20% market share”
We will decrease the time from research to customer delivery by 50% within two years
We will increase the quality of our largest product by 20% in three years.
Strategies
Where goals focus on what, strategies focus on how. Some examples include:
“We will re-engineer our research and development process”
“We will evaluate and improve our sales and marketing department”
We will conduct a SWOT analysis and then define our core competencies


Additional examples of strategies are included in the "Moving from the Future to your Strategy" chapter.
Wait a second. Aren't goals and strategies really the same. They are in one sense as they both need to be SMART. As what you might guess, the goals of a level are achieved by creating strategies at the lower levels.
The Measurement System
Without measures of success, the organization does not know if it has succeeded in its efforts. Someone once said, “What gets measured gets improved.” Someone else said, “If you don’t know where you are going, any road will get you there.”
For more information on measurement systems and their place in organizational change, please see the "Balanced Scorecard" article, along with a number of articles where employee surveys are used.
Implementation and Organizational Change
The success of any organizational change effort can be summed into an equation:

Success = Measurement X Method X Control X Focused Persistence X Consensus
Like any equation with multiplication, a high value of one variable can compensate for lower levels on other variables. Also like any equation with multiplication, if one variable equals 0, the result is zero.
On employee involvement
Some organizations involve employees right from the start, where they have significant influence in the strategic plan of the organization. This kind of involvement tends to reduce employees’ resistance, which is always a very important factor in the success of any organizational change. Such organizations as Eaton, Eastman Chemical and Rohm and Haas have used such an approach.
Such employee involvement, however, might also be threatening to management’s traditional power. Some organizations decide employee involvement will be limited to implementing the strategic decisions management makes, or further limit involvement to purely task-focused teams working on technical problems. Many aerospace organizations have used this approach.
Focused persistence, good project management and the sequence of implementation
The sequence of implementation is also an important factor. There are four basic options, with many variations of them. The first involves the entire organization from the start, with the whole organization intensively working at once on making the change. Ford Motor Company is currently restructuring its entire organization, moving from planning to implementation in nine months.
Another option is a more relaxed approach, in which divisions or business units of the organization go at their own pace. This option can often become an incremental approach like the first or second village. Many conglomerates or other companies with diverse operations try this approach.
A third option is similar to the previous one, with the focus being on individual business units doing the implementation. In this case, however, business units implement roughly the same things in roughly the same time schedule. Unisys, the computer company, is using this method on some of its organizational change efforts.
A fourth option is to create a pilot project in one division or business unit, learn from its mistakes, and then apply those lessons to the rest of the organization. Examples of this option include the Saturn car facility at General Motors and the Enfield plant of Digital Equipment Corporation. It’s important to note here that creating pilot projects is a high-risk business. In both cases, the lessons learned from these pilot projects have not gained widespread acceptance in their parent companies due to their heavily ingrained cultures.
Business process reengineering (BPR) is, in computer science and management, an approach aiming at improvements by means of elevating efficiency and effectiveness of the business process that exist within and across organizations. The key to BPR is for organizations to look at their business processes from a "clean slate" perspective and determine how they can best construct these processes to improve how they conduct business.


Business process reengineering is also known as BPR, Business Process Redesign, Business Transformation, or Business Process Change Management. Reengineering is a fundamental rethinking and radical redesign of business processes to achieve dramatic improvements in cost, quality, speed, and service. BPR combines a strategy of promoting business innovation with a strategy of making major improvements to business processes so that a company can become a much stronger and more successful competitor in the marketplace.
The main proponents of reengineering were Michael Hammer and James A. Champy. In a series of books including Reengineering the Corporation, Reengineering Management, and The Agenda, they argue that far too much time is wasted passing-on tasks from one department to another. They claim that it is far more efficient to appoint a team who are responsible for all the tasks in the process. In The Agenda they extend the argument to include suppliers, distributors, and other business partners.
Re-engineering is the basis for many recent developments in management. The cross-functional team, for example, has become popular because of the desire to re-engineer separate functional tasks into complete cross-functional processes. Also, many recent management information systems developments aim to integrate a wide number of business functions. Enterprise resource planning, supply chain management, knowledge management systems, groupware and collaborative systems, Human Resource Management Systems and customer relationship management systems all owe a debt to re-engineering theory.

Business process reengineering (BPR) began as a private sector technique to help organizations fundamentally rethink how they do their work in order to dramatically improve customer service, cut operational costs, and become world-class competitors. A key stimulus for reengineering has been the continuing development and deployment of sophisticated information systems and networks. Leading organizations are becoming bolder in using this technology to support innovative business processes, rather than refining current ways of doing work.

Business process reengineering is one approach for redesigning the way work is done to better support the organization's mission and reduce costs. Reengineering starts with a high-level assessment of the organization's mission, strategic goals, and customer needs. Basic questions are asked, such as "Does our mission need to be redefined? Are our strategic goals aligned with our mission? Who are our customers?" An organization may find that it is operating on questionable assumptions, particularly in terms of the wants and needs of its customers. Only after the organization rethinks what it should be doing, does it go on to decide how best to do it.[1]
Within the framework of this basic assessment of mission and goals, reengineering focuses on the organization's business processes--the steps and procedures that govern how resources are used to create products and services that meet the needs of particular customers or markets. As a structured ordering of work steps across time and place, a business process can be decomposed into specific activities, measured, modeled, and improved. It can also be completely redesigned or eliminated altogether. Reengineering identifies, analyzes, and redesigns an organization's core business processes with the aim of achieving dramatic improvements in critical performance measures, such as cost, quality, service, and speed.

Reengineering recognizes that an organization's business processes are usually fragmented into subprocesses and tasks that are carried out by several specialized functional areas within the organization. Often, no one is responsible for the overall performance of the entire process. Reengineering maintains that optimizing the performance of subprocesses can result in some benefits, but cannot yield dramatic improvements if the process itself is fundamentally inefficient and outmoded. For that reason, reengineering focuses on redesigning the process as a whole in order to achieve the greatest possible benefits to the organization and their customers. This drive for realizing dramatic improvements by fundamentally rethinking how the organization's work should be done distinguishes reengineering from process improvement efforts that focus on functional or incremental improvement.

Base on the articles I have read above, I think the most radical type of change in the spectrum of organizational change is the business reengineering or business process reengineering (BPR) which is the fundamental innovation of the business processes. Many companies wants a redesign of the business processes before considering automation or rationalization of procedures. Considering the fast changing environment due to technology-oriented generation, reengineering or changing the design of the company is focused in order to cope up with what is happening around. Reengineering becomes the basis for many development management also because recent management information systems developments wants to integrate a wide number or bigger business functions.


References:
David Chaudron, PhD
http://www.organizedchange.com/decide.htm

http://en.wikipedia.org/wiki/Business_process_reengineering