<u>WADA and qualitative data</u>
WADA ( West Africa Decentralized Alliance <https://www.wada.org/>) delivers groundbreaking projects in Africa to engage communities with Cardano. These include education and mentoring, community hubs, and engagement with students, entrepreneurs, healthcare workers, developers, and more. Many of the gains of these projects are qualitative as well as quantitative; they include what participants have learned, how included they feel, how confident they feel, how their understanding of Cardano has developed, what the facilitators noticed about how smoothly the project delivery went, and so on.
This kind of information is, naturally, extremely useful to WADA when designing future proposals, and also when developing their overall working methodology and best practice that they can share with Cardano as a whole. WADA is a very well-established organisation within the Cardano ecosystem, and has delivered a wide range of different kinds of project; so their experience is extremely useful to other organisations, particularly those who work in countries that face multiple barriers to participation.
<u>The audit information gap</u>
However, most of Catalyst’s existing audit requirements for funded proposals focus heavily on quantitative measures - numbers of developers, numbers of products, numbers of views. No matter how well-designed those quantitative metrics are, they inevitably miss a lot of crucial information - often, the information that represents the most important learning from the types of projects that WADA does. Although some qualitative information is used in making the final videos required to close out a project, this is essentially a marketing task, and the information that goes into making a video is rarely stored as data that can be interrogated or reused later. Instead, it stays in the heads of the project facilitators, who may not even have the time or resources to share it informally among themselves. Without a clear methodology for collecting it, qualitative and experiential data is not recorded with any consistency; and even when it is recorded informally, there is no system to document or archive it so as to make it discoverable, or to connect it or make it searchable so that patterns can be identified.
As a result, some of WADA’s most important learning about project development and community engagement on the ground is in danger of being lost. Each new WADA project is starting from scratch, other than whatever information teams are able to share informally; the voices and insights of project participants are lost; and this vital knowledge also does not reach the rest of the Cardano ecosystem, to facilitate skill-development for all of us.
<u>WADA needs a system to:</u>
- collect key qualitative data from projects in a way that is not onerous for project facilitators, and which focuses on the most useful and important information;
- archive this information so that it can be found, searched and used (for example, to support proposal-writing, by evidencing that a proposal is addressing the real issues as identified by previous work)
- link information from different projects, so it can be analysed, and so that different WADA projects can learn from each other, and so that an overall “best practice” can be developed, and WADA can grow in an evidence-based way;
- enable others in Catalyst to easily see and understand the insights that have been gathered; this will support WADA to share its expertise and its practice-based learning with the rest of Catalyst so that Catalyst overall can improve.
This proposal seeks to develop such a system, and pilot it with five key WADA funded projects.
<u>We will :</u>
- conduct insight-sharing and problem-sensing with existing WADA funded projects (talking both to facilitators and participants), to uncover what kinds of qualitative data is being missed by current audit processes; and to get a sense of what a WADA project actually *should* record in order to evaluate whether it has been successful
- use the information gathered during problem-sensing to develop a documentation / audit methodology using tools already common in the Catalyst community, such as Miro and GitBook, which will capture and collate both the qualitative AND quantitative data that facilitators and participants consider most important. The methodology will include an archiving workflow, making the data discoverable; and will enable users to search and link information from different projects
- pilot and run this methodology with 5 existing WADA funded projects, to ensure that it is usable, and that it enables facilitators to feed useful data in to project development, learning and best practice development
- share the insights from this process, and the project archive that we have developed, with the Catalyst community as a whole. We will particularly focus on the Funded Proposer and Audit communities, with a view to sharing best practice in auditing proposals that have a community engagement / qualitative focus.
The “Improve and Grow Auditability” challenge focuses on improving audit methodologies for funded proposals. By focusing on praxis and on qualitiative information, this proposal will address some key omissions in the current process, as idnetified by WADA in its projects so far. The learning from this proposal will improve how we, as a Catalyst community, audit proposals, by developing ways to collect a more complete picture of the successes of a project.
- Risk of limited engagement in the problem-sensing process, if project deliverers and participants do not have time. Mitigated by planning with them beforehand to ensure they can plan time for it; and also by paying them a contribution for their input.
- Risk of the methodology not being taken up and used by WADA projects. We will mitigate against this by ensuring it is no more time-consuming or complex than the existing process of monthly reports; and by our project team managing the participating projects’ existing IOG audit requirements for them, i.e. their monthly reports to IOG, leaving them free to focus on the new methodology.
- Risk that we devise a methodology that is unwieldy or unsuitable. Mitigate by a) ensuring that actual WADA projects are consulted at every stage and b) allowing time for iterating, and for going “back to the drawing board” if needs be.