<?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>Plain Text &#187; Case study writing</title>
	<atom:link href="http://www.plain-text.co.uk/tag/case-study-writing/feed" rel="self" type="application/rss+xml" />
	<link>http://www.plain-text.co.uk</link>
	<description>Copywriting that means business</description>
	<lastBuildDate>Thu, 12 Jan 2012 17:20:22 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Issue 3, May 2002</title>
		<link>http://www.plain-text.co.uk/issue-3-may-2002</link>
		<comments>http://www.plain-text.co.uk/issue-3-may-2002#comments</comments>
		<pubDate>Thu, 30 May 2002 22:23:17 +0000</pubDate>
		<dc:creator>Paul W</dc:creator>
				<category><![CDATA[Plain Text Gazette]]></category>
		<category><![CDATA[Case study writing]]></category>

		<guid isPermaLink="false">http://www.plain-text.co.uk/wp_cms/?p=225</guid>
		<description><![CDATA[================================================
THE PLAIN TEXT GAZETTE &#8211; Issue 3, May 2002
================================================
Contents
&#8212;&#8212;&#8211;
* Editorial
* When communication doesn&#8217;t #3: Case study carnage
* More jargon
Editorial
&#8212;&#8212;&#8212;
In the second Plain Text Gazette we railed against &#8216;Powerpoint Hell&#8217; and offered some principles for effective presentations
The response suggested that this subject is close to your hearts. We urge you to bring our training courses to [...]]]></description>
			<content:encoded><![CDATA[<p>================================================<br />
THE PLAIN TEXT GAZETTE &#8211; Issue 3, May 2002<br />
================================================</p>
<p>Contents<br />
&#8212;&#8212;&#8211;</p>
<p>* Editorial<br />
* When communication doesn&#8217;t #3: Case study carnage<br />
* More jargon</p>
<p>Editorial<br />
&#8212;&#8212;&#8212;</p>
<p>In the <a href="http://www.plain-text.co.uk/issue-2-december-2001">second Plain Text Gazette</a> we railed against &#8216;Powerpoint Hell&#8217; and offered some principles for effective presentations</p>
<p>The response suggested that this subject is close to your hearts. We urge you to bring our <a href="http://www.plain-text.co.uk/our-services/training">training courses</a> to the attention of particularly bad offenders so that we can help make conferences a better place to be!</p>
<p>This time we&#8217;re going for a more low-key but potentially very useful piece of business writing: the &#8216;case study&#8217;. Easy to mess up, but not too difficult to get right either. We show you how to do both.</p>
<p>And in our ongoing jargon series, this time we thought we&#8217;d create a small memorial to all that crazy jargon from the internet boomtime. Unfashionable, useless and without any particular value, it&#8217;s like the failed dotcoms themselves. But still fun to remember nonetheless.</p>
<p>Keep it plain,</p>
<p>The Editors</p>
<p><a id="case" name="case"></a>When communication doesn&#8217;t #3: Case study carnage<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-</p>
<p>Case studies are ideal for answering the &#8216;Yeah, but how does it really work?&#8217; questions that customers inevitably ask when faced with an abstract, high-tech proposition, for example &#8216;end-to-end workflow integration&#8217; (huh?). Rather than showing them a complex flow diagram (or, God forbid, another Powerpoint presentation), you hand the customer a short story that tells them how your product has worked in a particular, real-life situation.</p>
<p>This sounds easy, but it&#8217;s often tricky. Mainly because case studies require you to do two things that tend to cancel each other out: 1) find a genuinely interesting story and 2) write it up in a way that keeps both vendor and customer organisations, the relevant senior managers and their legal departments, happy.</p>
<p>Much of the skill in getting a case study right is therefore in making sure that everyone in the chain of approval knows what&#8217;s going on right from the start. There&#8217;s nothing worse than writing (or commissioning) a beautifully-crafted and riveting study only to have it turned into a meaningless mix of legalese, MBA-speak and PR guff by lawyers, senior managers and marketeers.</p>
<p>So here are two (condensed) examples of what happens when it all goes horribly wrong and what happens in an ideal world.</p>
<p>Example 1 &#8212; case study mugged by The Suits</p>
<p>&#8216;As a customer-centric organisation, naturally we want to deliver satisfaction at every customer touchpoint&#8217; explained MegaCorp COO Lee Everage. &#8216;IntiMate technology has fully enabled us to drive value into our customers&#8217; businesses.&#8217;</p>
<p>Megacorp wanted to find ways to improve their best-of-breed customer services capability to something that their COO Everage described as &#8216;better-of-breed&#8217;. So they chose the latest release of IntiMate from Kloser Technologies to deliver on this vision.</p>
<p>&#8216;Our vision is to help our customers to release value throughout their workflow&#8217; said Kloser CTO Val Chane. &#8216;So MegaCorp is a great partner for us&#8217;.</p>
<p>A team of consultants from Kloser&#8217;s &#8216;Solutioneering&#8217; division conducted an extensive &#8216;customer touchpoint audit&#8217; of MegaCorp&#8217;s value chain. They then built a customised turnkey solution based on IntiMate&#8217;s &#8216;TouchMe&#8217; architecture. Value was delivered immediately. Said Everage &#8216;Since we installed IntiMate, we have experienced significantly higher levels of customer proximity. We are truly getting Kloser&#8217;.</p>
<p>Example 2 &#8212; case study escapes intact</p>
<p>IntiMate helps Megacorp to increase customer loyalty</p>
<p>&#8216;We know that information from every customer contact &#8212; phone calls, visits, emails &#8212; can be used to help us improve our service&#8217; said MegaCorp CEO Frank Storey. &#8216;But collating and analysing it is very difficult. IntiMate helped us to do this and we are already seeing results&#8217;.</p>
<p>MegaCorp installed Kloser Technologies&#8217; IntiMate package to capture, analyse and interpret information from many sources: customer databases, salesforce automation packages and email records. With its award-winning TouchMe architecture, IntiMate was able to help MegaCorp prioritise its activities so that its support operation&#8217;s activities were focused on customers most in need of attention.</p>
<p>&#8216;IntiMate has helped us enormously&#8217;, said Storey. &#8216;First, it means that our staff time is better allocated. Second, our biggest customers tell us they are getting a better service. Third and most importantly, we&#8217;re seeing an increase in customer loyalty from our smallest to our biggest accounts. This has been a good investment for us.&#8217;</p>
<p>More business-speak &#8212; the jargon graveyard<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-</p>
<p>And finally: our jargon column looks back fondly at a random selection of &#8216;technology boom&#8217; terms that have gone the way of eurozone currencies and attempts a brief explanation of why they went.</p>
<p>&#8216;pureplay&#8217; (internet-only businesses): there aren&#8217;t any left<br />
&#8216;new media&#8217;: it isn&#8217;t<br />
&#8216;24/7/365&#8242;: not even computers can manage these hours<br />
&#8216;portal, vortal, hortal&#8217;: too preposterous to survive<br />
&#8216;disintermediation&#8217;: the middlemen prevailed<br />
&#8216;viral marketing&#8217;: finally unmasked as a pretentious reinvention of &#8216;word-of-mouth&#8217;<br />
&#8216;bricks and clicks&#8217;/'clicks and mortar&#8217; etc: just plain silly<br />
&#8216;e&#8217; or &#8216;@&#8217; prefixes: *so* mid &#8217;90s<br />
&#8216;convergence&#8217;: didn&#8217;t happen<br />
&#8217;sticky&#8217;: customers didn&#8217;t want to get messy<br />
&#8216;B2B/B2C/B2B4C/C2C/C2B&#8217;: just became too darn incomprehensible<br />
&#8216;monetise&#8217;: didn&#8217;t happen<br />
&#8216;incubator&#8217;: weren&#8217;t warm enough<br />
&#8216;turn-key&#8217;: OK, so it&#8217;s not strictly dotcom jargon. But it sounds so much like &#8216;turkey&#8217; that it really should be in the graveyard.<br />
&#8216;bleeding&#8217;/'leading&#8217;/'cutting edge&#8217;: can anyone explain the nuances here?<br />
As always, further suggestions and comments are welcome.</p>
<p>Paul &amp; Paul</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-oOo&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</p>
<p>© Plain Text Ltd 2002 all rights reserved</p>
]]></content:encoded>
			<wfw:commentRss>http://www.plain-text.co.uk/issue-3-may-2002/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

