The original version of this post first appeared on the Trellis blog. This is a revised version with some additions.
Last May, I attended was the 4-day Science of Team Science conference where the focus was on what we can learn about collaboration within science.
The opening workshop was a grounding in the fundamentals of team science – including discussing the pitfalls of team-based projects and how to communicate effectively when team members may come from diverse specialisms with their own sets of jargon and beliefs.
I particularly enjoyed Kara Hall’s 10 steps to consider when planning a team – which listed everything from assessing whether you have the technology in place to get your collaborative work done, to whether you have clearly outlined conflict resolution strategies if things go wrong.
I’ve captured the tweets from the session (mostly me, I’m afraid) in this Storify.
Kara initially had 6 things to consider when deciding whether a team-based approach was appropriate:
- Identify a unifying, over-arching problem, then:
- Identify smaller projects that help accomplish the aim.
- Carefully compose sub-project teams with requisite expertise (big teams get unwieldly).
- Aim to create balanced representation within team – include boundary spanners to bridge between sub-projects.
- Informal and formal leaders exist in every team – discuss explicitly and make roles and responsibilities clear.
- Not everyone can play nice within a team collaboration – consider whether better not to include them.
Later in the same session, she listed 10 items to consider as part of a “collaboration pre-nup” that would help ensure that any subsequent teamwork went smoothly:
- The rationale for a team approach to the problem – and what configuration to use (see above for thoughts on sub-projects for specific tasks)
- Are the individuals, team as a unit, and organisations involved all “collaboration ready“? What past history is there?
- Is the team “technologically ready” for a collaborative project – do they have communication tools and data sharing tools set up?
- How will the team function? Will it use a “co-creation” approach to working together on the problem?
- How will communication between team members occur? What does collaboration look like in this team?
- What about leadership and management of the team’s processes? What will this look like?
- What about conflict resolution? Discuss this upfront in case problems arise with working together.
- Create a training plan for team members throughout the various stages of the project.
- How will you ensure quality control throughout the project – and that standards continue to improve based on learnings?
- What about funding and budget management for the team – what resources for the project are there?
Does this list of 10 considerations reflect how you’ve organised any of your own team-based projects – and/or do you wish you’d seen it earlier? Do you think these pointers apply when managing solely online communities too?