<?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/05/design-critique-2/feed/" rel="self" type="application/rss+xml" />
    <link>https://elezea.com/2012/05/design-critique-2/</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>The fragile relationship between Ego and Design</title>
        <link>https://elezea.com/2012/05/design-critique-2/</link>
        <pubDate>Wed, 30 May 2012 07:40:17 +0000</pubDate>
        <dc:creator>Rian van der Merwe</dc:creator>
        <guid isPermaLink="false">https://elezea.com/?p=2810</guid>
        <description>
          <![CDATA[Christopher Butler wrote a good post on the relationship between Ego and Design, and how to structure design feedback better. It&#8217;s called Your Ego Is a Bad Designer, and he starts by explaining why development projects usually begin to go wrong during the design phase: Design&#8212;specifically, when we start making visual decisions&#8212;is the first point [&#8230;]]]>
        </description>
        <content:encoded>
          <![CDATA[<p>Christopher Butler wrote a good post on the relationship between Ego and Design, and how to structure design feedback better. It&#8217;s called <em><a href="http://imprint.printmag.com/design-thinking/your-ego-is-a-bad-designer/">Your Ego Is a Bad Designer</a></em>, and he starts by explaining why development projects usually begin to go wrong during the design phase:</p>
<blockquote>
<p>Design&mdash;specifically, when we start making visual decisions&mdash;is the first point in a project when we begin to engage one another in emotionally vulnerable ways. Every point in the process is an opportunity to second guess <em>who is in control?</em> and <em>how do I feel about that?</em> but design lacks the social decorum of sales negotiations and the regimentation of information architecture planning that would otherwise provide some structure for handling these potential conflicts. There&#8217;s simply no way to anticipate how the client will feel upon seeing that first mockup, or how you will respond, designer, to that initial deluge of feedback.</p>
</blockquote>
<p>He then shares his approach to sharing work with clients, and structuring their feedback in a positive and helpful way. I also like the way he makes us as designers responsible for the success of a project:</p>
<blockquote>
<p>We don&#8217;t fail at design because we lack tools, time, money, or the right clients. We fail at design because we lack insight. We don&#8217;t fail <em>at</em> design, <em>we</em> fail our design.</p>
</blockquote>
<p>For more on design critiques, see these three great posts:</p>
<ul>
<li><a href="http://www.ac4d.com/2012/04/30/do-you-want-critique-or-a-hug/">Do you want critique, or a hug? How to gain valuable criticism on your design</a></li>
<li><a href="http://www.uie.com/brainsparks/2011/10/27/moving-from-critical-review-to-critique/">Moving from Critical Review to Critique</a></li>
<li><a href="http://weblog.muledesign.com/2010/12/giving_better_feedback.php">Giving Better Design Feedback</a></li>
</ul>
          <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>