Digital Anatomy

Once we’ve done the work to understand our value chain, map it to evolution, and evaluate how context and doctrine bring clarity, it is time to decide what actions we should take (if any). The great thing about having a map is that, in additions to patterns of doctrine and context, there…

Up until now, we have been stepping through Simon Wardley’s brilliant work on Wardley Mapping (https://medium.com/wardleymaps). We’ve looked at a basic value chain for “real time business automation”, applied that value chain to a Wardley map to see both position and…

This post is a continuation of a process that I started in previous posts, including The Data Flow Value Chain and A Simple Wardley Map of Data Flow. If you haven’t been following the series, please take the time to read those posts first.

Last week I demonstrated the process for defining a “simple” value chain for “real time business automation”, which is my code phrase for stream processing in a business setting. This week, I want to turn my attention to building a Wardley Map from that value chain so…

In my last post, I highlighted the basic architecture of data flow, describing the “50 thousand foot view” of what data flow is from a technology perspective. I started with this, in part, because the core model (known by many as “stream processing”) is increasingly well understood…