Earlier this year, in a post entitled How to build an architecture of participation, I explained how, in my experience, systems designed for user contribution require the following elements:
- A clear mission
- An invitation to participate
- Easy onboarding
- A modular approach
- Strong leadership
- Ways of working openly and transparently
- Backchannels and watercoolers
- Celebration of milestones
To build on that post, I’d like to explain the kinds of tools and spaces that can create a positive architecture of participation. Please note that, in and of themselves, merely using a tool or creating a space does not guarantee participation. Rather, the tools and spaces help as part of a more holistic approach to encouraging contribution.
When I run projects, as I am doing for Moodle as of this week (more specific details on that in a future post), the following are the kinds of tools I tend to use and the spaces I look to create. It’s worth pointing out that my guiding principle is always the ‘scaffolding’ of people’s attention, and that my mental model for this is influenced by the ‘alternative’ version of the RACI matrix:
Those responsible for the performance of the task. There should be exactly one person with this assignment for each task.
Those who assist completion of the task
Those whose opinions are sought; and with whom there is two-way communication.
Those who are kept up-to-date on progress; and with whom there is one-way communication.
I’ve written before about why you need a single place to point people towards when discussing your project. Not only does it mean a single place for potentially-interested parties to bookmark and remember, but it ensures that the project team only have to perform the administrative duties of updating and curating links once.
Ideally, the URL you give out is a domain that you or your organisation owns, and which points to a server that you, or someone at your organisation, has direct control over. The specific software you choose to run that almost doesn’t matter, as it’s an index — a jumping off point to access spaces where things are actually happening.
Having a canonical URL for the project is useful to everyone in the RACI matrix, from the person responsible for its success, right through to those just being kept informed.
N.B. This is one of the points in Working openly on the web: a manifesto.
Every project needs a flexible, easy-to-update space where the roadmap can be shared, decisions can be recorded, and an overall sense of the project can be gained.
Wikis are perfect for this task, although increasingly there are tools with wiki-like functionality (e.g. revision history, on-the-fly rearrangement of categories) that do the job, too. Ideally, you’re looking for something that allows your project to look good enough to encourage contribution in someone new, while you don’t have to spend ages making everything look pretty.
Again, documentation is useful for everyone involved in the project, whether responsible, assisting, consulted, or informed.
One of the biggest things that people want to know about a project is the current status of its constituent parts. There are lots of ways of doing this, from a straightforward kanban approach, to a much more powerful (but potentially more confusing) ticket/issue-based system. The latter are favoured by those doing software development, as it helps avoid unhelpful ambiguity.
My time at Mozilla convinced me that there’s huge value of having everyone at an organisation, or at least on a particular project, using the same tool for tracking updates. The value of this is that you can see what is in progress, who’s working on it, what’s been completed, any questions/problems that have been raised, and so on.
While the tracker might only be used rarely by those being kept informed of the project, it’s invaluable for those responsible, assisting, or being consulted.
D) Asynchronous reports
Producing regular updates ensures that there is a regular flow of information to all parties. In my experience, it’s ‘out of sight, out of mind’ when it comes to digital projects. You have to keep reminding people that work is ongoing and that progress is being made on the project.
One way to do this is to blog about the project. Another way is to send out a newsletter. There are plenty of ways of doing this, and it’s worth experimenting with differing timescales as to the frequency of updates. While a bit of (appropriate) colour and humour is always appreciated, so is getting to the point as quickly as possible in these updates.
Reports are primarily for the benefit of those being kept informed about the project. It’s worth remembering that these people may, depending on changes in project direction (or their interest/free time), be in a position to assist or be consulted.
A word about social media. Sending out updates via Twitter, Facebook, and the like is great, but I find following the POSSE (Publish Once, Self-Syndicate Everywhere) approach works best. Use social networks for what they’re best at: surfacing and linking to information in a just-in-time fashion. I wouldn’t use them for the actualy content itself.
E) Synchronous meetings
Depending on the size of the project team and the nature of the project, you may decide to run synchronous meetings more or less regularly. You should certainly run some, however, as they afford a different kind of dynamic to asynchronous, text-based approaches.
There are plenty of tools that allow you to have multiple people on a synchronous audio (and/or video) call, ‘dialling-in’ from wherever they are in the world. It goes without saying that you should be mindful of the timezones of potential contributors when scheduling this. You should also all be looking at an agenda that can be updated as the meeting progresses. The project’s documentation area can be used for this, or something like Etherpad (one of my favourite tools!)
What have I missed? I’ve still lots to learn from those more experienced than me, so I’d welcome encouragement, pushback, and any other comments in the section below!
Image by Daniel Funes Fuentes and used under a CC0 license