<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: UIEtips: The Magical Short-Form Creative Brief</title>
	<atom:link href="http://www.uie.com/brainsparks/2012/05/03/uie-tips-short-form-brief/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2012/05/03/uie-tips-short-form-brief/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sat, 18 May 2013 00:44:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Rob Varney</title>
		<link>http://www.uie.com/brainsparks/2012/05/03/uie-tips-short-form-brief/comment-page-1/#comment-219105</link>
		<dc:creator>Rob Varney</dc:creator>
		<pubDate>Mon, 14 May 2012 13:25:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=6992#comment-219105</guid>
		<description>A very timely article Jared.

The clue is in the name: brief. In my experience, handing over a statement of work and a long email thread between client and agency to the studio is not sufficient. We&#039;re currently reviewing our briefing process, to distill these client-facing documents into something that enables the creative juices of our thinkers to start flowing.

A brief should clearly and succinctly describe the task in hand and how success will be judged, acting as a spring board for the creative process to begin.

Your article describes the kind of document we&#039;re about to trial, which will be limited to a sheet of A4* and act as a contract between the client, client services team and our design studio. Most importantly, it should be a living document which changes to reflect the status of the project and current thinking.

My question is, who ultimately writes and owns this briefing document?

*12pt Helvetica, +3pt linespacing. I&#039;ve falled foul of project owners trying to set briefs in 6pt and claim their submission is within tolerances...</description>
		<content:encoded><![CDATA[<p>A very timely article Jared.</p>
<p>The clue is in the name: brief. In my experience, handing over a statement of work and a long email thread between client and agency to the studio is not sufficient. We&#8217;re currently reviewing our briefing process, to distill these client-facing documents into something that enables the creative juices of our thinkers to start flowing.</p>
<p>A brief should clearly and succinctly describe the task in hand and how success will be judged, acting as a spring board for the creative process to begin.</p>
<p>Your article describes the kind of document we&#8217;re about to trial, which will be limited to a sheet of A4* and act as a contract between the client, client services team and our design studio. Most importantly, it should be a living document which changes to reflect the status of the project and current thinking.</p>
<p>My question is, who ultimately writes and owns this briefing document?</p>
<p>*12pt Helvetica, +3pt linespacing. I&#8217;ve falled foul of project owners trying to set briefs in 6pt and claim their submission is within tolerances&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
