<?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"
	>
<channel>
	<title>Comments on: 7 Tips To Run a Great Analyst Event: Dos and Don&#8217;ts.</title>
	<atom:link href="http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/</link>
	<description>An industry analyst blog looking at software ecosystems and convergence</description>
	<pubDate>Thu, 04 Dec 2008 01:48:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Tips from analysts about how to interact with them more effectively (new tip added 2/19/08) &#171; SageCircle Blog</title>
		<link>http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-311440</link>
		<dc:creator>Tips from analysts about how to interact with them more effectively (new tip added 2/19/08) &#171; SageCircle Blog</dc:creator>
		<pubDate>Tue, 19 Feb 2008 17:46:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-311440</guid>
		<description>[...] 7 Tips To Run a Great Analyst Event: Dos and Don’ts. [...]</description>
		<content:encoded><![CDATA[<p>[...] 7 Tips To Run a Great Analyst Event: Dos and Don’ts. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robb Mapp</title>
		<link>http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-308268</link>
		<dc:creator>Robb Mapp</dc:creator>
		<pubDate>Sat, 16 Feb 2008 01:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-308268</guid>
		<description>To Jon's point, death by ppt has killed a few analyst events. Having presenters dialogue with the group is much more useful than pitching strategy. Transparency versus selling always wins.

I might add that Scotch &#38; cigars are a good if you want to draw James &#38; Cote to an event...just a tip for other AR jocks...</description>
		<content:encoded><![CDATA[<p>To Jon&#8217;s point, death by ppt has killed a few analyst events. Having presenters dialogue with the group is much more useful than pitching strategy. Transparency versus selling always wins.</p>
<p>I might add that Scotch &amp; cigars are a good if you want to draw James &amp; Cote to an event&#8230;just a tip for other AR jocks&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tecosystems &#187; The Key to a Great Analyst Event: Do Less</title>
		<link>http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-307134</link>
		<dc:creator>tecosystems &#187; The Key to a Great Analyst Event: Do Less</dc:creator>
		<pubDate>Thu, 14 Feb 2008 21:50:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-307134</guid>
		<description>[...] anyway, James detailed his 7 Tips to a great analyst event, and I heartily agree with all of them but would like to expand [...]</description>
		<content:encoded><![CDATA[<p>[...] anyway, James detailed his 7 Tips to a great analyst event, and I heartily agree with all of them but would like to expand [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Cathcart</title>
		<link>http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-307112</link>
		<dc:creator>Mark Cathcart</dc:creator>
		<pubDate>Thu, 14 Feb 2008 21:24:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-307112</guid>
		<description>James, actually these are a great set of guidelines for any all day meeting where the content is mostly technical. Time is needed between sessions to discuss what you heard, to use other people as sounding boards for ideas etc. and we all have day jobs, and meetings almost certainly don't get factored in. Nice one, especially on your birthday!</description>
		<content:encoded><![CDATA[<p>James, actually these are a great set of guidelines for any all day meeting where the content is mostly technical. Time is needed between sessions to discuss what you heard, to use other people as sounding boards for ideas etc. and we all have day jobs, and meetings almost certainly don&#8217;t get factored in. Nice one, especially on your birthday!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Collins</title>
		<link>http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-306750</link>
		<dc:creator>Jon Collins</dc:creator>
		<pubDate>Thu, 14 Feb 2008 13:21:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-306750</guid>
		<description>Plus:

Don't start hyper-early in the morning and still expect analysts to be attentive late in the afternoon (particularly if (2) )

Make sure the event lasts as long as is necessary, but no longer

Ensure 1:1 schedules leave minimal dead time (but taking into account (6) )

For events that coincide with conferences, ensure time is allowed for walking the expo floor, but don't expect analysts to be enthralled about keynotes/general sessions

Look for alternative configurations to PPT-driven "chalk and talk" - "fireside chats" for example</description>
		<content:encoded><![CDATA[<p>Plus:</p>
<p>Don&#8217;t start hyper-early in the morning and still expect analysts to be attentive late in the afternoon (particularly if (2) )</p>
<p>Make sure the event lasts as long as is necessary, but no longer</p>
<p>Ensure 1:1 schedules leave minimal dead time (but taking into account (6) )</p>
<p>For events that coincide with conferences, ensure time is allowed for walking the expo floor, but don&#8217;t expect analysts to be enthralled about keynotes/general sessions</p>
<p>Look for alternative configurations to PPT-driven &#8220;chalk and talk&#8221; - &#8220;fireside chats&#8221; for example</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jgovernor</title>
		<link>http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-306744</link>
		<dc:creator>jgovernor</dc:creator>
		<pubDate>Thu, 14 Feb 2008 13:11:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-306744</guid>
		<description>cheers jonny. good ones. good catch on the NDA and the dietary issues. I HATE events where everything is NDA. totally pointless.</description>
		<content:encoded><![CDATA[<p>cheers jonny. good ones. good catch on the NDA and the dietary issues. I HATE events where everything is NDA. totally pointless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonny Bentwood</title>
		<link>http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-306737</link>
		<dc:creator>Jonny Bentwood</dc:creator>
		<pubDate>Thu, 14 Feb 2008 13:04:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2008/02/14/7-tips-to-run-a-great-analyst-event-dos-and-donts/#comment-306737</guid>
		<description>Good points James - I would also add a few more:

1) Provide NDA content but ensure that the entire meeting is not under embargo
2) Ask the analysts in advance if there are specific things they want to hear at the event (best to find out before the event so that you are prepared and give good info)
3) Give the analysts soft copies of the presentations (can be given on the morning of the event) so that they can make notes on the slides as they are being presented
4) Provide 1-2-1 opportunities. Having a 1-2-many session is great for presentations and analysts are happy to ask some questions in front of their peers but recognise that some analysts will want to ask their questions in private.

Always enjoyed having you at events - and with you in mind I would add one specific one...

5) Catering - not everyone is a meat eater. make sure you know dietary requirements beforehand.</description>
		<content:encoded><![CDATA[<p>Good points James - I would also add a few more:</p>
<p>1) Provide NDA content but ensure that the entire meeting is not under embargo<br />
2) Ask the analysts in advance if there are specific things they want to hear at the event (best to find out before the event so that you are prepared and give good info)<br />
3) Give the analysts soft copies of the presentations (can be given on the morning of the event) so that they can make notes on the slides as they are being presented<br />
4) Provide 1-2-1 opportunities. Having a 1-2-many session is great for presentations and analysts are happy to ask some questions in front of their peers but recognise that some analysts will want to ask their questions in private.</p>
<p>Always enjoyed having you at events - and with you in mind I would add one specific one&#8230;</p>
<p>5) Catering - not everyone is a meat eater. make sure you know dietary requirements beforehand.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
