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

Thought - node scores are a bit ambiguous #452

Open
keyserj opened this issue Jun 20, 2024 · 0 comments
Open

Thought - node scores are a bit ambiguous #452

keyserj opened this issue Jun 20, 2024 · 0 comments
Labels
clarity makes something easier to understand learn app helps people learn how to use Ameliorate needs ux design User experience should be solidified before implementing not sure if worth not sure if this is worth implementing yet

Comments

@keyserj
Copy link
Collaborator

keyserj commented Jun 20, 2024

Node scores can be understood a few different ways, and this can cause confusion about how to use or interpret them. Thoughts:

  • possible meanings of a high score
    • "I agree" - this seems implied by the color matching with support/critique + thumbs-up/-down representing these
    • "I think this is important" - I usually emphasize this as the meaning verbally/in docs
    • "I want to talk about this" - can be conflated with "important", seems useful to be able to convey
    • "I think this is good" - slightly different from the others, but I've also said "high = generally good"
  • possible improvements (topic https://ameliorate.app/keyserj/ameliorate-scores-UX)
    • keep one ambiguous score - maybe other things could reduce ambiguity while keeping only one kind of score
    • separate scores per meaning - would be nice but hard to keep UX from being overwhelming/cluttered
    • make score mean "important" - disallows concise communication of the other kinds of feelings
    • make score mean "agree" - disallows concise communication of the other kinds of feelings
    • remove scores - disallows concise communication of any kinds of feelings
    • separate score for import vs truth confidence, separate indicator for "want discuss"
      • two scores might be manageable
      • don't need score for "want to discuss" - this can be a temporary mark
      • "good" seems like it could be "important" instead
      • might still have ambiguity
        • does "I think this is a detriment" have overlapping justification with "I think this detriment is important to address"?
@keyserj keyserj added needs ux design User experience should be solidified before implementing clarity makes something easier to understand not sure if worth not sure if this is worth implementing yet learn app helps people learn how to use Ameliorate labels Jun 20, 2024
@keyserj keyserj changed the title Thought - scores are a bit ambiguous Thought - node scores are a bit ambiguous Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarity makes something easier to understand learn app helps people learn how to use Ameliorate needs ux design User experience should be solidified before implementing not sure if worth not sure if this is worth implementing yet
Projects
Status: No status
Development

No branches or pull requests

1 participant