The second half starts with an external input. I already wrote two blog posts about providing input as such. This time, the input will be text-based. As mentioned earlier, I like using hbr.org as a source for articles – they are informative, well-written and can easily be understood even if you’re not into all that management talk. For my topic of moving to agile collaboration, I found an article which in general fits this topic quite well: Agile at Scale. It is about scaling up agile teams in companies, and mentions many differences between traditional collaboration and the agile framework.
In our example workshop, I decided to go for a discussion as the input. As the topic is collaboration an possible improvements, there is no larger need for any input as the starting point. On the contrary – imagine being invited to a workshop to reflect on your collaboration practices, and the first thing you are presented with is a theoretical text about collaboration at work. Wouldn’t this feel like a punch in the face? It’s like saying Well, nice of you to be here, let’s look at what you did wrong your whole career… and nobody likes that!
Giving your team a text to read is a very common and handy approach to providing input. There are more than enough texts on the internet! Preparing a text as an input is quite easy and does not require much work – however, you should do your prep! Otherwise you’ll possibly end up with many lose ends and open questions during the workshop.