<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">

    <channel>
    
    <title>SK Blog from Slim Kiwi</title>
    <link>http://www.slimkiwi.com/blog</link>
    <description>The SK Blog from Slim Kiwi</description>
    <dc:language>en</dc:language>
    <dc:creator>mjr@slimkiwi.com</dc:creator>
    <dc:rights>Copyright 2009</dc:rights>
    <dc:date>2009-11-02T01:35:00-05:00</dc:date>
    <admin:generatorAgent rdf:resource="http://expressionengine.com/" />
    

    <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/slimkiwi" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
      <title>ExpressionEngine 2.0 is On Its Way</title>
      <link>http://www.slimkiwi.com/blog/post/expressionengine_20_is_on_its_way/</link>
      <guid>http://www.slimkiwi.com/blog/post/expressionengine_20_is_on_its_way/#When:02:35:00Z</guid>
      <description>The European ExpressionEngine CodeIgniter Conference&amp;mdash;eeci 2009&amp;mdash;took place October 22-23. While we weren't able to fly to The Netherlands to attend, we did follow posts from our peers and are really excited by all the buzz that's been generated about the next version of EE and some of our favorite tools.
ExpressionEngine 2.0
The long-awaited, next major version of ExpressionEngine, v2.0, will be officially released on December 1, 2009. This is huge news. EE 2.0 has been in development for a very, very long time. The team resisted rushing against a promised date and focused instead on working toward a thoroughly complete, worthwhile release. We've had access to, and installed, the beta and can say that it shows. The platform has been reworked and built off of EllisLab's CodeIgniter framework, which we've used in the past for custom application development. For our clients &amp;amp; end-users, ExpressionEngine 2.0 means:
An enhanced Control Panel with quicker access to most-used functions and features
More robust entry &amp;amp; editing tools, including a system-wide File Manager and robust image editing tools
CodeIgniter at the core, enhancing our ability to deliver custom solutions for you
Integration of powerful components, like Brandon Kelly's FieldFrame extension
Pricing
We've always touted ExpressionEngine's license fee as quite reasonable for the value it delivers, and that continues to be true. EE 2.0 comes with a modest price bump ($299 vs. $249, $149 vs. $99 for non-profits*) that is fully justifiable.
What about current ExpressionEngine sites?
Your site is probably running ExpressionEngine v1.6.x, which EllisLab will continue to support and release patches and updates for as necessary. If we're building your site with EE 1.6.8 right now, we can upgrade your site down the road for the EE upgrade fee ($50) and time spent. As we've been saying through the EE 2.0 development cycle, ExpressionEngine 1.6.8 is an incredibly solid and robust solution and we're comfortable deploying our clients' sites on it. If your site is about to launch, short of EE 2.0's release, you're still in a great place with a great product.
If you're coming on board with a new site after December 1, we'll be ready to work with you using the latest &amp;amp; greatest ExpressionEngine release.
* Prices are for 1 ExpressionEngine license. Yearly subscriptions are available for access to the latest updates and releases, though we don't always find those necessary. Find out more in the ExpressionEngine Store.</description>
      <content:encoded><![CDATA[<p>The European <a target="_blank" href="http://eeci2009.com">ExpressionEngine CodeIgniter Conference</a>&mdash;eeci 2009&mdash;took place October 22-23. While we weren't able to fly to The Netherlands to attend, we did follow posts from our peers and are really excited by all the buzz that's been generated about the next version of EE and some of our favorite tools.</p>
<h4>ExpressionEngine 2.0</h4>
<p>The long-awaited, next major version of ExpressionEngine, v2.0, will be officially released on December 1, 2009. This is huge news. EE 2.0 has been in development for a very, very long time. The team resisted rushing against a promised date and focused instead on working toward a thoroughly complete, worthwhile release. We've had access to, and installed, the beta and can say that it shows. The platform has been reworked and built off of EllisLab's CodeIgniter framework, which we've used in the past for custom application development. For our clients &amp; end-users, ExpressionEngine 2.0 means:</p>
<ul><li>An enhanced Control Panel with quicker access to most-used functions and features</li>
<li>More robust entry &amp; editing tools, including a system-wide File Manager and robust image editing tools</li>
<li>CodeIgniter at the core, enhancing our ability to deliver custom solutions for you</li>
<li>Integration of powerful components, like Brandon Kelly's <a target="_blank" href="http://brandon-kelly.com/fieldframe">FieldFrame</a> extension</li></ul>
<h4>Pricing</h4>
<p>We've always touted ExpressionEngine's license fee as quite reasonable for the value it delivers, and that continues to be true. EE 2.0 comes with a modest price bump ($299 vs. $249, $149 vs. $99 for non-profits*) that is fully justifiable.</p>
<h4>What about current ExpressionEngine sites?</h4>
<p>Your site is probably running ExpressionEngine v1.6.x, which EllisLab will continue to support and release patches and updates for as necessary. If we're building your site with EE 1.6.8 right now, we can upgrade your site down the road for the EE upgrade fee ($50) and time spent. As we've been saying through the EE 2.0 development cycle, ExpressionEngine 1.6.8 is an incredibly solid and robust solution and we're comfortable deploying our clients' sites on it. If your site is about to launch, short of EE 2.0's release, you're still in a great place with a great product.</p>
<p>If you're coming on board with a new site after December 1, we'll be ready to work with you using the latest &amp; greatest ExpressionEngine release.</p>
<p>* Prices are for 1 ExpressionEngine license. Yearly subscriptions are available for access to the latest updates and releases, though we don't always find those necessary. Find out more in the ExpressionEngine <a target="_blank" href="https://secure.expressionengine.com/">Store</a>.</p>]]></content:encoded>
      <dc:subject />
      <dc:date>2009-11-02T02:35:00-05:00</dc:date>
    </item>

    <item>
      <title>Design and Usability: Pantone.com, Chaotic Site Structure</title>
      <link>http://www.slimkiwi.com/blog/post/design_and_usability_pantonecom_caotic_site_structure/</link>
      <guid>http://www.slimkiwi.com/blog/post/design_and_usability_pantonecom_caotic_site_structure/#When:15:58:28Z</guid>
      <description>In this episode I continue to talk about the many great failures of the site Pantone.com. I show the benefits of the wireframing process and the downfalls of not investing time in site structure and information architecture. If you’d like to subscribe to this iPhone/Video iPod compatible podcast you can do so at iTunes.</description>
      <content:encoded><![CDATA[<p>In this episode I continue to talk about the many great failures of the site Pantone.com. I show the benefits of the wireframing process and the downfalls of not investing time in site structure and information architecture. If you&#8217;d like to subscribe to this iPhone/Video iPod compatible podcast you can do so <a target="_blank" href="http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=309898312">at iTunes</a>.</p>

<p>
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="545" height="361" id="viddler_afffd3b7"><param name="movie" value="http://www.viddler.com/simple/afffd3b7/" /><param name="allowScriptAccess" value="always" /><param name="allowFullScreen" value="true" /><embed src="http://www.viddler.com/simple/afffd3b7/" width="545" height="361" type="application/x-shockwave-flash" allowScriptAccess="always" allowFullScreen="true" name="viddler_afffd3b7"></embed></object>
</p>]]></content:encoded>
      <dc:subject>Creative, Podcast, Reviews, Usability</dc:subject>
      <dc:date>2009-07-24T15:58:28-05:00</dc:date>
    </item>

    <item>
      <title>From the Inside Looking In: Put Away the Mirror and Give Us a Window</title>
      <link>http://www.slimkiwi.com/blog/post/from_the_inside_looking_in_put_away_the_mirror_and_give_us_a_window/</link>
      <guid>http://www.slimkiwi.com/blog/post/from_the_inside_looking_in_put_away_the_mirror_and_give_us_a_window/#When:14:29:53Z</guid>
      <description>If your company is struggling with a complex design challenge it's probably time to seek input from someone on the outside. Corporate culture too often becomes insular, a team focused on internal objectives becomes self-reinforcing and a multitude of stakeholders with their respective agendas who all need to feel comfortable with the outcome end up with a watered-down, homogenized solution. Rather than looking through the window to get inspiration from the outside world, the team finds themselves looking into a mirror for what's familiar and efficient.
You need outside perspective. That's where an agency like Slim Kiwi comes in.
A Fast Company blog post, Are You Building a Consumer-Facing Company?, addressed this subject last week:
Design agencies, on the other hand, are born to think outside-looking-in. Not only do design agencies bring together radical talent and methodology that's difficult to maintain in a closed corporate environment, they have another advantage that's seldom talked about: Their ability to reflect across industries and companies and to form their opinion based on such experience. They have a role in creating many products, join many different teams, and can reflect, in hindsight, about the success or failure of certain ideas. That agency worldview cannot be counted in sketches, models or dollars--it is an invaluable trove of experience that is underutilized by both the agencies and their clients.
Our job goes beyond just executing a design. We're hired to provide critical insight and to evaluate your business and marketing efforts, provide you feedback, help you incorporate that feedback into your strategy, and then execute based on that strategy.
That might be a lot to sign onto. In the coming weeks, we'll be announcing a new service that will allow you to get an idea of what steps you should take and where we can contribute: Usability &amp;amp; Marketing Analysis Reports. You point us to your web site, pick a level of review to engage us on, and we provide you a report on what's working, what isn't, and what it would take for us to get you where you should be. Our goal is to give you a taste of our value, shake things up a bit and empower you to make an informed decision on the direction of your efforts without the big upfront commitment.
Outside looking in. Whether you're the corporate team that needs reinvigoration or just looking for expertise that isn't practical to maintain in-house, we're at our best when we're charged with bringing our outside perspective and our unique blend of expertise across industries, from consumer to business-to-business channels, for companies large and small, to the table to provide you fresh ideas. With this new offering, our goal is to let you opt for a first date rather than jumping into a relationship, while identifying where your organization can grow and optimize your efforts.</description>
      <content:encoded><![CDATA[<p>If your company is struggling with a complex design challenge it's probably time to seek input from someone on the outside. Corporate culture too often becomes insular, a team focused on internal objectives becomes self-reinforcing and a multitude of stakeholders with their respective agendas who all need to feel comfortable with the outcome end up with a watered-down, homogenized solution. Rather than looking through the window to get inspiration from the outside world, the team finds themselves looking into a mirror for what's familiar and efficient.</p>
<p>You need outside perspective. That's where an agency like Slim Kiwi comes in.</p>
<p>A Fast Company blog post, <a target="_blank" href="">Are You Building a Consumer-Facing Company?</a>, addressed this subject last week:</p>
<blockquote>Design agencies, on the other hand, are born to think outside-looking-in. Not only do design agencies bring together radical talent and methodology that's difficult to maintain in a closed corporate environment, they have another advantage that's seldom talked about: Their ability to reflect across industries and companies and to form their opinion based on such experience. They have a role in creating many products, join many different teams, and can reflect, in hindsight, about the success or failure of certain ideas. That agency worldview cannot be counted in sketches, models or dollars--it is an invaluable trove of experience that is underutilized by both the agencies and their clients.</blockquote>
<p>Our job goes beyond just executing a design. We're hired to provide critical insight and to evaluate your business and marketing efforts, provide you feedback, help you incorporate that feedback into your strategy, and then execute based on that strategy.</p>
<p>That might be a lot to sign onto. In the coming weeks, we'll be announcing a new service that will allow you to get an idea of what steps you should take and where we can contribute: <strong>Usability &amp; Marketing Analysis Reports</strong>. You point us to your web site, pick a level of review to engage us on, and we provide you a report on what's working, what isn't, and what it would take for us to get you where you should be. Our goal is to give you a taste of our value, shake things up a bit and empower you to make an informed decision on the direction of your efforts without the big upfront commitment.</p>
<p>Outside looking in. Whether you're the corporate team that needs reinvigoration or just looking for expertise that isn't practical to maintain in-house, we're at our best when we're charged with bringing our outside perspective and our unique blend of expertise across industries, from consumer to business-to-business channels, for companies large and small, to the table to provide you fresh ideas. With this new offering, our goal is to let you opt for a first date rather than jumping into a relationship, while identifying where your organization can grow and optimize your efforts.</p>]]></content:encoded>
      <dc:subject>Slim Kiwi, News, Marketing, Usability</dc:subject>
      <dc:date>2009-07-21T14:29:53-05:00</dc:date>
    </item>

    <item>
      <title>Slim Kiwi’s Take on Internet Explorer 6 Support &amp;amp; Client Projects</title>
      <link>http://www.slimkiwi.com/blog/post/slim_kiwis_take_on_internet_explorer_6_support_client_projects/</link>
      <guid>http://www.slimkiwi.com/blog/post/slim_kiwis_take_on_internet_explorer_6_support_client_projects/#When:19:06:56Z</guid>
      <description>IE6 (Version 6.x of Internet Explorer) is the web browser folks like us love to hate. If you haven’t gotten wind of that already, we expect you will.

In October, 2008, 37signals, provider of products such as Basecamp, which we use for project management, ceased supporting IE6.
Shortly after that, Sifter, a web-based bug tracking application, released a redesign which broke in IE6, to our client’s disappointment.
YouTube &amp;amp; Digg recently announced that they would soon be dropping IE6 support.

What does dropping IE6 support even mean? Well, it means that they’ll stop checking their web sites in IE6 to make sure they look good. When we launch a web site, we check it in a broad sampling of browsers: Safari 3, Safari 4, Firefox 3 and up, IE7, IE8 and, to our frequent dismay, IE6. Each of those browsers interpret how HTML should display in subtly different ways, and we need to adjust your web site’s code so that pages match the designs you approve in all those browsers. You’re paying for your designs and content to reach users regardless of their choice of platform and we support that.


But IE6? Well, two versions and ages old in internet years, it’s broken. To some extent, Microsoft ignored important trends and standards when building IE6, that the web development community and other browsers adopted, so it requires extra elbow grease to make sites work the same there as they do everywhere else. In the majority of cases, IE6 users are fringe users, less than 5%, and the costs of accommodating them outweigh the benefits, leading large web sites to announce they’re dropping support, in part to encourage users to upgrade, move on and get on the same page as everyone else. Web design firms announce new policies that they will no longer support IE6, or that doing so will incur an additional fee.


There are a few reasons IE6 hasn’t withered and vanished yet. The predominant reason is corporate IT departments. Some of them insist upon users staying with IE6 because years ago they built very expensive internal web sites that only work in that browser. Upgrading the browser on everyone’s computer would incur costs in redeveloping those sites. Others, like a financial services client we work for, stick with a specific IE6 release because a significant portion of their corporate security policy is based upon it.


Another client will soon be launching a site that may be accessed in Internet cafes anywhere in the world. We’re not entirely sure what browser might be installed there, so it’s a good idea to stick with supporting IE6 until we see some stats come in.


For now, we won’t be dropping IE6 support. We would certainly, for the sake of the web, appreciate it if you would drop IE6. We will continue to assume that we’re supporting IE6 in our work, but for those clients who feel it’s not worth the effort, we’ll discount the project commensurately and include a message on your site letting IE6 users know that a better experience awaits them in another browser. For the most part, those sites will work fine for those users and they’ll still get to the content. The design might come through a little rough, but we’ll collectively be doing our part for a better web by kindly requesting those users join us in the future.</description>
      <content:encoded><![CDATA[<p><abbr title="Internet Explorer 6">IE6</abbr> (Version 6.x of Internet Explorer) is the <a target="_blank" href="http://www.youtube.com/watch?v=o4MwTvtyrUQ">web browser</a> folks like us love to hate. If you haven&#8217;t gotten wind of that already, we expect you will.
</p>
<ul><li>In October, 2008, 37signals, provider of products such as Basecamp, which we use for project management, <a target="_blank" href="http://37signals.blogs.com/products/2008/07/basecamp-phasin.html">ceased supporting IE6</a>.</li>
<li>Shortly after that, Sifter, a web-based bug tracking application, released a redesign which broke in IE6, to our client&#8217;s disappointment.</li>
<li>YouTube &amp; Digg recently announced that they would soon be <a target="_blank" href="http://www.techcrunch.com/2009/07/14/youtube-will-be-next-to-kiss-ie6-support-goodbye/">dropping IE6 support</a>.</li></ul>
<p>
What does dropping IE6 support even mean? Well, it means that they&#8217;ll stop checking their web sites in IE6 to make sure they look good. When we launch a web site, we check it in a broad sampling of browsers: Safari 3, Safari 4, Firefox 3 and up, IE7, IE8 and, to our frequent dismay, IE6. Each of those browsers interpret how <abbr title="HyperText Markup Language">HTML</abbr> should display in subtly different ways, and we need to adjust your web site&#8217;s code so that pages match the designs you approve in all those browsers. You&#8217;re paying for your designs and content to reach users regardless of their choice of platform and we support that.
</p>
<p>
But IE6? Well, two versions and ages old in internet years, it&#8217;s broken. To some extent, Microsoft ignored important trends and standards when building IE6, that the web development community and other browsers adopted, so it requires extra elbow grease to make sites work the same there as they do everywhere else. In the majority of cases, IE6 users are fringe users, less than 5%, and the costs of accommodating them outweigh the benefits, leading large web sites to announce they&#8217;re dropping support, in part to encourage users to upgrade, move on and get on the same page as everyone else. Web design firms announce new policies that they will no longer support IE6, or that doing so will incur an additional fee.
</p>
<p>
There are a few reasons IE6 hasn&#8217;t withered and vanished yet. The predominant reason is corporate <abbr title="Information Technology">IT</abbr> departments. Some of them insist upon users staying with IE6 because years ago they built very expensive internal web sites that only work in that browser. Upgrading the browser on everyone&#8217;s computer would incur costs in redeveloping those sites. Others, like a financial services client we work for, stick with a specific IE6 release because a significant portion of their corporate security policy is based upon it.
</p>
<p>
Another client will soon be launching a site that may be accessed in Internet cafes anywhere in the world. We&#8217;re not entirely sure what browser might be installed there, so it&#8217;s a good idea to stick with supporting IE6 until we see some stats come in.
</p>
<p>
For now, we won&#8217;t be dropping IE6 support. We would certainly, for the sake of the web, appreciate it if you would drop IE6. We will continue to assume that we&#8217;re supporting IE6 in our work, but for those clients who feel it&#8217;s not worth the effort, we&#8217;ll discount the project commensurately and include a message on your site letting IE6 users know that a better experience awaits them in another browser. For the most part, those sites will work fine for those users and they&#8217;ll still get to the content. The design might come through a little rough, but we&#8217;ll collectively be doing our part for a better web by kindly requesting those users join us in the future.
</p>]]></content:encoded>
      <dc:subject>Technology</dc:subject>
      <dc:date>2009-07-17T19:06:56-05:00</dc:date>
    </item>

    <item>
      <title>MyZeo.com: A Client Relationship Success Story</title>
      <link>http://www.slimkiwi.com/blog/post/myzeocom_a_client_relationships_success_story/</link>
      <guid>http://www.slimkiwi.com/blog/post/myzeocom_a_client_relationships_success_story/#When:18:33:27Z</guid>
      <description>We’ve always sought to be more than an agency that just gets the job done. That should be expected of every agency you hire. Instead, we’re succeeding at showing clients that we have a genuine heartfelt interest in helping them succeed spectacularly. For this reason we get really excited when we see a client like Zeo, and others, get national attention with featured articles in the Wall Street Journal and making the front page of the business section of the New York Times. Zeo approached Slim Kiwi for online brand consulting, messaging and design after investing a lot of time, money, research and talent into building a consumer product that tracks and transmits brain waves wirelessly to a bedside clock while the user is sleeping and then charts and coaches that user on how to accomplish better nightly sleep.


We had many animated discussions with Zeo about their online strategy and design at myZeo.com. It was clear to us that they were carefully contemplating our advice and we made it clear to them (we hope) that we had a great amount of respect for the work they had done up to this point. We love the type of client relationships that we have with Zeo, where even amongst different opinions about strategy they can see we are more interested in their long-term success than their immediate happiness. We think the end result accomplished our task and plays a part in Zeo’s ongoing success, delivering a site that serves as their single largest point of sale for a new product that has achieved national attention.</description>
      <content:encoded><![CDATA[<p>We&#8217;ve always sought to be more than an agency that just gets the job done. That should be expected of every agency you hire. Instead, we&#8217;re succeeding at showing clients that we have a genuine heartfelt interest in helping them succeed spectacularly. For this reason we get really excited when we see a client like <a target="_blank" href="http://myzeo.com">Zeo</a>, and others, get national attention with featured articles in the <a target="_blank" href="http://online.wsj.com/article/SB124451280076496767.html">Wall Street Journal</a> and making the front page of the business section of the <a target="_blank" href="http://www.nytimes.com/2009/07/16/technology/personaltech/16pogue.html?_r=1&amp;scp=1&amp;sq=zeo&amp;st=cse">New York Times</a>. Zeo approached Slim Kiwi for online brand consulting, messaging and design after investing a lot of time, money, research and talent into building a consumer product that tracks and transmits brain waves wirelessly to a bedside clock while the user is sleeping and then charts and coaches that user on how to accomplish better nightly sleep.</p>
<br />
<div style="float: left; width: 298px;" class="image inline"><a target="_blank" href="http://myzeo.com"><img src="http://www.slimkiwi.com/images/uploads/zeoGraphic.jpg" alt="Zeo personal sleep coach" width="290" height="290" /></a><br /></div>
<p>We had many animated discussions with Zeo about their online strategy and design at <a target="_blank" href="http://myzeo.com">myZeo.com</a>. It was clear to us that they were carefully contemplating our advice and we made it clear to them (we hope) that we had a great amount of respect for the work they had done up to this point. We love the type of client relationships that we have with Zeo, where even amongst different opinions about strategy they can see we are more interested in their long-term success than their immediate happiness. We think the end result accomplished our task and plays a part in Zeo&#8217;s ongoing success, delivering a site that serves as their single largest point of sale for a new product that has achieved national attention.
</p>]]></content:encoded>
      <dc:subject>Creative, News, Marketing, Usability</dc:subject>
      <dc:date>2009-07-16T18:33:27-05:00</dc:date>
    </item>

    <item>
      <title>Design and Usability: Pantone.com, Inconsistent Navigation Language</title>
      <link>http://www.slimkiwi.com/blog/post/design_and_usability_pantonecom_inconsistent_navigation_language/</link>
      <guid>http://www.slimkiwi.com/blog/post/design_and_usability_pantonecom_inconsistent_navigation_language/#When:12:16:33Z</guid>
      <description>In this episode I continue to talk about the many great failures of the site Pantone.com. I point out the confusion caused by and inconsistencies in the visual language of their navigation. If you’d like to subscribe to this iPhone/Video iPod compatible podcast you can do so at iTunes.</description>
      <content:encoded><![CDATA[<p>In this episode I continue to talk about the many great failures of the site Pantone.com. I point out the confusion caused by and inconsistencies in the visual language of their navigation. If you&#8217;d like to subscribe to this iPhone/Video iPod compatible podcast you can do so <a target="_blank" href="http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=309898312">at iTunes</a>.</p>

<p>
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="545" height="361" id="viddler_7a009fa0"><param name="movie" value="http://www.viddler.com/simple/7a009fa0/" /><param name="allowScriptAccess" value="always" /><param name="allowFullScreen" value="true" /><embed src="http://www.viddler.com/simple/7a009fa0/" width="545" height="361" type="application/x-shockwave-flash" allowScriptAccess="always" allowFullScreen="true" name="viddler_7a009fa0"></embed></object>
</p>]]></content:encoded>
      <dc:subject>Creative, Podcast, Usability</dc:subject>
      <dc:date>2009-07-10T12:16:33-05:00</dc:date>
    </item>

    <item>
      <title>Design and Usability: Pantone.com, Failure to Acknowledge a Potential Customer</title>
      <link>http://www.slimkiwi.com/blog/post/design_and_usability_pantonecom_failure_to_acknowledge_a_potential_customer/</link>
      <guid>http://www.slimkiwi.com/blog/post/design_and_usability_pantonecom_failure_to_acknowledge_a_potential_customer/#When:14:20:02Z</guid>
      <description>In this episode I start a series where I talk about the many great failures of the site Pantone.com. I start by pointing out Pantone.com’s failure to acknowledge a potential customer and losing out on the opportunity to create a broader base for sales. If you’d like to subscribe to this iPhone/Video iPod compatible podcast you can do so at iTunes.</description>
      <content:encoded><![CDATA[<p>In this episode I start a series where I talk about the many great failures of the site Pantone.com. I start by pointing out Pantone.com&#8217;s failure to acknowledge a potential customer and losing out on the opportunity to create a broader base for sales. If you&#8217;d like to subscribe to this iPhone/Video iPod compatible podcast you can do so <a target="_blank" href="http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=309898312">at iTunes</a>.</p>

<p>
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="545" height="361" id="viddler_e8c3137a"><param name="movie" value="http://www.viddler.com/simple/e8c3137a/" /><param name="allowScriptAccess" value="always" /><param name="allowFullScreen" value="true" /><embed src="http://www.viddler.com/simple/e8c3137a/" width="545" height="361" type="application/x-shockwave-flash" allowScriptAccess="always" allowFullScreen="true" name="viddler_e8c3137a"></embed></object>
</p>]]></content:encoded>
      <dc:subject>Creative, Podcast, Reviews, Usability</dc:subject>
      <dc:date>2009-07-09T14:20:02-05:00</dc:date>
    </item>

    <item>
      <title>Design and Usability: Good Image Navigation</title>
      <link>http://www.slimkiwi.com/blog/post/design_and_usability_good_image_navigation/</link>
      <guid>http://www.slimkiwi.com/blog/post/design_and_usability_good_image_navigation/#When:12:55:01Z</guid>
      <description>In this episode I show and talk about GOOD examples of image navigation online. If you’d like to subscribe to this iPhone/Video iPod compatible podcast you can do so at iTunes.</description>
      <content:encoded><![CDATA[<p>In this episode I show and talk about GOOD examples of image navigation online. If you&#8217;d like to subscribe to this iPhone/Video iPod compatible podcast you can do so <a target="_blank" href="http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=309898312">at iTunes</a>.</p>

<p>
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="545" height="361" id="viddler_c6f17ed7"><param name="movie" value="http://www.viddler.com/simple/c6f17ed7/" /><param name="allowScriptAccess" value="always" /><param name="allowFullScreen" value="true" /><embed src="http://www.viddler.com/simple/c6f17ed7/" width="545" height="361" type="application/x-shockwave-flash" allowScriptAccess="always" allowFullScreen="true" name="viddler_c6f17ed7"></embed></object>
</p>
]]></content:encoded>
      <dc:subject>Creative, Podcast, Usability</dc:subject>
      <dc:date>2009-06-08T12:55:01-05:00</dc:date>
    </item>

    <item>
      <title>Design and Usability: Poor Image Navigation 3: Moving Navigation</title>
      <link>http://www.slimkiwi.com/blog/post/design_and_usability_poor_image_navigation_3_moving_navigation/</link>
      <guid>http://www.slimkiwi.com/blog/post/design_and_usability_poor_image_navigation_3_moving_navigation/#When:20:57:15Z</guid>
      <description>In this episode I show and talk about a bad example of image navigation online - the moving navigation example. If you’d like to subscribe to this iPhone/Video iPod compatible podcast you can do so at iTunes.</description>
      <content:encoded><![CDATA[<p>In this episode I show and talk about a bad example of image navigation online - the moving navigation example. If you&#8217;d like to subscribe to this iPhone/Video iPod compatible podcast you can do so <a target="_blank" href="http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=309898312">at iTunes</a>.</p>

<p><object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="545" height="361" id="viddler_43adff4e"><param name="movie" value="http://www.viddler.com/simple/43adff4e/" /><param name="allowScriptAccess" value="always" /><param name="allowFullScreen" value="true" /><embed src="http://www.viddler.com/simple/43adff4e/" width="545" height="361" type="application/x-shockwave-flash" allowScriptAccess="always" allowFullScreen="true" name="viddler_43adff4e"></embed></object>
</p>]]></content:encoded>
      <dc:subject>Creative, Podcast, Usability</dc:subject>
      <dc:date>2009-04-21T20:57:15-05:00</dc:date>
    </item>

    <item>
      <title>Design and Usability: Poor Image Navigation 2: Hidden Nav</title>
      <link>http://www.slimkiwi.com/blog/post/design_and_usability_poor_image_navigation_2_hidden_nav/</link>
      <guid>http://www.slimkiwi.com/blog/post/design_and_usability_poor_image_navigation_2_hidden_nav/#When:15:43:45Z</guid>
      <description>In this episode I show and talk about a bad example of image navigation online - the hidden navigation example. If you’d like to subscribe to this iPhone/Video iPod compatible podcast you can do so at iTunes.</description>
      <content:encoded><![CDATA[<p>In this episode I show and talk about a bad example of image navigation online - the hidden navigation example. If you&#8217;d like to subscribe to this iPhone/Video iPod compatible podcast you can do so <a target="_blank" href="http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=309898312">at iTunes</a>.</p>

<p><object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="545" height="361" id="viddler_f11d462a"><param name="movie" value="http://www.viddler.com/simple/f11d462a/" /><param name="allowScriptAccess" value="always" /><param name="allowFullScreen" value="true" /><embed src="http://www.viddler.com/simple/f11d462a/" width="545" height="361" type="application/x-shockwave-flash" allowScriptAccess="always" allowFullScreen="true" name="viddler_f11d462a"></embed></object>
</p>]]></content:encoded>
      <dc:subject>Creative, Podcast, Usability</dc:subject>
      <dc:date>2009-04-11T15:43:45-05:00</dc:date>
    </item>

    
    </channel>
</rss>
