Mapping is definitely a qualitative and often subjective process! There is never one correct map, there are only useful maps. I think the key takeaways from th

Mapping is definitely a qualitative and often subjective process! There is never one correct map, there are only useful maps. I think the key takeaways from the post are: 1. Always anchor discussions in user needs 2. Analyze crypto in the context of the broader economy 3. Plan for evolution 4. Wardley maps are really helpful at all of the above I've also written a follow up post detailing some of the strategic mistakes cryptocurrency projects make and how they can be avoided using maps: https://agost.blog/2019/06/mapping-crypto-common-pitfalls/ https://agost.blog/2019/06/mapping-crypto-common-pitfalls/ Edit: I'm not familiar with applying mapping for security, but these look like some good resources: https://community.wardleymaps.com/t/tackling-security-with-wardley-maps/76/3 https://community.wardleymaps.com/t/tackling-security-with-w...