<?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>Vertical Spin</title>
	<atom:link href="http://verticalspin.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://verticalspin.com</link>
	<description>Keeping technology simple</description>
	<lastBuildDate>Thu, 15 Sep 2011 06:32:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>How do I turn my idea into a successful technology project?</title>
		<link>http://verticalspin.com/2011/02/successful-technology-project/</link>
		<comments>http://verticalspin.com/2011/02/successful-technology-project/#comments</comments>
		<pubDate>Wed, 09 Feb 2011 10:43:08 +0000</pubDate>
		<dc:creator>Tony Severo</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http:/?p=1</guid>
		<description><![CDATA[In my career I have probably heard at least one good idea per week. That adds up to quite a few ideas. I often look back and reflect on the winners and losers and the differences between them. The common thread across the successful ideas]]></description>
			<content:encoded><![CDATA[<p>In my career I have probably heard at least one good idea per week.  That adds up to quite a few ideas.   I often look back and reflect on the winners and losers and the differences between them.   The common thread across the successful ideas has been good execution, which leads me to believe that idea is worth 10% and execution 90%.  I have seen incredible ideas never get past go and some fair ideas flourish into good revenue generating businesses.</p>
<p><strong>So what makes for good execution?</strong><em><br />
</em>In answering this question I like to flip it and thing through common themes of failed projects:</p>
<ul>
<li> The inaugural project was too ambitious.  It took too much time and money to deliver</li>
<li> The user experience did not convert as estimated in the business goals</li>
<li> The solution did not scale and could not meed the visitor goals</li>
<li> The solution was built too complicated and it was difficult to analyze and quickly optimize</li>
<li> The project did not have the right balance of local effective resource and remote affordable development</li>
<li> Too much resource was invested in building technologies that already exist.</li>
</ul>
<p><strong> So how do give your idea the best change for success?</strong><br />
Nothing can replace the critical technology professionals that are required in the beginning of a project.  This cannot be outsourced or compromised.  It is critical that you have a team that can collaborate with you and define the right approach.   I think the simple analogy can be made with building a new house.   A great house is one where a team of professionals have developed a great plan and that ensures you will have an aesthetically pleasing house that is both functional and well-built.   Get the approach wrong and you will spend a lifetime modifying the house to get it right.   Technology development is no different.  Get the user experience right and your solution will convert and deliver.  Get the technology right and the solution will perform.    Get them wrong and you will spend a lifetime releasing modifications on a faulty foundation.</p>
<p><strong>What are the critical decisions that need to be made early on?</strong><br />
There are many decisions spanning across user experience and technology platform that can be made very early on in the project.</p>
<ul>
<li> <strong>Don&#8217;t build everything.</strong> Only build what is considered unique.  Leverage everything else.   Mashups with open source and paid solutions are easier than every and can significantly reduce your time to market.</li>
<li> <strong>Phase your development.</strong> Don&#8217;t build it all at once.  Break the idea into small manageable projects and release often and early.</li>
<li> <strong>Focus on that Golden Feature</strong>.  Figure our what makes your solution unique and focus on that feature.</li>
<li> <strong>Make quick decisions</strong>.  Trust yourself and make the decisions you need to keep things moving.  A wrong decision is better than no decision and my experience has been that we often over thing things.</li>
<li> <strong>Find the right team balance.</strong> The least expensive development solution is not the best solution.  Ideas succeed when a talented team of professionals can quickly collaborate and iterate through ideas.  Go remote too soon and collaboration quickly turns into administration.</li>
<li> <strong>Find the right expertise</strong>.  Do not use the same solution for every project.  Search the world and find the resource that has successfully delivered using the techniques and solutions you are considering.</li>
<li><strong>Fund it correctly</strong>.   You no longer need millions to fund an idea to release but you do need more than $10,000.    The right number varies from idea to idea but be careful not to enter into an endeavor without enough gas in the tank.</li>
</ul>
<p>All of these decisions can be pulled together in a  Discovery process.   This process typically takes 4-8 weeks and the outcome of this process includes a product roadmap, release approach, technology platform approach, user experience considerations, and program design.  This is the key to successful execution.</p>
]]></content:encoded>
			<wfw:commentRss>http://verticalspin.com/2011/02/successful-technology-project/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

