>> my point was actually about his assertion that no one wanted it rather than that it would work. I wanted to address his assertion as well, but thought it wo

>> my point was actually about his assertion that no one wanted it rather than that it would work. I wanted to address his assertion as well, but thought it would be better as a child to yours than as a sibling. >> I've yet to see one that works really well for end users Yeah, this bit is very tricky. I would make the argument that your current approach might actually be one of the better approaches (at least from your customers' perspective). In a lot of the engagements I've been involved with, end users just want their responsibility to end at "this didn't work", and for the developers/consultants to figure out what the user did that caused an issue themselves. Reporting issues is work, and end users tend to be already busy with their own jobs. So the more work the end users have to do to report issues (i.e., filling out forms, taking screen shots), the more likely they are only going to report what they consider showstoppers.