How we made it happen
Limiting the scope
In the first workshop we worked to limit the scope of the ActionFunder product at MVP phase.
We wanted to really hone in on the core functionality that would deliver the biggest value to users. We established that this was the matchmaking feature, which acts like a virtual ‘funding agent’.
Funders save time by only receiving those applications that the system automatically deems to be right for them based on set criteria.
Managing secondary functionalities
There were two secondary functionalities which we decided not to include in the first release. We planned to leave them until after the product validation stage. The idea was that we would first observe how users reacted to the core product after they’ve been onboarded. We would then manage the other features in the roadmap based on user feedback. There were four distinct user groups defined for the product: the groups seeking funding, the funders, the wider community (offering support), and the internal team managing the funds.