Archive for June, 2012

Quality as the driver at the edge

Wednesday, June 20th, 2012

by Philip Boxer BSc MBA PhD

Much has been said on the subject of quality, including its tendency to focus on the quality of outputs rather than on the quality of outcome for the user of those outputs.1 See, for example, ‘Quality Management Gets Strategic and Discovers (Gasp!) The Customer‘.  The figure below approaches quality in a way that relates back to the challenges of working at the edge, of describing what-is-going-on at the edge in terms of 4 quadrants, and of addressing the limitations on quality created by a low strategy ceiling.2

The horizontal line represents the way primary task is defined, and the vertical line represents the way primary risk is defined.3 This gives us a way of distinguishing 4 types of Quality, each one built on the foundations of the one before:

  • Type I – the behaviour conforms to its contractual specification e.g. we delivered it in the time window we said we would.
  • Type II – the behaviour serves the supplier’s purpose in what it delivers e.g. we delivered it in a time window that fitted the urgency you were prepared to pay for.
  • Type III – the behaviour serves the user’s purpose in how it is delivered e.g. we installed it and ensured it was working as you expected within your environment.
  • Type IV – the behaviour continues to serve the user’s purpose over time through being adapted to the user’s changing needs e.g. we monitored its performance and modified what it was doing as your needs changed.

Using the rcKP language, the behaviours on the left are r-type and c-type, being at best customizable in ways that serve the supplier’s purpose.  In contrast, the behaviours on the right are K-type and P-type, being concerned with aligning performance to the current and/or evolving nature of the user’s situation.  Quality on the left can be defined largely independently of the context-of-use, while quality on the right cannot.

[1] A distinction can usefully be made between consumer, customer and client that speaks of increasing involvement with an active user’s context-of-use.
[2] The point being the lower the strategy ceiling, the fewer of the quadrants are judged to be relevant to quality, arms-length contracting restricting quality to the type I fulfillment of a contract to deliver.
[3] These definitions are implicit in the behaviour of an enterprise within the context of its domain of relevance, and reflect the way its managers’ identities are supported by those behaviours.