With member organisation in 75 countries and around 5000 activist groups worldwide, there is clearly a challenge in finding the right tools for the task. I love matching the right digital tools for different tasks, but the big question is always ”will people use it?”. So the whole process will need to be thoroughly based on user needs and expectations in the organisation.
We decided early on to follow the United Nations backed Principles for Digital Development, as they set a framework that I believe most digital projects should follow, and gives both the client and developers a common understanding of the process.
We also narrowed down the scope to initially focus on a Minimal Viable Product (MVP), both in order to focus on the main objectives and maybe more importantly to be able to involve the stakeholders in testing and evaluation the product as early as possible.
I have worked with (my own take on) a method called Effect Mapping for years, and I find it invaluable for understanding the focus, user groups and user needs in a project. The downside of this and a lot of other methods is however that they only focus on the new product. There is always some old system in the background that we are looking to replace. And the limitations or advantages of that system will always effect the expectations for the new project.
Another limitation in only looking at the current project is missing how it is linked to other systems that the organisation use, and how it enhances or interacts with them.
Thanks to the Development Impact and You Toolkit by Nesta I found this awesome workshop exercise called Evidence Planning.
In a really basic template with five fields, you and the client go through what the Key focus of the project is; how it Enhances current systems; Re-uses stuff that is already in use; which tools to Replace and what the Limits of the project is.
This method can be used for a lot of other cases than digital systems, but I found it really useful to quickly get the full picture of where this project fits into the organisations workflow.
In the case of FoEI, we found that we need to enhance internal systems like an Odoo installation that holds lots of organisational data, and the external web that is recruiting new members. By being the middle ground between these two: not for office workers or complete newbies, but people inside the organisation who wants to get more active.
It will re-use and present all the activities that are happening in groups all over the world and give a chance to share all those stories. And the systems that it is looking to replace are the intranet and it’s document repository, and possibly systems for internal communication, like email lists.
Thanks to this I now have a better grasp of where this project fits in and what the expectations from the organisation might be.
Looking ahead, we will work with User Stories to get all the details about what we want to get out of this, or these, new platforms.