Improve First-Run Kibana Telemetry Opt In Page

[bmcconaghy]

Improve design/UX. Current design is visually nice, but doesn’t do the best job encouraging people to opt in. At a minimum, worth learning from Apple
Re-consider defaulting to opt-in, with checkbox checked by default. Apple does it with MacOS. Firefox, and Microsoft Visual Studio do as well. Will need to work with Legal on this.

[joelgriffith]

Uploading current page for reference.

[joelgriffith]

I do think going to a checkbox might be better for this, and maybe some copy changes

[alexfrancoeur]

@gchaps this was one of the issues where we'll probably need your expertise. If it's helpful, we can touch base live to walk through in a bit more detail

[elasticmachine]

Pinging @elastic/kibana-stack-services (Team:Stack Services)

[joelgriffith]

@alexfrancoeur any headway here?

[alexfrancoeur]

I ran some PM mocks by legal and they're looking for some additional examples. I'll do some research, put together some more realistic mocks and get back to you tomorrow morning. If we can have placeholders for a checkbox with some text and a primary & secondary button, I think we'll be in a good spot. More to come in the morning, apologies that this one's taking a bit longer than expected. We'll probably need to rope in design for some options as well.

…

On Wed, Oct 30, 2019, 6:56 PM Joel Griffith ***@***.***> wrote: @alexfrancoeur <https://github.com/alexfrancoeur> any headway here? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#49518?email_source=notifications&email_token=AGAD476QKKEWB6AH4PFTLS3QRIGKZA5CNFSM4JF6ZCYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECWA64I#issuecomment-548147057>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGAD477QVJKJUISX4PO33KTQRIGKZANCNFSM4JF6ZCYA> .

[alexfrancoeur]

@cchaos @ryankeairns any ideas on how to streamline this flow?

[ryankeairns]

There was quite a bit of discussion about this in the original PR. It was also noted that opt-in was not an option at that time (#42110 (comment)). Reading on from that point, we also discussed other flow options...

Having designed several such prompts, people do not typically sign up for sending telemetry regardless of what you say. The best we can do is be friendly, provide a good reason (that insures them we will protect their individual privacy), don't prompt them numerous times, and don't leave them feeling tricked into it (i.e. opting them in by default is likely not a great option).

[cchaos]

The current design/layout for telemetry was based on the fact that we couldn't/didn't want telemetry on by default. Therefore, we had to force the user to make a decision on whether to enable/disable telemetry, hoping they'll pick enable.

With the new route of enabling by default, and allowing them to opt-out, it doesn't seem appropriate to have it as it's own call-to-action. We are no longer forcing them to make a decision therefore they don't need to press a button. But in the current layout they need to press a button to move forward.

In some way-back original mocks, we added the telemetry option as a checkbox below the welcome/no data CTA. Something like this but with the telemetry option checked by default.

For subsequent updates to Kibana where we would want to present them with the option again, we could create a new screen like this but instead of "Let's get started", it would say "What's new".

[alexfrancoeur]

For anyone watching this thread, we are still working through what will be the best approach for us. The most recent idea focuses on updating our telemetry statement before the 7.5 release. Rather than a checkbox, we'll provide some more detailed text that points to our telemetry statement with an option to opt out in advanced settings if needed. A flow like this will be necessary as we begin to integrate with Elastic Endpoint (formerly Endgame). We are still weighing the pros and cons but hope to have an answer shortly.

[alexfrancoeur]

An important part of the approach we're taking here is the link to opt-out in the data privacy notice (text almost finalized by legal). It would be nice link directly to the usage data filtered in advanced settings if possible.

[alexfrancoeur]

I think we're good to close this now, yeah?