I’ve put together a new X-Matrix A3 template to go with the Backbriefing and Experiment A3s I published last month. Together, these 3 templates work well together as part of a Strategy Deployment process, although I should reiterate again that the templates alone are not sufficient. A culture of collaboration and learning is also necessary as part of Catchball.
While creating the template I decided to change some of the language on it – mainly because I think it better reflects the intent of each section. However a side-benefit is that it nicely creates a new acronym, TASTE, as follows:
- True North – the orientation which informs what should be done. This is more of a direction and vision than a destination or future state. Decisions should take you towards rather than away from your True North.
- Aspirations – the results we hope to achieve. These are not targets, but should reflect the size of the ambition and the challenge ahead.
- Strategies – the guiding policies that enable us. This is the approach to meeting the aspirations by creating enabling constraints.
- Tactics – the coherent actions we will take. These represent the hypotheses to be tested and the work to be done to implement the strategies in the form of experiments.
- Evidence – the outcomes that indicate progress. These are the leading indicators which provide quick and frequent feedback on whether the tactics are having an impact on meeting the aspirations.
Hence working through these sections collaboratively can lead to being able to TASTE success 🙂
One of the challenges with an X-Matrix template is that there is no right number of items which should populate each section. With that in mind I have gone for what I think is a reasonable upper limit, and I would generally prefer to have fewer items than the template allows.
This version also provides no guidance on how to complete the correlations on the 4 matrices in the corners which create the X (e.g. Strong/Weak, Direct/Indirect, Probable/Possible/Plausible). I will probable come back to that with a future version and/or post.
I’ve been meaning to share a couple of A3 templates that I’ve developed over the last year or so while I’ve been using Strategy Deployment. To paraphrase what I said when I described my thoughts on Kanban Thinking, we need to create more templates, rather than reduce everything down to “common sense” or “good practice”. In other words, the more A3s and Canvases there are, the more variety there is for people to choose from, and hopefully, the more people will think about why they choose one over another. Further, if people can’t find one that’s quite right, I encourage them to develop their own, and then share it so there is even more variety and choice!
Having said that, the value of A3s is always in the conversations and collaborations that take part while populating them. They should be co-created as part of a Catchball process, and not filled in and handed down as instructions.
Here are the two I am making available. Both are used in the context of the X-Matrix Deployment Model. Click on the images to download the pdfs.
This one is heavily inspired by Stephen Bungay’s Art of Action. I use it to charter a team working on a tactical improvement initiative. The sections are:
- Context – why the team has been brought together
- Intent – what the team hopes to achieve
- Higher Intent – how the team’s work helps the business achieve its goals
- Team – who is, or needs to be, on the team
- Boundaries – what the team are or are not allowed to do in their work
- Plan – what the team are going to do to meet their intent, and the higher intent
The idea here is to ensure a tactical team has understood their mission and mission parameters before they move into action. The A3 helps ensure that the team remain aligned to the original strategy that has been deployed to them.
The Plan section naturally leads into the Experiment A3.
This is a more typical A3, but with a bias towards testing the hypotheses that are part of Strategy Deployment. I use this to help tactical teams in defining the experiments for their improvement initiative. The sections are:
- Context – the problem the experiment is trying to solve
- Hypothesis – the premise behind the experiment
- Rationale – the reasons why the experiment is coherent
- Actions – the steps required to run the experiment
- Results – the indicators of whether the experiment has worked or not
- Follow-up – the next steps based on what was learned from the experiment
Note that experiments can (and should) attempt to both prove and disprove a hypothesis to minimise the risk of confirmation bias. And the learning involved should be “safe to fail”.