This episode is brought to you by the Cloud Wars Expo. This in-person event will be held from June 28th to 30th at the Moscone Center in San Francisco, California.
00:17 — The term “reengineering” is frequently misunderstood to mean downsizing or cutting people. Originally, reengineering appeared in a 1990 article by Michael Hammer titled “Reengineering Work: Don’t Automate, Obliterate.”
01:00 — The article proposed identifying and eliminating steps within processes that don’t belong. Wayne relates an example of Ford using 500 people for invoice match and payment reconciliation compared to Mazda needing just five.
01:40 — Mazda removed steps in its process that either didn’t provide value commensurate with the associated cost or didn’t control risk commensurate with the amount of process work.
02:11 — Before heading to a CIO for automating a process, organizations need to evaluate the detailed costs and values connected to each step in its process.
02:45 — The work of digital automation should begin only when a process is reduced to its most efficient form.
Want more tech insights for the top execs? Subscribe to the CXO channel: