Thanks for reposting Kevin.
In my mind, we need quantifiable KPIs. In my mind “Ecosystem Impact” in your framework is the one that is most amenable to quantifying. Since the DAO is not in charge of the hackathon and Kernel business lines, we should restrict this to Grants, with an increasing focus on dGrants.
“Interconnectedness” — I’m not sure what metrics this would correspond to.
“Decentralization” — not sure what metrics this would correspond to.
These strike me as operational values, not KPIs — we know we’re only doing things right if we satisfy interconnected decentralization in the process.
With this in mind I’d like to put forward the following high level KPIs that all projects should be aiming to work on. In order to facilitate this, we’ll need support from Gitcoin core product team as well as the dGrants team. CCing @phutchins.
Grants ecosystem impact KPIs
- $ Matching funds raised
- Number of matching pool contributors / funder’s league members
- Number of individual contributors
- Average contribution per project
- Average contribution per contributor
These are high level enough to be broken down into subKPIs that different workstreams/orgs can be responsible for. If we want to expand the mandate here, we might include something like
- Number of individual developers who were able to work on OSS tech full time because of Gitcoin.
Looking for feedback on this!