Wardley mapping

Start with three lists: – Users (who) – User needs (what) – Components (to meet those needs) Place components along evolution (Genesis → Custom → Product → Commodity) and position them by visibility (user-facing vs. back-end). The point is to see where to build vs. buy, and to avoid reinventing commodities. Mapping turns vague strategy…

If a component is on the right side of a Wardley map (product/commodity), default to buy unless it’s a differentiator or a constraint. If it’s left (genesis/custom), default to build if it underpins your unique value. Revisit quarterly.