Image by Eoneren from iStock

IN THIS SECTION, YOU WILL: Get a summary of several resources on strategy that I use as inspiration for running the Grounded Architecture practice in complex organizations.


There are many definitions of business strategy, but I have found Roger L. Martin the most practical. Martin describes strategy as an integrated set of choices designed to achieve a specific objective. In that view, strategy is not just a plan; it is a decision-making framework that helps an organization move toward a chosen outcome.

For architects, this matters because architecture is most useful when it helps an organization make and execute those choices. This section shifts the book from internal architecture mechanics toward external business direction: where to play, how to win, and what capabilities to build.

In his work, Martin introduces the “Strategy Choice Cascade,” which outlines five critical questions that form the foundation of a robust strategy:

  1. What is our winning aspiration?
  2. Where will we play?
  3. How will we win?
  4. What capabilities must be in place to win?
  5. What management systems are required to ensure the capabilities are in place?

This cascade encourages organizations to make deliberate, connected choices so that each decision reinforces the others and contributes to a coherent strategy.

Martin also emphasizes the importance of making the logic of a strategy explicit. Strategists should state the cause-and-effect relationships they believe will lead to success, together with the assumptions that must hold for the strategy to work. Making that logic visible helps organizations test choices, identify risk, and adapt when conditions change.

Business strategy and IT are tightly connected. Strategy sets direction through goals, priorities, and choices; IT enables execution through systems, processes, and information. Business needs shape technology decisions, while technological change opens new strategic options. That is why architecture must stay close to both.

This relationship is dynamic. New technologies often require new management approaches, operating models, and workflows. Effective alignment depends on integrating business processes with systems, adapting ways of working, and maintaining strong collaboration between business leaders and IT teams. As both evolve, they need continuous realignment.

In thinking about business strategy and IT architecture, I draw on several sources, covered in the follow-up sections:

  • Enterprise Architecture as Strategy: The relationship between business strategy and IT architecture is dynamic and requires continuous realignment, leveraging different operating models, flexibility strategies, and IT maturity stages to maximize efficiency, agility, and strategic value.
  • Outsourcing Strategies: Outsourcing strategies—strategic outsourcing, co-sourcing, and transactional outsourcing—help organizations optimize external partnerships based on business goals, operational needs, and desired control levels, with IT architecture playing a critical role in ensuring integration, governance, and alignment with enterprise objectives.

In the Appendix, I also put my notes on diverse strategy models:

  • Achieving Market Leadership: The Discipline of Market Leaders framework highlights three distinct strategies for market leadership—operational excellence, product leadership, and customer intimacy—each requiring a tailored IT architecture to align technology with business goals, optimize processes, and sustain a competitive edge.
  • Value-Based Strategy: An IT architecture can align technology decisions with value-based business strategy by simplifying IT initiatives, enhancing customer experience, improving employee work conditions, optimizing supplier relationships, and enabling business model shifts to maximize overall value creation.
  • Connecting Marketing, Sales, and Customer Service Strategies: IT architects play a vital role in optimizing marketing, sales, and customer care by integrating technology, data, automation, and security to create seamless customer experiences, improve efficiency, and drive business growth.
  • Culture As a Strategy (aka Culture Eats Strategy for Breakfast): Organizational culture profoundly influences IT architecture by shaping how architects approach collaboration, decision-making, innovation, and technical priorities, requiring alignment between cultural values and architectural strategies for long-term success.

Taken together, these chapters position architecture as a strategic discipline rather than a support function. They show how architects can translate business direction into capabilities, operating choices, and technology decisions without losing sight of execution realities.

Notes on Human Complexity
Notes on Strategy
← →