Technology strategy patterns architecture as strategy

Technologists who want their ideas heard, understood, and funded are often told to speak the language of the business, without really knowing what that is. This book's toolkit provides architects, product managers, technology managers, and executives with a shared language, in the form of repea...

Full description

Bibliographic Details
Main Author: Hewitt, Eben
Format: eBook
Language:English
Published: Sebastopol, CA O'Reilly Media, Inc. 2018
Edition:First edition
Subjects:
Online Access:
Collection: O'Reilly - Collection details see MPG.ReNa
LEADER 05598nmm a2200613 u 4500
001 EB001947558
003 EBX01000000000000001110460
005 00000000000000.0
007 cr|||||||||||||||||||||
008 210123 ||| eng
020 |a 9781492040842 
020 |a 9781492040828 
020 |a 1492040843 
050 4 |a HD30.2 
100 1 |a Hewitt, Eben 
245 0 0 |a Technology strategy patterns  |b architecture as strategy  |c Eben Hewitt 
250 |a First edition 
260 |a Sebastopol, CA  |b O'Reilly Media, Inc.  |c 2018 
300 |a 1 online resource 
505 0 |a Includes bibliographical references and index 
505 0 |a Three Concerns of the ArchitectThe Strategist's Role; The Triumvirate: Strategy, Culture, and Execution; Summary; Part II. Creating the Strategy; A Logical Architecture of the Creation Patterns; Chapter 2. Analysis; MECE; Applying MECE Lists; Logic Tree; Diagnostic Logic Tree; Solution Logic Tree; Creating the Tree; Problems Versus Opportunities; Hypothesis; The Five Questions; 1. The Conjunct of Propositions Describing the Problem; 2. The Semantics Characterizing These Propositions; 3. Possible Outcomes; 4. Probability of Each Outcome; 5. Ease and Impact Scoring; Signal and Noise; Context 
505 0 |a Project Heat MapSummary; Part III. Communicating the Strategy; Chapter 7. Approach Patterns; 30-Second Answer; Rented Brain; Ars Rhetorica; Logical Fallacies; Fait Accompli; Facing a Cold Audience; The Meeting Before; Dramatic Structure; Establish the Status Quo; Create an Inciting Incident; The Plan; Shock and Awe; Deconstruction; Three Levels of Problems; Three Causes of Problems; Semiotics: Signs and Symbols; Scopes Without Center; The World as System: Synthetic Decomposition; Scalable Business Machines; Business as System; The Origin Theory; Aspects of the Scalable Business Machine 
505 0 |a Objects and RelationsStrategic Analysis as Machine Learning; Summary; Chapter 3. World Context; PESTEL; Creating the PESTEL; Researching for PESTEL; Applying the PESTEL; Scenario Planning; Steps for Scenario Planning; Futures Funnel; Backcasting; Summary; Chapter 4. Industry Context; SWOT; Porter's Five Forces; Threat of New Entrants; Ease of Substitution; Bargaining Power of Customers; Bargaining Power of Suppliers; Industry Rivalry; Applying the Five Forces; Ansoff Growth Matrix; Summary; Chapter 5. Corporate Context; Stakeholder Alignment; Determining Stakeholders; Determining Drivers 
505 0 |a Stakeholder ListStakeholder Matrix; RACI; Alignment Meetings; Life Cycle Stage; Value Chain; Maximizing Efficiency; Supporting Functions; Applying the Value Chain; Growth-Share Matrix; Core/Innovation Wave; Investment Map; Summary; Chapter 6. Department Context; Principles, Practices, Tools; Principles; Example: NASA Strategy; Current and Future Model; The Principles, Practices, Tools Sankey Diagram; Business Process Mapping; The Law of the Product of Probabilities; Application Portfolio Management; Planning with Asset Classes; Capability Mapping; Business and Technology Attributes 
505 0 |a Cover; Copyright; Table of Contents; Preface; Welcome; Intended Audience; Purpose of the Book; Conventions Used in This Book; Using Code Examples; O'Reilly Safari; How to Contact Us; Acknowledgments; Introduction; This Is Water; Discovering Strategy; Driving Strategy with Patterns; Part I. Context: Architecture and Strategy; The Origins of Patterns; Applying the Patterns; Chapter 1. Architect and Strategist; Business Strategies; Marketing at Michelin; Acquisition and Integration at Oracle; Differentiation at Xerox and Canon; The Architect's Role; Vitruvius and the Principles of Architecture 
653 |a Technologie de l'information / Gestion 
653 |a Strategic planning / http://id.loc.gov/authorities/subjects/sh85128511 
653 |a Information technology / Management / fast 
653 |a Planification stratégique 
653 |a BUSINESS & ECONOMICS / Management Science / bisacsh 
653 |a Strategic planning / fast 
653 |a BUSINESS & ECONOMICS / Management / bisacsh 
653 |a BUSINESS & ECONOMICS / Organizational Behavior / bisacsh 
653 |a Information technology / Management / http://id.loc.gov/authorities/subjects/sh2008006980 
653 |a BUSINESS & ECONOMICS / Industrial Management / bisacsh 
041 0 7 |a eng  |2 ISO 639-2 
989 |b OREILLY  |a O'Reilly 
015 |a GBB8K9924 
776 |z 1492040843 
776 |z 9781492040842 
776 |z 9781492040828 
776 |z 9781492040873 
776 |z 1492040878 
776 |z 1492040827 
856 4 0 |u https://learning.oreilly.com/library/view/~/9781492040866/?ar  |x Verlag  |3 Volltext 
082 0 |a 658 
082 0 |a 658.4038 
082 0 |a 500 
082 0 |a 658.4 
082 0 |a 302.3 
082 0 |a 670 
082 0 |a 300 
082 0 |a 330 
520 |a Technologists who want their ideas heard, understood, and funded are often told to speak the language of the business, without really knowing what that is. This book's toolkit provides architects, product managers, technology managers, and executives with a shared language, in the form of repeatable, practical patterns and templates, to produce great technology strategies. Author Eben Hewitt developed 39 patterns over the course of a decade in his work as CTO, CIO, and Chief Architect for several global tech companies. With these proven tools, you can define, create, elaborate, refine, and communicate your architecture goals, plans, and approach in a way that executives can readily understand, approve, and execute