Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency - Tom DeMarco

What is "Slack"?

According to Tom DeMarco, slack is "building capacity to change into the modern enterprise. It looks into the heart of the efficiency-flexibility quandary". He sees a "Hurry Up" mantra driving modern enterprises.

The book is divided into four parts, each with its own theme:
  1. Efficiency has been pursued by sacrificing the ability to change
  2. Effectiveness has been diminished through high organisational stress
  3. Growth requires change and how to make change possible
  4. Risk is inherent i change, and risk can (must) be sensibly managed.

The removal of flexibility - that is, the ability to change - occurred in two ways according to DeMarco:
  1. Flattening of organisational hierarchy through the elimination of middle management
  2. Obsession with making workers "busy".

A critical role of middle management is improvement, yet in modern organisations, fewer middle managers must manage more workers leading to a "steady state, … at the expense of the future". The workers themselves are required to do more for themselves as support roles, such as office assistants, have been eliminated. This leads to task switching and build up of work-in-progress. The result is increased waste and delay.

Organisational stress is a consequence - people try to work faster and work longer days. Excessive meetings take a further toll on the work day. Poor management practice - in the traditional management pursuits of planning, organising, staffing, directing/leading, controlling and improving - have a significant impact on organisational performance.

In the third part, DeMarco discusses familiar topics of vision, leadership, the dangers of fear in the workplace and the necessity of trust in a leader and how that trust is established and maintained, and organisational learning. He returns to the decimation of middle management emphasises their role in "reinvention" and how these middle managers must be able/allowed to work together as a team.

One chapter of Part 3 is devoted to "Quality" and it is here that I found myself disagreeing with DeMarco and feeling he has misunderstood the "quality movement". In essence, he has a narrow view of "quality" - seeing it as a "zero defects" approach at the expense of the "user experience". He must have had bad experiences himself with what he terms the "Corporate Quality Program". A more expansive view of "quality" - such as the Toyota Production System and its dual emphasis on "respect for people" and "continuous improvement" is perfectly consistent with the bulk of
Slack - that's why I enjoyed and recommend this work.

I first read Tom DeMarco's works sometime ago when his books were predominantly on topics related to software engineering and software project management. In Part 4 of this book, he reprises these teachings to an extent, emphasising that risk amazement is "planning for failure" and is critical to successful change.
Although not a long book (220 pages), and although I enjoyed reading it, my view is that tighter editing would have made it a more riveting and inspiring read.

Recommended