A Strategy Deployment Diagram

I came up with an initial diagram to visually summarise Strategy Deployment when I wrote about the dynamics. However, while it showed some of the collaborative elements, I never felt it was sufficient, and still had a hint of hierarchy about it that I didn’t like.

More recently, while reading “Understanding Hoshin Kanri: An Introduction by Greg Watson“, I saw a diagram I liked much more, and was inspired to tweak it to fit my understanding and experience of the approach.

Working from the outside of the picture…

The outer loop shows the people involved and their interactions as a collaboration rather than as a hierarchy. Whilst levels of seniority are represented, these levels describe the nature of decisions being made. Thus the three primary groups are the Leadership Team, Operational Teams and Implementation Teams which reflect the three primary roles in Catchball, and which are responsible for co-creating and owning the various A3 Templates. The bi-directional arrows between these teams show how they collaborate to discover, negotiate and agree on the Outcomes, Plans and Actions. (Note: the original diagram had the arrows only going clockwise, which suggested a directing and reporting dynamic to me).

The three inner circles show the main focuses of each team. The Strategy Team set direction through the True North and Aspirations. The Operational Teams maintain alignment to the intent of the Strategies by making Investments in improvement opportunities. The Implementation Teams have autonomy to realise the strategies by determining and carrying out Tactics and generating Evidence of progress.

The intersections of these circles map onto the three elements of Stephen Bungay’s Directed Opportunism (from his book “The Art of Action”), and they describe the essence of the collaboration between the different groups. The Strategy Team and Operational Teams work together to establish positive Outcomes. The Operational Teams and Implementation Teams work together to define plausible Plans. The Implementation Teams and Strategy Team work together to review the results of the Actions.

Finally, the central intersection of all the circles, and the combination of all of these elements, is a continuous Transformation –  the result of everyone working together with both alignment and autonomy.

Given this visualisation, we can also overlay the three A3 Templates on top, showing which teams have primary responsibility for each.

Like all diagrams, this is a simplification. Its the map, and not the territory. The collaborations are not as separate and clear cut as it might imply. Rather, much of this work is emerging and evolving, collectively and simultaneously. I still believe, however, that it is a useful picture of Strategy Deployment as “any form of organisational improvement in which solutions emerge from the people closest to the problem.”

VN:F [1.9.22_1171]
Rating: 3.0/5 (1 vote cast)

The Kanban Thinking Picture

I’ve recently settled on a visual representation of Kanban Thinking which has been working well. The structure took shape when I realised that Flow, Value and Capability were system impacts. Those are the arrows coming out of the right hand side of the central System. The arrows going into the left hand side are the levers we have to influence the system behaviour; Study, Share, Limit, Sense and Learn. The primary lever is limiting. Studying and sharing provide the transparency and visibility to enable the limits. Sensing and learning give the feedback to evolve the limits.


Feel free to use this picture. I hope it proves useful.

VN:F [1.9.22_1171]
Rating: 5.0/5 (2 votes cast)

A New Lean And Agile Picture

David Harvey posted a brilliant piece on his blog entitled “The Scrum Picture is Wrong”. I highly recommend reading it. His ideas and suggestions for an alternative Scrum picture got me thinking about how to visualise Lean and Agile software development in a process or label agnostic way. David’s picture looked like a figure of eight, and there seemed to be 2 inputs (a vision and reality), and 2 outputs (the product and the team). A quick google found me what I was looking for here – a figure of eight with a bar across the top and bottom. “A time sign that according to Diderot’s Encyclopedia meant hour for the chemists in eighteenth century France”. That seems quite appropriate. An hour would be quite a good interval for a feedback loop 🙂

This is what I came up with. A vision and reality come together to produce a product and a team through process and improvement (and process improvement)

Process Picture

Now I just need to find a good label to stick on it…

VN:F [1.9.22_1171]
Rating: 5.0/5 (2 votes cast)