Highlight new instance at conclusion of product tour

[gstout52]

Description

About half of new users cancel the product tour.

To ensure that users reach the final activation step in product, when a user cancels the product tour, start a new single-item "tour" that highlights the Open Editor button on the automatically-created instance, and says: "Get started building with Node-RED here" (or similar).

Epic/Story

No response

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

[joepavitt]

Feel like we are missing a key metric in this issue which is how many people open the editor? Especially then broken down by those that cancel the tour and those that completed it. If there is a difference, then we have merit in doing this, if it's the same, then the highlighting of the "Open Editor" button will be irrelevant.

[joepavitt]

We do actually have an issue whereby the product tour currently assumes you're on the Applications page though, which is no longer the case with our new landing page... that does need addressing...

[gstout52]

This chart shows the funnel from signup to open editor, broken down by completion step for the product tour. Users who cancel the tour at the start open the editor 7 percentage points less than users who do more than half of the tour or all of it. (Funny enough, users who did some of the tour but less than half of it opened the editor 100% of the time - but there were only 5 such users, polluting the chart.)

https://eu.posthog.com/project/2209/insights/67lAxmhU

[joepavitt]

Thanks Greg, the other interesting thing looking at the Insight is the time to next step:

• Tour Completed: 3m 16s
• Over 50%: 3m 15s
• Cancelled: 5m 17s

I'd also be interested to know, of those that cancel and do not open the Editor, what instead are they doing?

[gstout52]

I've now watched several of the videos of users from this cohort, and overwhelmingly they: close the tour, then click around frantically.

Other behaviors:

• Create a second instance (likely because they don't know they already have an instance)
• Delete their team
• Try to create a remote instance
• A couple of users were on mobile, where the product tour display is very poor. For a quick win, I've created an issue to present an alternative display for mobile users.

I think it would be a useful iteration to point to the editor as a natural next step.

The experience could go something like: user cancels tour -> modal highlights the editor on the newly-created instance. From there, the existing 'next steps' mini-tour shows, which provides four ideas about what to do next along with documentation.

For users who complete the tour, everything remains the same, as they will already have had the editor pointed out to them.