<?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>Event Ticket Printing &#187; planning</title>
	<atom:link href="http://eventticketprinting.co.uk/tag/planning/feed/" rel="self" type="application/rss+xml" />
	<link>http://eventticketprinting.co.uk</link>
	<description>A blog discussing event tickets, their creation, and how event tickets can help promote any event.</description>
	<lastBuildDate>Mon, 14 May 2012 00:15:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Coming to Yes</title>
		<link>http://eventticketprinting.co.uk/random/coming-to-yes/</link>
		<comments>http://eventticketprinting.co.uk/random/coming-to-yes/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 23:43:16 +0000</pubDate>
		<dc:creator>ticketprinting</dc:creator>
				<category><![CDATA[Random Thoughts]]></category>
		<category><![CDATA[events]]></category>
		<category><![CDATA[how to]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[printing]]></category>
		<category><![CDATA[publicity]]></category>

		<guid isPermaLink="false">http://eventticketprinting.co.uk/random/coming-to-yes</guid>
		<description><![CDATA[Odds are, decisions about event publicity and ticket printing are not entirely up to you. You may be among the lucky few who can make their own choices without answering to anyone, but most of us must muddle through layers of bureaucracy and consensus building before anything ever gets accomplished! Well, your printed materials are [...]]]></description>
			<content:encoded><![CDATA[<p>Odds are, <strong>decisions about event publicity and ticket printing</strong> are not entirely up to you. You may be among the lucky few who can make their own choices without answering to anyone, but most of us must muddle through layers of bureaucracy and consensus building before anything ever gets accomplished!</p>
<p>Well, your <strong>printed materials are a big deal</strong>. You print company knows this; that&#8217;s why any company worth its ink will offer you a <strong>100% satisfaction guarantee</strong> and work to make things right if they&#8217;re not right to begin with. You should be able to get exactly what you want. But what do you want?</p>
<p>Perhaps you have an idea about <strong>appropriate designs</strong>, or perhaps you are starting at the beginning. Here is a good checklist for event planners working with large groups to make decisions about publicity:</p>
<ul>
<li><strong>Brainstorm</strong> session: let everyone share ideas</li>
<li><strong>Reality</strong> check: what&#8217;s available? What can you afford</li>
<li><strong>Debate</strong>: Everyone gets to share their opinion</li>
<li><strong>Democracy</strong>: put it to a vote</li>
<li><strong>Repeat</strong>, if necessary, until everyone agrees on your course of action</li>
</ul>
<p>If you want to <strong>maintain an element of control</strong> over the process, do your research in advance. If you already know what&#8217;s available and what you can afford, it&#8217;s much easier to steer others toward your choice. Well-thought-out arguments are better received. </p>
<p>Working in groups is simple for some, complicated for others. When you are discussing how to <strong>hype your upcoming event</strong>, the choices you make can have great impact on attendance and fundraising. With a little extra effort, you can make it work!</p>
]]></content:encoded>
			<wfw:commentRss>http://eventticketprinting.co.uk/random/coming-to-yes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

