Include feelings in your debrief. How it made you feel is also a cue to your answer. Any body sensations. Example, wet, was it cold wet, warm, salty (it does feel different) When you touched the ball did it wind up having any texture since.
You make sure you understand your answer by doing a lot of image streams and working out your code.
If that were my image stream.
What was your answer before you asked the question, "how can I make sure I'm understanding the correct answer here"?
Pull up another image stream to answer the question. You'll get symbolism that is either positive or negative to you. Notice also your feelings and choice of words as you debrief your image stream they are cues to your code.
An example from my code,
Rigid, straight, upright all have similar meaning to describe a fence however there is significant difference in the message behind the word that popped out. E.g rigid can be a warning that it's too stiff, not flexible, unyielding. Straight can mean on a path, in line with the goal. Upright = can be snobbish, appearing to do the right thing, high morals.
In debriefing, I look for those cues, why I used one word and not another, How I felt at that point in the IS... (one very good reason for recording the IS) as it also cues me on the positive or negative of an IS.
Alex
