Business Process Reengineering (BPR) – Hammer & Champy (1993)

In 1993, Michael Hammer and James Champy published Reengineering the Corporation: A Manifesto for Business Revolution, one of the most provocative and widely read management books of the 1990s. Defining Business Process Reengineering as “the fundamental rethinking and radical redesign of business processes to achieve dramatic improvements in critical, contemporary measures of performance such as cost, quality, service, and speed,” the framework challenged organizations to abandon incremental improvement in favor of revolutionary change.

Where continuous improvement advocates like Deming counseled steady, incremental gains, Hammer and Champy argued that many organizations faced competitive conditions requiring step-change improvements of 50–300%—improvements that incremental optimization could never deliver within realistic timeframes. Rather than automating existing processes, BPR advocates completely reimagining how work is done, using information technology as the fundamental enabler of radically different organizational designs.

Why Was the Model Created?

Hammer and Champy developed the BPR framework because they observed that many organizations faced a fundamental dilemma. Their existing processes had been designed for different competitive conditions and technological possibilities. For example, manufacturing organizations had designed processes around the constraint that communication between departments was slow and expensive. Finance would batch-process invoices weekly because processing them individually was inefficient. Production made products in large batches because changeovers were costly.

But information technology had eliminated many of these constraints. Communication could be instant and essentially free. Information could be shared in real-time across departments. Systems could process exceptions individually rather than only in batches. Yet despite these technology advances, many organizations continued operating with processes designed for obsolete constraints. They automated existing processes—“paving the cow paths”—rather than reimagining how to work. The result was inefficient organizations using expensive technology to perpetuate inefficient processes.

Hammer and Champy argued that organizations needed to ask fundamental questions: Why do we do this process at all? Why is it structured this way? What would this process look like if we designed it today, using current technology and knowledge? The BPR framework was created to provide a methodology for this fundamental process redesign.

Several contextual forces amplified the need for such a framework:

• Global Competition: By the early 1990s, globalization had created competitive pressures requiring dramatic improvement quickly, not gradual improvement over years.
• IT Strategic Value Debate: For decades, IT managers had argued that information technology could drive strategic value, but executives often viewed IT as a cost center. BPR reframed IT as a fundamental enabler of business transformation.
• Manufacturing Transformation Evidence:Japanese companies’ success through process innovation demonstrated that reimagining how work is done created advantages that continuous improvement alone could not match.
• Limitations of TQM: While Total Quality Management generated significant gains, critics argued that incremental improvement had inherent limits for organizations needing step-change competitive transformation.

Core Concepts and Definitions

The BPR framework rests on several interconnected core concepts that together constitute its distinctive approach to organizational transformation:

Process Focus:Rather than viewing organizations as functional hierarchies (finance, operations, marketing, etc.), BPR views organizations as collections of business processes. A business process is an end-to-end set of activities that delivers value to customers. For example, “order fulfillment” spans from when customers place orders through delivery and billing. Traditional functional organization divides this process among sales (taking order), manufacturing (producing product), logistics (shipping), and finance (billing). BPR integrates these functions around the complete customer-centric process.

Radical Redesign: BPR is fundamentally radical, not incremental. Rather than optimizing existing processes, BPR asks: what would this process look like if we could start from scratch? What steps could be eliminated? What activities could be parallel rather than sequential? What could be centralized that is currently distributed? What decisions could be automated that are currently manual?

Technology as Enabler: Information technology is not applied to existing processes; it is used to enable dramatically different process designs. Advances in databases, telecommunications, user interfaces, and enterprise systems enable process possibilities that were previously impossible.

Dramatic Performance Improvement:BPR aims for dramatic improvements—50–300% gains in cycle time, cost, quality, or service rather than incremental 10–20% improvements. This requires process innovation, not just process optimization.

Customer-Centric Process Design: Processes are designed around customer needs and value, not organizational convenience. If the customer needs a rapid response, the process should provide rapid response. Quality should be built into the process, not inspected in later.

Staff Empowerment: Reengineered processes often involve empowering individual employees or teams to make decisions that previously required management approval. A customer service representative, with information systems providing complete customer history and decision rules, can resolve problems immediately rather than escalating to supervisors.

The framework measures process performance along several dimensions:

• Cycle Time: How long does the process take from initiation to completion? Reengineering typically aims to dramatically reduce cycle time through parallelization and elimination of delays.
• Cost: What is the total cost of delivering the process? BPR aims to reduce cost through eliminating unnecessary steps, automating activities, and improving efficiency.
• Quality: Does the process deliver the intended outcome reliably? Measured through defect rates, error rates, rework requirements, or customer satisfaction.
• Customer Satisfaction: Do customers perceive that the process delivers value? Measured through satisfaction surveys, retention rates, or complaint rates.
• Throughput: How much volume can the process handle? Reengineered processes often increase throughput capacity, allowing growth without proportional cost increases.
• Flexibility: Can the process accommodate variation and exceptions? Reengineered processes often increase flexibility to serve diverse customer needs.

Internal Validity

The BPR framework’s internal validity rests on case evidence and on the logical coherence of its core propositions about the relationship between process structure and organizational performance.

Hammer and Champy drew on consulting experience across multiple industries and documented successful BPR implementations to ground their framework. Key case evidence includes:

• Ford Motor Company redesigned its accounts payable process, eliminating 75% of the department’s headcount by integrating purchasing, receiving, and accounts payable around a single database rather than paper-based matching of documents.
• IBM Credit Corporation reduced its financing approval process from seven days to four hours by replacing a sequential seven-step process with a single generalist equipped with a computer system capable of processing most applications automatically.
• Kodak cut product development time for a new camera by 50% by redesigning the sequential product development process to enable parallel engineering activities supported by shared computer-aided design systems.

These cases demonstrate that the core proposition—that fundamental process redesign enabled by IT can achieve dramatically superior performance—holds across different functional areas and industry contexts. The logical mechanism is clear: sequential processes that exist because of historical constraints (slow communication, limited information sharing, expensive coordination) can be radically compressed when IT eliminates those constraints.

External Validity

BPR has been applied across an extraordinarily diverse range of organizational contexts, providing strong evidence for external validity:

Industries:BPR has been applied to manufacturing, financial services, healthcare, insurance, retail, telecommunications, government, and education. The principles of process-centric redesign apply across industries because the underlying logic—that process structure determines performance—is industry-agnostic.

Process Types:BPR has addressed diverse business processes—order fulfillment, customer service, accounts payable, human resources, product development, and others. The methodology works across process types because the core analytical approach (questioning why processes are structured as they are) is universally applicable.

Geographic Contexts: BPR has been applied in North America, Europe, Asia, and other regions, demonstrating cross-cultural applicability.

Temporal Persistence:BPR was particularly popular in the 1990s–early 2000s, though process redesign thinking continues in contemporary organizations through concepts like Lean, digital transformation, and automation. Federal Express, for example, redesigned customer service through technology, allowing customers to track packages in real-time rather than waiting for phone updates. This improved customer satisfaction while reducing service costs—a pattern consistent with BPR predictions.

The framework’s high failure rates (50–70% of BPR initiatives historically fell short of goals) do not undermine its external validity so much as they clarify the conditions under which it succeeds. Failed implementations typically suffered from insufficient change management, technology dependence without process redesign, or misalignment with organizational culture—all factors the framework itself identifies as critical.

Key Contributions

The Hammer & Champy BPR framework made several enduring contributions to organizational theory and practice:

• Addresses Real Limitations of Continuous Improvement: Continuous improvement has inherent limits on how much improvement is achievable within a fixed process structure. BPR acknowledges this limitation and provides methodology for step-change improvements through fundamental redesign.
• Technology as Strategic Tool: BPR reframes technology from a cost center to a strategic enabler of competitive transformation. This helped executives understand the strategic value of IT investment beyond simple cost reduction.
• Cross-Functional Integration: BPR breaks down silos by organizing around customer-centric processes rather than functions. This improves communication, coordination, and efficiency in ways that functional optimization cannot achieve.
• Practical Implementation Methodology:The framework provides practical steps—mapping, analysis, benchmarking, redesign, pilot, implementation. Organizations understand what to do, not just what to think about.
• Addresses Organizational Urgency: When organizations face competitive crisis or rapid change, incremental improvement feels insufficient. BPR addresses the legitimate need for rapid, dramatic transformation with a coherent framework for pursuing it.

Limitations and Critiques

Despite its contributions, the BPR framework attracted significant criticism, particularly as implementation experiences accumulated:

High Failure Rate: BPR implementations historically had very high failure rates. Implementation complexity, resistance to change, underestimation of required effort, and misalignment between process redesign and organizational culture contributed to failures.

Used as Justification for Layoffs: While BPR advocates claimed improvements would create new employment, in practice BPR implementations were often used as justification for reducing the workforce. This created justified cynicism among employees who viewed BPR as cover for downsizing.

Organizational Trauma: Implementations often required radical changes in how people worked, what skills were needed, and organizational structure. The organizational trauma sometimes exceeded the productivity gains, particularly when change management was insufficient.

Insufficient Change Management: Many BPR implementations underestimated the change management required. Process redesign is technical; change management is social and psychological. When organizations focused on process and technology while minimizing change management investment, adoption suffered significantly.

Overselling Potential: Some BPR advocates made claims about potential improvement that proved unrealistic in many contexts. Overselling benefits created disappointment and backlash when actual results fell short.

Relevance to Technology Adoption

Business Process Reengineering directly addresses organizational technology adoption by insisting that technology implementation without process redesign delivers minimal value. The framework’s central insight—that organizations should not automate existing processes but rather reimagine processes and then determine what technology enables those reimagined processes—remains one of the most important principles in technology adoption research.

BPR highlights a critical technology adoption barrier: organizations that view technology as an enhancement to existing ways of working, rather than as an enabler of fundamentally different ways of working, will consistently underperform their potential. The barrier is not technological capability but rather organizational imagination and willingness to question established process structures.

The framework’s emphasis on measuring dramatic performance improvement (50–300% gains) rather than incremental improvement sets an ambitious standard for technology adoption. This framing helps organizations distinguish between technology implementations that genuinely transform capabilities and those that merely automate the status quo.

BPR’s documented failures are themselves instructive for technology adoption research. They demonstrate that organizational culture, change management capacity, employee engagement, and leadership commitment are often more determinative of adoption outcomes than the quality of the technology or the soundness of the process design. These findings anticipate extensive subsequent research establishing that human and organizational factors consistently explain more variance in technology adoption outcomes than technical factors.

Note: This article provides an overview based on the comprehensive literature review. Readers are encouraged to consult the original publication for complete details.