Yesterday I spent the morning at WBMS, in a fascinating workshop run by Quirk Solutions exploring the value of ‘Wargaming’ as a way of testing the resilience of a strategy and related plans before putting them into effect.
Wargaming, as you might imagine, is based on the process developed by the military to evaluate their plans, but that is where any direct connection to anything military ends. If you called the process something else, nothing about it would tell you its origins. And in practice, it is really a somewhat more formalised and disciplined extension of testing approaches which you may well already use to some extent. Where Chis Paton and his team at Quirk really add value is in their in-depth experience of what works, and highly-polished skills for facilitating the process to make it maximally effective.
I took away a number of key ideas for running a good process which I thought it would be worth sharing.
The process is based around two teams: the Blue (plan-owning) Team and the Red (plan-challenging) Team. Although that sounds similar to the common approach of ‘Red Team Review’ for proposal improvement, in this process it is made more effective by asking each Red Team player to represent the views of a major interested party or parties. This makes for a much more engaged and lively process, better bringing out emotive issues. It can also bring out the important potential conflicts between different interests which may otherwise be ‘averaged out’. At least some of the Red Team can be externals – where there are no commercial issues, they could even be the relevant interest groups themselves! – which is clearly likely to help avoid blind spots. Even in a brief exercise, it was clear that the role-playing approach could bring much greater richness to the output.
The process is also iterative: the Blue Team present their outline plan (best not to develop too much detail early, as it is likely to change!); the Red Team make challenges back from their ‘interest’ perspectives; the Blue Team re-work the proposal to address as many of the issues as possible; further challenge, and so on. Clearly in a relatively brief review meeting, there will be very limited time for further analysis or data gathering between iterations, so the objective is not a finished plan, but the best possible framework to take away and work up, together with lists of actions and owners.
That leads me to my final point: While a Red Team Review would normally be looking at a more-or-less finished proposal, the process we tested will add most value early in the process of development. No-one likes to make significant changes to a plan that they have put a lot of effort into, however important, and that may well lead to the smallest adaptation possible, rather than the best.
Thanks WBMS and Quirk for organising a stimulating event!