<?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>Antonio Thonis &#187; process optimization</title>
	<atom:link href="http://www.antoniothonis.com/tag/process-optimization/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.antoniothonis.com</link>
	<description>Business Strategy &#38; Social Marketing</description>
	<lastBuildDate>Wed, 02 Nov 2011 02:02:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
		<item>
		<title>Optimizing the private beta invites process</title>
		<link>http://www.antoniothonis.com/2009/optimizing-private-beta-invites-process/</link>
		<comments>http://www.antoniothonis.com/2009/optimizing-private-beta-invites-process/#comments</comments>
		<pubDate>Sun, 01 Nov 2009 17:38:06 +0000</pubDate>
		<dc:creator>Antonio Thonis</dc:creator>
				<category><![CDATA[Concepts]]></category>
		<category><![CDATA[Startups]]></category>
		<category><![CDATA[beta]]></category>
		<category><![CDATA[concept]]></category>
		<category><![CDATA[ideas]]></category>
		<category><![CDATA[process optimization]]></category>

		<guid isPermaLink="false">http://www.antoniothonis.com/?p=369</guid>
		<description><![CDATA[One great way to create continues buzz around your startup is to release private beta invites in multiple phases. Startups often choose to do this at big events in collaboration with media partners to generate publicity and attract new users. The feeling of exclusivity of the participants will motivate influentials to sign up and hopefully [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-full wp-image-375" title="invitation system" src="http://www.antoniothonis.com/wp-content/uploads/2009/11/betainvite.PNG" alt="invitation system" width="220" height="116" />One great way to create continues buzz around your startup is to release private beta invites in multiple phases. Startups often choose to do this at big events in collaboration with media partners to generate publicity and attract new users. The feeling of exclusivity of the participants will motivate influentials to sign up and hopefully write about your company. A good example of this has been the madness surrounding the Google <a href="http://mashable.com/2009/10/01/google-wave-invites-site/" target="_blank">Wave invites</a>.</p>
<p>There are a few problems which startups seem to face in the process of rolling out invitations. In the case of Google Wave many people with an invite discovered they had non of their friends on the service to interact with. This is not beneficial for the user experience of your new service. Another problem is <span id="more-369"></span>seasonality in user activity. Startups receiving a lot of publicity when a new invite batch is released.  Shortly after the buzz has passed user activity flattens with only some active users remaining.</p>
<p>Both problems can be solved <strong>by</strong> <strong>focusing on the social experience of users in the beta invitation process</strong>. Beta invites should be send out in batches of two, just like concert tickets in a prize giveaway. This can increase the probability of users to remain active by channeling their social behavior through your service. (I only became an active foursquare user after finding someone offline to share the experience with.)</p>
<p>Something to think about and which should be fairly easy to integrate in the invitation process on your website. What do you think?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.antoniothonis.com/2009/optimizing-private-beta-invites-process/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

