Wardley Mapping for Tool Selection

Wardley Mapping visualizes value chain components on an evolution axis from Genesis (novel) through Custom Built and Product to Commodity (utility). Different stages require different strategies: Genesis needs in-house experimentation, Custom Built needs build-or-partner decisions, Product stage favors buying best-of-breed, and Commodity favors utility services. Choosing the wrong strategy for the stage wastes resources: building custom for commodity needs and buying commodity for genesis needs are equally wrong. Mapping your tool chain reveals which tools should be built, bought, or rented.

When to use it

When making build-vs-buy decisions. When evaluating a tool stack for over- or under-investment. When planning technology strategy and allocating engineering resources. When a team debates building custom versus using an existing solution.

How it can help

For technology leaders, Wardley Mapping prevents two expensive mistakes: over-building (custom solutions for commodity needs) and over-buying (expecting products for novel problems). List all capabilities, place each on the evolution axis, match strategy to stage. Email? Commodity—use Gmail. Core algorithmic advantage? Genesis—build custom. CRM? Product—buy Salesforce. This saves enormous engineering time by making build-vs-buy systematic rather than political, preventing the common default of building everything custom out of engineering preference.