<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="https://elezea.com/wp-content/themes/elz_2023/styles/pretty-feed-v3.xsl" type="text/xsl"?><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>Elezea by Rian van der Merwe - RSS Feed</title>
    <atom:link href="https://elezea.com/2012/11/improved-vs-no-ui/feed/" rel="self" type="application/rss+xml" />
    <link>https://elezea.com/2012/11/improved-vs-no-ui/</link>
    <description>A personal blog about product, technology, and interesting things that are worth sharing.</description>
    <lastBuildDate>Thu, 02 Apr 2026 17:43:52 +0000</lastBuildDate>
    <language></language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <generator>https://wordpress.org/?v=6.9.4</generator>
          <item>
        <title>When improved UI is better than no UI</title>
        <link>https://elezea.com/2012/11/improved-vs-no-ui/</link>
        <pubDate>Wed, 14 Nov 2012 06:36:21 +0000</pubDate>
        <dc:creator>Rian van der Merwe</dc:creator>
        <guid isPermaLink="false">https://elezea.com/?p=3775</guid>
        <description>
          <![CDATA[Stefan Klocek wrote a great post challenging the often-repeated idea that &#8220;the best UI is no UI.&#8221; From Should you ditch your interface?: For any particular interface in the system, ask: Does the user want or need control? Does the user get value from doing the work themselves? Does the user outperform technology? If you [&#8230;]]]>
        </description>
        <content:encoded>
          <![CDATA[<p>Stefan Klocek wrote a great post challenging the often-repeated idea that &#8220;the best UI is no UI.&#8221; From <em><a href="http://www.cooper.com/journal/2012/11/should-you-ditch-your-interface.html">Should you ditch your interface?</a></em>:</p>
<blockquote>
<p>For any particular interface in the system, ask:</p>
<ol>
<li>Does the user want or need control?</li>
<li>Does the user get value from doing the work themselves?</li>
<li>Does the user outperform technology?</li>
</ol>
<p>If you can answer “no” to every one of these questions, then put in the effort to eliminate the interface. If you answer “yes” to any one of these you should focus on improving the interface so that it supports the user better. If it’s not unanimously “yes” or “no” carefully consider how design can meet the conflicting needs. Get to know your users well. Design a solution that’s as sophisticated and nuanced as their situation calls for.</p>
</blockquote>
<p>Stefan goes into great detail on each of those questions, so <a href="http://www.cooper.com/journal/2012/11/should-you-ditch-your-interface.html">the post</a> is well worth your time.</p>
          <br>
          <br>
          <hr>
          Thanks for still believing in RSS! Get in touch <a href="https://elezea.com/contact">here</a> if you'd like.]]>
        </content:encoded>
                      </item>
      </channel>
</rss>