<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: HumanComputer Interfaces.  Problems with messaging - Part 2</title>
	<link>http://www.blog.methodsinexcel.co.uk/2007/02/13/humancomputer-interfaces-problems-with-messaging-part-2/</link>
	<description></description>
	<pubDate>Sun, 12 Oct 2008 08:23:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.1</generator>

	<item>
		<title>by: ross</title>
		<link>http://www.blog.methodsinexcel.co.uk/2007/02/13/humancomputer-interfaces-problems-with-messaging-part-2/#comment-3740</link>
		<pubDate>Mon, 19 Feb 2007 09:17:18 +0000</pubDate>
		<guid>http://www.blog.methodsinexcel.co.uk/2007/02/13/humancomputer-interfaces-problems-with-messaging-part-2/#comment-3740</guid>
					<description>Thanks Dick. 

Simon, your comments on deleting a file is an excellent example of one of the ideas I'm going to suggest in the last part - keep messages low(not so good in your example), and provid a way to undo the action, which the recycle bin does well.</description>
		<content:encoded><![CDATA[<p>Thanks Dick. </p>
<p>Simon, your comments on deleting a file is an excellent example of one of the ideas I&#8217;m going to suggest in the last part - keep messages low(not so good in your example), and provid a way to undo the action, which the recycle bin does well.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Simon Murphy</title>
		<link>http://www.blog.methodsinexcel.co.uk/2007/02/13/humancomputer-interfaces-problems-with-messaging-part-2/#comment-3726</link>
		<pubDate>Mon, 19 Feb 2007 04:27:03 +0000</pubDate>
		<guid>http://www.blog.methodsinexcel.co.uk/2007/02/13/humancomputer-interfaces-problems-with-messaging-part-2/#comment-3726</guid>
					<description>Ross
You know when you a delete  file - do you ever change your mind because of the warning?
I don't, the very odd time I get it wrong I just restore from the recycle bin. I keep thinking to turn off the warning but I'm so conditioned to software asking me to confirm everything I do it seems wrong to turn it off. Imagine driving your car and it asking you to confirm everything.
I've read software dev standards that say all dialogs should default to making no change 'to protect the user from themselves'. how annoying would that be?
I'd say the no damage one is the easiest to code, the most likely probably needs smarter code to work out what to choose.
cheers
Simon</description>
		<content:encoded><![CDATA[<p>Ross<br />
You know when you a delete  file - do you ever change your mind because of the warning?<br />
I don&#8217;t, the very odd time I get it wrong I just restore from the recycle bin. I keep thinking to turn off the warning but I&#8217;m so conditioned to software asking me to confirm everything I do it seems wrong to turn it off. Imagine driving your car and it asking you to confirm everything.<br />
I&#8217;ve read software dev standards that say all dialogs should default to making no change &#8216;to protect the user from themselves&#8217;. how annoying would that be?<br />
I&#8217;d say the no damage one is the easiest to code, the most likely probably needs smarter code to work out what to choose.<br />
cheers<br />
Simon
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dick Kusleika</title>
		<link>http://www.blog.methodsinexcel.co.uk/2007/02/13/humancomputer-interfaces-problems-with-messaging-part-2/#comment-3686</link>
		<pubDate>Sun, 18 Feb 2007 16:58:19 +0000</pubDate>
		<guid>http://www.blog.methodsinexcel.co.uk/2007/02/13/humancomputer-interfaces-problems-with-messaging-part-2/#comment-3686</guid>
					<description>The content is good enough that I'll keep reading whatever you decide to do. :)</description>
		<content:encoded><![CDATA[<p>The content is good enough that I&#8217;ll keep reading whatever you decide to do. :)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ross</title>
		<link>http://www.blog.methodsinexcel.co.uk/2007/02/13/humancomputer-interfaces-problems-with-messaging-part-2/#comment-3668</link>
		<pubDate>Sun, 18 Feb 2007 11:02:39 +0000</pubDate>
		<guid>http://www.blog.methodsinexcel.co.uk/2007/02/13/humancomputer-interfaces-problems-with-messaging-part-2/#comment-3668</guid>
					<description>Re RSS:
Yeah I might change that - don't what people rippping my content though (poor as it maybe)</description>
		<content:encoded><![CDATA[<p>Re RSS:<br />
Yeah I might change that - don&#8217;t what people rippping my content though (poor as it maybe)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ross</title>
		<link>http://www.blog.methodsinexcel.co.uk/2007/02/13/humancomputer-interfaces-problems-with-messaging-part-2/#comment-3667</link>
		<pubDate>Sun, 18 Feb 2007 11:01:21 +0000</pubDate>
		<guid>http://www.blog.methodsinexcel.co.uk/2007/02/13/humancomputer-interfaces-problems-with-messaging-part-2/#comment-3667</guid>
					<description>Hi Dick, 
Yes, I agree. I would also say that on a number of occasions I find myself having to read the text about 4-5 times because by the time i get to the bottom i have forgotten what the first 2 points where. 
Joel Has some thoughts on this here:
http://www.joelonsoftware.com/uibook/chapters/fog0000000062.html

I think the important thing is to provide the key info clearly and quickly - that is be able to make an accurate judgment quickly, and to do this you need to provide context. Ideally you should then provide further information which can help the user.  

Default option  - I would make it the most likely choice, it will for sure catch you out, but I think it would be the better way to go. Basically it's a difficult choice. 

Cheers
Ross</description>
		<content:encoded><![CDATA[<p>Hi Dick,<br />
Yes, I agree. I would also say that on a number of occasions I find myself having to read the text about 4-5 times because by the time i get to the bottom i have forgotten what the first 2 points where.<br />
Joel Has some thoughts on this here:<br />
<a href='http://www.joelonsoftware.com/uibook/chapters/fog0000000062.html' rel='nofollow'>http://www.joelonsoftware.com/uibook/chapters/fog0000000062.html</a></p>
<p>I think the important thing is to provide the key info clearly and quickly - that is be able to make an accurate judgment quickly, and to do this you need to provide context. Ideally you should then provide further information which can help the user.  </p>
<p>Default option  - I would make it the most likely choice, it will for sure catch you out, but I think it would be the better way to go. Basically it&#8217;s a difficult choice. </p>
<p>Cheers<br />
Ross
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dick Kusleika</title>
		<link>http://www.blog.methodsinexcel.co.uk/2007/02/13/humancomputer-interfaces-problems-with-messaging-part-2/#comment-3359</link>
		<pubDate>Wed, 14 Feb 2007 22:14:01 +0000</pubDate>
		<guid>http://www.blog.methodsinexcel.co.uk/2007/02/13/humancomputer-interfaces-problems-with-messaging-part-2/#comment-3359</guid>
					<description>All good.  I've been trying lately to minimize the number of words in my message boxes.  I read that people won't read more than eight words.  It's harder than I thought it would be.  How about the default (the click-without-reading option)?  Should that be the most likely choice or the least destructive choice?

Re RSS: It appears you're only displaying partial posts in your RSS.  I prefer full posts.</description>
		<content:encoded><![CDATA[<p>All good.  I&#8217;ve been trying lately to minimize the number of words in my message boxes.  I read that people won&#8217;t read more than eight words.  It&#8217;s harder than I thought it would be.  How about the default (the click-without-reading option)?  Should that be the most likely choice or the least destructive choice?</p>
<p>Re RSS: It appears you&#8217;re only displaying partial posts in your RSS.  I prefer full posts.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
