Skip to content
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

[ObsUx] Standardize the button for providing feedback. #174719

Open
kpatticha opened this issue Jan 11, 2024 · 5 comments
Open

[ObsUx] Standardize the button for providing feedback. #174719

kpatticha opened this issue Jan 11, 2024 · 5 comments
Labels
enhancement New value added to drive a business result Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team

Comments

@kpatticha
Copy link
Contributor

kpatticha commented Jan 11, 2024

Apps Call to action(s) Show in settings pages Notes
APM 1. Tell us what you think!, 2. Give Feedback Google form, discuss.elastic.co mixed way to prodive feedback, google forms and elastic discuss forum. Tell us what you think! button within labs points to a different google form
Infra 1. Tell us what you think! Google form Button doesn't show up in all pages (ex app/metrics/detail/host/{host}
Universal Profiling 1. Give feedback Google form Google form is quite different from apm and infra
Synthetics afaict No feedback button

APM

Screen.Recording.2024-01-11.at.20.27.38.mov

Infra

Screen.Recording.2024-01-11.at.20.54.06.mov

Profiling

Screen.Recording.2024-01-11.at.20.54.21.mov

Proposal

  1. Use the same call to action across ObsUx.
  2. APM uses both google forms and the elastic discuss forum. Any benefit of having both? Can we pick one?
  3. In APM, in some pages we have side by side links for feedback. Generic feedback and feature specific feedback. Can we have only one?
@botelastic botelastic bot added the needs-team Issues missing a team label label Jan 11, 2024
@kpatticha kpatticha added the Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team label Jan 11, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 11, 2024
@jennypavlova
Copy link
Member

@kpatticha Thank you for adding this issue! In infra, we have different Google forms based on the feature used ATM ( so we added those buttons separately and we also have a different form/button label in case K8s pods are selected in the Show drop-down for example):

Image

I think the idea of Google Forms is to collect feedback and contact details in case the user wants to chat with us about the product and their use case. I am not sure about the discuss forum.

I don't know if we need to add the feedback button on the other infra pages and if there will be any benefit. Logs is a separate thing for example and the settings page is different from APM - it's just a simple single form.
@roshan-elastic can help us here - he is analyzing the feedback from the Google forms and is helping our customers. I want to hear your opinion here as well.

@kpatticha
Copy link
Contributor Author

@jennypavlova thanks for the context. I didn't realize that the top right button could be for specific features as well.
I agree for Infra, settings page is pretty simple.

As for the discuss forum, I don't know the historical context either. Also, I'm not sure who is monitoring it.

@roshan-elastic
Copy link

Hey @kpatticha,

I'm not sure how much this helps but the goal of the Google form buttons for feedback was to:

  1. Get quickly actionable feedback from customers on either the specific feature they're looking at (or perhaps a wider area...it depends on what form we link to)...we typically try and route the feedback to google groups that engineers, designers and PMs can read as the feedback comes in

  2. Get a trend of user satisfaction for features (effectively to use as a KPI) to see if we're improving things

  3. Recruit customers who are using the features to help us gauge demand and also work with them on developing new features.

In my experience, the Discuss forums weren't really meeting these three needs and it's been pretty successful so far.

I'm conscious about consistency (and also ensuring we don't spam customers with surveys) so any suggestions on how to improve this welcome!

Note : I really wish we had some survey software (e.g. HotJar) to help standardise this and ensure we don't spam users but unfortunately we don't :(

@botelastic
Copy link

botelastic bot commented Jul 13, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added the stale Used to mark issues that were closed for being stale label Jul 13, 2024
@smith smith added the enhancement New value added to drive a business result label Jul 14, 2024
@botelastic botelastic bot removed the stale Used to mark issues that were closed for being stale label Jul 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team
Projects
None yet
Development

No branches or pull requests

5 participants