[roguecoder]

This matches with how every other form of feedback works: we get a signal expressed to us with the signals available, but it is up to us to trace back and derive from the signal what actually kicked it off.

Think about it this way: when a user gives you some user feedback, you don't build the thing they tell you to build. Instead, you figure out what was frustrating them about the product that they wanted that thing build, and then you consider what the consequences of implementing various solutions to that underlying problem might be before you decide what to do with the feedback you got.

I don't do what my emotions tell me to do, but that is no reason to ignore the underlying dynamics that sparked them.