<?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>Daniel Irvine &#187; presentations</title>
	<atom:link href="http://danielirvine.com/blog/tag/presentations/feed/" rel="self" type="application/rss+xml" />
	<link>http://danielirvine.com</link>
	<description>Code in a cold climate</description>
	<lastBuildDate>Thu, 17 May 2012 17:11:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>A picture&#039;s worth a thousand words. But diagrams are difficult to draw&#8230;</title>
		<link>http://danielirvine.com/blog/2010/06/25/a-pictures-worth-a-thousand-words-but-diagrams-are-difficult-to-draw/</link>
		<comments>http://danielirvine.com/blog/2010/06/25/a-pictures-worth-a-thousand-words-but-diagrams-are-difficult-to-draw/#comments</comments>
		<pubDate>Fri, 25 Jun 2010 19:53:20 +0000</pubDate>
		<dc:creator>daniel</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[drawing]]></category>
		<category><![CDATA[presentations]]></category>
		<category><![CDATA[team]]></category>

		<guid isPermaLink="false">http://danielirvine.com/blog/?p=24</guid>
		<description><![CDATA[<p>Nightmare! Earlier this week at work, I wasted a good few hours attempting to draw a diagram. &#8220;Wasted&#8221; because, shock horror, it wasn&#8217;t a very successful attempt. The awful truth is that I can&#8217;t draw to save my life.</p> <p>I&#8217;d love to blame the tools, but since <a href="http://rachelcreative.wordpress.com/2007/09/25/a-bad-workman-drawing/">I&#8217;m trying to be a better workman</a>, [...]]]></description>
			<content:encoded><![CDATA[<p><em>Nightmare!</em> Earlier this week at work, I wasted a good few hours attempting to draw a diagram.  &#8220;Wasted&#8221; because, shock horror, it wasn&#8217;t a very successful attempt.  The awful truth is that <em>I can&#8217;t draw to save my life</em>.</p>
<p>I&#8217;d love to blame the tools, but since <a href="http://rachelcreative.wordpress.com/2007/09/25/a-bad-workman-drawing/">I&#8217;m trying to be a better workman</a>, I won&#8217;t do that. The tool in question is Microsoft PowerPoint. The scene is my lounge: me with my trusty laptop, alongside a strong pot of coffee for moral support.  The task is this:</p>
<blockquote><p>
Explain your six-month product vision to your team, your boss and your customers. Leave no one confused, and everyone enlightened.
</p></blockquote>
<p>Let me go back a bit and fill in some of the back-story.  The software product my team develops is great and all, but it has a knack for leaving our users in tears.  There are various “product features” (yep, you guessed it, I&#8217;m using that term loosely) that hinder our users in their day-to-day jobs. So, I&#8217;m hosting a conference call for some of our disgruntled users, and during this call I&#8217;ll describe how we plan to fix it all.</p>
<blockquote><p>
<strong>Feature</strong>, <em>n</em>. A bug that has been documented.
</p></blockquote>
<p>Because of the scale of the task, it struck me that <strong>a diagram</strong> was the way to tackle it.  If I were to do it in speech, I&#8217;d want to cover:</p>
<ul>
<li>The current problems we&#8217;re facing</li>
<li>The proposed changes to the architecture</li>
<li>Reasons why it simplifies the product</li>
<li>Some blurb about how this is the right approach to take. In other words, plead for approval.</li>
</ul>
<p>Now I&#8217;m sure this can all be said in a diagram, but I sure as hell haven&#8217;t figured out how.  I needed a sort of process diagram, showing the various nouns and connecting them with verbs—a <i>user</i> submits a request to the <i>build server</i> which kicks off this <i>automation task</i> that reports to a <i>database</i>—but when I started it just looked crap.  A bit like this.<br />
<div id="attachment_26" class="wp-caption aligncenter" style="width: 399px"><a href="http://danielirvine.com/blog/wp-content/uploads/2010/06/epicFail.png"><img src="http://danielirvine.com/blog/wp-content/uploads/2010/06/epicFail.png" alt="" title="An epic failure of a PowerPoint diagram" width="389" height="152" class="size-full wp-image-26" /></a><p class="wp-caption-text">An epic failure of a PowerPoint diagram</p></div></p>
<p>The concise diagram I had in my head ended up as a series of soulless boxes and arrows, all very bland and yes, I&#8217;m too ashamed to show you the end result.</p>
<p><strong>Am I the only one with this problem?</strong> I&#8217;d like to think not. On the day of the conference call, two things happened:</p>
<ol>
<li>I decided against using the presentation and just talked instead.</li>
<li>I questioned my teammates if any of them could teach me how to make awesome PowerPoint diagrams.</li>
</ol>
<p>One of the answers I got was <i>you can&#8217;t; just stick with text</i>.  The other answer I got was <i>do it the old-fashioned way, with a paper and a pen.</i>  That struck me and a damn good idea: one quick visit to Waterstone’s and I&#8217;ve now got this sitting beside me:<br />
<div id="attachment_27" class="wp-caption aligncenter" style="width: 488px"><a href="http://danielirvine.com/blog/wp-content/uploads/2010/06/emptyPad.png"><img src="http://danielirvine.com/blog/wp-content/uploads/2010/06/emptyPad.png" alt="" title="What fun awaits?" class="size-full wp-image-27" /></a><p class="wp-caption-text">What fun awaits?</p></div></p>
<p>I haven&#8217;t made an attempt yet to draw anything, but I&#8217;ll keep you posted&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://danielirvine.com/blog/2010/06/25/a-pictures-worth-a-thousand-words-but-diagrams-are-difficult-to-draw/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

