I use this as many of my cards are spelling-oriented/have sometimes a leading/trailing space when I enter them.
If I had only pass/fail, I’d get some false failures. This way, I can use the options to note as yes, I passed it. And indeed, sometimes I have a minor problem with the word and just need to mark it as hard.
I use Anki to study a foreign language, and I used to only press Again when I answered incorrectly and Good when I answered correctly, regardless of whether the answer came quickly or with a delay. Later, I realized that I wanted to differentiate between those “Good” answers so that more difficult cards would show up more often.
As a result, I wrote a script into my card template that:
Takes into account the time it took me to answer (i.e., how long the front side was visible)
Counts the number of answers (since in my case a word can have up to 6 translations—these are 6 separate fields)
Measures the length of the comment (in my case, the comment is spoken using TTS, and listening to it also increases decision-making time)
For cards where I have to type in a word, I simply count the number of letters that need to be typed, etc.
You can add any logic you believe affects the response speed.
As a result, I now have a clear, time-based hint indicating which button I should press.
For example, if it took me less than 3.5 seconds to answer, I’m recommended to press Easy.
But if it took 3.6 seconds, then Good is recommended, which means the card will reappear slightly sooner.
And if I answered correctly but took 30 seconds, then it’s Again anyway—because with language, you can’t afford to think that long during a conversation.
As it turned out, this cognitive load (Is this card difficult for me or easy? Which button should I press: Hard or Good?) was consuming quite a bit of my mental energy, and after implementing this hint system, I started to feel less fatigued.