Technology Strategy Patterns: Architecture as Strategy

From the Preface

The book has two aims. The first is to help architects, product managers, and executives at technology companies or in technology organizations who are charged with producing technology strategies. This stuff works across industries. My hope is that with these practical tools and guidance, your strategies will be deeper, stronger, and clearer, and you’ll get approval, support, and funding to make your ideas a reality. The primary assumption of the book is that you’re in technology management of some kind, or want to be, and want to think more holistically and incisively about your technical roadmaps. The second aim is to help you in your career. I suppose an alternate, but less becoming, title for this book could be How to Become the CTO.

Whether you are a senior developer, enterprise architect, or CTO, or have never read a line of code in your life, I know you’ll find something useful, and feel welcome and at home here.

This book is for anyone in information technology who wants to do more strategic, relevant, important work for their organizations. Therefore, there is no code in the book, and nothing too technical. People who will get the most out of it include.

• Architects
• Principal developers or tech leads who wish to become architects
• Technology managers in engineering, testing, and analysis, whether on the product development side or the IT back office
• Product managers
• Project and portfolio managers
• Business consultants
• Technology executives
• Strategy analysts and managers
• Anyone interested in strategy, architecture, and leadership