When a user hits Gitcoin, they're immediately bombarded by townsquare and a navigation bar up top that indiscriminately introduces them to the whole product suite of Gitcoin. New folks find this confusing, and returning users have to dig through a dropdown list or URLs in order to find where they're going. From the Gitcoin operator side, we have no idea what that user is on the site for, and serving an entire buffet of products lengthens the "time to value" for a particular user.
[Frank to add data support.]
When a user hits the site, we surface a modal with a list of primary options to classify what they're looking for. Their preference will be logged, and they will have the option to simply change it in the settings, like they do for a funder/contributor designation. This immediately allows us to cohort our users by what stage of the open source journey they're at.
When they return to the site, we can use that simple categorical reference to gently guide them to the correct product within Gitcoin that gives them the highest ROI on value. For example, if I say I'm interested in Grants, then it'll deposit me onto the Grants page after my selection.
Fat Marker Sketch / Example: https://www.figma.com/proto/S7yxF6zdY4BQLi90twugH4/onboarding?node-id=1%3A2&viewport=-527%2C114%2C0.4587502181529999&scaling=min-zoom
From a data perspective, once we have a categorization, it's easy to measure the categorical actions of that user to see if they align with their selection.
How interesting is this problem to our Gitcoin core development team? [Octavio et al to answer.]
A minimal solution can be merged and deployed in [2] weeks time.
The scope of this should encompass:
- determining user categorization
- categorization changes in the settings
- site behavior after categorization selection
- site behavior when a user returns with a categorization.
Scope is subject to change but we ensure that we have a finished iteration at the end of our fixed time period.
- We are not redesigning the navigation bar.
- We are not redesigning the homepage.
- We are not using the categorizations to affect email, yet.
- We are not refactoring the settings page.
- Does this require new technical work we’ve never done before?
- Are we making assumptions about how the parts fit together? Does the pop up keep happening if they don't answer it? What happens if they continuously close the modal?
- Are there any hard decisions we should settle in advance so it doesn’t trip up the engineering team?