<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IT Solutions Blog &#187; Usability &amp; UCD</title>
	<atom:link href="http://www.michaelgaigg.com/blog/category/usabilityucduser-centered-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.michaelgaigg.com/blog</link>
	<description>Web Design Guidelines and Tips</description>
	<lastBuildDate>Fri, 30 Jul 2010 03:10:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Job Posting: User Interface (UI) Engineer at ESRI</title>
		<link>http://www.michaelgaigg.com/blog/2010/06/30/job-posting-user-interface-ui-engineer-at-esri/</link>
		<comments>http://www.michaelgaigg.com/blog/2010/06/30/job-posting-user-interface-ui-engineer-at-esri/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 01:44:08 +0000</pubDate>
		<dc:creator>Michael Gaigg</dc:creator>
				<category><![CDATA[Here and there]]></category>
		<category><![CDATA[Usability & UCD]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[esri]]></category>
		<category><![CDATA[full-time]]></category>
		<category><![CDATA[job]]></category>
		<category><![CDATA[posting]]></category>
		<category><![CDATA[Qualifications]]></category>
		<category><![CDATA[redlands]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[Responsibilities]]></category>
		<category><![CDATA[ui engineer]]></category>

		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=747</guid>
		<description><![CDATA[We are actively looking for a full-time <a href="http://careers.esri.com/sap(bD1lbiZwPTMzMDQ2JmM9MDUwJmQ9bWlu)/bc/bsp/sap/hrrcf_pinstappl/application.do?sap-themeRoot=%2fsap%2fpublic%2fbc%2fur%2fDesign2002%2fthemes%2fztest&#038;sap-client=050&#038;sap-language=EN&#038;rcfContext=ESRI&#038;PARAM=UElOU1RfR1VJRD00QzI2QjNBMkRGMkI1QjM5RTEwMDAwMDAwQTMyMUExMA%3d%3d">User Interface (UI) Engineer</a> here in <a href="http://www.esri.com/services/professional-services/index.html">Professional Services</a> (Applications Development Services) at <a href="http://www.esri.com">ESRI</a>.



<blockquote>If you feel qualified and are interested please send me your resume to <strong>mgaigg at esri.com</strong>. I'm also happy to answer any kind of question (except payment) you might have.</blockquote>

<h2>My job here</h2>
A little bit about what you can expect here: In my daily job I consult, design and help implementing customized web applications that are for the most part based on our <a href="http://www.esri.com/software/arcgis/arcgisserver/index.html">core mapping products</a> and API's for <a href="http://resources.esri.com/help/9.3/arcgisserver/apis/javascript/arcgis/help/jssamples_start.htm">JavaScript</a>, <a href="http://resources.esri.com/help/9.3/arcgisserver/apis/flex/samples/index.html">Flex</a> and <a href="http://resources.esri.com/help/9.3/arcgisserver/apis/silverlight/samples/start.htm">Silverlight</a>. Clients range from local and federal government to vertical markets like energy, water, environmental, etc. and reach local, domestic and international audiences - <strong>the challenges are never-ending</strong>, I promise ;) You can become part of this group!

<h2>Job Description</h2>
Use your technical background and innovative visual design skills to simplify complex business processes through the creation of intuitive and visually engaging user interfaces.

<h2>Responsibilities</h2>
<ul>
<li>Create sophisticated, imaginative, efficient, and visually striking interfaces for front-end solutions</li>
<li>Design reusable UI components by utilizing or building UI framework components</li>
<li>Develop storyboards, mock-ups, and prototypes to communicate ideas for navigation and interaction models</li>
<li>Evaluate requirements and initial mock-ups; make technology recommendations that support optimal construction, maintenance, and performance</li>
<li>Translate complex functional and technical requirements into detailed architecture and design prototypes</li>
<li>Ensure cross-browser/platform integrity of Web designs</li>
<li>Work closely with software developers and software testers to create a working end-to-end solution</li>
<li>Define, maintain, implement, and enforce style guides, standards, reusable templates, and best practices for client-side software development</li>
<li>Leverage the latest developments in Internet technologies</li>
<li>Serve as a technical resource and mentor</li>
</ul>
<h2>Requirements</h2>
<ul>
<li>Bachelor’s or master’s in computer science, graphic design, visual design, human factors engineering, interaction design, information architecture, or other relevant field</li>
<li>A minimum of five years of experience in user interface design, information architecture, user-centered design methodology, and implementation in complex enterprise environments</li>
<li>Significant and proven experience demonstrating innovative UI visual design skills</li>
<li>Ability to balance designs with the understanding of technical constraints within a software development environment</li>
<li>Highly proficient with cross-browser/platform CSS, HTML, XHTML, and JavaScript; knowledge of browser compatibility issues and their workarounds</li>
<li>Extensive experience using JavaScript libraries such as Dojo and jQuery</li>
<li>Good understanding of user experience (UX) and user-centered design (UCD)</li>
<li>Ability to take a concept from sketch to final implementation</li>
<li>Ability and willingness to take ownership of projects and help drive them to effective implementation</li>
<li>Exceptional attention to detail, organizational, communication, and presentation skills</li>
<li>Passionate about novel user interface design and software development</li>
</ul>
<h2>Recommended Qualifications</h2>
<ul>
<li>Experience with GIS/ESRI products and solutions</li>
<li>Experience with .NET, C#, Silverlight, and Expression Blend</li>
<li>Experience with JSP, Java Web frameworks, Flash, and ActionScript</li>
<li>Experience with Linux, PHP, and MySQL</li>
<li>Proficiency with Adobe Creative Suite including InDesign, Photoshop, and Illustrator</li>
<li>Ability to interface with customers, gather requirements, and implement new solutions</li>
</ul>
<h2>Employment Fraction</h2>
Full-time

<h2>Work Location</h2>
ESRI Headquarters, Redlands, CA]]></description>
		<wfw:commentRss>http://www.michaelgaigg.com/blog/2010/06/30/job-posting-user-interface-ui-engineer-at-esri/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Undercover Boss is User-centered Design at its best</title>
		<link>http://www.michaelgaigg.com/blog/2010/02/23/undercover-boss-is-user-centered-design-at-its-best/</link>
		<comments>http://www.michaelgaigg.com/blog/2010/02/23/undercover-boss-is-user-centered-design-at-its-best/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 05:37:29 +0000</pubDate>
		<dc:creator>Michael Gaigg</dc:creator>
				<category><![CDATA[Usability & UCD]]></category>
		<category><![CDATA[7-eleven]]></category>
		<category><![CDATA[cbs]]></category>
		<category><![CDATA[CEO]]></category>
		<category><![CDATA[experience]]></category>
		<category><![CDATA[Field Studies]]></category>
		<category><![CDATA[hooters]]></category>
		<category><![CDATA[humanity]]></category>
		<category><![CDATA[incognito]]></category>
		<category><![CDATA[jobs]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[potential]]></category>
		<category><![CDATA[reality]]></category>
		<category><![CDATA[tv]]></category>
		<category><![CDATA[UCD]]></category>
		<category><![CDATA[undercover boss]]></category>
		<category><![CDATA[waste management]]></category>

		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=651</guid>
		<description><![CDATA[I'm amazed, though not surprised, how <strong>revealing and informative</strong> field trips can be. Three episodes into <a href="http://www.cbs.com/primetime/undercover_boss">Undercover Boss</a>, a reality TV series by <a href="http://www.cbs.com">CBS</a>, it becomes obvious how easy it is for upper management to get disconnected from the base, for a CEO to know little to nothing about its employees and their work conditions, for a corporate policy being counterproductive. High-level assumptions don't live up to their expectations, prove to be ineffective, are misinterpreted or simply not useful at all.

[caption id="" align="alignright" width="200" caption="Undercover Boss logo"]<img alt="Undercover Boss logo" src="http://upload.wikimedia.org/wikipedia/commons/thumb/e/ef/Undercover_Boss_logo.jpg/200px-Undercover_Boss_logo.jpg" title="Undercover Boss logo" width="200" height="95" />[/caption]

For all that haven't seen the show yet, each episode of the <a href="http://en.wikipedia.org/wiki/Undercover_Boss">show</a> features a <strong>senior executive at a major corporation working incognito</strong> as a new entry-level hire in his or her company for one week, to find out how the company really works and identify some of the unsung heroes among the employees.

<h2>Setting the stage</h2>

The show usually starts with the CEO of the corporation entering a board meeting revealing his plan to go undercover. I enjoy seeing the directors' <strong>mouths dropping with shear fear in their faces</strong> of the possible outcome and its consequences. Could it be that they know something might be wrong? Or not perfect? 

<h2>Learning the hard way</h2>

The undercover boss assumes a new identity and with the excuse of being filmed for a documentary on a person working entry-level jobs in several different industries (or similar) starts digging dirt for <a href="http://www.wm.com/">Waste Mangement</a>, cleaning dishes at <a href="http://www.hooters.com">Hooters </a>or serving coffee at <a href="http://www.7-eleven.com/">7-Eleven</a>.

We see a woman that has to pee in a can for lack of time to make a toilet stop en route, store lights that cannot be replaced within a 30-day window, a restaurant manager having his employees competing in degrading games so the winner can leave early. All examples of failed management and policies with <strong>huge potential for change</strong>!

We also live with some incredible and heartbreaking stories of inspiring people that are on dialysis or waiting for a kidney transplant but still work hard and motivated. A guy that works long nights to finance his studies but without perspective within the company, something is not going right here. 
All these people are invaluable to any company but unfortunately mostly overlooked, another missed chance of <strong>finding hidden potential</strong>. Some of them with incredible skills that are simply not needed at their current job position but might be essential in another. Where to go?

Overall, the experience is eye-opening and a <strong>dedication to humanity</strong>, the revelation that every "position" is held by a person, that every "customer relation" is an interaction between people, that every "policy" directly or indirectly affects the life of an employee.

<h2>Catharsis</h2>
Finally the CEO, overwhelmed by his experiences, seems cleansed by his experiences and vows to correct the disgrace before it becomes outrage. In the show the boss <strong>reveals his true identity</strong> to the employees and like a big family they watch clips from the show, laugh, cheer and live happily ever after.

<h2>Effect on UX</h2>

Field studies, a widely accepted and practiced method of user-centered design, seems to find its way into the conscience of the American (and British - the show is based on the 2009 British Channel 4 <a href="http://www.realitytvworld.com/news/report-cbs-orders-secret-millionaire-like-undercover-boss-series-8362.php">series of the same name</a>) viewers. It appears as <strong>the obvious thing to do</strong>.

My very positive take-away from the show is that without knowing, managers, directors and CEO's will ask for more involvement of the base (real people), will <strong>involve field studies or user testing in their methodology</strong> which surely won't disappointed them. Their insights will improve the live of their employees (the society) and gain considerable business advantages over their competition in the long run. 

Am I dreaming or reaching for the stars? <strong>Let me know what you think?</strong>]]></description>
		<wfw:commentRss>http://www.michaelgaigg.com/blog/2010/02/23/undercover-boss-is-user-centered-design-at-its-best/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What part of &#8220;No-reply&#8221; don&#8217;t you understand?</title>
		<link>http://www.michaelgaigg.com/blog/2010/02/15/what-part-of-no-reply-dont-you-understand/</link>
		<comments>http://www.michaelgaigg.com/blog/2010/02/15/what-part-of-no-reply-dont-you-understand/#comments</comments>
		<pubDate>Mon, 15 Feb 2010 18:28:34 +0000</pubDate>
		<dc:creator>Michael Gaigg</dc:creator>
				<category><![CDATA[Usability & UCD]]></category>
		<category><![CDATA[answer]]></category>
		<category><![CDATA[automated]]></category>
		<category><![CDATA[contextual insight]]></category>
		<category><![CDATA[correspondence]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[learn]]></category>
		<category><![CDATA[no-reply]]></category>
		<category><![CDATA[transactional]]></category>

		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=632</guid>
		<description><![CDATA[<h2>Scenario</h2>
The application sends out automated emails with links to a report that was requested by the user and created by the application. The <strong>sender address is 'no-reply@company.com'</strong> and obviously not meant to receive any further correspondence. 

As it turns out, this exact no-reply email alias receives 'feedback' almost on a daily basis, some valuable and constructive, others from painfully true to filled with hatred, meaningless and doubtful.

Here an example:
<blockquote>Thx….this rocks……I am soooo gonna use u for this shit :)</blockquote>

What should we do with this answer?

<strong>Learn!</strong>

It is important that you hear something... anything... that you give your users a <strong>channel to voice their experience</strong> from which you can/should learn and grow. Don't label them 'stupid' just because they "didn't get it", all the opposite, maybe YOU didn't get it because a <strong>reply to an incoming email seems intuitive</strong> and picking up the phone or opening a web browser with a link to a feedback form isn't. 

<h2>Lessons</h2>

So what can be learned from something seemingly unwanted - or to say it differently: not anticipated?

<ul>
<li>Take your customers serious. </li>
<li>Turn supposedly unwanted correspondence into <a href="http://experiencematters.wordpress.com/2010/02/08/market-research-needs-less-statistical-analysis/">contextual insight</a> (observations drawn from data that resonates with an understanding of the business).</li>
<li>Turn them into business opportunities. Let them help you make better and faster decisions or simply improve the quality and perception of your application.</li>
<li>Optimize your automated emails following the <a href="http://www.michaelgaigg.com/blog/2009/06/30/design-guidelines-transactional-email/">guidelines for transactional email</a></li>
</ul>

<strong>Do it like Facebook</strong>. When <a href="http://www.facebook.com">Facebook</a> realized that their users reply to email notifications about let's say comments on a picture of them, they simply turned those replies into a comment on the comment. 
On the <strong>downside</strong>, less users go to the actual site to post the comment and continue using the service but on the <strong>upside </strong>the communication doesn't stop and becomes more real-time and valuable. A little give is a little more take I would say. Right on!]]></description>
		<wfw:commentRss>http://www.michaelgaigg.com/blog/2010/02/15/what-part-of-no-reply-dont-you-understand/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>World Usability Day 2009</title>
		<link>http://www.michaelgaigg.com/blog/2009/11/12/world-usability-day-2009/</link>
		<comments>http://www.michaelgaigg.com/blog/2009/11/12/world-usability-day-2009/#comments</comments>
		<pubDate>Thu, 12 Nov 2009 15:44:29 +0000</pubDate>
		<dc:creator>Michael Gaigg</dc:creator>
				<category><![CDATA[Usability & UCD]]></category>
		<category><![CDATA[events]]></category>
		<category><![CDATA[key questions]]></category>
		<category><![CDATA[stakeholders]]></category>
		<category><![CDATA[success]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[world usability day 2009]]></category>

		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=575</guid>
		<description><![CDATA[Today is World Usability Day (check out events in your area)! What is World Usability Day? &#8220;World Usability Day was founded in 2005 as an initiative of the Usability Professionals&#8217; Association to ensure that services and products important to human life are easier to access and simpler to use. Each year, on the second Thursday [...]]]></description>
		<wfw:commentRss>http://www.michaelgaigg.com/blog/2009/11/12/world-usability-day-2009/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>5 Usability Newsletters to Follow</title>
		<link>http://www.michaelgaigg.com/blog/2009/10/14/5-usability-newsletters-to-follow/</link>
		<comments>http://www.michaelgaigg.com/blog/2009/10/14/5-usability-newsletters-to-follow/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 21:26:33 +0000</pubDate>
		<dc:creator>Michael Gaigg</dc:creator>
				<category><![CDATA[Usability & UCD]]></category>
		<category><![CDATA[alertbox]]></category>
		<category><![CDATA[Barbara S. Chaparro]]></category>
		<category><![CDATA[Dana Chisnell]]></category>
		<category><![CDATA[Donna Spencer]]></category>
		<category><![CDATA[jakob nielsen]]></category>
		<category><![CDATA[jared spool]]></category>
		<category><![CDATA[jeff sauro]]></category>
		<category><![CDATA[Luke Wroblewski]]></category>
		<category><![CDATA[measuring usability]]></category>
		<category><![CDATA[newsletter]]></category>
		<category><![CDATA[SURL]]></category>
		<category><![CDATA[UI Design Newsletter]]></category>
		<category><![CDATA[UIEtips]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=543</guid>
		<description><![CDATA[Yes, you heard right, &#8220;Newsletter&#8221;, this old-fashioned, &#8216;traditional&#8217; thing that pollutes our mailboxes. Well, at least according to Jakob Nielsen email newsletters are more powerful than stream-based media (RSS or other social media feeds) in terms of maintaining a customer relationship, i.e. because newsletters need to be deleted manually versus &#8216;dropping off&#8217; the users&#8217; main [...]]]></description>
		<wfw:commentRss>http://www.michaelgaigg.com/blog/2009/10/14/5-usability-newsletters-to-follow/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Remote User Testing &#8211; A Comprehensive Guide</title>
		<link>http://www.michaelgaigg.com/blog/2009/10/12/remote-user-testing-a-comprehensive-guide/</link>
		<comments>http://www.michaelgaigg.com/blog/2009/10/12/remote-user-testing-a-comprehensive-guide/#comments</comments>
		<pubDate>Mon, 12 Oct 2009 18:10:01 +0000</pubDate>
		<dc:creator>Michael Gaigg</dc:creator>
				<category><![CDATA[Usability & UCD]]></category>
		<category><![CDATA[advantages]]></category>
		<category><![CDATA[cost]]></category>
		<category><![CDATA[disadvantages]]></category>
		<category><![CDATA[estimates]]></category>
		<category><![CDATA[morae]]></category>
		<category><![CDATA[output]]></category>
		<category><![CDATA[remote]]></category>
		<category><![CDATA[session]]></category>
		<category><![CDATA[techsmith]]></category>
		<category><![CDATA[UCD]]></category>
		<category><![CDATA[User Testing]]></category>
		<category><![CDATA[uservue]]></category>

		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=539</guid>
		<description><![CDATA[No doubt, user testing increases the usability and acceptance of your website and can/should be done as early as possible, preferably during <a href="http://www.michaelgaigg.com/blog/2009/09/30/integrating-prototyping-into-your-projects/">Prototyping</a>.

The following blog entry discusses the <strong>advantages &#038; disadvantages</strong> of remote user testing, describes <strong>time estimates &#038; costs</strong> and explains how a <strong>session </strong>looks like using <a href="http://www.techsmith.com/uservue.asp">Techsmith's UserVue</a>.  

<div style="width:425px;text-align:left;" id="__ss_2200121"><a style="font:14px Helvetica,Arial,Sans-serif;display:block;margin:12px 0 3px 0;text-decoration:underline;" href="http://www.slideshare.net/mgitsolutions/remote-user-testing" title="Remote User Testing">See my slide presentation on Remote User Testing</a><object style="margin:0px" width="425" height="355"><param name="movie" value="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=remoteusertesting-091012123920-phpapp01&#038;stripped_title=remote-user-testing" /><param name="allowFullScreen" value="true"/><param name="allowScriptAccess" value="always"/><embed src="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=remoteusertesting-091012123920-phpapp01&#038;stripped_title=remote-user-testing" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="355"></embed></object><div style="font-size:11px;font-family:tahoma,arial;height:26px;padding-top:2px;">View more <a style="text-decoration:underline;" href="http://www.slideshare.net/">presentations</a> from <a style="text-decoration:underline;" href="http://www.slideshare.net/mgitsolutions">Michael Gaigg</a>.</div></div>

<h2>General Discussion</h2>

<h3>Advantages</h3>
<ul>
<li>Reduced (or no) travel time and expenses.</li>
<li>Higher exposure through easy screen sharing (managers can sneak in easily).</li>
<li>Actual user environment, familiar and comfortable.</li>
<li>Possibly fewer drop-outs.</li>
</ul>
<h3>Disadvantages</h3>
<ul>
<li>Facilitator not physically present (degree of separation can be challenging).</li>
<li>Can't see facial expressions or non-verbal cues.</li>
<li>Difficult to build rapport and trust.</li>
<li>Difficult to control environment.</li>
<li>Possibly technical difficulties (firewall, etc.).</li>
<li>Setup and use of software or usability lab might be challenging and requires a liaison.</li>
</ul>

<h2>Time estimates &#038; Costs</h2>
<h3>Task Breakdown</h3>
The following time estimates are to be taken with a grain of salt, they can change significantly up or down depending on the project size, experience of the team and infrastructure.
<ul>
<li>Preparation (18 hours)
<ul>
<li>User screening: 8 hours</li>
<li>Task creation: 8 hours</li>
<li>Environment: 2 hours</li>
</ul>
</li>
<li>User testing (10 hours)
<ul>
<li>2 hours per user</li>
<li>5 users per round</li>
</ul>
</li>
<li>Post-test (32 hours)
<ul>
<li>Test report: 16 hours</li>
<li>Implementation: 12 hours</li>
<li>Communication: 4 hours</li>
</ul>
</li>
</ul>

<h3>Summary: Our Time</h3>
1 Round = 60 hours
2 Rounds = 110 hrs.
3 Rounds = 160 hrs.

+ User comps
+ Time additional observers

<h2>How it works</h2>
<h3>Software</h3>
<h4>UserVue</h4>
<a href="http://www.techsmith.com/uservue.asp">UserVue</a> is a Remote user testing software that enables a Facilitator to remotely observe a Participant using a phone line for communication. Multiple Observers can passively join the Session and share their observations with the Facilitator.
<h4>Morae Manager</h4>
<a href="http://www.techsmith.com/morae.asp">Morae Manager</a> uses the collected data (observation markers and notes, video, keyboard and mouse inputs) to analyze and calculate task times, error quotes and other common measurements. 
<h3>Session</h3>
A Session is initiated by the Facilitator. Invitation emails are being sent to the Participant and Observer(s). 

At the announced time all the involved parties need to download a small software bundle that allows them to connect to the UserVue software. The Facilitator then calls the Participant and gives instructions on how to start the Session. 

After the session has ended the installed software bundle will be removed from computers of the involved parties.

<h3>Participant Requirements</h3>
<h4>Operating System</h4>
Microsoft Windows 2000 and Windows XP or later version of Windows.
<h4>Web Browser</h4>
Internet Explorer 5.0 or later, Firefox 1.0 or later.
<h4>JavaScript</h4>
Enabling JavaScript is recommended.


<h3>Security?</h3>

All communication with the UserVue Web site is performed over an encrypted Secure Sockets Layer transport mechanism (HTTPS). All session data is encrypted with a 128-bit Blowfish cipher as it is sent over the network.
<h4>Can anyone "eavesdrop" on my session? </h4>
All session data (including audio, video, chat data, etc.) is encrypted with a 128-bit Blowfish cipher as it is sent over the network. This makes it exceedingly difficult for anyone to intercept and observe session data.
<h4>Are copies of my session data stored anywhere?</h4>
No copies of session data are stored on any server. The only recording happens directly on the facilitator's computer. Session data may pass through TechSmith's servers to facilitate firewall and NAT traversal. However, this data is never stored. Also, this data is undecipherable as it is in an encrypted form as it passes through TechSmith's servers.


<h2>What are your experiences with Remote User Testing?</h2>

<h2>References</h2>
<ul>
	<li>Bolt, N.; Guide to Remote Usability Testing; <a href="http://www.ok-cancel.com/archives/article/2006/07/guide-to-remote-usability-testing.html" target="_blank">http://www.ok-cancel.com/archives/article/2006/07/guide-to-remote-usability-testing.html</a></li>
	<li>Gough, D., Phillips, H.; Remote Online Usability Testing: Why, How, and When to Use It; <a href="http://www.boxesandarrows.com/view/remote_online_usability_testing_why_how_and_when_to_use_it" target="_blank">http://www.boxesandarrows.com/view/remote_online_usability_testing_why_how_and_when_to_use_it</a></li>
</ul>]]></description>
		<wfw:commentRss>http://www.michaelgaigg.com/blog/2009/10/12/remote-user-testing-a-comprehensive-guide/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Steps to improve User Experience for Government</title>
		<link>http://www.michaelgaigg.com/blog/2009/03/31/steps-to-improve-user-experience-for-government/</link>
		<comments>http://www.michaelgaigg.com/blog/2009/03/31/steps-to-improve-user-experience-for-government/#comments</comments>
		<pubDate>Tue, 31 Mar 2009 22:19:42 +0000</pubDate>
		<dc:creator>Michael Gaigg</dc:creator>
				<category><![CDATA[Usability & UCD]]></category>
		<category><![CDATA[audience]]></category>
		<category><![CDATA[boundaries]]></category>
		<category><![CDATA[citizens]]></category>
		<category><![CDATA[communicate]]></category>
		<category><![CDATA[contribution]]></category>
		<category><![CDATA[cost reduction]]></category>
		<category><![CDATA[culture]]></category>
		<category><![CDATA[efficiency]]></category>
		<category><![CDATA[egovernment]]></category>
		<category><![CDATA[enhance productivity]]></category>
		<category><![CDATA[fixmystreet]]></category>
		<category><![CDATA[future]]></category>
		<category><![CDATA[gadgets]]></category>
		<category><![CDATA[government]]></category>
		<category><![CDATA[hfi]]></category>
		<category><![CDATA[igov]]></category>
		<category><![CDATA[improvements]]></category>
		<category><![CDATA[interact]]></category>
		<category><![CDATA[language]]></category>
		<category><![CDATA[legislative offices]]></category>
		<category><![CDATA[movement]]></category>
		<category><![CDATA[needs]]></category>
		<category><![CDATA[processes]]></category>
		<category><![CDATA[progress]]></category>
		<category><![CDATA[reduced effort]]></category>
		<category><![CDATA[report]]></category>
		<category><![CDATA[solutions]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[transact]]></category>
		<category><![CDATA[usage]]></category>
		<category><![CDATA[UX]]></category>

		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=378</guid>
		<description><![CDATA[In my daily work I'm constantly confronted with developments for government sites. Often I hear confusion in <strong>what needs to be achieved</strong>, <strong>who needs to be served</strong> and especially <strong>why it should matter</strong>.

<img src="http://www.michaelgaigg.com/blog/wp-content/uploads/2009/03/ux-government-fixmystreet.jpg" alt="Become creative to engage citizens in governmental issues (using the citizen’s language), e.g. upload a photo of the damaged street (http://www.fixmystreet.com/)" title="Become creative to engage citizens in governmental issues (using the citizen’s language), e.g. upload a photo of the damaged street (http://www.fixmystreet.com/)" />

Listening into a Webcast by Human Factors International (download white paper on <a href="http://www.humanfactors.com/downloads/whitepapers.asp#egovernment">Designing the e-government experience through citizen-centered usability</a>, March 2008) gave me additional insights that I want to summarize and present here:

<h2>Goals of eGovernment</h2>
The web offers governmental sites the potential for <strong>increased operational efficiency</strong> and <strong>cost reductions</strong> while improving access to information and services for <strong>their citizens</strong>. 

Levels of interaction between these two actors (government &#038; citizens) include:
<ul>
<li><strong>Connect </strong>citizens with legislative offices</li>
<li><strong>Communicate </strong>faster and more targeted</li>
<li><strong>Leverage access</strong> to public services (enhanced productivity with reduced effort)</li>
</ul>

<h2>Steps to improve eGovernment</h2>
Traditionally the government has three main functions:
<ol>
<li>Report</li>
<li>Transact</li>
<li>Interact</li>
</ol>

What can be done to improve these functions/processes?

<h3>Get it out there</h3>
<ul>
	<li>What information is interesting?</li>
	<li>What is already available?</li>
</ul>



<h3>Make it useful &#038; usable</h3>

<ul>
	<li>Pre-digest the information (e.g. into charts, comparisons, …)</li>

	<li>Understand the citizen’s needs (e.g. Spanish language, search, text size, …)</li>

	<li>Assist citizen’s in finding the information (sometimes they don’t know it exists)</li>

	<li>Avoid: limited business focus, internal focus, lack of shared resource</li>

</ul>


<h3>Provide self-service</h3>
<ul>
	<li>Assist citizens to walk through business logic (avoid unnecessary pages, forms, fields, …)</li>
</ul>



<h3>Track improvement</h3>
<ul>
	<li>Establish a baseline (best practices review, scorecard, usability testing success rates, web analytics, call center volume, server logs, …)</li>

	<li>Validate improvements (success rate, task time) &#038; seek for support within your organization for doing this</li>

	<li>Continuously track usage</li>

	<li><strong>Why?</strong> Avoid falling back in national ranking, reduce costs for service calls, …</li>

</ul>


<h3>Make it engaging</h3>
<ul>
	<li>“Will? Can?” <strong>Will</strong> citizens use the service? <strong>Can</strong> they find it?</li>

	<li>Make it exciting</li>

	<li>Use experiences or technologies that are current and up to date (videos, gadgets, …)</li>
</ul>



<h3>Embrace the future</h3>
<ul>
	<li><strong>Become creative</strong> to engage citizens in governmental issues (using the citizen’s language), e.g. upload a photo of the damaged street (http://www.fixmystreet.com/)</li>

	<li>Encourage citizens to interact through social tools</li>

</ul>


<h3>Erase boundaries</h3>
<ul>
	<li>Integration of “Report”, “Transact” and “Interact” means to remove the disparity between organizational structures of governments and the mental models of the citizens</li>

	<li>Understand and channel the motivation of citizens to use online services</li>

	<li>Integrate offers from multiple agencies into one comprehensible user experience</li>

</ul>


<h3>Start a movement</h3>
<ul>
	<li><strong>Create a community</strong> by involving State &#038; Agency Leadership, Agency CIO’s and Webmasters</li>

	<li><strong>Recognition and adoption</strong> are key aspects</li>

	<li>Embrace the chaos</li>

	<li>Provide useful &#038; usable tools</li>

	<li>Reward contributions &#038; demonstrate progress</li>

	<li>View webmasters as a partner, not as recipient</li>

</ul>




<h2>Transparency</h2>
<ul>
	<li>The user’s perspective of the organization and the actual organizational structures are mostly very different. Citizens should not need to know how an agency is organized or be familiar with its terminology. </li>

	<li>Focus on the citizen means to understand how they look for information!</li>

	<li>Integrate internal processes into <strong>one intelligent solution</strong> (iGov = integrated Government)</li>

	<li>Understanding the level of literacy is key to success. <strong>Easy language</strong> assists citizens in filling out bureaucratic forms.</li>

</ul>



<h2>Government must view itself as a business</h2>
<ul>
	<li>Attract and satisfy citizens. Beware of competition and consider concepts like ‘brand loyalty’. Effective interaction adds benefits to citizens. </li>

	<li>Convert visitors into customers meaning that <strong>citizens become active online users</strong> of the services.</li>

	<li>Broaden the focus onto international audience which is important to attract entrepreneurship and investment capital and is a good indicator of a strong technology market and research and development environment.</li>
</ul>



<h2>Assistance through technology, tools and continuous improvement</h2>
<ul>
	<li>Support CIO’s and webmasters through tools like <strong>design templates, standards, guidelines</strong> and an effective means of governance. </li>

	<li>Adjust technology to changing market conditions, population demographics and the user’s level of expectations.</li>

	<li>Create a culture and long-term commitment (=institutionalization) of usability within the agency!</li>

	<li>Establish a baseline of improvement and continuously validate and improve through benchmarks.</li>

</ul>

<h2>Your thoughts?</h2>
I'd like to hear your feedback and if you have applied one or many of above techniques in your agency and <strong>what your experiences were</strong>. 

<h2>References</h2>
<ul>
	<li>Straub, K., Gerrol, S.; Designing the e-government experience through citizen-centered usability; Human Factors International, Inc.; White paper; March 6, 2008</li>
</ul>]]></description>
		<wfw:commentRss>http://www.michaelgaigg.com/blog/2009/03/31/steps-to-improve-user-experience-for-government/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Benefits &amp; Principles of User-Centered Design</title>
		<link>http://www.michaelgaigg.com/blog/2009/03/05/benefits-principles-of-user-centered-design/</link>
		<comments>http://www.michaelgaigg.com/blog/2009/03/05/benefits-principles-of-user-centered-design/#comments</comments>
		<pubDate>Thu, 05 Mar 2009 16:30:18 +0000</pubDate>
		<dc:creator>Michael Gaigg</dc:creator>
				<category><![CDATA[Usability & UCD]]></category>
		<category><![CDATA[audience]]></category>
		<category><![CDATA[benefits]]></category>
		<category><![CDATA[costs]]></category>
		<category><![CDATA[experience]]></category>
		<category><![CDATA[goals]]></category>
		<category><![CDATA[principles]]></category>
		<category><![CDATA[return of investment]]></category>
		<category><![CDATA[revenue]]></category>
		<category><![CDATA[ROI]]></category>
		<category><![CDATA[target]]></category>
		<category><![CDATA[tasks]]></category>
		<category><![CDATA[training]]></category>
		<category><![CDATA[UCD]]></category>
		<category><![CDATA[ui]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user]]></category>
		<category><![CDATA[user-centered design]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=93</guid>
		<description><![CDATA[We, the people, have been around for quite some years now. Computers, software, applications and the web not so much. Therefore it is clear that <strong>applications have to adjust to the people</strong> and not the other way round.

Many design principles have developed throughout the decades, but the main difference of user-centered design to others is that 

<blockquote>UCD tries to <strong>optimize the user interface around how people can, want, or need to work</strong>, rather than forcing the users to change how they work to accommodate the system or function.</blockquote>



<h2>Purpose of UCD</h2>
UCD answers questions about users and their tasks and goals, then use the findings to make decisions about development and design. 

UCD seeks to answer the following questions:
<ul>
<li>Who are the users of the application? </li>
<li>What are the users’ main tasks and goals? </li>
<li>What are the users’ experience levels with the application? </li>
<li>What functions do the users need from the application? </li>
<li>What information might the users need, and in what form do they need it? </li>
<li>How do users think the application should work?</li>
</ul>

<h2>Benefits &#38; Return of Investment</h2>
<ul>
	<li>Increased usability
<ul>
	<li>Higher degree of customer satisfaction</li>
	<li>Continued business</li>
	<li>Higher revenues</li>
</ul>
</li>
	<li>Project management optimization
<ul>
	<li>Focus on important functionality early</li>
	<li>Unforeseen user requirements</li>
</ul>
</li>
	<li>Reduced costs
<ul>
	<li>Training costs</li>
	<li>Help-Desk calls and service costs</li>
</ul>
</li>
</ul>

<h2>UCD Principles</h2>

<ul>
	<li>Focus on users’ needs, tasks and goals</li>
	<li>Spend time on initial research and requirements
<ul>
	<li>Identify your target audience and observe them (accomplishing their tasks)</li>
	<li>Let users define product requirements</li>
</ul>
</li>
	<li>Emphasis on iterative design process</li>
	<li>Evaluate system on real target users</li>
</ul>

<h2>Summary</h2>
Nobody could state it simpler than Susan Dray: "If the user can’t use it, it doesn’t work". ]]></description>
		<wfw:commentRss>http://www.michaelgaigg.com/blog/2009/03/05/benefits-principles-of-user-centered-design/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Feature Fatigue: Say NO to Your Clients</title>
		<link>http://www.michaelgaigg.com/blog/2009/02/11/feature-fatigue-say-no-to-your-clients/</link>
		<comments>http://www.michaelgaigg.com/blog/2009/02/11/feature-fatigue-say-no-to-your-clients/#comments</comments>
		<pubDate>Wed, 11 Feb 2009 23:54:00 +0000</pubDate>
		<dc:creator>Michael Gaigg</dc:creator>
				<category><![CDATA[Usability & UCD]]></category>
		<category><![CDATA[clients]]></category>
		<category><![CDATA[ease of use]]></category>
		<category><![CDATA[feature fatigue]]></category>
		<category><![CDATA[features]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[harvard business review]]></category>
		<category><![CDATA[sales]]></category>
		<category><![CDATA[task]]></category>

		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=295</guid>
		<description><![CDATA[Are your clients asking to add features upon features to your application because they think it will boost their success? This might really harm them and therefore you in the long run. Here is why:
<h2>Feature Fatigue</h2>
A study by Harvard Business Review (<a href="http://harvardbusinessonline.hbsp.harvard.edu/b01/en/common/viewFileNavBean.jhtml;jsessionid=4FU4YU4C2PRW0AKRGWDR5VQBKE0YIISW?_requestid=49091" target="_blank">Defeating Feature Fatigue</a>) has found that the features of a product mattered more to participants (customers) <strong>before </strong>they bought a product but <strong>after </strong>the purchase the actual satisfaction was greater with the simpler version of the product.
<img class="size-full wp-image-296" title="Feature Fatigue" src="http://www.michaelgaigg.com/blog/wp-content/uploads/2009/02/feature_fatigue.gif" alt="Feature Fatigue" width="342" height="288" />

That means that customers <strong>think</strong> they want feature-loaded offerings while they are shopping but once they start using their purchase, they suffer feature fatigue: they <strong>become overwhelmed by the product's complexity</strong> and <strong>annoyed by features</strong> they realize they don't want or need. 

There is a <strong>inverse relation between expected utility and experienced utility</strong>. The turning point is the purchase and subsequent use of the product.

<h2>Say NO to your Clients</h2>

It's been <a href="http://atomiq.org/archives/2006/03/capability_usability_and_feature_fatigue.html" target="_blank">common knowledge</a> for some time and we all kinda felt it. I can find plenty of useful features for my new search portal but the reason why <a href="http://www.google.com" target="_blank">google</a> is so successful is because they perfected their main task and <strong>prevented adding useful but unnecessary features</strong> to their portal.
So now you know why you should say NO to your clients when they brainstorm cool and sexy features. 

<h2>What you should do</h2>
<ul>
<li>Design products with just enough features to stimulate sales</li>
<li>Ensure the features are easy enough to use once the customers start using them.</li>
<li>Provide a variety of simpler application, each tailored to a particular task.</li>
<li>Remind your client and your team about the main task that enables their users to do something outstanding.</li>
</ul>]]></description>
		<wfw:commentRss>http://www.michaelgaigg.com/blog/2009/02/11/feature-fatigue-say-no-to-your-clients/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>UCD Method: Focus Groups</title>
		<link>http://www.michaelgaigg.com/blog/2008/12/17/ucd-method-focus-groups/</link>
		<comments>http://www.michaelgaigg.com/blog/2008/12/17/ucd-method-focus-groups/#comments</comments>
		<pubDate>Wed, 17 Dec 2008 23:59:14 +0000</pubDate>
		<dc:creator>Michael Gaigg</dc:creator>
				<category><![CDATA[Usability & UCD]]></category>
		<category><![CDATA[cons]]></category>
		<category><![CDATA[cost]]></category>
		<category><![CDATA[disadvantages]]></category>
		<category><![CDATA[discussion]]></category>
		<category><![CDATA[focus group]]></category>
		<category><![CDATA[gains]]></category>
		<category><![CDATA[method]]></category>
		<category><![CDATA[moderator]]></category>
		<category><![CDATA[output]]></category>
		<category><![CDATA[participants]]></category>
		<category><![CDATA[perform]]></category>
		<category><![CDATA[pros]]></category>
		<category><![CDATA[sample size]]></category>
		<category><![CDATA[UCD]]></category>
		<category><![CDATA[user-centered design]]></category>

		<guid isPermaLink="false">http://www.michaelgaigg.com/blog/?p=222</guid>
		<description><![CDATA[<h2 class="icon use">What it is</h2>
A focus group is a moderated discussion that lasts about two hours and covers a range of pre-selected topics.

In traditional focus groups, a screened (qualified target audience) group of respondents gathers in the same room. A moderator guides the group through a loosely structured discussion that probes attitudes about a client's proposed products or services. The moderator is typically given a list of objectives or an anticipated outline. Additional questions might serve to initiate open-ended discussions.

<h2 class="icon when">When to use</h2>
Requirements phase

<h2 class="icon cost">Cost</h2>
High

<h2 class="icon output">Output</h2>
Non-Statistical

<h2 class="icon sample-size">Sample Size</h2>
6-9 users

<h2 class="icon pros">Pro's / Gains</h2>
<ul>
	<li>Discover what users want/desire/belief</li>
	<li>Observe group dynamics and organizational issues</li>
	<li>Show users spontaneous reactions and ideas</li>
</ul>

<h2 class="icon cons">Con's / Disadvantages</h2>
<ul>
	<li>Don’t trust what people say or pretend to do</li>
	<li>Possible bias through specialized groups</li>
</ul>

<h2 class="icon how">How to perform</h2>

<ul>
	<li>Select <strong>representative participants</strong>.</li>
	<li>Identify <strong>problem area</strong> (what you want to learn).</li>
	<li>Prepare a <strong>script</strong> for the moderator to follow.</li>
	<li>Hire a <strong>skilled moderator</strong> (facilitator).</li>
	<li><strong>Allow flexibility</strong> during the test to keep the discussion flowing.</li>
	<li><strong>Tape and/or observe</strong> the test.</li>
	<li>Create <strong>good notes</strong> of the test.</li>
</ul>]]></description>
		<wfw:commentRss>http://www.michaelgaigg.com/blog/2008/12/17/ucd-method-focus-groups/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
