<?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>Jonathan C Dickinson &#187; Brutal</title>
	<atom:link href="http://jonathan.dickinsons.co.za/blog/category/brutal/feed/" rel="self" type="application/rss+xml" />
	<link>http://jonathan.dickinsons.co.za/blog</link>
	<description>&#34;Jonathan Chayce Dickinson&#34;.ToString()</description>
	<lastBuildDate>Sun, 06 Jun 2010 11:07:31 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Constructive RTFM</title>
		<link>http://jonathan.dickinsons.co.za/blog/2009/07/constructive-rtfm/</link>
		<comments>http://jonathan.dickinsons.co.za/blog/2009/07/constructive-rtfm/#comments</comments>
		<pubDate>Wed, 22 Jul 2009 06:36:20 +0000</pubDate>
		<dc:creator>Jonathan Dickinson</dc:creator>
				<category><![CDATA[Brutal]]></category>
		<category><![CDATA[Ideas]]></category>

		<guid isPermaLink="false">http://jonathan.dickinsons.co.za/blog/?p=142</guid>
		<description><![CDATA[How to reduce the strain on your support team AND improve customer experience.]]></description>
			<content:encoded><![CDATA[<p>I present to you, an improvement on support ticket forms:</p>
<div id="attachment_143" class="wp-caption aligncenter" style="width: 444px"><img class="size-full wp-image-143" title="New Support Request Form" src="http://jonathan.dickinsons.co.za/blog/wp-content/uploads/2009/07/New-Support-Request.png" alt="New Support Request Form" width="434" height="500" /><p class="wp-caption-text">New Support Request Form</p></div>
<p>&#8220;You need massive cajones to put that up!&#8221; I hear you say, but hear me out.</p>
<p>Firstly there is the obvious advantage of users realising that there is, in actual fact, documentation available that will assist them with simple things like this. Notice the inline help even at this point – some users might not use the documentation because they don’t know how to reach it.</p>
<p>You now have a compounded situation. If the user actually decides to click the submit button with a reason and the validation passes (140 characters minimum is probably a good bet) you really do have a problem – they did RTFM and got no answers. In this situation you have already solved your problem; you now know what areas of your documentation you need to address. The next customer who comes across this page with the same problem won’t be submitting a ticket.</p>
<p>You could always even provide a group of radio buttons so that the user has quick answers – and at the same time you will have data that can be graphed.</p>
<p>It is important to remember – you are not being rude at all. Referring to the documentation will mean that the turnaround time for an answer will be orders of magnitudes faster than relying on a limited amount of human resources.</p>
]]></content:encoded>
			<wfw:commentRss>http://jonathan.dickinsons.co.za/blog/2009/07/constructive-rtfm/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Getting into GTD</title>
		<link>http://jonathan.dickinsons.co.za/blog/2009/06/getting-into-gtd/</link>
		<comments>http://jonathan.dickinsons.co.za/blog/2009/06/getting-into-gtd/#comments</comments>
		<pubDate>Thu, 11 Jun 2009 08:30:37 +0000</pubDate>
		<dc:creator>Jonathan Dickinson</dc:creator>
				<category><![CDATA[Brutal]]></category>
		<category><![CDATA[GTD]]></category>
		<category><![CDATA[Ideas]]></category>

		<guid isPermaLink="false">http://jonathan.dickinsons.co.za/blog/?p=32</guid>
		<description><![CDATA[An efficient way to deal with large amounts of mail.]]></description>
			<content:encoded><![CDATA[<p>Getting things done is one of the concepts introduced by life hacking (where programmers apply productivity paradigms they encounter while programming to real life).</p>
<p>Truth be told I tried GTD but I found that it stymied my productivity. I spent most of my time running around trying to GTD instead of GTD. I recently read an article on <a href="http://blogs.harvardbusiness.org/trapani/2009/06/extreme-makeover-the-email-inb.html" target="_blank">Havard Business</a> that said you should have 3 &#8216;inboxes&#8217;:</p>
<ul>
<li>Follow Up &#8211; Stuff you need to follow up soon.</li>
<li>Hold &#8211; Stuff you are waiting for.</li>
<li>Archive &#8211; Important information you need to keep.</li>
</ul>
<p>On top of that you should do quick responses immediately. It&#8217;s a great concept: but my email volume is too high for even that (I would spend my life sorting my inbox). I go for a slightly hybrid approach. I won&#8217;t be giving a click-through tutorial here: rather a broad overview.</p>
<ol>
<li>Create a folder for Archive.</li>
<li>Create a folder for Pend (stuff that doesn&#8217;t fall under one of the others automatically).</li>
<li>If you have any existing filters keep them &#8211; only move the target under the appropriate folder (e.g. my &#8220;Source=Someone in the Company&#8221; folder is under Pend, mailing lists go under Archive).</li>
<li>Create two categories (Hold and Follow Up).</li>
<li>Assign hot-keys to the categories.</li>
<li>Create search folders for those categories.</li>
<li>Drop those search folders into your favourite folders.</li>
</ol>
<p>You now have hot-keys for to categorise things and views for those categories.</p>
<p>Email becomes manageable again!</p>
]]></content:encoded>
			<wfw:commentRss>http://jonathan.dickinsons.co.za/blog/2009/06/getting-into-gtd/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
