<?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/"
		>
<channel>
	<title>Comments on: Psst Customers &#8211; Some Software Demo Tips For You</title>
	<atom:link href="http://infoboxinc.com/psst-customers-some-software-demo-tips-for-you/feed/" rel="self" type="application/rss+xml" />
	<link>http://infoboxinc.com/psst-customers-some-software-demo-tips-for-you/</link>
	<description>A Tidy package of HR and Technology information, insight, wit and wisdom.</description>
	<lastBuildDate>Sat, 10 Dec 2011 12:01:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Here&#8217;s the Not So Corporate #HRCarnival &#124; ImSoCorporate.com</title>
		<link>http://infoboxinc.com/psst-customers-some-software-demo-tips-for-you/comment-page-1/#comment-318</link>
		<dc:creator>Here&#8217;s the Not So Corporate #HRCarnival &#124; ImSoCorporate.com</dc:creator>
		<pubDate>Wed, 14 Apr 2010 05:17:25 +0000</pubDate>
		<guid isPermaLink="false">http://infoboxinc.com/?p=249#comment-318</guid>
		<description>[...] Some software Demo tips for CUSTOMERS from the InfoBox blog of Mike Krupa [...]</description>
		<content:encoded><![CDATA[<p>[...] Some software Demo tips for CUSTOMERS from the InfoBox blog of Mike Krupa [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt chapman</title>
		<link>http://infoboxinc.com/psst-customers-some-software-demo-tips-for-you/comment-page-1/#comment-312</link>
		<dc:creator>matt chapman</dc:creator>
		<pubDate>Mon, 12 Apr 2010 20:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://infoboxinc.com/?p=249#comment-312</guid>
		<description>Confirm whether a function/workflow is standard out of box functionality, configured (by vendor) as part of implementation fee, can be configured by client (no additional cost) or requires a customization (code change by vendor).</description>
		<content:encoded><![CDATA[<p>Confirm whether a function/workflow is standard out of box functionality, configured (by vendor) as part of implementation fee, can be configured by client (no additional cost) or requires a customization (code change by vendor).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beth N. Carvin, Nobscot Corporation</title>
		<link>http://infoboxinc.com/psst-customers-some-software-demo-tips-for-you/comment-page-1/#comment-311</link>
		<dc:creator>Beth N. Carvin, Nobscot Corporation</dc:creator>
		<pubDate>Mon, 12 Apr 2010 03:05:07 +0000</pubDate>
		<guid isPermaLink="false">http://infoboxinc.com/?p=249#comment-311</guid>
		<description>That&#039;s great that you had a review of your killer scenarios prior to meeting with the vendor.   I bet that made a big difference.  Narrow scenarios can really lead you to miss out things you you hadn&#039;t thought of previously.  

I think the best demos are the ones that are flexible enough to allow for some good brainstorming between the company and the vendor.  

Which reminds me about one more thing --  It&#039;s great if you can find out from the vendor not only WHAT the technology does but also WHY the vendor uses a particular approach.  You can learn a lot about new best practices and also discover the vendor&#039;s level of knowledge of the Industry.</description>
		<content:encoded><![CDATA[<p>That&#8217;s great that you had a review of your killer scenarios prior to meeting with the vendor.   I bet that made a big difference.  Narrow scenarios can really lead you to miss out things you you hadn&#8217;t thought of previously.  </p>
<p>I think the best demos are the ones that are flexible enough to allow for some good brainstorming between the company and the vendor.  </p>
<p>Which reminds me about one more thing &#8212;  It&#8217;s great if you can find out from the vendor not only WHAT the technology does but also WHY the vendor uses a particular approach.  You can learn a lot about new best practices and also discover the vendor&#8217;s level of knowledge of the Industry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Krupa</title>
		<link>http://infoboxinc.com/psst-customers-some-software-demo-tips-for-you/comment-page-1/#comment-310</link>
		<dc:creator>Michael Krupa</dc:creator>
		<pubDate>Sun, 11 Apr 2010 17:17:12 +0000</pubDate>
		<guid isPermaLink="false">http://infoboxinc.com/?p=249#comment-310</guid>
		<description>Beth - Thanks. These are great.  To your second point, I&#039;ll add don&#039;t let your teammate run off with the vendor during the break to have a side conversation/demo.  All questions and functionality demos should be done with the entire group.  Good point about being flexible on the killer scenarios. We had the team create the killer scenarios and then the leads reviewed and re-worded any scenarios that were too narrow or only applied to the system that was being replaced.  Thanks for mentioning the last point about restroom and water. I&#039;m sure in the excitement of getting ready for the demo many customers forget this one.</description>
		<content:encoded><![CDATA[<p>Beth &#8211; Thanks. These are great.  To your second point, I&#8217;ll add don&#8217;t let your teammate run off with the vendor during the break to have a side conversation/demo.  All questions and functionality demos should be done with the entire group.  Good point about being flexible on the killer scenarios. We had the team create the killer scenarios and then the leads reviewed and re-worded any scenarios that were too narrow or only applied to the system that was being replaced.  Thanks for mentioning the last point about restroom and water. I&#8217;m sure in the excitement of getting ready for the demo many customers forget this one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Krupa</title>
		<link>http://infoboxinc.com/psst-customers-some-software-demo-tips-for-you/comment-page-1/#comment-309</link>
		<dc:creator>Michael Krupa</dc:creator>
		<pubDate>Sun, 11 Apr 2010 17:06:37 +0000</pubDate>
		<guid isPermaLink="false">http://infoboxinc.com/?p=249#comment-309</guid>
		<description>Love these.  Thanks.  In all of my vendor demos the last couple of months we actually did do all 5 of these so I guess we are following more best practices than I thought.</description>
		<content:encoded><![CDATA[<p>Love these.  Thanks.  In all of my vendor demos the last couple of months we actually did do all 5 of these so I guess we are following more best practices than I thought.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beth N. Carvin, Nobscot Corporation</title>
		<link>http://infoboxinc.com/psst-customers-some-software-demo-tips-for-you/comment-page-1/#comment-306</link>
		<dc:creator>Beth N. Carvin, Nobscot Corporation</dc:creator>
		<pubDate>Sat, 10 Apr 2010 03:01:59 +0000</pubDate>
		<guid isPermaLink="false">http://infoboxinc.com/?p=249#comment-306</guid>
		<description>Great lists by both Mike and Bryon.

Here are some more items to consider:

- Make sure you schedule enough time.  If your Sr. Exec tells you to give each vendor 10 minutes, you need to question authority.  

- Prep your team to keep questions relevant to the primary objectives and topics at hand.  Often there is one person who either gets excited about a side functionality and uses up a lot of time asking peripherally related questions or someone who wants to show how smart they are by throwing out &quot;hardball&quot; (but irrelevant) questions that would be better saved for post-demo discussion.

- Be flexible on how the killer scenario will play out. Allow the vendor to approach it from whatever angle they think is most relevant and helpful. Sometimes with new technology you don&#039;t know what you don&#039;t know. By defining narrow parameters for the demo you may miss out on seeing better ways of approaching things.  You will also learn more about how the vendor thinks and what kind of overall, business strategy expertise they have.  Anyone can follow a script, knowledgeable vendors can start with an objective and work backwards. 

- Last, my colleagues would say that I was remiss if I didn&#039;t add - Offer your guests the use of the restroom when they first arrive and a glass of water (in that order!)</description>
		<content:encoded><![CDATA[<p>Great lists by both Mike and Bryon.</p>
<p>Here are some more items to consider:</p>
<p>- Make sure you schedule enough time.  If your Sr. Exec tells you to give each vendor 10 minutes, you need to question authority.  </p>
<p>- Prep your team to keep questions relevant to the primary objectives and topics at hand.  Often there is one person who either gets excited about a side functionality and uses up a lot of time asking peripherally related questions or someone who wants to show how smart they are by throwing out &#8220;hardball&#8221; (but irrelevant) questions that would be better saved for post-demo discussion.</p>
<p>- Be flexible on how the killer scenario will play out. Allow the vendor to approach it from whatever angle they think is most relevant and helpful. Sometimes with new technology you don&#8217;t know what you don&#8217;t know. By defining narrow parameters for the demo you may miss out on seeing better ways of approaching things.  You will also learn more about how the vendor thinks and what kind of overall, business strategy expertise they have.  Anyone can follow a script, knowledgeable vendors can start with an objective and work backwards. </p>
<p>- Last, my colleagues would say that I was remiss if I didn&#8217;t add &#8211; Offer your guests the use of the restroom when they first arrive and a glass of water (in that order!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryon Abramowitz</title>
		<link>http://infoboxinc.com/psst-customers-some-software-demo-tips-for-you/comment-page-1/#comment-303</link>
		<dc:creator>Bryon Abramowitz</dc:creator>
		<pubDate>Thu, 08 Apr 2010 15:22:40 +0000</pubDate>
		<guid isPermaLink="false">http://infoboxinc.com/?p=249#comment-303</guid>
		<description>Mike - great list!  A few other key suggestions for a highly successful demo:

1.  Schedule time for everyone to debrief immediately following the demo - while the demonstration is still fresh in everyone&#039;s memory.  Discuss, debate, fight over what everyone liked/disliked and concerns

2.  Appoint a single individual to serve as the official note-taker.  Have this person track all unanswered questions, follow-up/action items, etc.  At the end of each scenario - review the outstanding items and assign ownership and due dates right there.  Submit the list to all participants at the end of the demonstration

3.  Scorecards!  In order to allow people to more easily follow along with the demonstration and provide structured feedback I&#039;ve found scorecards to be critical. This helps to provide a formal quantitative analysis of the feedback to support any discussions or decisions regarding product

4.  Schedule breaks into the agenda.  Seems silly to have to mention this, but I&#039;ve seen this overlooked more than I would care to admit.  In addition to the biological needs, responding to voicemail (you did ask them to turn phones off, right?)  demos rarely go according to schedule and failure to schedule breaks doesn&#039;t allow for any opportunities to make up lost ground.  

5.  Always have a whiteboard or flip chart handy.  Some demonstrations are best augmented by some &quot;chalk talk&quot;, and not having this available for the demonstrations may result in key concepts being overlooked, misunderstood, etc.</description>
		<content:encoded><![CDATA[<p>Mike &#8211; great list!  A few other key suggestions for a highly successful demo:</p>
<p>1.  Schedule time for everyone to debrief immediately following the demo &#8211; while the demonstration is still fresh in everyone&#8217;s memory.  Discuss, debate, fight over what everyone liked/disliked and concerns</p>
<p>2.  Appoint a single individual to serve as the official note-taker.  Have this person track all unanswered questions, follow-up/action items, etc.  At the end of each scenario &#8211; review the outstanding items and assign ownership and due dates right there.  Submit the list to all participants at the end of the demonstration</p>
<p>3.  Scorecards!  In order to allow people to more easily follow along with the demonstration and provide structured feedback I&#8217;ve found scorecards to be critical. This helps to provide a formal quantitative analysis of the feedback to support any discussions or decisions regarding product</p>
<p>4.  Schedule breaks into the agenda.  Seems silly to have to mention this, but I&#8217;ve seen this overlooked more than I would care to admit.  In addition to the biological needs, responding to voicemail (you did ask them to turn phones off, right?)  demos rarely go according to schedule and failure to schedule breaks doesn&#8217;t allow for any opportunities to make up lost ground.  </p>
<p>5.  Always have a whiteboard or flip chart handy.  Some demonstrations are best augmented by some &#8220;chalk talk&#8221;, and not having this available for the demonstrations may result in key concepts being overlooked, misunderstood, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Krupa</title>
		<link>http://infoboxinc.com/psst-customers-some-software-demo-tips-for-you/comment-page-1/#comment-302</link>
		<dc:creator>Michael Krupa</dc:creator>
		<pubDate>Thu, 08 Apr 2010 13:15:22 +0000</pubDate>
		<guid isPermaLink="false">http://infoboxinc.com/?p=249#comment-302</guid>
		<description>Thanks. Good tips.  I&#039;m okay with interrupting the presenters if the question is very relevant to the demo at that moment. Idle comments that interrupt the flow are a no-no.</description>
		<content:encoded><![CDATA[<p>Thanks. Good tips.  I&#8217;m okay with interrupting the presenters if the question is very relevant to the demo at that moment. Idle comments that interrupt the flow are a no-no.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deirdre</title>
		<link>http://infoboxinc.com/psst-customers-some-software-demo-tips-for-you/comment-page-1/#comment-300</link>
		<dc:creator>Deirdre</dc:creator>
		<pubDate>Thu, 08 Apr 2010 11:04:38 +0000</pubDate>
		<guid isPermaLink="false">http://infoboxinc.com/?p=249#comment-300</guid>
		<description>Don&#039;t interrupt the presenters 
Take notes 
Don&#039;t leave to &quot;take an important call&quot;  unless it is truly life or death. 

:)</description>
		<content:encoded><![CDATA[<p>Don&#8217;t interrupt the presenters<br />
Take notes<br />
Don&#8217;t leave to &#8220;take an important call&#8221;  unless it is truly life or death. </p>
<p> <img src='http://infoboxinc.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

