Strategic IT is software whose contribution to a business capability helps an organization differentiate. Utility IT supports necessary work but offers little competitive advantage beyond reliable, good-enough service. The distinction concerns what the software enables, not whether the underlying business function is important. It is a guide to investment, not permission to neglect utility software quality. section 10.1
A transport company
Software for optimizing freight loads and routes, and calculating live arrival estimates, helped a transport company win business, retain customers, and reduce costs. Its invoicing system was treated as utility IT: making it more sophisticated would not have provided the same market advantage. section 10.1
To identify where IT is strategic:
- Start with how each business domain differentiates the organization, then ask how much software contributes to that differentiation. A highly differentiating domain does not, by itself, make its IT strategic. section 10.1.2
- Use a Wardley Map to find candidates, not to assign a final label automatically. Investigate each candidate’s contribution to strategy; early ideas may need research and experimentation before major investment. section 10.1.2
- Use a Core Domain Chart after identifying candidate subdomains to discuss differentiation and complexity. Work with business, product, and technology stakeholders to make the choices explicit. section 10.2.5 section 10.5
Treat architecture as a portfolio rather than modernizing every area equally. Where IT creates differentiation, greater investment may be warranted in discovery, collaboration, skilled teams, domain modeling, code health, and architecture that sustains change. Dependencies that slow strategic IT can be especially costly. In less differentiating areas, simpler solutions, off-the-shelf tools, or outsourcing may be better uses of resources. Revisit these judgments as evidence about business value changes. section 10.0 section 10.1.1
