Technology Strategy Patterns. Architecture as Strategy (Category Strategy)

This week we were selecting a new book to read by our book architecture club at Tinkoff. We had just finished discussing Martin Kleppman’s book Designing Data Intensive Application and wanted to pick something equally interesting. We’ve looked at the different books I’ll talk about in this and next posts.

And I'll start with Eben Hewitt's book "Technology Strategy Patterns: Architecture as Strategy," which I once received at the O'Reilly counter as a visitor to O'Reilly's Software Architecture Conference:) In short, the book is excellent in general, and for me it was also very relevant a couple of years ago:) The bottom line is that the author shares his approaches and patterns on how to be a strategist and architect. He talks about how to create a strategy and how to effectively communicate it to stakeholders at different levels. To do this, the author gives a little less than forty templates, which he describes very briefly and simply. It is funny that many of these templates are dedicated to individual Talmuds, for example. 5 Porter forces:) The book consists of two large parts:

• creating strategy
• communicating strategy The strategy section begins with a chapter on situation analysis, in which the author first talks about the MECE pattern. (Mutually Exclusive, Collectively Exhaustive) The story continues with the story of Logic Tree. (tree) and concludes with a description of the work with hypotheses, in which he gives a brief intro in propositional logic and probability theory:) And then the author also discusses in separate chapters how to work with:
• world context
• industry context
• corporate context
• department context I recommend reading these chapters – they are very interesting. In the part about “communicating strategy”, the author focuses on the patterns and patterns that will allow your strategy to resonate in the hearts and minds of listeners, and you get the help of its implementation in the form of resources. (time, money, people). In general, a very good book to learn new or, as in my case, to structure a long-studied and forgotten old one:) P.S. Attached an illustration with a list of patterns and their relationship, which the author attached to one of the last chapters in which he summarized what was considered. I even have a brief samaree of this book in the form of an article on Medium - bit.ly/TechStrgPatterns

#Software #ExternalReview #Patterns #Strategy #Architecture