Tag Archives: interactions

Lessons on Competition from Mother Nature

An interesting short article by Joel Barker with some ideas to think about, Surviving the Fittest: New Lessons on Competition from Mother Nature:

As a result of this emerging body of research, we now must reexamine our competitive paradigm and factor in the new information. It is now clear that ‘the fittest’ not only don’t win all the time, but are only a piece of the more complex system. This information can lead to new strategies for small companies and new insights for the big companies that presently dominate their industries.

The idea that what is winning right now is best is flawed. What is successful now is dependent on the larger system and the conditions that impact that system. In the news the last few days British Airways had to shut down flights worldwide. This has happened numerous times for major airlines in the last few years.

view from a train in Rocky Mountain National Park with tree and snow covered mountains in the background

By John Hunter, see more of my trip to Rocky Mountain National Park.

The systems that they settled on may seem to be working well for years and then suffer catastrophic failures. Why did they accept systems that could fail so completely? Given the frequency it is happening numerous competitors are choosing solutions that are too fragile. And it isn’t just one organization doing it, numerous huge airlines (United, Delta, British Airways, Southwest) have found themselves caught in a situation where they fail to deliver what customers pay for due to so complete a failure of their IT system that they cannot fly any planes many hours in a row.

I suppose this could be evidence that designing an IT system for a huge airline is not something that can be done with the reliability we expect from most things (that the business doesn’t have a day every decade or two where they business just can’t operate that day). But I doubt it. It seems much more likely the existing system creates organizations that are more focused on other things than building a reliable, robust IT infrastructure.

A post I wrote on my Curious Cat Science and Engineering blog a few years ago, 500 Year Floods, looked at the problem of making judgements about unknown systems. The concept of 100 and 500 year floods is to help us make decisions about long term planning and risks. Looking at an area to build a building (or city) can be aided by history and seeing what the area has experienced in the past. But you can’t just assume the future will be the same as the past. Systems change over time. What worked in the past doesn’t necessarily work well in the future.

And as I mentioned in my article, our evidence and understanding also changes (hopefully by us gaining more knowledge and gaining a clearer understanding as we learn more). Thinking systemically takes into account the impact of interactions on results. Results are not independent of the circumstances.

Continue reading

Improving Management with Tools and Knowledge

Too often today I hear people disparaging management tools/concepts (PDSA cycle, mistake proofing, flowcharts, design of experiments, gemba…). The frequently voiced notion is that tools are being applied and not helping improve management in the organization.

But it seems to me using these tools re-enforce the best practices of management improvement. Yes, ignoring the underlying principles (while applying tools and concepts) drastically limits how successful an organization will be in improving management practices (and limits the results the organization will achieve). But using the tools is not the problem. Using the tools is a necessary but not sufficient part of the process to improve.

What is needed is to use the tools with engaged people that are continually learning and adjusting the management system based on their increase understanding of the organization as a system. Using management tools effectively (if you are unsure of what those tools are, read the posts on this blog discussing many management improvement tools) supports gaining insight into the underlying management improvement principles.

It is important to understand there are fundamental concepts that connect and reinforce each other. And those organizations that are successful are using management tools and continually building their understanding of the underlying principles.

Continue reading

George Box Webcast on Statistical Design in Quality Improvement

George Box lecture on Statistical Design in Quality Improvement at the Second International Tampere Conference in Statistics, University of Tampere, Finland (1987).

Early on he shows a graph showing the problems with American cars steady over a 10 years period. Then he overlays the results for Japanese cars which show a steady and significant decline of the same period.

Those who didn’t get to see presentations before power point also get a chance to see old school, hand drawn, overhead slides.

He discusses how to improve the pace of improvement. To start with informative events (events we can learn from) have to be brought to the attention of informed observers. Otherwise only when those events happen to catch the attention of the right observer will we capture knowledge we can use to improve. This results in slow improvement.

A control chart is an example of highlighting that something worth studying happened. The chart will indicate when to pay attention. And we can then improve the pace of improvement.

Next we want to encourage directed experimentation. We intentionally induce informative events and pay close attention while doing so in order to learn.

Every process generates information that can be used to improve it.

He emphasis the point that this isn’t about only manufacturing but it true of any process (drafting, invoicing, computer service, checking into a hospital, booking an airline ticket etc.).

He then discussed an example from a class my father taught and where the students all when to a TV plant outside Chicago to visit. The plant had been run by Motorola. It was sold to a Japanese company that found there was a 146% defect rate (which meant most TVs were taken off the line to be fixed at least once and many twice) – this is just the defect rate before then even get off the line. After 5 years the same plant, with the same American workers but a Japanese management system had reduced the defect rate to 2%. Everyone, including managers, were from the USA they were just using quality improvement methods. We may forget now, but one of the many objections managers gave for why quality improvement wouldn’t work in their company was due to their bad workers (it might work in Japan but not here).

He references how Deming’s 14 points will get management to allow quality improvement to be done by the workforce. Because without management support quality improvement processes can’t be used.

With experimentation we are looking to find clues for what to experiment with next. Experimentation is an iterative process. This is very much the mindset of fast iteration and minimal viable product (say minimal viable experimentation as voiced in 1987).

There is great value in creating iterative processes with fast feedback to those attempting to design and improve. Box and Deming (with rapid turns of the PDSA cycle) and others promoted this 20, 30 and 40 years ago and now we get the same ideas tweaked for startups. The lean startup stuff is as closely related to Box’s ideas of experimentation as an iterative process as it is to anything else.

Related: Ishikawa’s seven quality control tools

He also provided a bit of history that I was not aware of saying the first application of orthogonal arrays (fractional factorial designs) in industry was by Tippett in 1933. And he then mentioned work by Finney in 1945, Plackett and Burman in 1946 and Rao in 1947.