Archive

Giants

The Catch-22 of Productivity

What Fuels Top-Performing Software Companies?

The secret sauce of top-performing software companies often lies in their willingness to explore and implement ideas that fall outside the mainstream. Unlike many companies that stick to orthodoxy and status quo practices, these high-performers embrace the works of thinkers like Deming, Ackoff, Buckminster Fuller, Goldratt, Drucker, Seddon, and Trybus. They find value in methods and theories that many businesses either don’t know about or choose to ignore. This approach fosters a culture of continuous improvement and innovative problem-solving, setting them apart from their competitors.

Why Aren’t These Ideas More Widely Adopted?

There’s a paradox here: The ideas from these thought leaders are available, and their effectiveness has been demonstrated, yet few companies make the leap to implement them. This is usually not due to a lack of resources or information but stems from organisational inertia compounded by ignorance. Companies often feel safer sticking to conventional methods, even when evidence suggests that non-mainstream ideas could lead to significant improvements. This risk-averse mentality can create a barrier to adopting transformative approaches.

How Do Beliefs Impact Productivity?

The collective mindset or shared beliefs within an organisation can serve as either a catalyst or an obstacle to productivity. In high-performing software companies, you’ll often find a culture that not only welcomes but also thrives on unconventional wisdom. This creates a fertile ground for out-of-the-box methods to take root and flourish, driving the company forward in ways that more conventional organisations can’t easily replicate. If you’re curious, my recent book “Quintessence” catalogues and maps over seventy of the unorthodox memes of these top-performing companies.

Can We Simply Adopt Another Company’s Methods?

Transplanting methods from one company to another might seem like a straightforward way to boost productivity. However, those methods were developed within a unique ecosystem, shaped by specific challenges, goals, and culture. Attempting to graft them onto an organisation with differing assumptions and beliefs leads to misalignment, cognitive dissonance, resistance from team members, and even failure of the adopted methods to deliver the expected benefits. “Agile” is a classic example in this regard.

Has Benchmarking Any Value Here?

Many companies rely on industry-standard metrics to gauge their performance, but this approach has its limitations, particularly when comparing against top-performers who use unconventional approaches and thus metrics. These high-performers often evaluate success based on measures specifically tailored to their methods and organisational beliefs. This makes traditional benchmarking ineffective and even misleading when trying to measure up to these high-performing companies.

How Do You Close the Productivity Gap?

If you’re looking to close the productivity gap, tweaking existing methods won’t be sufficient. What’s required is a fundamental shift in organisational beliefs and assumptions that pave the way for consideration and implementation of radical, unorthodox ideas. Companies that are willing to examine their own culture critically, and to challenge the industry status quo, stand a much better chance of making significant strides in productivity.

What’s the Cost of Inaction?

Ignoring the widening gap between your company and high-performers comes at a steep price. As these leading companies continue to innovate and improve, companies that stick to conventional methods risk stagnation. In a worst-case scenario, they become increasingly irrelevant in their industry, losing out on both market share and talent to more forward-thinking competitors.

Here’s a video in which the great Russel L. Ackoff explains the difference between knowledge and understanding, and thereby the difference between analytic and synergistic thinking (Cf. Rightshifting and the Marshall Model).

https://deming.org/ackoff-on-systems-thinking-and-management/

 

The Relevance of Giants – 2. O Sensei (Morihei Ueshiba)

On most every occasion when I’m speaking in public – at conferences, workshops, and the like – I tend to mention one or more of my “Giants” of Rightshifting. Men and women who, through their lives and work have contributed significantly to my understanding of work, and in particular to my understanding of effective collaborative knowledge work.

Many folks express interest in these Giants, but I do wonder if they appreciate the relevance of the ideas and experiences of these Giants to their own daily lives at work.

I mean, what relevance does, say, O Sensei have to developers, testers, operations staff and the like? Which aspects of any of these Giants’ work could be useful or helpful or simply comforting to these folks?

In this occasional series of posts I’ll be exploring some of the Giants’ relevance to folks other than theorists, managers, consultants and the like. I’ll be sharing some insights into their work, and specifically, the likely relevance.

With these posts I hope to pique your curiosity just a little. Let’s continue, with this second post in the series, with O Sensei.

O Sensei

Morihei Ueshiba

(December 14, 1883 – April 26, 1969)  (See also: Wikipedia entry)

I’m not going to dwell on his early life and experiences in the Japanese Army, his adventures in Mongolia, nor his experiences in Manchuria and Japan during the time of World War 2.

Aikido

I suggest the primary relevance of O Sensei to most folks working in the field of software development (and production operations) is Aikido – the martial art he developed. Excepting it’s less a martial art, and more a philosophy for life, and for harmonising with others.

Unlike many other martial arts, Aikido is focussed on caring for others, as emphasised by the translation of the three kanji: ai-ki-do as the Way of Unifying Spirit or the Way of Spiritual Harmony. O Sensei envisioned Aikido as an expression of his personal philosophy of universal peace and reconciliation. O Sensei’s goal was to create an art that practitioners could use to defend themselves while also protecting their attacker from injury.

Blending“, one of the core techniques of Aikido, invites us to look at conflicts from the perspectives of the other person – or people – involved. For me, this has a direct connection with empathy – as promoted by e.g. Marshall Rosenberg and others of the nonviolent community.

“Life is growth. If we stop growing, technically and spiritually, we are as good as dead.”

~ Morihei Ueshiba

Where’s the Relevance?

How do we make it more likely that we’re all spending our time on stuff that matters? How do we go about attending to folks’ real needs? I find blending a great asset in identifying with the needs of others. As I blend, I see their perspective, and their needs, more clearly. And in turn, they can feel more listened-to. And choose to reveal other things, crucial things, that means we get to understand more about what matters to us all. With this knowledge – and goodwill – we have a better chance of focusing on what matters, and of reducing the chance of wasting some or all of our time on the inconsequential, on detours, and on dead ends.

Practical Investigation

You might like to join an Aikido dojo, to practice the physical forms of the techniques. And to discuss the philosophy with like-minded people wha have already started the journey. Beware, though, of those dojos and sensei that emphasise the physical forms at the expense of Aikido philosophy.

– Bob

Further Reading

The Life We Are Given ~ Michael Murphy, George Leonard
The Way of Aikido ~ George Leonard
It’s A Lot Like Dancing ~ Terry Dobson

The Relevance of Giants – 1. Deming

On most every occasion when I’m speaking in public – at conferences, workshops, and the like – I tend to mention one or more of my “Giants” of Rightshifting. Men and women who, through their lives and work have contributed significantly to my understanding of work, and in particular to my understanding of effective collaborative knowledge work.

Many folks express interest in these Giants, but I do wonder if they appreciate the relevance of the ideas and experiences of these Giants to their own daily lives at work.

I mean, what relevance does, say, Bill Deming have to developers, testers, operations staff and the like? Which aspects of any of these Giants’ work could be useful or helpful or simply comforting to these folks?

In this occasional series of posts I’ll be exploring some of the Giants’ relevance to folks other than theorists, managers, consultants and the like. I’ll be sharing some insights into their work, and specifically, the likely relevance.

With these posts I hope to pique your curiosity just a little. Let’s start with Bill Deming.

W. Edwards Deming

Bill Deming

(October 14, 1900 – December 20, 1993)  (See also: Wikipedia entry)

I’m not going to dwell on his work in SPC (Statistical Process Control) or SQC (Statistical Quality Control), his pivotal role in the Japanese post-war economic miracle, his 14 Point system of thought he called the “System of Profound Knowledge”, nor his Plan-Do-Study-Act (PDSA) cycle (the latter being the basis for most Agile approaches, btw).

Deming’s 95/5

I suggest the primary relevance of Deming to most folks working in the field of software development (and production operations) is primarily the idea known as “Deming’s 95/5” (although this originated in a quote from Peter Scholtes).

“The fact is that the system that people work in and the interaction with people may account for 90 or 95 percent of performance.”

From my studies of Deming, and from applying his ideas in my practice, I have come to believe that it’s the interactions between people that account for the lions share of “productivity”, “performance” and “success” in collaborative knowledge work. And the “system” a.k.a. the way the works works has a major (hidden) influence on the quality of those relationships, as well as on the work (output, results) of the individual workers.

“Dr. Deming taught me that 95% of the performance of an organization is attributable to the system (processes, technology, work design, regulations, etc.) and [only] 5% is attributable to the individual.”

~ Tripp Babbitt

Where’s the Relevance?

If, like most people, you’re looking for a better quality of life at work, Deming points the way to us improving our relationships with our colleagues, peers and managers. Maybe this perspective is something to consider on those occasions when you’re less than happy in your work, when you’re checked-out, or disengaged, or frustrated.

And Deming’s attribution of 90-95% of your performance to the system within which you’re obliged to work throws a new light on many typical organisational practices such as history-led recruitment, performance appraisals and reviews, stack ranking, criticisms (and praise) for your efforts, etc.. Your results (and self-esteem) may be taking a hit from the effects and constraints inherent in that system, not from anything you’re doing (or not doing) yourself.

Practical Investigation

Deming designed the Red Bead Experiment to illustrate these very points, in a way that most people can directly relate to.

– Bob

Further Reading

Four Days with Dr Deming ~ Latzko and Saunders
95% of performance is governed by the system ~ Vanguard web page