Product Tour: Dashboard

[alexfrancoeur]

As part of #58506 and a follow up from #61549, we'd like to add product tours to some of Kibana's core applications. Dashboard is one of the most heavily utilized applications and it'd be great to provide quick, optional onboarding. Dashboard will be one of the first POC's for a product tour but if successful, we can begin to adopt across Elastic.

Steps

1. Add panel
2. Add visualization with Lens
3. Drag and drop fields
4. Save visualization
5. Name
6. Save and return to dashboard

There is descriptive text in the mockups, but we'll need to review text with @gchaps

Requirements

• These tours should only be viewable to new users
  • While we wait on Per-user profiles, settings in Kibana #17888, we may have to rely on local cache. Which means we should probably only focus on new deployments initially
• The tours should be dismissible
• If the tour was complete and others are available (like Discover Product Tour: Discover - Step One #80514), we should give them the option to do that next
• Entry point should not matter. Whether you're coming from the Kibana overview page, file upload, a data tutorial or simply trying out Kibana for the first time - you should be presented with this tour

Product analytics questions

Need to open separate telemetry issue to track

• How many users complete the tour?
• How many users ignore the tour?
• How many users drop out of the tour?
• Where do they drop out?
• Is the cluster successfully using Dashboard and Kibana after tours have been completed?

EUI component

https://elastic.github.io/eui/#/display/tour

Mockups and prototype

• Figma mockups
• Figma clickable prototype

cc: @AlonaNadler @rayafratkina @ryankeairns

[elasticmachine]

Pinging @elastic/kibana-core-ui (Team:Core UI)

[AlonaNadler]

These tours should only be viewable to new users
While we wait on #17888, we may have to rely on local cache. Which means we should probably only focus on new deployments initially

this can be a good first step while we optimize the tour. In general, the tours should be available for anyone coming from the overview page whether they have data or not. Otherwise, the tour is only available for the first user or Kibana and we are missing out on the onboarding of the end-users in every company

[rayafratkina]

+1 to using local cache initially. I feel like it solves most of the cases anyway.

[alexfrancoeur]

the tours should be available for anyone coming from the overview page whether they have data or not.

++ I agree. This is probably an implementation detail we'll need to figure out, but let me clarify what I meant with my statement. By "new deployment" I was referring to a new Kibana instance vs. an upgrade. We don't have a concept of persisted user states, would need to rely on local cache and we don't want to only focus tours on clusters that have no data (empty state). Because of this, I'm worried that if a cluster upgrades from the previous version all end users would be hit with this tour. They may have been using Kibana for years or days, we'd have no idea. I'm sure we can get creative here, but that feels like a scenario we'd want to avoid. What do you think?

[ryankeairns]

Until we have true user profile support, we could consider treating it like the newsfeed. In other words, provide a Kibana config to disable product tours that is also whitelisted for use by Cloud admins.

The obvious downside is that this would disable tours for new users on these instances, going forward. I don't love this approach, but it would provide an escape hatch for customers who find the recurrence of tour prompts to be problematic. It's an intermediate solution until user profiles exist.

[elasticmachine]

Pinging @elastic/kibana-design (Team:Kibana-Design)

[ryankeairns]

Not specific to this issue, but @liza-mae provided some quick thoughts on how this might be implemented (or what to consider in a proof of concept). In particular, whomever goes first (i.e. takes on the PoC) should consider the possibility of this being a separate plugin which provides a way to manage tours from a central location as opposed to sprinkling EuiTour wrappers throughout numerous application files.

[ryankeairns]

On hold until we have a broader plan for tours across Analytics.