-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Extend the existing tooltip system to educate and guide new paid leads #55872
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
Comments
Current assignee @anmurali is eligible for the NewFeature assigner, not assigning anyone new. |
|
Triggered auto assignment to Design team member for new feature review - @shawnborton ( |
@shawnborton have you had a chance to review the pre-design? As a next step I think we want to put mockups together and then perhaps make a video to show some user flows through some combination of those tooltips. What do you think? |
I haven't reviewed it too thoroughly yet. Are you able to make a list of the exact flows/mockups you need me to create? |
@shawnborton see below: Format: [shows where the user is] where the tooltip should be pointed: "copy on the tooltip"
Copy is preliminary, we can polish it later. After we make these mockups, can we put together a short video to show progression through tasks? And can we look at tasks with and without an |
Desktop mocks here. @anmurali let's sync in person on this? A walkthrough prototype makes sense as a next step but I am wondering if number 9 above should actually come after 6 instead of at the end? ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
These look pretty nice to me. I'm not in love with the legibility of links in the tooltip and kinda think that they don't make sense as tapping the tooltip is gonna action what it's saying right? So is there now two tap targets on the tooltip? |
Yeah, fair point about legibility there - we can maybe back down the blue a bit?
I guess the problem here is that the tooltip has basically two different things that it's saying:
|
Hmm yeah this is a good point |
Yeah, I kinda think we should ditch the pitch of 2 min tour cause it's already a task and it's already in GC if you haven't used it already. Feels like starting to build links and multiple tap targets into a tooltip becomes too complex |
+1, totally agree. |
Yeah, I think that's the whole point. Anu wanted to explore something like this:
So basically the link is just the last remaining task that exists. I think you make a fair point though, that we have a lot of targets happening within the same tooltip. I don't mind it too much though if I'm being honest, though maybe I am just thinking of things like growls/toasts that have separate links in them as well as a separate close target? Let's see what @anmurali thinks |
Yeah I think the difference to me is that you usually can't also tap on the whole thing to perform another action. But that's just my 2 cents! |
Happy to hear what @anmurali thinks. I kinda think that something as simple as a tooltip shouldn't try to carry too many jobs and it would allow us to simplify the messaging a lot more if we focus on one thing which is kinda what tooltips should be used for. On mobile the tap targets also would be more iffy. |
@shawnborton, @youssef-lr, @anmurali Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Sounds like we're still pausing until the close button is implemented for tooltips. |
@shawnborton, @youssef-lr, @anmurali Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@shawnborton, @youssef-lr, @anmurali Still overdue 6 days?! Let's take care of this! |
What's the latest here @youssef-lr @anmurali ? |
I'm not sure myself. @anmurali @puneetlath are we moving forward with this? |
I believe we're still on hold for the "x" dismissing feature on tooltips to go live. Then the plan is to reassess from there. |
When do we think the "x" dismissing tooltips will go live? Could have sworn I saw a PR for that a while ago? |
amazing! |
@shawnborton, @youssef-lr, @anmurali Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
What's the latest here @anmurali @youssef-lr? |
@shawnborton, @youssef-lr, @anmurali Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
I think we're going to close this for now. See this convo If our confidence in tooltip usage improves after those improvements go live, we will revisit this. |
Uh oh!
There was an error while loading. Please reload this page.
Design Doc
Proposal
Extend the existing tooltip system to new paid leads to guide them toward key product areas and improve engagement during onboarding. (What's Next Post)
Background:
We have a set of onboarding tasks along with a setup specialist to help a new paid lead learn the product and set it up for their company. We have 1000s of paid leads being sent to New Dot per month. 20-30% of leads engage with onboarding tasks or setup specialists.
Problem:
Conversion depends on a paid lead’s engagement with onboarding tasks or their setup specialist. However, only 20-30% of leads engage with one or the other. When leads do not engage, they are left to explore the product independently. Given the complexity and depth of the product, this lack of structured guidance likely results in a higher drop-off rate among the 70-80% of leads who remain disengaged. Additionally, not all users share the same learning style, making it challenging to provide a universally effective onboarding experience.
This creates a significant opportunity to explore alternative approaches to guiding paid leads through the onboarding process, particularly for those who do not engage with existing methods.
Solution:
We already have a tooltip system in place for migrated users to learn the new product. We propose leveraging this system and extending it to new paid leads, guiding them toward key areas of the product that could benefit them. This would allow experimentation with different engagement styles to identify approaches that yield meaningful success over time.
Tasks
#expensify-open-source
[email protected]
and paste in the Proposal[email protected]
(continue the same email chain as before) with the link to your Design Doc#expensify-open-source
to discuss any necessary details in public before filling out the High-level of proposed solution section.[email protected]
again with links to the doc and pre-design conversation in SlackDesignDocReview
label to get the High-level of proposed solution section reviewed#expensify-open-source
to ask for engineering feedback on the technical solution.DesignDocReview
label to this issue[email protected]
one last time to let them know the Design Doc is moving into the implementation phase[email protected]
once everything has been implemented and do a Project Wrap-Up retrospective that provides:The text was updated successfully, but these errors were encountered: