<?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/2013/03/collaboration-for-introverts/feed/" rel="self" type="application/rss+xml" />
    <link>https://elezea.com/2013/03/collaboration-for-introverts/</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>Collaboration for introverts</title>
        <link>https://elezea.com/2013/03/collaboration-for-introverts/</link>
        <pubDate>Tue, 26 Mar 2013 07:01:38 +0000</pubDate>
        <dc:creator>Rian van der Merwe</dc:creator>
        <guid isPermaLink="false">https://elezea.com/?p=4139</guid>
        <description>
          <![CDATA[Collaboration doesn't mean that everyone should do everything together. Important decisions are made together, but the production details happens while working alone.]]>
        </description>
        <content:encoded>
          <![CDATA[<p>Mark Boulton wrote a forceful counter-argument to the common mantra that collaboration results in better design. From <em><a href="http://markboulton.co.uk/journal/quietlyworking">Quietly working</a></em>:</p>
<blockquote>
<p>I see plenty of banner waving for collaborative working. Co-designing, pair programming, brainstorming, collaborative workshops. The overwhelming message is that these tools are better for reaching consensus, sharing work, and, ultimately, lead to better work. Well, I’m not so sure that’s the truth. Given my introverted nature, sometimes these activities can rush the process too much. They allow no time for me to think. […]</p>
<p>Personally speaking, a lot of the time, I’d rather listen to what you have to say and go and have a good think.</p>
</blockquote>
<p>Mark makes some very good points, and as an introvert myself, his message really resonates with me. But I don&#8217;t think it&#8217;s an either/or situation. It&#8217;s not that we either collaborate, or work alone. Collaboration that doesn&#8217;t allow time and space for working alone is ineffective collaboration.</p>
<p>There are two illustrations about the collaboration process that summarize this idea well. The first is from Trent Walton&#8217;s <em><a href="http://24ways.org/2012/being-prepared-to-contribute/">Being Prepared To Contribute</a></em>:</p>
<p><img decoding="async" style="display: block; margin-left: auto; margin-right: auto;" title="Better ideas" src="https://cdn.elezea.com/images/better-ideas.png" border="0" alt="Better ideas" /></p>
<p>An idea, followed by discussion, often results in <em>better</em> ideas. But the &#8220;Better idea&#8221; step doesn&#8217;t happen in a meeting room — it happens at the designer&#8217;s desk, when they have time to reflect and focus on the problem without interruption.</p>
<p>The second illustration is from Stefan Klocek&#8217;s excellent post <em><a href="http://www.cooper.com/journal/2011/04/great_creative_partnership_pai.html">Better together; the practice of successful creative collaboration</a></em>:</p>
<p><img decoding="async" style="display: block; margin-left: auto; margin-right: auto;" title="Together" src="https://cdn.elezea.com/images/together.png" border="0" alt="Together" /></p>
<p>It shows how collaboration doesn&#8217;t mean that everyone should do everything together. Important decisions are made together, but the production details (the &#8220;better ideas&#8221;) happen while working alone.</p>
<p>So I&#8217;m definitely with Mark on his call for having more time to think and work alone. But that isn&#8217;t an <em>alternative</em> to collaborative working. It&#8217;s just a necessary — and too often ignored — part of the collaboration process.</p>
<p><em>(link via <a href="http://twitter.com/ChrisFerdinandi">@ChrisFerdinandi</a>)</em></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>