Hi all – I recently posted an update to our roadmap based on GG18 feedback. You can see that GG18 feedback here on the forum (Grants Stack Product Reflections: GG18) and on Twitter (https://twitter.com/MegLister/status/1697326744544616602). The Twitter thread to accompany this post is here: https://twitter.com/MegLister/status/1708832178333970532 
First, a few things we’ve been up to since GG18!
- We’ve been supporting community-led rounds by launching Grants Stack on Polygon, Arbitrum, and Avalanche. Arbitrum is just wrapping up 4 Quadratic Funding rounds on Grants Stack, and Polygon and Avalanche have plans to launch QF rounds within the next month!
- We launched Direct Grants, a new feature that allows grants managers to allocate funds directly to projects. You can view a demo of that feature here: Loom | Free Screen & Video Recording Software | Loom
- We resolved some persistent bugs in our build process and upgraded our front-end deployment system from Fleek to Vercel, enabling us to ship faster
- In the coming days, you can expect to see us ship Matching Estimates – a favorite feature from the old platform that estimates how much matching power individual donations might have!
To address GG18-specific feedback, we summarized all of the pain points and loosely ideated features we could build to address those. We then prioritized those features by impact, feasibility and readiness.
- Impact: will this accelerate Grants Stack adoption?
- Feasibility: level of effort + do we have all of the tools and skills we need to do this?
- Readiness: are we confident in the viability of our product solution?
As you can see, Passport and Explorer features rose to the top!
This week we’ll kick off creating a sliding scale for Passport, so that donations that don’t reach >20 can still be eligible for some matching funds. Wou can also expect to see Explorer homepage redesigns rolled out for GG19. We’re particularly excited about new sort/filter options and community-curated collections!
Preview of those designs:
Unfortunately, we’re not going to be able to fix the edit application flow or in-product accept/reject rationale for GG19. I know that the edit application flow is particularly painful and sucks!! We will fix it in the future, but we need more time and thought behind the architecture.
Luckily, our awesome PGF team is working on some automated accept/reject rationale messaging outside of the product that should hopefully ease pain around timeliness and transparency of those decisions.
As always, our roadmap is public, my DMs are open, and would love to hear thoughts/feedback/etc!
(maybe it’s even possible atm…idk)