What makes Lessons from History series unique to other books?

The Characteristics of Historical Projects

History shows that most technological developments, or new solutions, are worked out conceptually many years or decades in advance of realization, but can not be fulfilled with the technology of the time.  So the project is literally put aside only to be picked up again when a different emerging technology becomes available. James Burke explored this phenomenon through his “Connections" series.  

For example, the concepts of a programmable computer were worked out by Charles Babbage as early as 1832 but were not transferred into a successful prototype till the end of the 19th century by Hollerith. Both Charles Babbage and Herman Hollerith had remarkably strong business cases to get their mechanical computers completed. These were single purpose built systems that solved particular problems hence the high payback. Although both systems were soundly engineered only Hollerith’s project was completed, as he took a more pragmatic approach with a very specific end goal in sight. He was a more effective project manager. Similarly, today many technology projects are not unique, and have parallels to previously tried projects that used different emerging technologies.

 Taking hard learned lessons from a ”nuts-and-bolts" historical project and   applying these to  today's IT projects cuts away the  layers of  modern jargon and complexity.

There are certain characteristics upon which the series is based:

Characteristic #1 - views historical projects through a modern lens

It looks at historical projects through a modern lens where each chapter reflects one stage of the project (requirements to deployment through 6 stages, and 2 iterations).

Viewing historical projects through this modern lens provides new insights into these projects as most didn't follow any formalized method (this only became widely available after 1945) but a logical evolution.

 
Characteristic #2 - lays out the two projects in parallel

The books intertwine the two project narratives or threads (modern/historical), in alternative paragraphs, throughout each section. This highlights the architects design decisions in the project and insights as to whether they were good or bad.

For example, the layout outlines today’s business situation and IT project (top) vs the historical analogy (bottom). This makes the comparison more immediate and the lesson more obvious.

 
Characteristic #3 - diminishes the complexity of IT solutions

For many businesses today creating complex IT solutions may appear daunting. For example, an adaptive enterprise may seem very complex. However, viewing similar solutions from a previous era should inspire the reader. These solutions were achieved with a less sophisticated (inferior) technology, and less refined techniques and methods.          

For example, a 1940 RAF operations center can be compared to a “real-time information dashboard displaying information aggregated from disparate sources, used for decision making." In reality an on demand solution or part of an adaptive enterprise. Understanding these concepts in a readily familiar (historical) environment increases understanding. 

 
Characteristic #4 - explains IT concepts

It defines concepts such as functional and non-functional requirements in the context of the emerging technology from the past. Looking at a historical project with these concepts increases overall understanding. It then reexamines these concepts in the context of today's emerging technology, to provide further clarity. 

 
Characteristic #5 - explores the rationale behind an emerging technology

It outlines how a solution for solving a problem was first conceived. It then provides the rationale,  justification, and business case for why an emerging technology was initially developed and applied. Each chapter shows how the technology emerged and grew, driven by the business problem. 

For example, it looks at the challenges faced by the project like the availability of technologies and the integration of these, the effort and cost. It outlines the alternatives and the how eventually the project team arrived at the given solution.