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

"Calibrate" intuition around percentage of support / uptake of features #206

Closed
romainmenke opened this issue May 25, 2023 · 3 comments
Closed

Comments

@romainmenke
Copy link
Contributor

In the topics on the definition of Baseline (numbers of versions supported, ...) we use percentages of support a lot.

Everyone seems to agree that "more than 90%" is good and that "less than 90%" is questionable.
But this doesn't seem based on reality or research, more a intuition based on past experience.

I think it could be useful to "calibrate" our intuition around these numbers.
I don't have an immediate suggestion for how this can be done.

This is directly related to #190

We first need to agree on a dataset.
Without all looking at the same data we might all be talking about a different 90% :)

If we do find a dataset it might be interesting to test our intuition.
Maybe 80% is perfectly fine?
Maybe 99% really is required?

@romainmenke romainmenke changed the title "Calibrate" percentage of support / uptake of features "Calibrate" intuition around percentage of support / uptake of features May 25, 2023
@atopal
Copy link
Collaborator

atopal commented May 28, 2023

Yes, usually we talk about something higher than 90% and lower than 98% as the threshold and that almost always refers to caniuse.com stats, even if that's implicit.

I can think of multiple ways to go about testing that, with any given data set:

  • Check multiple features that are on a threshold boundary and survey developers how they feel about them
  • Check usage counters for those multiple features that have crossed the threshold boundary and see if that leads to higher usage
  • Expert review: check multiple features on a threshold boundary and categorize them accordingly

@romainmenke
Copy link
Contributor Author

Sounds good!

@romainmenke
Copy link
Contributor Author

This work has all been done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants