Utility IT supports a business function without materially setting the organization apart from competitors. It should work reliably and be good enough for its purpose, but beyond a point, new features bring little benefit. “Utility” is not permission to accept poor quality: unreliable software can still hurt employee productivity or customers. section 10.1
Freight transport
For a transport company, software for loading freight, planning itineraries, and calculating live arrival estimates helped win business and reduce costs. Its invoicing system offered little comparable advantage, so it was treated as utility IT. section 10.1
Treat utility and strategic IT as a range, not a permanent binary label. First ask how a business function differentiates the organization; then ask how much its software contributes to that differentiation. Use a Wardley Map to find candidates for closer examination, not to classify them automatically. A Core Domain Chart offers another view: generic subdomains commonly align with utility IT, while classifications can change over time. section 10.1 section 10.1.2 section 10.5
Match investment to that assessment. Off-the-shelf software may suit a function with little scope to differentiate, often better than customizing it. Spend enough to keep utility IT dependable and costs reasonable; reserve heavier discovery, collaboration, and architectural investment for areas where faster change can improve competitive outcomes. section 10.0 section 10.1.1
