Repository navigation
Replies: 1 comment
0-10 Scale: Design RationaleThe 0-10 scale is a deliberate design choice based on several factors: 1. Human Cognitive LoadResearch in cognitive psychology (Miller's Law) shows humans can comfortably distinguish about 7±2 levels on a scale. A 0-10 scale provides 11 points, which is at the upper edge of what's cognitively manageable for quick assessment.
2. Granularity vs. ActionabilityA finer scale (e.g., 0-100) would provide more precision but less actionability. The difference between 73 and 76 is meaningless. The difference between 7 and 8 is meaningful. 3. Comparison with Other Standards
Scorecard's 0-10 scale provides more granularity than these while remaining interpretable. 4. Statistical DistributionThe 0-10 scale allows for a reasonable distribution of scores across the ~1M+ repositories in the public dataset. Most repos cluster around 4-7, with clear differentiation at the extremes. 5. Weighted Check CompositionEach check contributes to the overall score based on its weight. The final score is a weighted average normalized to 0-10. This allows individual checks to have varying impact while keeping the final score interpretable. Reference
|
Uh oh!
There was an error while loading. Please reload this page.
Hey dear community,
I was scrolling through the documentation of the scorecard, looking for a particular design decision that I would like to understand for a research project.
What is well described is how the scores for a check are calculated, along with the associated risk. However, I am looking for the reasoning behind the decision to use a scoring range from 0-10. For some checks, I have the feeling that the way they fill the range from 0 to 10 is somewhat arbitrary. In some cases, it feels like the scale could also be from 0-7, and the score would still be granular enough to be meaningful.
Therefore, I would like to understand whether there is a specific reason behind this range -- whether it is based on
Best,
Marvin
All reactions