<?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>Limina - Blog &#187; Hot Topics</title>
	<atom:link href="http://limina-ao.com/blog/category/hot-topics/feed/" rel="self" type="application/rss+xml" />
	<link>http://limina-ao.com/blog</link>
	<description>Observations, Issues, Events, &#38; Trends in User Experience Design</description>
	<lastBuildDate>Tue, 27 Dec 2011 07:15:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>OptionIt Launching&#8230;</title>
		<link>http://limina-ao.com/blog/2011/09/28/optionit-launching/</link>
		<comments>http://limina-ao.com/blog/2011/09/28/optionit-launching/#comments</comments>
		<pubDate>Wed, 28 Sep 2011 21:45:20 +0000</pubDate>
		<dc:creator>Jon</dc:creator>
				<category><![CDATA[Hot Topics]]></category>
		<category><![CDATA[Information Design]]></category>
		<category><![CDATA[Interactive Design]]></category>

		<guid isPermaLink="false">http://limina-ao.com/blog/?p=492</guid>
		<description><![CDATA[Keep your eye open for a fresh new Limina design hitting the streets this evening.  OptionIt allows it&#8217;s members to reserve their spot at any of their partners&#8217; events at a fraction of the cost.  New site should be live tonight: OptionIt.com]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-full wp-image-493" title="optionit-under-construction" src="http://limina-ao.com/blog/wp-content/uploads/2011/09/optionit-under-construction.png" alt="" width="657" height="442" />Keep your eye open for a fresh new Limina design hitting the streets this evening.  OptionIt allows it&#8217;s members to reserve their spot at any of their partners&#8217; events at a fraction of the cost.  New site should be live tonight: <a title="website" href="http://www.optionit.com">OptionIt.com</a></p>
]]></content:encoded>
			<wfw:commentRss>http://limina-ao.com/blog/2011/09/28/optionit-launching/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Gap &#8211; Lessons in a Logo Makeover Fail</title>
		<link>http://limina-ao.com/blog/2010/10/12/gap-lessons-in-a-logo-makeove-rfail/</link>
		<comments>http://limina-ao.com/blog/2010/10/12/gap-lessons-in-a-logo-makeove-rfail/#comments</comments>
		<pubDate>Tue, 12 Oct 2010 14:47:21 +0000</pubDate>
		<dc:creator>Jon</dc:creator>
				<category><![CDATA[Hot Topics]]></category>
		<category><![CDATA[Limina Perspective]]></category>
		<category><![CDATA[Social Web]]></category>

		<guid isPermaLink="false">http://limina-ao.com/blog/?p=415</guid>
		<description><![CDATA[We&#8217;ve been tracking this story for about a week now &#8211; trying to see where things would end up. Here&#8217;s just a brief overview an analysis, along with some interesting links on what you might have missed. On October 5th,  2010 &#8211; GAP, inc.  quietly swapped out their logo on their website (soft launch) without [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://limina-ao.com/blog/wp-content/uploads/2010/10/logo_fail.png"><img class="aligncenter size-full wp-image-416" title="logo_fail" src="http://limina-ao.com/blog/wp-content/uploads/2010/10/logo_fail.png" alt="" width="601" height="279" /></a></p>
<p>We&#8217;ve been tracking this story for about a week now &#8211; trying to see where things would end up.  Here&#8217;s just a brief overview an analysis, along with some interesting links on what you might have missed.</p>
<p><strong>On October 5th,  2010</strong> &#8211; GAP, inc.  quietly swapped out their logo on their website (soft launch) without warning or announcement.</p>
<p><strong>On October 6th, 2010</strong> -  <a href="http://www.underconsideration.com" target="_blank">UnderConsideration</a> posted an article &#8220;<a href="http://www.underconsideration.com/brandnew/archives/dont_mind_the_gap_or_the_square.php" target="_blank">Don&#8217;t Mind the Gap, or the Square</a>&#8221; where they provided a little background on the company, the history of the logo and some initial reactions to the new logo.</p>
<p>Gap&#8217;s Facebook Page starts getting customer comments on the new look&#8230; and Gap responds:</p>
<blockquote><p>Thanks for everyone’s input on the new logo! We’ve had the same logo for  20+ years, and this is just one of the things we’re changing. We know  this logo created a lot of buzz and we’re thrilled to see passionate  debates unfolding! So much so we’re asking you to share your designs. We  love our version, but we’d like to see other ideas. Stay tuned for  details in the next few days on this crowd sourcing project.<br />
— <a href="http://www.facebook.com/gap?v=wall&amp;story_fbid=159977040694165" target="_blank">Gap’s Facebook status update</a></p></blockquote>
<p><strong>October 7th, 2010</strong> &#8211; <a href="http://www.idsgn.org/posts/gap-turns-to-crowdsourcing/" target="_blank">idsng.org</a> posts a roll-up of reactions to the new logo and Gap&#8217;s plans to crowd-source, or not.</p>
<p><strong>October 8th, 2010</strong> -  UnderConsideration pulls together the Mother-load post &#8220;<a href="http://www.underconsideration.com/brandnew/archives/follow-up_gapgate.php" target="_blank">Followup: Gap Gate</a>&#8221; &#8211; demonstrating that gap consumers, designers, bloggers and the social web weren&#8217;t going to swallow the new logo and were ready to poke fun and actually compete for the title of &#8220;I designed the new Gap logo&#8221;</p>
<p>The <a href="http://gapify.tumblr.com/" target="_blank">Gapify Tumblr</a> demonstrated how asinine the design decisions were and how applying them completely oversimplify and disregarded the key brand identity in any logo.</p>
<p>And my personal favorite <a href="http://craplogo.me" target="_blank">CrapLogo.Me</a> took a more in-your-face approach to describe how they feel about the new logo by creating a Gap logo meme.</p>
<p>By far the most controversial of reactions (see below)  is Gap&#8217;s marketing pivot &#8211; &#8220;Let&#8217;s crowd source the logo design&#8221; which spurs into motion a <a href="http://99designs.com/logo-design/contests/design-better-gap-logo-community-project-54693" target="_blank">$500 logo design competition</a> by <a href="http://www.99designs.com" target="_blank">99 Designs</a>.  The competition rang in a healthy 4660 entries &#8211; which spanned  wide range of humorous satirical design to some legitimate attempts to resolve the company&#8217;s desire to move their brand forward.  While this competition is not officially sponsored by Gap, we&#8217;re awaiting to learn the outcome of the, now closed, competition and what 99 Designs intends to do with the winning design.  <strong>(UPDATE 10.18.10 &#8211; below)</strong></p>
<p>Post-post Analysis Post: Everyone is all excited about crowd-sourcing design..  aren&#8217;t they?  Wait&#8230;  not everyone.  Crowd-sourcing has done wonders for open technology platforms like Drupal and Jquery and opened content platforms like Wikipedia,  but is it right for design?  The main complaint to the world of crowd sourced design is that it appeals to the bottom feeder in design consumers and the desperation of a struggling designer which has a downward spiraling effect on the design market.   Mike Monteiro from Mule Design sums it up in his <a href="http://weblog.muledesign.com/2010/10/dear_gap_i_have_your_new_logo.php" target="_blank">&#8220;Gap, I have your new logo&#8221;</a> post from Off the Hoof.  Another jab at 99 Designs and Crowd sourced design at <a href="http://bonfx.com/gaps-new-crowdsourced-logo-unveiled-after-rebranding-fail/" target="_blank">BonFX</a>.</p>
<p><strong>Oct 11, 2010</strong> &#8211; Gap Inc. Issues an official press release- <a href="http://www.gapinc.com/public/Media/Press_Releases/med_pr_GapLogoStatement10112010.shtml" target="_blank">&#8220;Gap Listens to Customers and Will Keep the Classic Blue Box Logo&#8221;</a></p>
<p><strong>Oct, 11, 2010</strong> &#8211; AP Marketing Writer, Emily Fredrix,  picks up the story and posts:  <a href="http://hosted.ap.org/dynamic/stories/U/US_GAP_LOGO_FLAP" target="_blank">Gap&#8217;s logo back to blue after fans gripe about new</a> &#8211; now headlining on <a href="http://finance.yahoo.com/news/Gaps-logo-back-to-blue-after-apf-3578440916.html" target="_blank">Yahoo.com</a> Oct.12, 2010.</p>
<p><strong>Oct 12, 2010</strong> &#8211; Richard Grefé, Executive Director of AIGA| the professional association for design, (re) posts his <a href="http://www.aiga.org/content.cfm/how-do-businesses-balance-crowd-participation-and-design" target="_blank">position on Spec work with a letter sent to the Gap</a> on October 7th.</p>
<p>If you want quality, if you have respect for the design process  (research, conceptualization, design, testing), along with an ounce of  self respect &#8211; you&#8217;ll pay the designer the true value of the labor and  the product.</p>
<p>Why does Limina care about this?  Our customers are primarily  software, web-app and website design oriented, looking for ways to  improve the user experience.  While this resides heavily in user  research and user centered design, it often touches and occasionally  includes heavy consideration for brand identity.  We don&#8217;t take the  subject lightly &#8211; use acceptance can make or break a product.  As we&#8217;ve  seen with <a href="../2009/03/25/ux-for-breakfast-brand-vs-usability/" target="_blank">Tropicana</a> and now with Gap &#8211; this level of market rejection can be costly &#8211;  fortunately for Gap they didn&#8217;t roll out the new design across all of  the product lines, stores, packaging, bags and collateral.</p>
<p><strong>UPDATE 10.17.10</strong> &#8211; Things just went from bad to worse.  99Designs sent out a blast to the community to participate in &#8220;voting&#8221; for the best Gap logo design.  It&#8217;s as if the 99Designs crew got cold feet  in fear of a backlash from the design community if they picked a weak design.  So they&#8217;re throwing it back at the crowd.  &#8220;Here&#8230;  you guys sort out this mess&#8221;.</p>
<p>-Jon Fukuda</p>
]]></content:encoded>
			<wfw:commentRss>http://limina-ao.com/blog/2010/10/12/gap-lessons-in-a-logo-makeove-rfail/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>IDEO &#8211; The Future of the Book</title>
		<link>http://limina-ao.com/blog/2010/10/11/ideo-the-future-of-the-book/</link>
		<comments>http://limina-ao.com/blog/2010/10/11/ideo-the-future-of-the-book/#comments</comments>
		<pubDate>Mon, 11 Oct 2010 13:42:08 +0000</pubDate>
		<dc:creator>Jon</dc:creator>
				<category><![CDATA[Hot Topics]]></category>
		<category><![CDATA[Information Design]]></category>
		<category><![CDATA[Interactive Design]]></category>
		<category><![CDATA[Limina Perspective]]></category>

		<guid isPermaLink="false">http://limina-ao.com/blog/?p=407</guid>
		<description><![CDATA[It&#8217;s clear that the digitization of the Book has opened great possibilities for changing the way we consume, contextualize and engage in literature. Below is a post I found on Core 77  which shares IDEO&#8217;s exploration of various ux themes and concepts for interacting with digital books. (Reblog) IDEO released a five-minute video exploring the [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s clear that the digitization of the Book has opened great possibilities for changing the way we consume, contextualize and engage in literature. Below is a post I found on Core 77  which shares IDEO&#8217;s exploration of various ux themes and concepts for interacting with digital books.</p>
<p><a href="http://www.uxbooth.com/resources/the-future-of-the-book/"><img alt="" src="http://www.core77.com/blog/assets_c/2010/09/Coupland_HiRes-thumb-468x312-6523-thumb-468x312-6524.jpg" title="IDEO&#039;s - Future of the Book" class="alignnone" width="468" height="312" /></a><br />
(Reblog)</p>
<blockquote><p><a href="http://www.ideo.com/">IDEO</a> released a five-minute  video exploring the future of digital books. Their illustrated concepts  highlight some interesting opportunity areas in the publishing industry  through three distinct reading experiences:</p>
<p><em>Nelson</em> reinforces books as critical thinking tools,  providing multiple perspectives, references, and current conversations  on a single subject. The layers of information beyond the book itself  provide greater context and encourages a deeper dive into the book  throughout history and into the future.</p>
<p><iframe src="http://player.vimeo.com/video/15142335" width="400" height="225" frameborder="0"></iframe>
<p><a href="http://vimeo.com/15142335">The Future of the Book.</a> from <a href="http://vimeo.com/ideo">IDEO</a> on <a href="http://vimeo.com">Vimeo</a>.</p>
<p><em>Coupland</em> addresses the challenge to stay on top of the  thinking and writing in our world and professional field that so many of  us feel. Readers can easily keep up with &#8220;must-reads&#8221; by following what  colleagues are reading and interact with them through &#8220;book clubs&#8221; and  other social layers (discussions, suggestions, lists, purchases) to help  each other share and learn.</p>
<p><em>Alice</em> explores new ways for users to interact and affect  written narratives by introducing non-linear and game mechanics to  reading. By introducing the reader&#8217;s active participation, this concept  &#8220;blurs the lines between reality and fiction.&#8221; Certain interactions  allow the reader to transcend traditional media by utilizing geographic  location, communication with characters, and user contribution to  storyline and plot.</p>
<p>A very cool blue sky project from IDEO to say the least. I enjoyed  the way they chose to compartmentalize the functionality rather than  attempting to redefine the book in a single all-inclusive interface (a  failure we see in most of these concept projects). This project, and  examples appearing all over the industry, only further prove that the  future of books in the digital age does not lie in single solution but  rather a utilization of technology to better address the wants and needs  of users to share, interact, and learn more through specialized design  solutions. We are certainly on the precipice of a whole new world for  this morphed understanding of the &#8220;book.&#8221;If you are interested in hearing more about IDEO&#8217;s project, check out  the interview with two of the project&#8217;s designers, Duane Bray and  Robert Lenne, on <a href="http://beta.wnyc.org/shows/bl/2010/sep/21/future-books/">WNYC&#8217;s Brian Lehrer Show</a>. There&#8217;s also a conversation about the topic going on over at <a href="http://www.facebook.com/ideobigconversations">IDEO&#8217;s Facebook page</a>.</p>
<p><em>Video and photos from <a href="http://www.ideo.com/">IDEO</a>.</em></p></blockquote>
<p>This post was originally posted by Willem Van Lancker, 21 Sep 2010</p>
]]></content:encoded>
			<wfw:commentRss>http://limina-ao.com/blog/2010/10/11/ideo-the-future-of-the-book/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Agile Usability &#8211; How we see it.</title>
		<link>http://limina-ao.com/blog/2009/12/17/agile-usability-how-we-see-it/</link>
		<comments>http://limina-ao.com/blog/2009/12/17/agile-usability-how-we-see-it/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 03:14:12 +0000</pubDate>
		<dc:creator>Jon</dc:creator>
				<category><![CDATA[Agile Usability]]></category>
		<category><![CDATA[Hot Topics]]></category>
		<category><![CDATA[Limina Perspective]]></category>

		<guid isPermaLink="false">http://limina-ao.com/blog/?p=141</guid>
		<description><![CDATA[We get a ton of hits on our Agile Approach page so I thought I&#8217;d take an opportunity to give some more background on our methods and share some of our experiences.  The Limina Team comes from a traditional Waterfall or Rational Unified Process software development background.  Our consulting history and practice methodology is an [...]]]></description>
			<content:encoded><![CDATA[<p>We get a ton of hits on our <a href="http://www.limina-ao.com/approach/agile.html" target="_self">Agile Approach</a> page so I thought I&#8217;d take an opportunity to give some more background on our methods and share some of our experiences.  The <a title="Limina Team" href="http://www.limina-ao.com/about/our_team.html" target="_self">Limina Team </a>comes from a traditional <a href="http://www.limina-ao.com/approach/waterfall.html" target="_self">Waterfall</a> or Rational Unified Process software development background.  Our consulting history and practice methodology is an adaptation of best practices developed in-house by user experience professionals and collaborators who&#8217;s expertise run the full spectrum of user interface; research, analysis, strategy, management, interaction modeling, information architecture, design and development.  As a result, we have developed a suite of services that can be applied throughout the full span of the product development lifecycle.</p>
<p>As a practice, our methodology has been flexible enough to add value to every client engagement in <a href="http://www.limina-ao.com/clients" target="_self">our portfolio</a>.  As our team engaged on increasingly more frequent Agile/<a title="SCRUM Definition" href="http://en.wikipedia.org/wiki/Scrum_(development)">SCRUM </a>driven teams, a trend which began for us in 2006, we needed to make some adaptations to keep pace with rapid iterations.  The following is a rough breakdown of the adaptations we made by &#8220;activity&#8221;.</p>
<p>We tool a look at the activities and deliverables we execute in a more verbose and lengthy cycle and dissected each phase to   determine which tasks and deliverables dovetail with the Project, Incremental Release and Sprint cycles of an agile project life cycle. Each level invariably incorporates tasks and deliverables from the traditional Analysis, Definition, Design, Development phases.  Here&#8217;s what we came up with:</p>
<p><strong>Product Cycle: Assuming 6-9 months.</strong></p>
<p>Intense Observation and Analysis activity in the all important &#8220;Phase Zero&#8221; a period of three to six weeks.  In the absence of the waterfall lead time, this is the cycle where UX research seeks to identify the following in rank order:</p>
<ul>
<li>Task / Activity Model</li>
<li>User Role Model</li>
<li>Business Stakeholder Goals</li>
<li>User Goals</li>
<li>Competitive Analysis</li>
</ul>
<p><strong>Release planning: &#8220;Iteration Zero&#8221;.</strong></p>
<p>While rough concepts are being established to determine technical frameworks and baseline use cases, the UX team takes 2 weeks to elaborate on the primary storyboards to cover feature definitions in the first iteration.</p>
<p>The At this phase, requirement gaps have been identified, rudimentary user typologies have been identified, development road map has been established based on technical complexity, feasibility, business benefit and user benefit.  Relevant personas for the user stories and features are drafted, usage scenarios are  drilled down, the draft interaction model is established and the associated process flows and wire frames are generated.  This iterative cycle is a  lather, rinse,and repeat.</p>
<p>Ideally after 2 weeks iteration zero kicks off user stories, wire frames and mockups and will be available for itteration one development work.</p>
<p>While UX team is cranking out user stories and related assets for iteration two, custom asset creation and spot UI reviews run in parallel in support of iteration one.</p>
<p><strong>This  completes the </strong><strong>lather, </strong><strong>rinse, repeat cycle.</strong></p>
<p>Meanwhile, persona assets, user stories and related assets are aggregated up for incremental release review.  Any usability or user experience hurdles are triaged and assessed for re-insertion into the iteration plan.  Instructive text, user help documentation are written and evaluated for release.</p>
<p><strong>Benefits and Lessons Learned</strong></p>
<p>As a seasoned UX practitioner, I know the value of getting the requirements right before writing a line of code and my initial reaction to agile development was harsh to say the least.  It&#8217;s just a temporary jolt.  Once you get in the swing of rapid iteration and continuous design, you barely miss lengthy requirements gathering and documentation.  The clear benefit is low upfront project spend and near term return on investment.  In traditional models, upfront costs on analysis, strategy, definition and design don&#8217;t immediately translate to rapid deployment.  And the upfront cost is significantly higher to account for  end to end specification prior to development.</p>
<p>In an agile team, the analysis, strategy and definition are more light weight and design an development run in parallel.  If high yielding business benefits are addressed in the early release, you will be seeing a return on the investment   earlier than you would have if you staggered the design and development in waterfall fashion.</p>
<p>One major lesson learned for Agile UX in practice:  It is absolutely critical to get one or two iterations ahead of the development team. One slip, and you lose any runway for giving yourself the time  necessary to construct successful solution to meet the needs of your users.</p>
<p>Happy Sprinting UXers</p>
<p>-Jon Fukuda</p>
<p><!--digg--></p>
]]></content:encoded>
			<wfw:commentRss>http://limina-ao.com/blog/2009/12/17/agile-usability-how-we-see-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Ubiquitous Computer Redux</title>
		<link>http://limina-ao.com/blog/2009/08/03/the-ubiquitous-computer-redux/</link>
		<comments>http://limina-ao.com/blog/2009/08/03/the-ubiquitous-computer-redux/#comments</comments>
		<pubDate>Mon, 03 Aug 2009 16:47:22 +0000</pubDate>
		<dc:creator>Kipp</dc:creator>
				<category><![CDATA[Hot Topics]]></category>
		<category><![CDATA[Limina Perspective]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Information Visualization]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[ubiquitous computing]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://limina-ao.com/blog/?p=295</guid>
		<description><![CDATA[Years ago, various UX gurus touted the coming of the ubiquitous computer– every device would have a computer built in and they would all talk to one another. Mark Weiser coined the term while at Xerox PARC in 1988 and Alan Kay of Apple called this the “Third Paradigm”. It began with mainframe computers (one [...]]]></description>
			<content:encoded><![CDATA[<p><!--digg--></p>
<p>Years ago, various UX gurus touted the coming of the ubiquitous computer– every device would have a computer built in and they would all talk to one another. Mark Weiser coined the term while at Xerox PARC in 1988 and Alan Kay of Apple called this the “Third Paradigm”. It began with mainframe computers (one compute -&gt; many people), followed by the personal computer (one person -&gt; one computer), bringing us to ubiquitous computing (one person -&gt; many computers). Ubiquitous computing can be considered the opposite of virtual reality, rather than surrounding the person within a computer-generated environment, ubiquitous computing surrounds the individual with computers (in between, lies augmented reality). In other words, computers are made to live in our world and not the other way around. Donald Norman updated the term in 1999 and used the term invisible computer and information appliance to refer to the coming revolution of devices that that would have embedded computer chips and effortlessly communicate with one another.</p>
<p>To some degree that has happened, even if you disregard the multiple computers that most people own (desktop, laptop, netbook) even the simple electronic devices that surround us have considerable computing power. According to futurists, my toaster should be talking with my refrigerator to know what kind of bread I have and how I like it toasted or to notify my online grocer that I only had two slices left (some of the early predictions were pretty bizarre and stretched the definition of “usefulness”). But why did their prediction fail to materialize and we’re all living in remedial houses rather than the smarthouse we were promised? Even though my appliances are much smarter than the ones my parents had there is little chatter between my toaster, coffeemaker, or any other smart appliances in my household. Most of the things I own don’t really need to communicate with one another, nor do they have much to say to Net. In fact, most of devices don’t have much to say about anything. My refrigerator still doesn’t know when I’m almost out of orange juice, though, given <a href="http://limina-ao.com/blog/2009/03/25/ux-for-breakfast-brand-vs-usability/" target="_blank">Tropicana’s new packaging</a> I wish it could tell me what kind I just bought and why it was not the one I wanted. Is ubiquitous computing just one more failed prediction like fifth generation computing (expert systems) or has ubiquitous computing shifting to something else?</p>
<p>Apple takes an interesting two-pronged approach to ubiquitous computing, instead of everything communicating with everything else, the iPhone says – “talk to me, and I’ll talk to those that need to know” and asks “no need for multiple devices, just give me a simple focused task and I can do that.” The latter approach is familiar to everyone who has ever downloaded an app from the iTunes Store, while the former is somewhat new and is made possible by the introduction of OS 3.0 and APIs that allow for easy communication with other devices. The application approach is akin to a universal Turing machine, and the API model is more like a universal interface. It’s not quite two-pronged, rather applications are developed that allow devices to integrate seamlessly with iPhone – I consider it a different enough model as to warrant it’s unique status. For example, Johnson &amp; Johnson made a bit of splash at the Apple developer conference with their demo of LifeScan a tool that integrates a glucose monitor with the iPhone and provides a range of features from simple visualizations of historical data to food tracking to uploading data to your healthcare provider.</p>
<p><img class="alignnone size-full wp-image-297" src="http://limina-ao.com/blog/wp-content/uploads/2009/08/glucoipod.jpg" alt="glucoipod" width="458" height="242" /></p>
<p>Whether or not one believes the hype surrounding LifeScan (is it vaporware or will it see production?), it’s easy to imagine a range of medical devices (or any category of devices) all communicating through the iPhone, all using the iPhone’s screen and its Samsung S5PC100 processor &#8211; one person, one user interface with many devices.</p>
<p><img class="alignnone size-full wp-image-296" src="http://limina-ao.com/blog/wp-content/uploads/2009/08/bxcvbxcvb.jpg" alt="bxcvbxcvb" width="298" height="268" /></p>
<p>I’m not sure if Apple is going to be the one that finally surrounds us with computers or smart devices, but I think their model puts us in more control than the previous one of smart appliances “deciding” for us – when to order OJ, how to toast my bread, etc. My toaster can simply communicate with my iPhone, and I can set how the bread is toasted (silly ideas never really die, they just move around the ether). I think the future is looking less like <em>Terminator Salvation</em> and maybe more like <em>Star Trek</em> [Note: It is very hard to find good science fiction movies or shows that paint a bright picture].</p>
<p>&#8211;kipp</p>
]]></content:encoded>
			<wfw:commentRss>http://limina-ao.com/blog/2009/08/03/the-ubiquitous-computer-redux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Crowdsourcing Usability  &#8211; Or Not?</title>
		<link>http://limina-ao.com/blog/2009/07/01/crowdsourcing-usability-or-not/</link>
		<comments>http://limina-ao.com/blog/2009/07/01/crowdsourcing-usability-or-not/#comments</comments>
		<pubDate>Wed, 01 Jul 2009 17:10:26 +0000</pubDate>
		<dc:creator>Jon</dc:creator>
				<category><![CDATA[Agile Usability]]></category>
		<category><![CDATA[Hot Topics]]></category>
		<category><![CDATA[Limina Perspective]]></category>
		<category><![CDATA[Software Usability]]></category>
		<category><![CDATA[Crowd-sourcing]]></category>
		<category><![CDATA[remote user testing]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[User Research]]></category>

		<guid isPermaLink="false">http://limina-ao.com/blog/?p=240</guid>
		<description><![CDATA[There have been some recent crowd-sourcing business models making their way on the Usability Research and User Experience Design scene.  The crowd source value proposition is, &#8220;High Volume Results &#8211; Cheap&#8221; &#8211; with some important variables like: Quality, Usefulness, Relevance, Focus, Strategy, and more. How do you make the right decision on whether or not [...]]]></description>
			<content:encoded><![CDATA[<p><!--digg--></p>
<p>There have been some recent crowd-sourcing business models making their way on the Usability Research and User Experience Design scene.  The crowd source value proposition is, &#8220;High Volume Results &#8211; Cheap&#8221; &#8211; with some important variables like: Quality, Usefulness, Relevance, Focus, Strategy, and more.</p>
<p>How do you make the right decision on whether or not to crowd-source UX research for your project/product and where will you get the most yield for your time, money and energy?  Here&#8217;s a quick review of Feedback Army and Loop 11 as well as some tips for your back pocket.</p>
<h2><strong>FeedbackArmy</strong></h2>
<p style="text-align: center;"><a href="http://www.feedbackarmy.com"><img class="aligncenter" title="Feedback Army" src="http://farm3.static.flickr.com/2582/3676028476_c361c92437.jpg" alt="" width="456" height="408" /></a></p>
<p><strong>What is it?</strong></p>
<p>We first heard of <a title="Feedback Army" href="http://www.feedbackarmy.com" target="_blank">Feedback Army</a> back in January &#8217;09.  This site is almost exactly what you think it might be.</p>
<ol>
<li>You post up a URL and a list of questions/criteria to evaluate against (3-6 recommended)</li>
<li>You select the number of responders to your posting (3 tiers &#8211; 10 users for $10, 25 users for $23 and 50 users for $40)</li>
<li>Make a payment, wait and watch the reviews roll in.</li>
</ol>
<p><strong>What do you get?</strong></p>
<p>Just what the site claims you get: &#8220;Simple, Cheap &#8216;Usability Testing&#8217; for your Website.&#8221;</p>
<p>Depending on your questions and the range of responses you select, you have some variable control on the quality of the responses.  The site allows you to reject responses that are not of the quality you feel is deserving of $1.00 (or less depending on how many you selected).  The site has some tips on usability testing and some guidance on how best to use the service with a nice little endorsement for Steve Krug&#8217;s &#8220;<a title="the book" href="http://www.amazon.com/dp/0321344758/?tag=googhydr-20&amp;hvadid=2481203545&amp;ref=pd_sl_pb7ngvstp_e#reader" target="_blank">Don&#8217;t Make Me Think</a>&#8220;.  For what you pay, you get a fair shake.</p>
<p>As part of my research, I read over comments in the <a title="Example reviews" href="http://www.feedbackarmy.com/samples.slp" target="_blank">sample reviews</a>, I submitted my own request for review, assessed <a title="The Results" href="http://www.feedbackarmy.com/get_feedback.slp?url=http%3A%2F%2Fwww.limina-ao.com&amp;code=f8d4e459a452228e91805e5796dfaa9b" target="_blank">the responses</a> and I also nosed around some <a title="Usability Post - On Feedback Army" href="http://www.usabilitypost.com/2009/01/23/feedback-army-review/" target="_blank">discussion forums</a> where Feedback Army was the topic de jour.</p>
<p style="text-align: center;"><img class="aligncenter" title="Limina on Feedback Army" src="http://farm4.static.flickr.com/3615/3676028976_28337b85bd.jpg" alt="" width="449" height="324" /></p>
<p>Certainly, this service has it&#8217;s benefits (particularly on your bottom line) but there are the typical responses from folks disappointed by their own misguided expectations.  Look, you can&#8217;t use a service like this, then complain when you&#8217;re not handed a glossy analysis of your user findings broken down by persona &amp; scenario that map 1 to 1 with your research goals.  It just won&#8217;t happen.  So when you get shorthand &#8220;unintelligent&#8221; lol-speak responses you really can&#8217;t complain.  Some users may/may not follow your posting to the letter and may spout off whatever comes to mind&#8230;  that&#8217;s the level of expectation you should have going in.</p>
<p><strong>What you don&#8217;t get&#8230;</strong></p>
<p>User Demographics &amp; Targeted Personas &#8211; you&#8217;re dreaming.  The reviewer pool comes from Amazon&#8217;s <a title="Amazon's Mechanical Turk" href="http://www.mturk.com" target="_blank">Mechanical Turk</a> &#8211; a crowd-sourcing work-in-progress.  While there are advantages here, there is limited control over who is actually doing the work.  The m-turk pool is 70% American&#8230; combine that with Feedback Army&#8217;s English only UI framework, and you&#8217;re limited to US domestic testing.</p>
<p>Quantitative Metrics &#8211; You won&#8217;t get time to completion and conversion rates,  and industry benchmarks.  If you outfit your test environment with <a title="Google Analytics" href="http://www.google.com/analytics/" target="_blank">Google Analytics</a>, you can get at some success metrics around goals, popular content, and bounce rates, but with limited specificity on who&#8217;s feedback maps to which metrics.</p>
<p>Qualitative Metrics  &#8211; You can get if you&#8217;re explicit about ratings, but you&#8217;ll have to compile your own report if you want the pretty charts.</p>
<p>A Usability Report &#8211; this one is all you &#8211; if you played your cards right, you can get some decent raw feedback to compile into a report, but this requires a lot of planning.</p>
<p><strong>How to make up the difference:</strong></p>
<p>What are your research goals, what candidate  features/functions to test, what evaluation criteria, etc?  Ideally, you run a series of these to arrive at a more comprehensive view of your product&#8217;s usability, and compile the report in the end.  Hiring a consultant or using an internal dedicated resource to own this task will help ensure the value added direction setting and iteration planning for your product post feedback solicitation.</p>
<h2><strong>Loop 11</strong></h2>
<p style="text-align: center;"><img src="file:///C:/Users/JONFUK%7E1/AppData/Local/Temp/moz-screenshot.jpg" alt="" /><a href="http://www.loop11.com"><img class="aligncenter" title="Loop 11 Home Page" src="http://farm3.static.flickr.com/2565/3677692415_9eb5c7e6a7.jpg" alt="" width="497" height="470" /></a></p>
<p>More recently we took a look at <a title="Loop 11" href="http://www.loop11.com" target="_blank">Loop 11</a>.  Currently in private beta, Loop 11 is hooking up some usability testing bells and whistles.  I used &#8216;quotes&#8217; around &#8220;usability testing&#8221; on my FeedbackArmy review because it&#8217;s really just a feedback machine.  Loop 11, however, has scratched the surface on tackling the tough stuff: Targeted Personas, Quantitative Metrics, Industry Benchmarks, and more.</p>
<p><strong>What <span style="text-decoration: line-through;">do</span> will you get?</strong></p>
<p>To be honest, I can&#8217;t tell you everything&#8230;  Loop 11&#8242;s closed beta is by invitation only.  Here&#8217;s what the site claims:</p>
<p><a href="http://www.loop11.com/media/images/screenshots/create.jpg"><img class="alignleft" style="margin-left: 15px; margin-right: 15px;" title="Create User Test" src="http://farm3.static.flickr.com/2542/3678506574_2767f5afee_m.jpg" alt="" width="132" height="93" /></a><strong>Create a user test. </strong> This is a lightweight form, but it takes more thought and detail than simply posting a URL.  A 3 step set up walks you through adding test details, tasks &amp; questions and additional test options. The demo suggests you can organize tests into &#8220;projects&#8221; and save tests as templates.  (nice touch)</p>
<p><a href="http://www.loop11.com/media/images/screenshots/invite.jpg"><img class="alignleft" style="padding: 15px;" title="Invite Users" src="http://farm3.static.flickr.com/2621/3678506632_1d7057e05f_m.jpg" alt="" width="131" height="92" /></a><strong>Invite test participants.</strong> This looks like a nice set of options: Get link to user test: presumably, you can send it out to a predetermined list of users (the ideal scenario), create pop-up invitation for your site: this gives you random users which may or may not be what you&#8217;re looking for (less ideal) or purchase from their panel users (needs investigation).  The site claims separation of test participants, making data roll up and drill down more interesting.</p>
<p><a href="http://www.loop11.com/media/images/screenshots/analyse.jpg"><img class="alignleft" style="margin: 15px;" title="Testing Analysis" src="http://farm4.static.flickr.com/3612/3677692605_018f28431c_m.jpg" alt="" width="131" height="92" /></a><strong>Everyone loves dashboards&#8230;</strong> so why not, a nice dashboard to give you high level data on average page views, avg. time per page, avg. task completion rate and average industry completion rates&#8230; That&#8217;s right, I said Industry Benchmarks.  Now that&#8217;s a rich claim &#8211; noting their closed beta partners, they&#8217;ve picked Amazon, Ikea, HSBC, Toyota&#8230;  these will be your benchmarks folks!  Not a bad competitive pool.  Well done Loop.</p>
<p>Here is a list of metrics you can get in the dashboard:</p>
<table style="height: 119px;" border="0" width="575" align="center">
<tbody>
<tr>
<td>
<ul>
<li>Task completion rate</li>
<li>Time per task</li>
<li>Most common success page</li>
<li>Most common fail page</li>
</ul>
</td>
<td>
<ul>
<li>Most common first click</li>
<li>Most common navigation path</li>
<li>Detailed participant path analysis</li>
<li>Number of page views to complete tasks</li>
</ul>
</td>
</tr>
</tbody>
</table>
<p><strong>What you<span style="text-decoration: line-through;"> don&#8217;t </span>might not get.</strong></p>
<p>You already know that I can&#8217;t get a good handle on the truth here based on their current closed beta status.  But here&#8217;s a list of assumption you can make based on what they&#8217;ve exposed.  I found a posting by <a href="http://www.seosmarty.com/ann-smartys-profile/" target="_blank">Ann Smarty</a> who somehow got into their beta, she posted a light review <a title="Ann Smarty - Loop 11 post" href="http://www.searchenginejournal.com/test-your-site-usability-with-loop11/10853/" target="_blank">here</a>.</p>
<p>Validated qualitative metrics &#8211; you may get ratings, but you miss out on non-explicit reactions.  The classic,&#8221;users will say one thing but do another&#8221; is always in effect- you&#8217;ll get their feedback, but miss facial expressions, eye tracking, mouse hovering, heat mapping and general behavior surrounding their remarks.</p>
<p>That&#8217;s about it, it looks like you get a good set of data collection and analysis features &#8211; you still have to set up your test(s) properly.  This means well thought out targeted test goals and participant recruitment.</p>
<h2><strong>Online User Testing Service/Tool Limitations:</strong></h2>
<p>If you&#8217;ve found yourself staring down the barrel of some usability crowd-source projects you&#8217;re most likely dealing with tight time-frames and or budgets and you&#8217;ve ruled  out a lengthy and potentially costly full blown usability study.  What tips can you learn from user research professionals to make the most of your crowd-sourced efforts and build a design strategy from your study outputs?</p>
<p>1) You can&#8217;t meet everyone&#8217;s needs.  Take some time to look over the feedback and group them into &#8220;UI themes&#8221; or &#8220;issue categories&#8221;.  There will always be outliers &#8211; if your study was targeted and you knew the demographic weight of missing the mark on an outlier, then you can factor them in &#8211; or, if this outlier hit the exact note that all of the others missed &#8211; the note you have been attempting to hit&#8230;  then factor them in, but be careful not to upset the balance of maintaining a clear grasp of mass appeal.  You can alway run multiple targeted feedback sessions once you know what your issue categories are. Try your hand at feedback and observation analysis you may find affinity diagramming or mental modeling useful, but don&#8217;t forget to segment and simplify your feedback &#8211; &#8220;verb + noun = atomic task&#8221;.</p>
<p>2) <a title="User Personas" href="http://www.limina-ao.com/services/research.html#userpersonas" target="_blank">User segmentation and personas</a>.  Getting at the psychographics and demographics of your user takes a little extra time &amp; thought and has very real user experience implications.  While no two users on any given system are the same, you can loosely characterize their behavior and relationship to information, objects and tasks into 3-6 types.  ex. Novice, Intermediate, Advanced, Specialist, etc.  The more comprehensive your view of your users going into a study, the more focused your test and test results can be.</p>
<p>3) Reconciliation &#8211; <a href="http://www.limina-ao.com/approach/observe.html" target="_blank">User requirements</a> and business requirements don&#8217;t always map1:1 to each other, and the technical architecture may or may not support all of the requirements. Map out your requirements into a functionality matrix where you look at all of the system functions and features, making sure that you account for all business and user requirements (using excel helps you stay concise and color coded).  Rank each item by business benefit, user benefit and technical complexity (H/M/L).  Use the matrix to build an iteration plan based on your ranking.</p>
<p>4) Mapping study results to information and interaction <a title="UX Strategy" href="http://www.limina-ao.com/services/strategy.html" target="_blank">design strategy</a>.  You may have a head for this, and if you do, you&#8217;ve most likely covered your bases, but it never hurts to get an outside opinion.  Great design is rarely achieved without a great deal of planning.  Knowing where you are, where you&#8217;ve come from and where you&#8217;re going at all points of development can keep your tests and iteration plans focused and practical.  Understanding how to meet the needs of your users in rapid order with a long range view of feature extensibility will go a long way towards keeping your product on track.</p>
<p>Additional on-line usability testing tools:</p>
<p><a href="http://web.mit.edu/is/usability/usability-guidelines.html" target="_blank">Lightweight Usability Checklist</a></p>
<p><a title="Feng GUI" href="http://www.feng-gui.com/" target="_blank">Remote Eye Tracking Service</a></p>
<p><a title="Concept Feedback" href="http://www.conceptfeedback.com/" target="_blank">Concept Feedback</a></p>
<p><a title="Rew.iew.me" href="http://rev.iew.me/" target="_blank">Web Review Community</a></p>
<p><a title="Usabillia" href="http://www.usabilla.com/" target="_blank">Remote Task Analysis</a></p>
<p><a title="Userfly" href="http://userfly.com/" target="_blank">Remote Usability Testing</a></p>
<p><a title="uTest" href="http://www.utest.com/" target="_blank">Application Testing</a></p>
<p>Other (unrelated) Product Crowd-Sourcing Sites:</p>
<p><a title="99 Designs" href="http://www.99designs.com" target="_blank">Graphic Design</a></p>
<p><a title="Local Motors" href="http://www.local-motors.com/" target="_blank">Automobile Design</a> (just because it&#8217;s cool)</p>
<p><a title="Get Satisfaction" href="http://getsatisfaction.com/" target="_blank">Feedback</a></p>
<p><a title="eLance" href="http://www.elance.com/" target="_blank">Freelancing</a></p>
<p>Happy testing all.  Remember: &#8220;Test early &amp; test often&#8221;.  Don&#8217;t be afraid to admit you need help, we&#8217;re pretty good at what we do.</p>
<p>-Jon Fukuda</p>
]]></content:encoded>
			<wfw:commentRss>http://limina-ao.com/blog/2009/07/01/crowdsourcing-usability-or-not/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Good User Experience &#8211; Interrupted</title>
		<link>http://limina-ao.com/blog/2009/06/11/good-ux-interrupted/</link>
		<comments>http://limina-ao.com/blog/2009/06/11/good-ux-interrupted/#comments</comments>
		<pubDate>Thu, 11 Jun 2009 19:52:49 +0000</pubDate>
		<dc:creator>Mimi</dc:creator>
				<category><![CDATA[Hot Topics]]></category>
		<category><![CDATA[Limina Perspective]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[AT&T]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[iPhone3G S]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://limina-ao.com/blog/?p=228</guid>
		<description><![CDATA[Apple's stellar user experience is being thwarted by AT&#038;T's contract policies and limitations on functionality. How much will users be affected these inconveniences?]]></description>
			<content:encoded><![CDATA[<p><!--digg--></p>
<p><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val=" " /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--><!--  /* Font Definitions */  @font-face 	{font-family:"Cambria Math"; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:roman; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face 	{font-family:Calibri; 	panose-1:2 15 5 2 2 2 4 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:swiss; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1073750139 0 0 159 0;}  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-parent:""; 	margin:0in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman";} span.EmailStyle15 	{mso-style-type:personal; 	mso-style-noshow:yes; 	mso-style-unhide:no; 	mso-ansi-font-size:11.0pt; 	mso-bidi-font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:Calibri; 	mso-fareast-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi; 	color:#1F497D; 	mso-themecolor:dark2;} .MsoChpDefault 	{mso-style-type:export-only; 	mso-default-props:yes; 	font-size:10.0pt; 	mso-ansi-font-size:10.0pt; 	mso-bidi-font-size:10.0pt;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.0in 1.0in 1.0in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} --><!--[if gte mso 10]> <mce:style><!   /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-fareast-font-family:"Times New Roman"; 	mso-fareast-theme-font:minor-fareast; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin; 	mso-bidi-font-family:"Times New Roman"; 	mso-bidi-theme-font:minor-bidi;} --> <!--[endif]--></p>
<p class="MsoNormal"><strong>Big news! <a title="Apple web site" href="http://www.apple.com" target="_blank">Apple</a> just announced the much anticipated <a title="iPhone home" href="http://www.apple.com/iphone/" target="_blank">iPhone3G S</a>, along with the new 3.0 platform.</strong> As usual, Apple has done a stellar job of hyping the release, providing the 3.0 SDK (Software Development Kit) to their huge following of app developers in advance, encouraging them to take advantage of the new capabilities such as copy/paste, voice dialing, compass positioning, video support with editing, and, of course, improved speed (brought to you by the letter “S”).</p>
<div id="attachment_229" class="wp-caption alignleft" style="width: 195px"><a href="http://www.apple.com/iphone"><img class="size-full wp-image-229" title="iPhone pic" src="http://farm3.static.flickr.com/2450/3617843870_156a29eed4.jpg" alt="New iPhone3G S" width="185" height="327" /></a><p class="wp-caption-text">New iPhone3G S</p></div>
<p class="MsoNormal">
<p class="MsoNormal">These are exciting times for Mac fanatics, and for those who were waiting for the new and improved version to be released before jumping on the iPhone bandwagon. The pricing structure for newbies appears relatively reasonable and assures Apple of many new iPhone customers. However, for existing iPhone customers it’s a bit more confusing, and expensive. This is where the ever present Apple <a title="Wikipedia entry for user experience" href="http://en.wikipedia.org/wiki/User_experience" target="_blank">user experience</a> gets interrupted. <a title="AT&amp;T website" href="http://www.att.com/" target="_blank">AT&amp;T</a>, in their ultimate, and very typical wisdom, are essentially punishing their customer base for upgrading to the new iPhone – by charging premiums of two or three hundred dollars for those users who haven’t yet fulfilled their 2-year contract; which by the way is practically impossible seeing as it hasn’t yet been 2 years since the iPhone was released! In other words, just when everyone is getting excited about the new iPhone, loving their experience with the brilliant Apple brand, they get hit in the face with the harsh, predictably bad experience provided by AT&amp;T. Not only are they charging premiums for making the upgrade, but there are doubts about whether the AT&amp;T network will actually support the speed at which the iPhone3G S is programmed to run. And, one of the key features that will be supported across the globe (but not in the U.S. thanks to AT&amp;T) is tethering – a feature many customers have looked forward to since the beginning.</p>
<p class="MsoNormal">
<p class="MsoNormal">During the preview of the new iPhone there were many app demos that didn’t go as planned, and actually completely flopped, but that doesn’t come anywhere close to turning the fan base away from their beloved brand. But now, thanks to AT&amp;T, the supreme user experience has been interrupted. The question is, given today’s economy, how many current iPhone users will go for the upgrade and sustain the blows from AT&amp;T? I know at least one who is determined to keep up with the Jones’, but how many more will do the same? Unlike AT&amp;T, Apple’s <a title="Wikipedia entry for user experience" href="http://en.wikipedia.org/wiki/User_experience" target="_blank">user experience</a> has only improved over the past few years. Let’s see how many users overlook the grey cloud of <a title="AT&amp;T website" href="http://www.att.com" target="_blank">AT&amp;T</a> to continue their journey with new products from <a title="Apple web site" href="http://www.apple.com" target="_blank">Apple</a>.</p>
<p>- Mimi Knowles</p>
<p>pssst! Limina has embarked on developing our own iPhone app &#8211; &#8220;Top Secret&#8221; for now &#8211; but be on the lookout for the official announcement!</p>
]]></content:encoded>
			<wfw:commentRss>http://limina-ao.com/blog/2009/06/11/good-ux-interrupted/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Power to the People &#8211; The New Energy Experience</title>
		<link>http://limina-ao.com/blog/2009/05/27/power-to-the-people-the-new-energy-experience/</link>
		<comments>http://limina-ao.com/blog/2009/05/27/power-to-the-people-the-new-energy-experience/#comments</comments>
		<pubDate>Wed, 27 May 2009 21:32:19 +0000</pubDate>
		<dc:creator>Jon</dc:creator>
				<category><![CDATA[Hot Topics]]></category>
		<category><![CDATA[Information Design]]></category>
		<category><![CDATA[Crowd-sourcing]]></category>
		<category><![CDATA[dashboard]]></category>
		<category><![CDATA[data visulization]]></category>
		<category><![CDATA[energy management]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[Information Visualization]]></category>
		<category><![CDATA[smart meters]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://limina-ao.com/blog/?p=219</guid>
		<description><![CDATA[The set up In October 2007, GE Energy signed a memorandum to deploy advanced energy delivery and metering technologies that will give residential and industrial consumers greater control over their energy usage and costs.  November 2007, Google announces investment in energy technologies marking the tipping point of a new era on our energy experience.  Just [...]]]></description>
			<content:encoded><![CDATA[<p><!--digg--></p>
<p><strong>The set up</strong></p>
<p>In October 2007, <a href="http://www.gepower.com/about/press/en/2007_press/100407.htm" target="_blank">GE Energy</a> signed a memorandum to deploy advanced energy delivery and metering technologies that will give residential and industrial consumers greater control over their energy usage and costs.  November 2007, <a title="Google.org" href="http://blog.google.org/2007_11_01_archive.html" target="_blank">Google announces investment in energy technologies</a> marking the tipping point of a new era on our energy experience.  Just this month, Google revealed the iceberg tip of their Smart Meter consumer solution, harnessing the power of their analytic tool set, Google has settled in the keystone position of the smart meter user experience.</p>
<p align="center"><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="425" height="344" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="src" value="http://www.youtube.com/v/6Dx38hzRWDQ&amp;color1=0xb1b1b1&amp;color2=0xcfcfcf&amp;hl=en&amp;feature=player_embedded&amp;fs=1" /><param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="425" height="344" src="http://www.youtube.com/v/6Dx38hzRWDQ&amp;color1=0xb1b1b1&amp;color2=0xcfcfcf&amp;hl=en&amp;feature=player_embedded&amp;fs=1" allowfullscreen="true"></embed></object></p>
<p>Earlier this month, Limina had the privilege to compete against leading technology consulting firms for a contract to research, design, deploy and test a consumer facing portal that would empower consumers to make the smart consumption decisions and, in the future, play a key role in consumption based home automation.</p>
<p>Much of how this future scenario is already in the works as demonstrated by <a href="http://www.luciddesigngroup.com/" target="_blank">LucidDesignGroup&#8217;s</a> Building Dashboard product for schools, companies and homes.  With this dashboard you will, not only monitor and your building&#8217;s usage, but chart it against your usage history and, if you have on-site renewable power generation such as wind and solar, you can make smart decisions on when to sell back to the grid to maximize your return.</p>
<p style="text-align: center;"><a title="View a Live Demo" href="http://www.buildingdashboard.com/demo/starter/" target="_blank"><img class="aligncenter" title="Building Dashboard" src="http://www.luciddesigngroup.com/images/starter/starter_screenshot1.jpg" alt="" width="516" height="306" /></a></p>
<p>This display panel was featured in a <a title="Michelle Kaughman - Architect" href="http://www.mkd-arc.com/" target="_blank">Michelle Kaughman</a> home on an Episode of NextWorld on the <a title="recently added to my tivo play-list" href="http://science.discovery.com/" target="_blank">Science Channel</a>, where she discussed live scenarios for home and energy automation with the dashboard as the centerpiece.</p>
<p><strong>The Challenge:</strong></p>
<p>1) Getting the energy providers, homes and consumers ready: In October 2008 the Government in the UK announced a mandate to have every household outfitted with gas and electricity smart meters by the year 2020.  On March 19 2009, <a title="Energy &amp; Environment" href="http://www.whitehouse.gov/issues/energy_and_environment/" target="_blank">www.whitehouse.gov</a> posted the <a title="Recovery.gov" href="http://www.recovery.gov/" target="_blank">recovery act</a> with an $11billion dollar investment in a smart-grid.  While there are no mandates, one can predict action is imminent.</p>
<p>2) Ubiquity: Google is about as ubiquitous of a technology service provider as you can get, their interest and investment in this space is a key indicator that this challenge will be met.  LucidDesignGroup&#8217;s Dashboard has thought forward to live case for interfacing with consumers in an easy to use way making the information and more importantly calls to action accessible and elegant.</p>
<p>Limina is always looking forward to turnkey technological and experience innovations in any industry, but has a special interest in contributing to the global efforts to reduce energy waste and build awareness in renewable resources.</p>
<p>-Jon Fukuda</p>
<p>Submit your RFP&#8217;s to services at limina-ao dot com</p>
]]></content:encoded>
			<wfw:commentRss>http://limina-ao.com/blog/2009/05/27/power-to-the-people-the-new-energy-experience/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

