Speed blogging and tips for writing a speed blog post
Photo by Jake Givens.
By Shoaib Sufi, Community Lead
After an hour of discussion on a research software related topic at a workshop, a discussion group would stand up for 2-3 minutes and present back their findings (e.g. problems, solutions, future work or however they chose to speak about a topic). However without context the notes produced from such a session are not of much use to the wider community after the workshop. So, what's the solution?
As well as a discussion, it was my idea that the group should also produce their outputs as blog posts. We trialed this at the Fellows Inaugural meeting in Feb 2016 and Institute Fellow, Melodee Beals coined the term 'speed blogging' which we now use.
Speed blogs can be completed and be publication read during the allotted time at an event or they can be near complete after the event and then tidied up and made ready for publication soon after the event. Thus they are time bound, time sensitive and are a fixed task that does not represent an ongoing commitment. They are a referenceable record of collaboration which gives credit to those involved in writing them. Speed blogging is a method of co-production that can be adapted to produce different styles of writing and other types of outputs (e.g. checklists, diagrams).
Tips for writing collaborative speed blogs
Speed blogs are normally written pieces but you may sometimes choose a different format.
Ideally your speed blog will be a written piece with a picture (max 2) and contain some links and references. In terms of word count you are aiming for between 500 and 1200 words.
In case you want to try something different for you speed blog this is also possible. Perhaps the output from your discussions is better expressed as a table of information, an audio podcast, a video log, a short play or a diagram. These are OK and can count as valid and useful speed blogs, just make sure to include enough context that those who were not at the session can gain from them.
How do you balance thinking about a topic and writing about a topic at the same time?
You don't! Ideally you have a reasonable amount of time for your discussion and speed blogging session. At CW17 we scheduled 1 hour and 30 minutes for the session and that included the write up. You might discuss the topic you have chosen for about half of the time available using your creative, enquiring and brain storming faculties. Then the other half of the time should then be spent trying to bring this all together in your product/construction oriented frame of mind.
If the topic of discussion that you have chosen turns out to be too complex, broad or in depth then you could focus on choosing a sub-topic of the main discussion or reporting on an aspect which you think is particularly interesting or important.
You could also decide to take an iterative approach and have two cycles for exploring and writing to help hone your ideas and clarify your message.
How can you best utilise a team to write together?
Once all the discussions are done you may look through your notes and pull out some of the main themes as well as the context/problem(s) and solution(s)/take home. With this plan in mind you could then assign paragraphs to different team members and write your first set of paragraphs in parallel. As a group you could then come together to review the article and make it more coherent, adding links and references if necessary.
Speed blogging group are ideally 2-6 people in size. In a bigger group you could let some of the people do background on topics that came up while other write and the background folk could act as reviewers.
Templates to help structure your articles and thoughts
Here are two suggested format, they are only suggestions though, you may decide to use them as a basis for you own article and it's fine to use a different approach.
Template 1 - Five important things
You could take a conclusion first oriented approach to your blog and cover:
- What are the five most important things learnt during this discussion
You could also include:
- What are the problems, and are there solutions?
- What further work could be done, and who should do it?
- Are there any useful resources that people should know about?
Template 2 - Summary and related areas
These could include all or some of:
- Why is this issue important?
- Summary of the discussion topic
- Other significant points outside the main topic of discussion
Examples of Speed Blogs
The speed blogging technique has been used by various workshops the Institute has organised and co-organised. Here is a list of some and their speed blog outputs:
- Speed blogs from the Collaborations Workshop 2022 (CW22)
- Speed blogs from the Collaborations Workshop 2021 (CW21)
- Speed blogs from the Collaborations Workshop 2020 (CW20)
- Speed blogs from the Collaborations Workshop 2019 (CW19)
- Speed blogs from the 9th International Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE6.1)
- Speed blogs from Collaborations Workshop 2018 (CW18)
- Speed blogs from the Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE5.1)
- Speed blogs from Collaborations Workshop 2017 (CW17)
Speed blogs used for research
Work done by Daniel S. Katz, Stephan Druskat, Robert Haines, Caroline Jay and Alexander Struck used the speed blogs of WSSSPE5.1 as a date set to analyse in their paper - The State of Sustainable Research Software: Results from the Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE5.1)
Frequently Asked Questions in Research Software
We have a frequently discussed topics in research software page, showing the questions that were discussed at various workshops and their resulting speed blog or blog series. Useful for getting up to speed on a particular question and knowing where to start from for further discussions on the same topic.
Further guidance on contributing to the Software Sustainability Institute website (e.g. blogs and speed blogs) is available.