Get the latest tech news

Rough notes on learning Wardley Mapping

In my ongoing efforts to draft a book on engineering strategy, I’ve finally reached the point where I need to transition “Wardley Mapping” from a topic to consider including into a topic that I either do or do not include. The first step on that line is getting much deeper at understanding how it works. This is rather different than systems modeling, which is a technique I’ve been using off-and-on at work for 15-plus years, but I will make a solid go at it.

It’s also giving me a better sense of what sort of problems Wardley mapping is useful for exploring (and which it isn’t so useful at digging into). There’s also a lot of stuff bundled into Wardley mapping that I think is quite useful, but isn’t as important to me as the components I’ve focused on here. For example, Wardley’s idea of doctrine and gameplay are great, but I generally would approach these sorts of things as “one particular kind of strategy” rather than a different category.

Get the Android app