Project Management

So, Who’s Against Quality?

From the Game Theory in Management Blog
by
Modelling Business Decisions and their Consequences

About this Blog

RSS

Recent Posts

George Jetson, Bring Me A Rock!

How To Obstruct A PMO

Rage, Rage Against The Dying Of The Project

Think You Have A Culture Problem? Think Again.

Finally! A GAAP Concept PMs Can Get Behind!

Categories

Game Theory, PMO, Politics, Risk Management, Strategic Management

Date

linkedin twitter facebook Request to reuse this  


It’s easy to laugh at nineteenth century pharmaceutical promoters, also known as snake oil salesmen, who would go to elaborate lengths to convince potential customers of the efficacy of whatever compound or solution they were selling in healing various and sundry ailments. How silly of them to misrepresent their wares so! And how naïve the people who actually spent hard-earned cash to acquire such dubious products! Certainly, people today would never be prone to fall for such tomfoolery, no siree! 

Let’s flash forward to the 21st Century, and the realm of project management which encompasses a plethora of management science hypotheses and theories, many of which are recognized as generally-accepted ways of doing business, with little (or no) empirical evidence to support their validity. Yes, yes, I know that in the business world, it’s virtually impossible to isolate the variables needed to support or overturn any given management science theory. And you know who else knows this? The project management science equivalent of the snake oil salesmen.

I (metaphorically) beat up on the accountants a lot, but that might not be fair – not because their ideas are valid beyond the asset management realm, but because they are not technically part of the PM universe. I also pick on the risk managers a lot, but they’re such easy targets that that might also be considered unfair (is there an equivalent of the “mercy rule” from High School Football for the universe of bloggers? Once an opponent is clearly subdued, are we business writers supposed to ease up on them?).

All of which brings me to the quality guys. I mean, seriously, who could possibly be against quality, as a concept?  Surely these naysayers must be confined to those short-sighted, careless and cheap people who are just out to make the proverbial “quick buck” (a “buck” is one United States Dollar, and not a male deer, for my overseas readers) and hasten out of town before their consumers realize they’ve been had, right?

Well, let’s all take a deep breath, and look at this. What are the quality guys actually selling us? Much of modern-day quality management centers on the performance of specific analysis techniques to help determine the causal factors of the perceived quality issue. This analysis often entails changing the attitudes of the people who actually create the products or services made available to the consumer, and performing an assessment of which processes or personnel are most responsible for any delta between desired scope delivery, and what is actually being delivered.

Okay, so now we’ve left the production room floor, and entered into business analysis territory. How is business analysis performed? With information, of course. What information? Well, one popular technique used by the quality guys is the Ishikawa Diagram, also known as the fishbone diagram. It’s a line intersected by slanted lines above and below it, and on these lines are listed the causal factors that lead to a given perceived problem. In the example listed on Wikipedia 1 , the categories of these causal factors are:
•    Equipment
•    Process 
•    People
•    Materials
•    Environment
•    Management
Most Ishikawa Diagrams will have at least one intersecting line devoted to each category. As I have noted in previous blogs, at the time the Titanic sank, the lookouts had no binoculars, because they were locked in Second Officer David Blair’s locker, and Blair wasn’t on board for the voyage, having disembarked at Southampton without telling anybody where they were 2 . So, this one causal factor falls into which Ishikawa Diagram category, exactly?
•    Equipment, since we’re talking about binoculars.
•    Process, since there should have been a process that required Blair to at least communicate the location of the binoculars.
•    People, since Blair wasn’t aboard.
•    Materials, since the binoculars were locked away behind a panel of wood, which could have (presumably) been demolished by one of the many metal axes on board.
•    Environment, because, of course, the Titanic hit an iceberg.
•    Management, because, well, all of the above.
Could it be, then, that a key commonly-used quality management technique has, in fact, invoked categories of causality that are so blurry that something as simple and straight-forward as some binoculars being locked away can’t fit specifically into one of those categories? And if the categories are thus blurred, doesn’t that at least imply that, in some circumstances, little or no usable information can be gleaned from them on a consistent basis? 

And, to ask just one more uncomfortable rhetorical question, could it be that a few of those organizations that claimed to be suddenly cured after having engaged quality techniques were either not really cured, or were misattributing the cause (ironically) of their improvement?

  1 Retrieved from https://en.wikipedia.org/wiki/Ishikawa_diagram#/media/File:Ishikawa_Fishbone_Diagram.svg on September 19, 2015, 20:25 MDT.
  2 Retrieved from http://nmni.com/titanic/Myth-Memory/Myth/No-binoculars-for-the-lookouts-on-Titanic.aspx on September 19, 2015, 20:21 MDT.
 


Posted on: September 21, 2015 10:12 PM | Permalink

Comments (9)

Please login or join to subscribe to this item
avatar
Arul SP Muthupandian Senior Manager - Operations - IMS| Tech Mahindra Chennai, Tamilnadu, India
Game theory is a good way to improve quality of the deliverables, performance, and projects.

avatar
Prakash Waknis Pune, Maharashtra, India
It''s a dilemma- who is responsible for quality? The book says Quality must be built in and not inspected in. The quality people are not welcome on shop-floor as they point out mistake and thus hindering/stopping production. Quality people say we only hold a mirror in front of you. As always we wake up only when a Titanic sinks (did "pokyoke" exist in 1912?). The recent Volkswagen fiasco is a typical example.

avatar
Thilo Wack Head of Existing Product and Test Lab| optimed Tholey-Hasborn, Germany
I have used Ishikawa on many occasions and actually found it very helpful as a kind of brainstorming tool for hypotheses about a root cause. As, like you mentioned, things tend to come up under different categories, depending on the perspective of team members, there is actually a good chance that you'll identify all possible root causes and not overlook something. In the end it is not important under which category you list your issues but only that they have been uncovered.

avatar
MAEN QADDOURAH Project Director| AJ SAUDI Jeddah, Saudi Arabia
game theory is a good tool.

avatar
Arasudayan Anand Arasappan Product Manager| CRISIL Limited Chennai, Tamil Nadu, India
Most of the times (atleast in the Software industry) the quality folks are too rigid and do not understand the ground level issues that are faced by the development teams. It also the management of few organizations who 'define' quality metrics just for the sake of showcasing. Quality should be tailored according to the requirements in each project is a very important for many to understand.

avatar
John Kendall Lott CEO and President| M POWERED STRATEGIES INC. Washington, Dc, United States
I am going to agree with Thilo. I liked the analysis in the article A LOT, but do not agree with the logic of the conclusion. In fact the article presents the cart before the horse. While I don't know how the specifics of the Titanic and binocular story were unearthed, the value in root cause analysis (which itself is a mechanism underlying quality, and thus disliking it doesn't really speak to the inherent value of "quality" as a management practice, but I digress), is that whatever category it would fall into, that fact that a root cause team would uncover "binoculars" as a problem is what is important...it is a brainstorming technique at its foundation. Indeed, that it could be "uncovered" in multiple traditional (and certainly not the only categories, Wikipedia notwithstanding) gives fishbone analysis a huge boost...we will get to the problem one way or another!

avatar
Prakash Waknis Pune, Maharashtra, India
The binocular theory is not a theory, it is a reality unearthed by a senate inquiry unearthed after the Titanic disaster. There is a complete book on this inquiry. Titanic got its seaworthiness certificate in just one day.

avatar
Michael Hatfield Author / Blogger| Author Albuquerque, Nm, United States
Mr. Waknis -- the "theory" aspect is not whether or not the binoculars were on-board, but whether or not they could have saved the ship had they been in use.

Mr. Lott -- Part of the point I was trying to make had to do with the nature of the fishbone analysis. Is it a structured analytical technique for improving decision-making, or is it an unstructured "brainstorming" method? My perception is that it's presented as the one, and, when called out on it, the QA guys resort to calling it the other.

Good comments on this piece!

avatar
Prakash Waknis Pune, Maharashtra, India

Sir-
If and but is a discussion. The senate inquiry ensured that ALL preventive measures were incorporated. The senator visited "Carapthia" to get a demo of life boats (fully loaded) were lowered in time. Fishbone diagram may or may not be THE technique. At least it helps to put the problems on the table. Next steps include identifying the problem that is most crucial. Quality improvement is a journey.There is NEVER a quick-fix for a problem.

Please Login/Register to leave a comment.

ADVERTISEMENTS

"All you need in this life is ignorance and confidence, and then success is sure."

- Mark Twain

ADVERTISEMENT

Sponsors