This is how senior IT architects and CTOs understand change. To me, it's a pretty unusual point of view. It explains the roles and qualities of an architect in a large enterprise, and how to train yourself to achieve those qualities. It includes expert advice on how to explain stuff, draw diagrams, examine architecture, communicate with stakeholders, to name a few.

The book is not about systems architecture.

The writing is superb, it's super easy to read and profound at the same time.

Go and read it if you:

• Think that "Move fast and break things" is not a good idea most of the time. The book explained why and when economies of speed are better than economies of scale.
• Fear code and prefer configuration
• Don't know what to do with black markets inside of your organization
• Don't know how to achieve better software quality by increasing speed