On 26 Aug 2009, at 20:51, Jared Spool wrote:
People click on things all the time that are *not* things they
inevitably want. Thus the problem with pogosticking (http://is.gd/2AiMU
).
The problem with clickstream analysis is you can't tell the misfired
clicks from the desired clicks.
I agree completely :-)
What I was trying to say (obviously badly) was that there is (usually)
a deliberate intent to "click" - most of the time they didn't hit the
button accidentally. Not that the user wanted to go wherever that
click led (or not). Or that you could necessarily infer anything about
the reason for that click without further investigation.
So when I have a chunk of interface that is purely informative but
looks like it's something that should be interactive, and the designer/
PO don't believe me, looking at a nice fuzzy heatmap of hundreds of
users clicking on the darn thing is trez useful.
Of course this is nothing that you wouldn't get from a five minute
user test - but sometimes it's politically easier/cheaper/faster to
get a lump of javascript added to a web site and look at those results
rather that do some quick guerilla testing. Annoying I know. I can
then use those results to push for more pre-release testing to catch
those issues earlier.
Make vague sense?
Cheers,
Adrian
--
http://quietstars.com - twitter.com/adrianh - delicious.com/adrianh
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
