[Meta][Fleet] Simplify UX for getting started with agent integrations

[mostlyjason]

Its important to provide a simple experience for users to get started with Elastic Agent integrations to improve ingestion rate and reduce churn. Full story data indicates there is a significant drop-off at each step of our funnel so simplifying may lift overall success rate. Among new users that click to add an integration, only 31% click to add an agent to their host and only 8.6% click the download agent button. Note that full story offers a first impression but we'll have more accurate data with https://github.com/elastic/kibana/issues/117236.

We hypothesize that a simpler onboarding flow will increase the ingestion rate for trials and data onboarding. We should design a vision for the best possible UX for adding integrations, and then work backwards to what we can accomplish today towards that vision. There are several areas of UX debt that are a result of making narrow changes over time within the existing system constraints. Starting with the vision first would help us avoid UX debt.

Problems include:

• New users need more context to understand what Elastic Agent is and whether it will meet their needs
• New users find integration and agent policies confusing, and they don't need to see these concepts when starting for the first time
• Add integration flow is disjointed across multiple pages, dialogs and flyouts. Its even worse when there are multiple steps, such as adding fleet server or APM agents, or adding custom logs.
• Limited guidance on next steps to analyze data. People often don't see or miss the buttons to view dashboards, and some get lost trying to find their data.
• Need better support for turnkey cloud platform ingestion and synthetics, where ingestion is hosted on the cloud, so the add agent step should be removed.
• Hard to track user success through each step because they are disjoint https://github.com/elastic/kibana/issues/117236

Open questions:

• Should we start by adding integrations or by adding agents? (CC @snide )

CC @dborodyansky

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[ecezalp]

Hello! CTI team here, there is a specific flow we have that was identified here - it would be great if it could be added to your considerations. Thank you 😃