<?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: How much do you share with beta program participants?</title>
	<atom:link href="http://ask.goodproductmanager.com/2008/05/28/how-much-do-you-share-with-beta-program-participants/feed/" rel="self" type="application/rss+xml" />
	<link>http://ask.goodproductmanager.com/2008/05/28/how-much-do-you-share-with-beta-program-participants/</link>
	<description>Your product management questions answered</description>
	<lastBuildDate>Tue, 13 Dec 2011 18:48:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Derek Britton</title>
		<link>http://ask.goodproductmanager.com/2008/05/28/how-much-do-you-share-with-beta-program-participants/comment-page-1/#comment-164</link>
		<dc:creator>Derek Britton</dc:creator>
		<pubDate>Wed, 28 May 2008 13:17:11 +0000</pubDate>
		<guid isPermaLink="false">http://ask.goodproductmanager.com/?p=37#comment-164</guid>
		<description>I would support Brian&#039;s view here about the simple steps involved - ask yourself WHY you are running the Beta program and that way you will uncover the criteria for its success, which can then be set as measurable objectives. Really this is conceptually all you need to start with, because who you involve, for how long, doing what is determined (largely) by your objectives.

I can vouch for Brian&#039;s &#039;Expert Product Management&#039; book being an excellent guide to running a Beta program. I would also expect that most organizations of a certain size would (should) have best-practice method written down, or at least some examples of programs already run.

My personal experience is that customers will respond well to honesty and transparency, so yes as much timeline, scope, task information is key; but you might need to also sell the upside for them (i.e. there is a give as well as an ask, and you need to be clear up front what that is in order to entice them).</description>
		<content:encoded><![CDATA[<p>I would support Brian&#8217;s view here about the simple steps involved &#8211; ask yourself WHY you are running the Beta program and that way you will uncover the criteria for its success, which can then be set as measurable objectives. Really this is conceptually all you need to start with, because who you involve, for how long, doing what is determined (largely) by your objectives.</p>
<p>I can vouch for Brian&#8217;s &#8216;Expert Product Management&#8217; book being an excellent guide to running a Beta program. I would also expect that most organizations of a certain size would (should) have best-practice method written down, or at least some examples of programs already run.</p>
<p>My personal experience is that customers will respond well to honesty and transparency, so yes as much timeline, scope, task information is key; but you might need to also sell the upside for them (i.e. there is a give as well as an ask, and you need to be clear up front what that is in order to entice them).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

