What Is “Reengineering”?

Wrench clip artHow it Started

Reengineering—sometimes called business process reengineering, or BPR—originated in a 1990 article in the Harvard Business Review by former MIT professor Michael Hammer, who followed up in 1993 with the seminal book Reengineering the Corporation.

The Core of Reengineering

The core of reengineering is a change in organizational structure, in which people who were formerly organized by function (“functional silos”) are instead organized by process or product. That is, all the people who need to work together in a process or product report to the same manager, instead of separate functional managers.  There’s more to it than this, but this is the heart of reengineering.

The Problem with Traditional Organizational Structures

“Functional silos” are at odds with producing a great product quickly and efficiently.  For example, a new product may start out as an idea from Marketing, then Marketing “throws it over the wall” to R&D, which develops technologies to meet Marketing’s idea.  Then R&D throws it over the wall to Engineering, which designs the product.  Then Engineering throws it over the wall to Operations, which figures out how to make it.  Once in production, all the people who need to work together to make the product—line workers, technicians, manufacturing and equipment and industrial engineers—report to separate managers.  There’s not good flow and communication and coordination between all these different functions.  The product suffers.  Delays occur.  A lot of time and money must be expended just coordinating and communicating between departments, who are working on a variety of products and processes at once.

Definition of a Reengineered Organization

All the people who need to work together to produce a great product are in the same organization, receiving the same marching orders from the same boss, and are—ideally—in the same room.  How could this not lead to a smoother, faster product delivery that better satisfies the customer’s needs?

Oftentimes, organizing by product isn’t practical.  For example, a job shop that produces a great variety of low-volume custom products cannot have a separate production area or production team for each product (or even product category).  When organizing by product at a company level cannot be done, organizing by process can bring many of the benefits of reengineering, even on a scale as small as a particular production area in a factory.  That is, everyone working in a particular process—such as a certain production area—reports to a common manager.

An Example of a Traditional Organization

I was in a company that made a product that required about twenty production operations.  One of those production operations had, working within it:

  1. Equipment operators that reported to the production supervisor
  2. Equipment technicians that reported to the maintenance manager
  3. An equipment engineer who reported to the equipment engineering manager
  4. A manufacturing engineer who reported to the manufacturing engineering manager

These are classic functional silos.  All the people who needed to work together to perform the operation effectively and efficiently reported to a variety of different managers with a variety of different priorities, giving their people a variety of different marching orders.  For this reason, problems were very difficult to resolve.  It would be hard to get people to attend improvement meetings because they were more beholden to their bosses and their functions than to a particular operation.  If people were not doing their jobs, one had to go up to their functional managers to try to get it resolved.  The functional manager was often lackadaisical about resolving the problem because this was just one area out of a whole factory that his functional group covered.

An Example of a Reengineered Organization

In contrast, early in my career, I worked at the very successful company Applied Materials, which makes computer-chip-making equipment.  Applied had its manufacturing organized into work cells by process, such as Chamber Assembly, Gas-Panel Assembly, and Final Assembly.  In each of these work cells were assemblers, a manufacturing engineer, and a buyer/planner, all reporting to that cell’s work-cell manager—organized by process, rather than segregated by function.  In my work cell, we would have a weekly process-improvement meeting with all members present.  We would discuss problems and ideas for improvement, decide how to implement them, agree on action items, and boom-boom-boom it would all get done.  If we had been segregated by function, each attempted improvement would have dragged on for weeks or months if it got done at all.  During my work at Applied, the company moved from #7 in its industry to #1, due in part I think to its efficient work-cell-based manufacturing. 

Summary

The heart of reengineering is replacing functional silos with an organization organized by product or process: all people who work on a particular product or in a particular process report to a common manager.

Simitar, Inc. permits republication of all or part of this article, provided that (1) it is attributed to Robert Kotcher of Simitar, Inc., and (2) a link is provided to either the Simitar Home Page (if article is wholly republished) or to this article’s page (if the article is partly republished).

Sign up for free operations-improvement tips



Your information will not be shared with anyone. You may unsubscribe at any time.

Archives of the weekly e-zine are below, in chronological order

Simitar founder

Bob Kotcher

LinkedIn E-mail
Testimonial

loading Loading

    • “At Western Digital, I brought in Bob Kotcher based on his exemplary job performance, project management skills, academic & practical knowledge, and teamwork/communications skills, all of which Bob had repeatedly demonstrated to me when I had the opportunity to work with him prior to Western Digital. Bob brought with him world-class academic credentials and a simply outstanding knowledge of Factory Physics, including Capacity Modeling, Cycle-Time Simulation, and Lean Manufacturing. Bob is a great guy to work with and would be a valued member of any operations staff wanting to improve its productivity and/or lower operating costs. He won’t let you down.”

      Guy Harper – Engineering Projects Director
      Calisolar, Inc.
    • “At MMC, Bob initiated and led numerous cross-functional process improvement teams that made significant improvements to our production. For example, in one area, he linked together several disparate operations into a cell, reducing cycle time and WIP by 97% and saving $220,000 a year in labor and damaged product.”

      John Kim – Director, Thermal Reactor Process Engineering
      Nuvosun
    • “At Headway Technologies, we were planning a major capital investment in an additional photolithography stepper tool in order to improve throughput at this bottleneck. Bob did a Monte Carlo simulation analysis of this area and found something that none of us had suspected. The capacity at this work-center was actually operator-constrained, not machine-constrained. He showed us how, by adding operators, we could meet the required capacity increase. A few additional operators in the photolithography area kept these tools at an optimum utilization and this extra Opex was a small fraction of the capital depreciation that another stepper would have cost.” 

      Guy Harper – Engineering Projects Director
      Calisolar, Inc.
    • “At each company that he works with, [Simitar founder Bob Kotcher] strives to improve day-to-day operations, and thus to improve the bottom line.  Bob is not afraid to present politically unpalatable truths, if his work suggests that a change will lead to overall improvement.”

      Dr. Jennifer Robinson – Chief Operating Officer
      Fabtime, Inc.
Upcoming Events

There are no upcoming events.