This doc represents an Outcome, or something that needs to be true to hit a strategic Goal. You can learn more about Outcomes in Backlogs and Roadmaps 101.
Note: this outcome is from Season 15 — it has been combined and reframed in the Season 16 outcome v1 Quadratic Funding Rounds.
Why is this desired outcome potentially important to the business?
A core component of a successful quadratic funding (QF) grants round is community participation — you need to have a pool of people donating to projects to determine how to allocate the matching pool funds. The Grant Explorer and Checkout flows facilitated that public interaction in the cGrants world, but we have yet to build the interface for the protocol. We know that some partners (including our flagship Gitcoin grant program) will want an off-the-shelf contribution front-end for QF rounds, so this is a “table-stakes” outcome to ensure that the base protocol is viable.
The cGrants Explorer and Cart are two of the most-used (and most-criticized) components of the legacy platform. Every community member has to go through those flows, and the hodgepodge of features has created a number of temperamental quirks to the user experience. In order to take advantage of our greenfield opportunity, we want to ground development of the new QF front-end in user-based first principles, instead of attempting to copy/paste the existing experience onto the protocol.
To get to those first principles, we conducted a round of user interviews and reviewed past feedback channels to synthesize key themes.
S15: Grant Explorer Usability Testing Synthesis
There are common themes that users want a clean browsing experience and more insightful project recommendations, but there are still open questions around how much of that is rooted in the past gitcoin.co experience and how to tease out core user needs. Given discussions with our design partners, we are opting to focus on delivering a simple browse and vote experience for our October rounds while continuing to research deeper browsing and recommendation requirements.