Eben Hewitt

This book does contain a bunch of good patterns and guidance of what to include in a Technology Strategy and a great starting point for what to include in an Architecture Definition. As a shopping list of things to consider putting in a strategy it is good, but reading through each of them was a bit dry.

I found a good number of patterns that will help to discuss with upper management/strategy members of an organization - with a in-depth focus on what and how to present information to build up a strong strategy model.

MECE, PESTEL, futures funnel and various forms of 2-by-2s are patterns that I'm guessing I will refer back to.

My background is predominantly in RDBMS. I think a bit more discussion and examples of data modeling would have been helpful. Otherwise pretty informative.

My background is predominantly in RDBMS. I think a bit more discussion and examples of data modeling would have been helpful. Otherwise pretty informative.