-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rethink activation experience (onboarding & event ingestion) #2822
Comments
Another relevant piece of information. Watching some session recordings (saw a user attempting to find something around this), I remembered that one of the key reasons we separated "Live" and "Just experimenting" modes in preflight was to speed up the process of getting an instance up and running. We should consider this when revamping this process. |
Some random thoughts to consider: inviting your team members, users Slack invite, #2287, enabling & showcasing session recording on onboarding, after ingestion process, adding more instructions / simple tutorial to key pages (like we have for the actions page). |
* refactor Signup location * personalization route stub * radio buttons base UI * select radio options * continue button * save personalization state * report personalization answers to PH * all data & nicer UI * mark personalization completed on DB * cannot complete personalization twice * rename components * more fixes * undo completed_personalization as per discussion, @macobo's PR coming * fix ts
Co-authored-by: Karl-Aksel Puulmann <[email protected]>
Following (and superseding) #1408, #1504 & #1547, a lot has happened since then. The designs (and assumptions) we had are now a bit outdated. We need to revisit the original designs, and rethink the experience based on the new information we have and the new design strategy.
This will have a huge impact on activation (and therefore retention), as of today, about ~40%+ of our customers don't activate well (retained only the first week).
This issue is intended for ideas, discussion and design feedback. Once we have a draft design, we can move implementation to a separate issue (or PR).
The text was updated successfully, but these errors were encountered: