<?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>Brass Tack Thinking &#187; Risk aversion</title>
	<atom:link href="http://www.brasstackthinking.com/tag/risk-aversion/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brasstackthinking.com</link>
	<description>Make Things Happen</description>
	<lastBuildDate>Thu, 26 Jan 2012 14:00:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>		<item>
		<title>7 Steps to Executing a Pilot Project</title>
		<link>http://www.brasstackthinking.com/2010/04/7-steps-to-executing-a-pilot-project/</link>
		<comments>http://www.brasstackthinking.com/2010/04/7-steps-to-executing-a-pilot-project/#comments</comments>
		<pubDate>Thu, 15 Apr 2010 15:46:55 +0000</pubDate>
		<dc:creator>Amber Naslund</dc:creator>
				<category><![CDATA[Community]]></category>
		<category><![CDATA[Productivity]]></category>
		<category><![CDATA[Project Management and Planning]]></category>
		<category><![CDATA[Social media]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[culture change]]></category>
		<category><![CDATA[innovation]]></category>
		<category><![CDATA[pilot projects]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Risk aversion]]></category>

		<guid isPermaLink="false">http://altitudebranding.com/?p=1287</guid>
		<description><![CDATA[Have you read Switch by Chip and Dan Heath yet? If you haven&#8217;t, go over here and order it. (Amazon affiliate link) I&#8217;ll hang out. Good? Okay. One of the concepts they talk about that I utterly and completely believe in is the idea of having a &#8220;learning phase&#8221; for <span class="post_excerpt_readmore"><a href="http://www.brasstackthinking.com/2010/04/7-steps-to-executing-a-pilot-project/" title="Read more">Read more &#187;</a></span><p><br/><br/>A post from <a href="http://www.brasstackthinking.com">Brass Tack Thinking</a>
<br/><a href="http://www.brasstackthinking.com/2010/04/7-steps-to-executing-a-pilot-project/">7 Steps to Executing a Pilot Project</a></p>
]]></description>
			<content:encoded><![CDATA[<p><a href="http://farm4.static.flickr.com/3333/3654782487_b8bda37f01.jpg"><img class="alignright" style="padding-left:5px" title="Altitude Branding - 7 Steps to Executing a Pilot Project" src="http://farm4.static.flickr.com/3333/3654782487_b8bda37f01.jpg" alt="Altitude Branding - 7 Steps to Executing a Pilot Project" width="300" height="200" /></a>Have you read <a href="http://www.amazon.com/gp/product/0385528752?ie=UTF8&amp;tag=altitbrand-20&amp;linkCode=as2&amp;camp=1789&amp;creative=9325&amp;creativeASIN=0385528752"><em>Switch</em> by Chip and Dan Heath</a><img style="border:none !important; margin:0px !important;" src="http://www.assoc-amazon.com/e/ir?t=altitbrand-20&amp;l=as2&amp;o=1&amp;a=0385528752" border="0" alt="" width="1" height="1" /> yet? If you haven&#8217;t, go over here and order it. (Amazon affiliate link) I&#8217;ll hang out.</p>
<p>Good? Okay.</p>
<p>One of the concepts they talk about that I utterly and completely believe in is the idea of having a &#8220;learning phase&#8221; for new initiatives. It&#8217;s somewhere between the initial concept and the full-blown strategy, and allows for dedicated and purposeful time to test an idea before rolling it out fully.</p>
<p>This is something that I think more companies need to do, especially given their risk aversion for the unproven world of new media.</p>
<p>So how, exactly, do you do that? It&#8217;s as much a sales job as it is an execution job, but here&#8217;s my take.</p>
<p><strong>1. Create Your Hypothesis</strong></p>
<p>In science, your hypothesis is your proposed explanation, a testable statement that says what you think is going to happen based on your research. Same thing here. For you, it&#8217;s an educated guess about what&#8217;s going to happen if you do said project. For example, if you&#8217;re going to start a corporate blog, one hypothesis might be that you&#8217;ll capture 50 subscribers in the first 90 days, and generate five qualified leads from the blog within the first six months.</p>
<p>You&#8217;ll form that hypothesis by looking at your current website traffic to get a sense of what&#8217;s reasonable, the density of your social networks (how much trust and connection power you have online to draw interest in the blog), what your current lead generation numbers are, stuff like that. You&#8217;ll have to do some reasoning here.</p>
<p><strong>2. Stage the Experiment</strong></p>
<p>This is where you sell in what you&#8217;re planning, step by step. The key to the first and second steps is that this is a <em>finite</em> trial, with a start and end date. That helps mitigate risk against something that doesn&#8217;t work, and provides a dedicated stopping point for you to pause, take stock, and review your efforts.</p>
<p>Tell your management team exactly the steps you&#8217;ll take to prepare for the project, execute it, and how you&#8217;ll wind down the pilot (or roll it into a more permanent program should it be successful. You&#8217;ll want to address:</p>
<ul>
<li>How much capital/budget this will require, if any</li>
<li>How long it will last</li>
<li>How you plan to communicate this initiative both internally and externally</li>
<li>What time commitments you&#8217;ll need and from which staff members in order to support the program</li>
<li>Any technology or infrastructure needs you&#8217;ll have</li>
<li>How the experiment will impact existing processes and projects</li>
<li>Risk assessment: What&#8217;s the worst case scenario? Best case?</li>
<li>Who the point people are for questions, concerns, etc</li>
<li>Where the feedback mechanisms are for people to share their input about the project, both internal and external</li>
<li>How you&#8217;ll evaluate the success of the trial and present your findings</li>
<li>Your transition plan to roll out the project more permanently (if successful) or shutter it (if not)</li>
</ul>
<p><strong>3. Communicate the Pilot</strong></p>
<p>I&#8217;m a fan of telling folks they&#8217;re participating in a pilot program, or what you&#8217;re testing and trying. Publicly. If you&#8217;re not sure that your Facebook page will work, tell folks when you launch it that you&#8217;re doing so as a trial, and a way to find out what works for your company in the Facebook community.</p>
<p>Being up front about that can actually help elicit stronger and more active feedback, and give you the more graceful exit or the flexibility to change your approach should things not quite go to plan. Setting that expectation from the get-go can really be helpful, and generate some great open discussion and dialogue.</p>
<p><strong>4. Execute</strong></p>
<p>This is the meat of the process of course, but it&#8217;s where you take all the stuff you outlined in step 3 and actually do it. If you&#8217;ve done that part carefully, this ought to be rather straightforward.</p>
<p>Don&#8217;t forget to continue with regular status reports to your team and management so they can keep tabs on how you&#8217;re doing, what you&#8217;re learning, what your impressions are, and what feedback you&#8217;re receiving. Weekly or bi-weekly updates are usually good, depending on the length of your trial program.</p>
<p><strong>5. Capture Feedback</strong></p>
<p>This is concurrent with step 4, but should be a continuous part of your learning phase project. From the beginning, you should have indicated three or four key data points that you&#8217;ll track against based on the hypothesis you outlined. In our original example of the blog, it might be as simple as tracking number of subscribers on a weekly trend graph, and number of qualified leads that come through a dedicated link on the blog.</p>
<p>It&#8217;s also important to capture qualitative feedback, both from your colleagues and the external audiences you&#8217;re trying to reach or engage. Ask them whether they like this idea or don&#8217;t, and why. Solicit suggestions. Set up an ongoing feedback email address, ask your social networks to give their opinions, use a short survey at key points during the process to inquire. Whatever the mechanism, keep the doors of communication WIDE open and don&#8217;t discount any feedback until the end of the project.</p>
<p><strong>6. Shutter the Pilot</strong></p>
<p>At the end of your prescribed time period for the project, you&#8217;ll need to make a decision about whether you&#8217;re going to end the project completely, or roll it into a longer or more permanent effort.</p>
<p>By now, you probably have a pretty good sense of whether your hypothesis is going to hold up. If the program isn&#8217;t as successful as you&#8217;d hoped, it&#8217;s time to start thinking about how you&#8217;re going to communicate it&#8217;s end. Honesty and openness are good here. If your blog isn&#8217;t flying, perhaps you put up a post that says that you&#8217;re grateful for the attention of your readers to date, but that you need to step back and evaluate how you&#8217;re going to carry it forward (or just say that you&#8217;re ending it all together, and thank them for their interest).</p>
<p>Remember: failure isn&#8217;t permanent. It&#8217;s a temporary state. And while one thing might not work, something else may. That&#8217;s the point of this kind of project, to fail in a controlled environment where you&#8217;re prepared for the possibility that things won&#8217;t take off, and that you don&#8217;t put all your eggs in that basket before you know how strong it is.</p>
<p>If the pilot goes really well, this is the time when you want to maintain the status quo while you take a few weeks to draw out a transition plan. This is the map you&#8217;ll write to take you from temporary experiment to resident program. That transition plan could be anywhere from a few weeks to a few months, depending on how much you&#8217;ll need to scale out the existing effort, and what temporary changes you&#8217;ll need to make more permanent in order to support it for the long term.</p>
<p><strong>6. Present Your Findings</strong></p>
<p>Accountability time! This is where all the work you&#8217;ve done to track, tweak, measure, get input, and all of those things pays off. Keep in mind that measurement and reporting can be brutally simple and straightforward and still be compelling. At this point, the only thing you care about is answering the question of whether your initial hypothesis was right or wrong.</p>
<p>If it was right, illustrate why you think that was, and what factors contributed to its success. If you were more successful than you imagined, analyze and discuss what assumptions made your initial estimates conservative, and how the reality of the project&#8217;s execution and adoption may have turbo charged the results.</p>
<p>If you were wrong, remember that there are varying degrees. Were you completely wrong, and you got a handful of blog subscribers and no leads whatsoever? That&#8217;d be missing the mark completely. Or did you miss the mark by a few degrees that indicate more that you need refinement rather than abandonment? That&#8217;s an important distinction. What factors do you think contributed to not getting the results you wanted? (Hint: be sure your analysis is brutally honest, which includes not just external factors, but things that YOU could have done better or differently).</p>
<p><strong>7. Transition</strong></p>
<p>Just what it sounds like, this is the part where you execute the transition plan.</p>
<p>You&#8217;ll likely need to repeat your initial business case presentation to management, this time wrapping in your learnings from the experiment, and outlining your longer execution strategy (revisiting all of the impact factors we talked about in step 2).</p>
<h3><strong>Why This Matters</strong></h3>
<p>For those that are struggling to make a long term, predictive business case for a new initiative, this is the stop gap. It&#8217;s the bit in between that helps management teams see that they&#8217;re not committing to forever, they&#8217;re just endorsing testing the waters.</p>
<p>This is going to be much more of a culture sell for you than anything else. You&#8217;ll have to understand the personalities involved and whether they&#8217;re going to see the risks or the potential first, and tool your presentation and updates accordingly. But the purpose is to buy yourself a proving ground, a safe sandbox where you can tinker with some things based on ideas you have and be accountable for the outcomes, which makes it beneficial for everyone involved.</p>
<p>So what do you think? Have you tried this approach as an alternative to the full-blown megaproject? Is your culture open to this kind of thing, or are you already seeing how they&#8217;re going to resist it?</p>
<p>Let&#8217;s talk about it in the comments.</p>
<h5><em>image credit: </em><a title="Link to Christian Haugen's photostream" rel="dc:creator cc:attributionURL" href="/photos/christianhaugen/"><strong><em>Christian Haugen</em></strong></a></h5>
<div id="facebook_like"><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.brasstackthinking.com%2F2010%2F04%2F7-steps-to-executing-a-pilot-project%2F&amp;layout=standard&amp;show_faces=true&amp;width=500&amp;action=like&amp;font=segoe+ui&amp;colorscheme=light&amp;height=80" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:500px; height:80px;" allowTransparency="true"></iframe></div><p><br/><br/>A post from <a href="http://www.brasstackthinking.com">Brass Tack Thinking</a>
<br/><a href="http://www.brasstackthinking.com/2010/04/7-steps-to-executing-a-pilot-project/">7 Steps to Executing a Pilot Project</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.brasstackthinking.com/2010/04/7-steps-to-executing-a-pilot-project/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>You Can Only Lead the Horse</title>
		<link>http://www.brasstackthinking.com/2009/12/you-can-only-lead-the-horse/</link>
		<comments>http://www.brasstackthinking.com/2009/12/you-can-only-lead-the-horse/#comments</comments>
		<pubDate>Thu, 03 Dec 2009 08:00:51 +0000</pubDate>
		<dc:creator>Amber Naslund</dc:creator>
				<category><![CDATA[Culture]]></category>
		<category><![CDATA[Social media]]></category>
		<category><![CDATA[Business]]></category>
		<category><![CDATA[change management]]></category>
		<category><![CDATA[Fear]]></category>
		<category><![CDATA[Risk aversion]]></category>

		<guid isPermaLink="false">http://altitudebranding.com/?p=897</guid>
		<description><![CDATA[Is it possible that some organizations just simply aren&#8217;t ready for social media adoption? Yep. Why? Because they&#8217;re not equipped, ready, or open to evolve or change the way they&#8217;ve been doing things. Sometimes, it&#8217;s because change is complex, as in industries that are highly matrixed, or have complex regulatory <span class="post_excerpt_readmore"><a href="http://www.brasstackthinking.com/2009/12/you-can-only-lead-the-horse/" title="Read more">Read more &#187;</a></span><p><br/><br/>A post from <a href="http://www.brasstackthinking.com">Brass Tack Thinking</a>
<br/><a href="http://www.brasstackthinking.com/2009/12/you-can-only-lead-the-horse/">You Can Only Lead the Horse</a></p>
]]></description>
			<content:encoded><![CDATA[<p><a href="http://farm1.static.flickr.com/233/520891762_9a0dd4a09c.jpg"><img class="alignleft" style="padding-right:5px" title="Lead The Horse" src="http://farm1.static.flickr.com/233/520891762_9a0dd4a09c.jpg" alt="" width="320" height="213" /></a>Is it possible that some organizations just simply aren&#8217;t ready for social media adoption?</p>
<p><strong>Yep.</strong></p>
<p>Why? Because they&#8217;re not equipped, ready, or open to evolve or change the way they&#8217;ve been doing things.</p>
<p>Sometimes, it&#8217;s because change is complex, as in industries that are highly matrixed, or have complex regulatory or compliance issues that will require lots of detailed, nuanced, and potentially frustrating conversations with the powers that oversee such things.</p>
<p>Sometimes, it&#8217;s because we just can&#8217;t seem to find a solution for the things standing in our way. We&#8217;re not prepared to have the conversations, or ask the hard questions, or make staffing or operational changes to make change happen.</p>
<p>Sometimes, it&#8217;s because of out and out fear of the unknown, and the unwillingness to risk known quantities and accepted norms for things that are unproven or lack precedent and success standards.</p>
<p>Sometimes, it&#8217;s the inability or unwillingness to reallocate human and capital resources to something that doesn&#8217;t have established procedures and processes that ensure some level of efficiency out of the gate.</p>
<p>Sometimes, it&#8217;s because we misunderstand or haven&#8217;t thought through all of the implications &#8211; both positive and negative &#8211; for new ideas, and aren&#8217;t willing to spend the time doing so.</p>
<p>Sometimes, it&#8217;s just willful ignorance.</p>
<p>Innovation isn&#8217;t everyone&#8217;s bag, and we are still in the phase with social media where the companies that are doing this at scale and with long term intent are deserving of the label of trailblazers. Not every company is prepared to be first. Not every company is prepared to take the risks that come with trying something new or different. And you know what? <strong>That&#8217;s okay.</strong></p>
<p>Yes, there&#8217;s proof that social media works. More and more of it. But the critical mass of proof is going to be different for every organization&#8217;s culture and risk tolerance level.</p>
<p>If you are working in or with one of the organizations that is digging their heels in, you have two choices, and two only.</p>
<p>You can continue to work in small, progressive steps toward re-engineering your organization in whatever capacity you can. You will have to find like minds, recruit help, teach, re-teach, show, try, demonstrate, explain, justify, negotiate, compromise. You will need to be fiercely committed to the idea you are the translator and the illustrator, but it&#8217;s only time and tenacity that will help you make strides. Some will be small. Some steps will be backward. And eventually, you may find that you have either inched forward, or uncovered a lost cause.</p>
<p>The alternative is to walk away. Let them be. For some of you, that means being brave enough to go find a new job if this matters enough to you. For some, that means saying no to a client because they&#8217;re not yet ready to take advantage of what you can help them do. But sometimes, this is the only right answer. Not everyone is ready yet, nor should they be.</p>
<p>The only filter for deciding which situation you&#8217;re facing? You. Your experience and intuition and tolerance level.</p>
<p>Am I passionate about this? You bet I am. But there are plenty of people and organizations passionate but uneducated. Ready, but who need guidance. Curious, but who need reassurance and some help along the way. I&#8217;m ready to concentrate on <em>them</em> &#8211; the ones with the mindset if not the framework &#8211; and let the other folks find their way when they&#8217;re ready. I can&#8217;t save them all, and neither can you.</p>
<p>Our job is to illustrate and inform. Theirs is to choose. You can only lead the horse.</p>
<p><em>image by A<strong><a title="Link to Allen Dale Thompson's photostream" rel="dc:creator cc:attributionURL" href="http://www.flickr.com/photos/thompsoniannet/"><strong>llen Dale Thompson</strong></a></strong></em></p>
<div class="zemanta-pixie" style="margin-top: 10px; height: 15px;"><a class="zemanta-pixie-a" title="Reblog this post [with Zemanta]" href="http://reblog.zemanta.com/zemified/3988f5fa-0d6d-49d5-b71a-048c854f7eb1/"><img class="zemanta-pixie-img" style="border: medium none; float: right;" src="http://img.zemanta.com/reblog_e.png?x-id=3988f5fa-0d6d-49d5-b71a-048c854f7eb1" alt="Reblog this post [with Zemanta]" /></a><span class="zem-script more-related pretty-attribution"><script src="http://static.zemanta.com/readside/loader.js" type="text/javascript"></script></span></div>
<div id="facebook_like"><iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.brasstackthinking.com%2F2009%2F12%2Fyou-can-only-lead-the-horse%2F&amp;layout=standard&amp;show_faces=true&amp;width=500&amp;action=like&amp;font=segoe+ui&amp;colorscheme=light&amp;height=80" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:500px; height:80px;" allowTransparency="true"></iframe></div><p><br/><br/>A post from <a href="http://www.brasstackthinking.com">Brass Tack Thinking</a>
<br/><a href="http://www.brasstackthinking.com/2009/12/you-can-only-lead-the-horse/">You Can Only Lead the Horse</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.brasstackthinking.com/2009/12/you-can-only-lead-the-horse/feed/</wfw:commentRss>
		<slash:comments>30</slash:comments>
		</item>
	</channel>
</rss>

