<?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>Lushai &#187; Approach and Process</title>
	<atom:link href="http://www.lushai.com/category/all-posts/approach-and-process/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lushai.com</link>
	<description>User Experience Design - Strategy, Interaction Design, Information Architecture</description>
	<lastBuildDate>Sat, 05 Nov 2011 21:21:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Define terminology &amp; jargons as part of your design process</title>
		<link>http://www.lushai.com/2011/10/20/define-terminology-jargons-as-part-of-your-design-process/</link>
		<comments>http://www.lushai.com/2011/10/20/define-terminology-jargons-as-part-of-your-design-process/#comments</comments>
		<pubDate>Wed, 19 Oct 2011 21:37:06 +0000</pubDate>
		<dc:creator>Lulu</dc:creator>
				<category><![CDATA[All Posts]]></category>
		<category><![CDATA[Approach and Process]]></category>
		<category><![CDATA[Experience Strategy]]></category>
		<category><![CDATA[Interaction Design]]></category>
		<category><![CDATA[Thoughts & Rants]]></category>

		<guid isPermaLink="false">http://www.lushai.com/?p=993</guid>
		<description><![CDATA[<p>The other night, I was up till quite late reading up on a popular portal solution. In the beginning, I thought everything made sense, and I was pretty happy that I “got it”. But after a while, probably about two hrs in, found myself googling or going to <a href="http://www.wikipedia.org">wikipedia</a> to find the definitions of every other technical word, even the terms I thought I understood at the start. I found myself getting more and more confused about the thing [...]]]></description>
		<wfw:commentRss>http://www.lushai.com/2011/10/20/define-terminology-jargons-as-part-of-your-design-process/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Our Approach</title>
		<link>http://www.lushai.com/2009/02/23/our-approach/</link>
		<comments>http://www.lushai.com/2009/02/23/our-approach/#comments</comments>
		<pubDate>Mon, 23 Feb 2009 10:39:20 +0000</pubDate>
		<dc:creator>Lulu</dc:creator>
				<category><![CDATA[Approach and Process]]></category>
		<category><![CDATA[methodology]]></category>
		<category><![CDATA[process]]></category>

		<guid isPermaLink="false">http://www.lushai.com/?p=59</guid>
		<description><![CDATA[<p>I&#8217;ve been asked a few times by friends and clients to write up the steps I take to produce the design documents that we give them. This is my attempt at putting a process or approach together. I think these constitute what we usually do at Lushai. I will update and refine it as I work on more projects. I&#8217;ll even put in a diagram.</p>
<p>So, here goes&#8230;</p>
<p>Lushai’s approach to projects is based on transparency, adaptability to clients’ requirements and quality. [...]]]></description>
		<wfw:commentRss>http://www.lushai.com/2009/02/23/our-approach/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

