Should we Blame BPM for a Jobless Recovery?

  • October 19, 2010
  • Scott
  • 3 Comments

Max J. Pucher always writes interesting copy on his blog.  And one of his latest, on BPM and the Jobless Recovery, is no exception:

Well, I propose that it is the efficiency and cost-cutting mindset also employed in BPMS justifications that is a major cause of the ongoing lack of jobs in the US. BPM implementations focused on automating work with flowcharted processes (and excuse me,  the majority are!!!) are only usable for a subset of work – those repeatable, low value, high-volume admin processes that ERP can’t handle. The ROI justification is virtually always about less people needed per revenue!

I’m afraid that BPM isn’t in such common usage as to affect the staffing decisions of the local bakery, the law firm, the ad agencies, and the factory floors, which have all shed quite a few jobs in the US (and, of further note, manufacturing jobs in most countries around the world are in decline, as non-BPMS automation is displacing more and more human workers in the manufacturing process).  And it isn’t relevant as an explanation for the dramatic job losses in construction, real estate, mortgage financing, and other related businesses.  (Moreover, according to the New York Times, Eurozone unemployment was steady at 10% as of May 2010… perhaps the US is more volatile, but at 9.6% it doesn’t seem to be an order of magnitude off).

While I agree with Max’s frustration with companies that are so focused on cost-cutting that they’ve cut bone as well as fat – and I agree that this extreme cost-cutting actually deepened the recession and slowed the recovery (because, in this particular recession, the primary driver has been a reduction in consumer spending, rather than in corporate investment).  But BPM is hardly the reason that home building, mortgage processing, loan origination, and other related fields were hit so hard. Quite simply, there was a bubble in that segment of the US economy that had nothing to do with BPM. The bubble led to over-investment, and the bubble bursting led to dramatic re-valuation and contraction in those sectors.

But there’s more meat to Max’s article, regarding the cost of BPM implementations:

Yes, I totally agree with Jim’s assessment of the complexity and substantial people effort need to get BPMS implemented. Some of the cost is also not process related, but caused by the technology stack being used and the resulting INTEGRATION work. Therefore I propose a consolidated platform rather than integration with others. Businesses who try to integrate existing ECM, BPM, CRM, BRM, E20 and BI suites will never achieve a truly dynamic, adaptive and financially sound BPM.

Not too much to take issue with there. Integration is usually one of the biggest costs… And later:

Because the BPMS skills are expensive and rare they are mostly provided by outside consultants. In effect that means that once the processes are implemented the people who know and understand them move on, leaving the business with unskilled workers and killing the ability to improve or innovate. This is the worst possible business proposition I can think of.

(Max’s emphasis).  Max is blaming the wrong party here.  If businesses are left with unskilled workers, then it is the business that must change – by hiring and retaining talent for improvement and innovation.  Hiring consultants as part of a strategy for change makes sense. But making outside consultants the beginning, middle, and end of a strategy for change is not the answer.  Like *all* human resources applied to projects, consultants will move on.  But so will full-time employees.  It is important to build enough critical mass and momentum in BPM efforts to create sustainable organizational learning that can survive the departure of a key team member(s).

Mainly, however, I disagree with Max’ dark view of BPM:

I hope that Jim is wrong with BPMS adoptions speeding up and that we are rather on the verge of enough people realizing that BPM as a concept that turns people in to process monkeys is a failure.  In the worst case, it won’t just be the ‘jobless recovery’ that is going to crash on top of us, but it will be the inhumane, fully automated, mass-produced, market-segmented, analytically predicted process nonsense that will make even those customers walk away that still have a job.

As I’ve argued many times before, BPM can’t be about turning people into “process monkeys”.  It has to be about removing the mundane, and enabling the real humans in the process to excel.  Once someone’s job has been reduced to “process monkey” it is truly something that will be automated.  The point is to remove the “process monkey” parts via automation and leave the judgment calls behind.

Related Posts
  • November 8, 2018
  • Larry
  • 0 Comments

[Editor’s note: This guest post is the ninth in a series from Larry Taber, BP3’s Digital Strategy Officer ...

  • November 6, 2018
  • Joe
  • 0 Comments

Editor's note: This is a series devoted to the migrations from the IBM Digital Process Automation eclipse base...

  • November 5, 2018
  • Scott
  • 0 Comments

I was really pleased to see Jonathan Huang of Centric writing a review of his experience with Brazos UI Toolki...