<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.2" -->
<rss version="0.92">
<channel>
	<title>User Harmony</title>
	<link>http://userharmony.com/blog</link>
	<description>Cultivating harmony between software and users</description>
	<lastBuildDate>Mon, 21 Jun 2010 03:43:48 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>3 Steps to 1 Goal</title>
		<description><![CDATA[Observe. 
Innovate. 
Build. 
Happiness. 
]]></description>
		<link>http://userharmony.com/blog/2010/06/20/3-steps-to-1-goal/</link>
			</item>
	<item>
		<title>How to do user experience when engaged on a new client project?</title>
		<description><![CDATA[The challenge &#8211; fit in user experience at all stages of your agile project. I looked at the &#8220;IDEO way&#8220;.
Observation
It starts with observation. Observation should start with shadowing people, taking notes, taking photographs, and taking videos. This stage will establish the overall context for the problem solving exercise. The context will establish the end user [...]]]></description>
		<link>http://userharmony.com/blog/2010/04/11/how-to-do-user-experience-when-engaged-on-a-new-client-project/</link>
			</item>
	<item>
		<title>Are you developing self driven teams?</title>
		<description><![CDATA[During the course of helping clients execute their projects, I observed a common theme across industries. There was a disproportionate amount of project leaders who were strong &#8220;drivers&#8221; and were &#8220;making things happen&#8221;. However, beneath the surface revealed teams that became dependent on having such drivers in place.

So I went and re-read Steve Yegge&#8217;s landmark [...]]]></description>
		<link>http://userharmony.com/blog/2009/10/30/are-you-developing-self-driven-teams/</link>
			</item>
	<item>
		<title>10 ways to ensure failure to produce great enterprise software</title>
		<description><![CDATA[
Where do most enterprise software projects go wrong? As a software manager, how can you ensure that the next application your team is about to build will revolutionize your enterprise? Here are my top ten ways to ensure failure to raise the body of work beyond mediocrity:

Have no real vision behind the project: If the [...]]]></description>
		<link>http://userharmony.com/blog/2009/05/17/10-ways-to-ensure-failure-to-produce-great-enterprise-software/</link>
			</item>
	<item>
		<title>Made in China</title>
		<description><![CDATA[Progressing from the slideshow last week, I converted the presentation into a podcast. Watch it here. 

]]></description>
		<link>http://userharmony.com/blog/2009/04/05/made-in-china/</link>
			</item>
	<item>
		<title>Great philosophies underlie great products</title>
		<description><![CDATA[Ever since I first used hulu.com, I knew that it was a work of a great team. I was even more delighted to learn that the product was developed partly in China with the help of an offshore team. The core teams are located in Los Angeles, Chicago and Beijing.
From the CNN article, &#8220;Money, it [...]]]></description>
		<link>http://userharmony.com/blog/2008/10/06/great-philosophies-underlie-great-products/</link>
			</item>
	<item>
		<title>&quot;No matter how cool your interface, less would be better.&quot;</title>
		<description><![CDATA[How long will we keep building software that has 10 search boxes on its search page? Google launched in year 1999, and its user interface has one text field and two buttons(one too many in my opinion). Today we are still building screens with more than 50 items, numerous buttons, drop-downs, long scroll after scroll. [...]]]></description>
		<link>http://userharmony.com/blog/2008/10/06/no-matter-how-cool-your-interface-less-would-be-better/</link>
			</item>
	<item>
		<title>Let your code automatically open defects</title>
		<description><![CDATA[Opening defects is time consuming. So why not let the code automatically enter defects in your bug tracking system. Of course, this means your bug tracking software should provide ability to open defects via APIs, via Emails, or any other programmatic means. 
Second, all untrapped exceptions must be logged as defects automatically by the exception [...]]]></description>
		<link>http://userharmony.com/blog/2008/10/06/let-your-code-automatically-open-defects/</link>
			</item>
	<item>
		<title>Need for Speed</title>
		<description><![CDATA[When porting a thick client application to a web based application, there are some significant challenges that the team needs to think about. 
Let me illustrate this transition by hypothetically taking away some of your favorite thick client applications. Imagine your boss comes in one day, and tells you &#8220;We are getting rid of all [...]]]></description>
		<link>http://userharmony.com/blog/2008/10/06/need-for-speed/</link>
			</item>
	<item>
		<title>Performance and Usability &#8211; The missing link</title>
		<description><![CDATA[When an existing application is being replaced by a new application, performance and usability requirements become intricately linked. In case of data entry applications, what matters is the speed and agility with which the user can get through a given scenario. This is where things get tricky. The speed is not only a function of [...]]]></description>
		<link>http://userharmony.com/blog/2008/10/06/performance-and-usability-the-missing-link/</link>
			</item>
</channel>
</rss>
