Replica of a Fokker Dr.1 Triplane in the Deutsches Museum, Munich. A very agile airplane, but not very fast, so by the end of the war, no longer capable of operating inside opponents’ OODA loops.

If you look down through the sweep of history, you might see two broad trends in the concept we call “agility” or “maneuver.” In the military, including the martial arts, people have known that certain practices could disorient opponents, making the physical act of combat much easier to win.  Among these were deception, ambiguity (the “fog of war”), the ability to operate at a rapid tempo, and especially a rapid shift between what the opponent expects and what they experience. The oldest known documentation of these ideas comes from the Sun Tzu text, fragments of which date back to 300 BCE, and they flow like a stream through later Chinese commentators, the Japanese samurai, various schools of the martial arts, the campaigns of Genghis Khan, the German “blitzkrieg,” and on to our day via the works of John Boyd and the US Marine Corps doctrine of maneuver warfare.

Sometime after World War II, in Japan, they jumped the military track and into, of all things, automobile manufacturing.  Known today as “lean manufacturing,” the philosophy and set of practices that began as the Toyota Production System broke longstanding tradeoffs between cost, delivery time, and quality.  Before the TPS, and in US auto manufacturing up until the 1990s, higher quality meant higher costs. The TPS showed that it was possible to build better cars cheaper.

Why is the TPS another manifestation of the principles that underlie maneuver warfare?  For one thing, they both accord a central role to time. Sun Tzu wrote that quickness is the essence of war. Similarly, the TPS stresses the continuous reduction in the time between when a customer places an order and when they receive the vehicle. And as this chart from my keynote illustrates, they both rest on a philosophy that stresses human creativity and initiative:

Both maneuver warfare and lean are mature concepts.  One could argue that all the elements that define maneuver warfare were identified and in place no later than the early 1940s and might even make a case for 1936, when the German Army issued its doctrine for command of troops, the Truppenführung. If you’re interested in the details, Martin van Creveld provides an extensive analysis of the Truppenführung in his book Fighting Power.  These concepts were refined by John Boyd, Bill Lind, and a group of young officers in the Marine Corps beginning in the early 1980s and reached what is essentially their current state with the publication of Marine Corps Doctrine Publication 1, Warfighting in 1989.

Similarly, Taiichi Ohno, one of the prime creators of the system at Toyota, maintained in his book Toyota Production System that the basics of the system were in place by 1973.  In 1979, in response to claims that the Japanese were dumping cars at below cost (nobody could sell a car that good for so little!), MIT began the International Motor Vehicle Program, which documented the system and compiled data that demonstrated its effectiveness. Their results were presented in a number of articles principally in the Harvard Business Review and Sloan Management Review and popularized in the 1990 book, The Machine that Changed the World.  Two of the authors of that work continued to develop the ideas into a more general theory of lean and published them in Lean Thinking (1996).  At about the same time, Allen Ward and his colleagues at the University of Michigan were researching the Toyota Vehicle Development System, which applies the same underlying principles but in quite novel ways. This may be evident from the subtitle of their 1995 paper, “How Delaying Decisions Can Make Better Cars Faster.”

It’s been 20 years since anything significant developed in the world of maneuver, agile, and lean.  My 2004 book, Certain to Win, looked more at the relationships between maneuver and lean. It was the first to point out the common foundation of maneuver and lean, particularly the “human” factors that underly both (by “pumping up creativity …”). It noted that in business, the military concept of grand strategy reduces to “ordinary” strategy. It offered an interpretation of the maneuver concept of cheng / chi that, by focusing on the customer, not the competitor, works for business, too.  Good foundational stuff, but it wasn’t written to divert the lean / maneuver pattern into a new field of application.

So it’s about time that the maneuver stream found a new channel, that it broke out of the worlds of manufacturing and war and over into what we might call “white collar” occupations.  From the quality and intensity of the discussions at LKCE15, building on what I first observed at Lean Software & Systems 2011 in Long Beach, we may be seeing the power of these ideas manifesting in an entirely new area:

Lean kanban incorporates many of the practices associated with classical maneuver / lean theory: managing flow, limiting work-in-process inventory (which can hide problems and distort orientation), and employing an hypothesis-test methodology for learning.  According to the web site of one of its founders (and a keynote speaker at this conference), David Anderson, it also “encourages acts of leadership at all levels.” Depending on how they implement this idea, it could be in harmony with “Pump up the creativity and initiative of everybody …” Because this concept is the real foundation of classical lean and maneuver, I’d need to know more before pronouncing a final judgment.  Looks promising, though.

For more information, check out the conference’s sponsors — there are links down at the bottom of the conference’s home page.