<?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>anyfeedback.co.uk</title>
	<atom:link href="http://www.anyfeedback.co.uk/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.anyfeedback.co.uk</link>
	<description>anyfeedback.co.uk the home of feedback simplicity</description>
	<lastBuildDate>Mon, 12 Mar 2012 14:13:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>some feedback faux-pas</title>
		<link>http://www.anyfeedback.co.uk/?p=131</link>
		<comments>http://www.anyfeedback.co.uk/?p=131#comments</comments>
		<pubDate>Mon, 05 Mar 2012 19:52:08 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.anyfeedback.co.uk/?p=131</guid>
		<description><![CDATA[Here&#8217;s a short list of things to avoid when you are gathering feedback or conducting surveys. Dont&#8217; ask so many questions! It&#8217;s probably the most common mistake. It annoys the very people you are trying to satisfy. Don&#8217;t ignore the results. People have committed their time to tell you their thoughts, if you ignore what [...]]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s a short list of things to avoid when you are gathering feedback or conducting surveys.</p>
<ol>
<li>Dont&#8217; ask so many questions! It&#8217;s probably the most common mistake. It annoys the very people you are trying to satisfy.</li>
<li>Don&#8217;t ignore the results. People have committed their time to tell you their thoughts, if you ignore what they tell you or do nothing with the results, it annoys them too. Better still, make feedback a two way thing, communicate the results and what you have done with them to the people giving you the information.</li>
<li>Don&#8217;t irritate them by sending out word docs to print out, find an envelope, stamp and postbox. It&#8217;s a half baked approach and says you are more interested in making it convenient for you rather than the &#8216;customer&#8217;.</li>
<li>Keep the scales consistent and easy to understand. Having a scale &#8216;strongly agree&#8217; to &#8216;strongly disagree&#8217; on one question, and &#8216;very satisfied&#8217; to &#8216;strongly dissatisfied&#8217; on the next, and even worse to reverse the scales on another is irritating and likely to yield bad data.</li>
<li>Don&#8217;t use words the recipient is baffled by. Most people don&#8217;t understand all the terminology you do, so ensure you know who you are asking.</li>
<li>Use routing as little as possible (if you answered 1 to this go to question 5, else go to question 3 if you answered 2). I have confused myself, so it is likely that most people will be too.</li>
<li>Don&#8217;t make the common section so small. If people have something to say they are not going to do it in 1 line.</li>
<li>Make text fields big enough for the data you are expected to receive in them. It is really annoying when you only have the equivalent of 5 characters for an email address.</li>
</ol>
<p>That&#8217;s just the start!! Hope it has been useful.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.anyfeedback.co.uk/?feed=rss2&#038;p=131</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Some tips for running events.</title>
		<link>http://www.anyfeedback.co.uk/?p=96</link>
		<comments>http://www.anyfeedback.co.uk/?p=96#comments</comments>
		<pubDate>Mon, 05 Mar 2012 14:35:31 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[events]]></category>
		<category><![CDATA[feedback]]></category>
		<category><![CDATA[surveying]]></category>

		<guid isPermaLink="false">http://www.anyfeedback.co.uk/?p=96</guid>
		<description><![CDATA[So you are running an event. How can you add value, stimulate the audience and find out how it went? Here are some basic guidelines about how you can produce a better event. 1) Where possible, use an online booking system to gather attendee information. Free services like eventbrite.com are excellent, and are simple to [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-full wp-image-101" title="tipsandtricks" src="http://www.anyfeedback.co.uk/wp-content/uploads/2012/03/tipsandtricks.jpg" alt="" width="250" height="250" />So you are running an event. How can you add value, stimulate the audience and find out how it went? Here are some basic guidelines about how you can produce a better event.</p>
<p>1) Where possible, use an online booking system to gather attendee information. Free services like eventbrite.com are excellent, and are simple to use. The benefit of these is clear: you know who&#8217;s coming, all the admin is handled for you (like reminders, badges etc) and you develop a powerful attendee database from day 1.</p>
<p>2) Find out what people&#8217;s expectations are before hand. Knowing what people want to get out of the event often guides the event itself. It is more likely the event is successful if everyone is clear what is expected.</p>
<p>3) Involve the audience during the event and make it interactive. Most people are familiar with how to send a text-message, and free polling systems (like livefeedback.co.uk) can be used to gauge an audience&#8217;s view on any particular issue. This often equips speakers with a clearer understanding of the audience and helps the presentations.</p>
<p>4) Find out what people think after the event. How did it go? Did it meet expectations (if you knew them)? What can you learn from feedback?</p>
<p>5) Ask as little as possible. Keep surveys short and focussed on what you need to know. Don&#8217;t pre-empt what is important to the audience. Sometimes understanding an audience&#8217;s enthusiasm to attend a similar event in the future and why will tell you most of what you need to know.</p>
<p>6) Feedback what you learn to the speakers. Great speakers are encouraged by praise, and poor feedback will help highlight improvements to be made.</p>
<p>-Martin Kentish, Free Range People Ltd</p>
]]></content:encoded>
			<wfw:commentRss>http://www.anyfeedback.co.uk/?feed=rss2&#038;p=96</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hello world!</title>
		<link>http://www.anyfeedback.co.uk/?p=1</link>
		<comments>http://www.anyfeedback.co.uk/?p=1#comments</comments>
		<pubDate>Fri, 27 Jan 2012 13:04:30 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.anyfeedback.co.uk/?p=1</guid>
		<description><![CDATA[Time to launch anyfeedback properly! You probably don&#8217;t know, but this site has been used for about 3 years now by hundreds of different companies to do thousands of different surveys. It worked really well, but it looked rather ugly (more like Google home page than a surveying system).  So here it is, the new [...]]]></description>
			<content:encoded><![CDATA[<p>Time to launch anyfeedback properly!</p>
<p>You probably don&#8217;t know, but this site has been used for about 3 years now by hundreds of different companies to do thousands of different surveys. It worked really well, but it looked rather ugly (more like Google home page than a surveying system).  So here it is, the new look anyfeedback system available in new shiney orange.</p>
<p>If you have any comments, pop me a line (martin@freerangepeople.co.uk) or use our <a title="contact us" href="http://www.anyfeedback.co.uk/?page_id=12">contact form.</a></p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.anyfeedback.co.uk/?feed=rss2&#038;p=1</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

