
It's on the reporting process that I want to focus in this post. We're starting to work with a new partner this week with whom we're doing the design, and will eventually deliver, a two-day workshop at the end of the month. We were asked if we would also write up the report at the end of the meeting. This particular request we had to decline.
Writing up the final report from a workshop or discussion is one of the deep learning opportunities that these kinds of events provide. To externalise this learning to an outside team means that part of the value of the event goes with them when they leave. Quite apart from structuring the report content (much of which is done with a logical workshop design), thinking into the concepts, identifying patterns, unearthing potential contradictions or differences in understanding, can all be used to go back to the team to continue the learning and conversation on the topic. It gives the host or manager (or someone in his/her team) a feeling for the nuances of the discussion that simply reading the report would not necessarily provide. It also puts their fingerprints and style on the report, and the act of synthesizing content and repackaging it into narrative form (like writing a blog post), helps them remember it.
Reporting might seem like a part of the workshop process that you want to outsource, but think again. This parts really embeds the learning so it can be used later, which presumably is one of the reasons to hold the event in the first place!