<?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>Firestarter LabsStartups | Firestarter Labs</title>
	<atom:link href="http://firestarterlabs.com/category/startups/feed/" rel="self" type="application/rss+xml" />
	<link>http://firestarterlabs.com</link>
	<description>A Seattle startup creating online tools that make tough jobs dead simple.</description>
	<lastBuildDate>Tue, 31 Jan 2012 18:53:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Being a lean startup, Redux</title>
		<link>http://firestarterlabs.com/2011/12/being-a-lean-startup-redux/</link>
		<comments>http://firestarterlabs.com/2011/12/being-a-lean-startup-redux/#comments</comments>
		<pubDate>Sat, 03 Dec 2011 19:00:11 +0000</pubDate>
		<dc:creator>Aaron</dc:creator>
				<category><![CDATA[Lessons Learned]]></category>
		<category><![CDATA[Startups]]></category>

		<guid isPermaLink="false">http://firestarterlabs.com/?p=211</guid>
		<description><![CDATA[Eric Ries, author of The Lean Startup, describes a startup as: a human institution designed to create a new product or service under conditions of extreme uncertainty. Our company, while not the stereotypical garage startup, fits all three aspects of this definition.  Every project our team undertakes is essentially a startup effort designed to (hopefully)...]]></description>
			<content:encoded><![CDATA[<p dir="ltr">Eric Ries, author of<a href="http://theleanstartup.com/book"> The Lean Startup</a>, describes a startup as:</p>
<blockquote><p>a human institution designed to create a new product or service under conditions of extreme uncertainty.</p></blockquote>
<p>Our company, while not the stereotypical garage startup, fits all three aspects of this definition.  Every project our team undertakes is essentially a startup effort designed to (hopefully) bring a new product or service to market, in addition to serving the project’s client.  Our batting average over the last 23 years, unfortunately, is not much better than the typical startup success rate.  In terms of long-term commercial success, a few succeed &#8212; most fail.</p>
<p dir="ltr">Frustrated with this pattern of dead-end, shelf-ware projects, our team started looking for new approaches to building commercial success.  We discovered the Lean Startup methodology&#8211;oh my, was that really <a href="2009/10/being-a-lean-startup/">two years ago?</a>&#8211;and Firestarter Labs was born.  Of course, that’s only the beginning of the story.</p>
<p dir="ltr">Fast-forward to today. We’ve fielded <a href="http://presentationnext.com">PresentationNext</a> in private beta tests and are in the early stages of a new effort.  Looking back over the last couple years, we realize that we have made definite progress &#8212; but we also have lots of room for improvement. The first thing we hope to do is, for better or worse, write more blog posts.  From here on out we&#8217;ll write about the lessons we&#8217;ve already learned, be more transparent about our ongoing progress, and share what we discover along the way.</p>
<p dir="ltr">Keep us honest by <a href="/contact-us/">sending a note</a> or <a href="https://twitter.com/#!/FirestarterLabs">harassing us on twitter</a>.</p>
<p dir="ltr">
]]></content:encoded>
			<wfw:commentRss>http://firestarterlabs.com/2011/12/being-a-lean-startup-redux/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What I&#8217;ve learned about crowdSpring</title>
		<link>http://firestarterlabs.com/2009/11/what-ive-learned-about-crowdspring/</link>
		<comments>http://firestarterlabs.com/2009/11/what-ive-learned-about-crowdspring/#comments</comments>
		<pubDate>Thu, 05 Nov 2009 03:02:58 +0000</pubDate>
		<dc:creator>TJ</dc:creator>
				<category><![CDATA[Lessons Learned]]></category>
		<category><![CDATA[Startups]]></category>

		<guid isPermaLink="false">http://firestarterlabs.com/?p=94</guid>
		<description><![CDATA[For those of you that don&#8217;t know, crowdSpring is a crowdsourcing site for logo, business card, illustration, and web site design.  Basically crowdSpring manages design contests.  If you need a logo, you just describe what you are looking for and put up the prize money.  The creatives then compete for that prize &#8211; submitting their designs...]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-medium wp-image-97" title="biz card" src="http://firestarterlabs.com/wp-content/uploads/2009/11/biz-card1-255x300.jpg" alt="biz card" width="255" height="300" />For those of you that don&#8217;t know, <a href="http://www.crowdspring.com" target="_blank">crowdSpring</a> is a crowdsourcing site for logo, business card, illustration, and web site design.  Basically crowdSpring manages design contests.  If you need a logo, you just describe what you are looking for and put up the prize money.  The creatives then compete for that prize &#8211; submitting their designs for your review and feedback. </p>
<p>The primary aspect of their business model that convinced us to give it a try was their money back guarantee &#8211; if you don&#8217;t receive at least 25 entries to your contest, you face no obligation.  We also gained some confidence from the fact that we could observe ongoing contests.  It was pretty clear that (for whatever reason) some real rockstar designers like to play in these contests.</p>
<p>What we had in mind was the design of a logo and business cards.  We had checked around locally and it seemed that logo design would likely cost us $500 and that wouldn&#8217;t include business card layout.   For that money we&#8217;d get a handful of design ideas as well as refinements on the chosen design.  The primary benefit of choosing a local designer was that we would get to interact face-to-face.</p>
<p>On crowdSpring however, that $500 would be a larger than average prize and would include business card layout.  Given the size of the prize we thought it was reasonable (based on a review of similar contests) to expect that we might get 100 different options to choose from.  While all interaction would happen online, we were satisfied that the risk/reward ratio was in our favor so we set up a contest.</p>
<p>What did we learn:</p>
<ul>
<li><strong>The creatives are starved for feedback.</strong>  In many contests, the buyers provide little or no feedback and this discourages input from the creatives.  We found that all constructive criticism was highly appreciated and that the designers were smart about learning from the feedback given to them or to their competitors.</li>
<li><strong>Being involved is time-consuming.</strong>  This was the biggest surprise.  We set out to provide at least a little feedback on every unique design.  Given that the creatives take all the risk in these contests, it seemed only fair to prevent unnecessary work.  You need to expect to spend an hour or so a day to keep up (although I really got sucked into the process and probably spent 3).  In addition to being courteous, staying involved helps you as the buyer learn about your own likes and dislikes (these were not obvious to us at the start).</li>
<li><strong>Choice is good.</strong>  In the end our contest had an amazing 267 entries.  While the vast majority of these were well off the mark, it was incredibly invigorating to have a handful of high quality and completely different designs to choose from.  We were extremely pleased in the end.  <a href="http://www.crowdspring.com/myspring/profile/jeditiffin">JediTiffin</a> had the winning entry.  The business cards he designed, in particular, have been extremely effective.  It is very satisfying to see them pique people&#8217;s curiosity about what we&#8217;re doing here at Firestarter Labs.</li>
</ul>
<p>We&#8217;re now preparing for a new contest focused on giving our web application a needed face-lift.</p>
]]></content:encoded>
			<wfw:commentRss>http://firestarterlabs.com/2009/11/what-ive-learned-about-crowdspring/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Being a lean startup</title>
		<link>http://firestarterlabs.com/2009/10/being-a-lean-startup/</link>
		<comments>http://firestarterlabs.com/2009/10/being-a-lean-startup/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 18:41:01 +0000</pubDate>
		<dc:creator>TJ</dc:creator>
				<category><![CDATA[Product development]]></category>
		<category><![CDATA[Startups]]></category>

		<guid isPermaLink="false">http://firestarterlabs.com/?p=71</guid>
		<description><![CDATA[I read Steve Blank&#8217;s &#8220;The Four Step to the Epiphany&#8221; a few years ago and thoroughly enjoyed it.   In a nutshell Gary argues that startup founders need to begin a &#8221;customer development&#8221; process from the get go.  The key insight is that questions regarding the needs of the user can almost never be answered in your own conference room,...]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.amazon.com/gp/product/0976470705?ie=UTF8&amp;tag=ecisions-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0976470705"><img class="alignleft" style="border: 0px;" src="http://firestarterlabs.com/wp-content/uploads/2009/10/four-steps.jpg" border="0" alt="" /></a><img style="border:none !important; margin:0px !important;" src="http://www.assoc-amazon.com/e/ir?t=ecisions-20&amp;l=as2&amp;o=1&amp;a=0976470705" border="0" alt="" width="1" height="1" />I read Steve Blank&#8217;s &#8220;<a href="http://www.amazon.com/gp/product/0976470705?ie=UTF8&amp;tag=ecisions-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0976470705" target="_blank">The Four Step to the Epiphany</a>&#8221; a few years ago and thoroughly enjoyed it.   In a nutshell Gary argues that startup founders need to begin a &#8221;customer development&#8221; process from the get go.  The key insight is that questions regarding the needs of the user can almost never be answered in your own conference room, rather you need to get out and interact with real users and find out which of your many assumptions really hold water (if any). </p>
<p>While I found the book very motivating, I wasn&#8217;t in a place where I could act on the advice Steve offered.  Well to be honest, I could have, but I found the prospect of interacting with customers very early in product development a bit scary.  How would I find prospective users that would be willing to talk with me before I had something really useful to demonstrate?  In my mind I had defined &#8220;really useful&#8221; as being nearly perfect. </p>
<p>With the founding of Firestarter Labs, I want things to be different.  I have lived through several less than satisfying product development efforts, and I&#8217;ve vowed to learn from my mistakes.  Taking the lessons of Steve Blank and <a href="http://www.startuplessonslearned.com/">Eric Ries</a> to heart we are developing a series of hypotheses and  seeking to test them with the least amount of effort.  To date we&#8217;ve used the concept of the Minimum Viable Product (MVP) to:</p>
<ol>
<li><strong>Test a set of domain names and marketing messages.</strong>  We first wanted to determine if it would be feasible to reach prospective customers through search engine ads.  We had only a simple landing page which described our basic offering and allowed people to sign up for an upcoming Beta test.  We tested a few different domain names and ad copy to get a feel for what worked, and tracked our conversion rate (how many people registered for the Beta).  For $50 we learned a lot.  Did we identify the optimal domain name and marketing copy?  Of course not, but it was good enough for us to move on with a little more confidence.</li>
<li><strong>Test the intuitiveness of the solution.</strong>  Using the <a href="http://www.balsamiq.com/">Balsamiq</a> paper prototype software we mocked up some variations of the user interface.  Working with just a handful of outsiders (not carefully chosen early adopters) we were able to determine that people got the idea and that the most basic of our designs might give an acceptable user experience.  From here we began our Web-based implementation &#8211; working in no longer than three week iterations.  We define the functionality required to test our next hypothesis and estimate how long it will take to implement.  We then work to that deadline &#8211; compromising functionality if necessary. </li>
</ol>
<p>The tests so far have been useful, but not yet surprising.  We&#8217;ve found that our user interfaces are intelligible and we&#8217;ve been able to simplify, however we have not yet verified exactly which features will generate the real value to our users.  In a month or so we will begin testing for utility.  That is to say, determining whether users obtain meaningful benefits from our software as they go about creating their own presentations. </p>
<p>Now if I could only get over my fear that with every new test we&#8217;ll discover something awful.</p>
<p>If you want more on the Lean Startup methodology check out <a href="http://www.startuplessonslearned.com/2009/10/large-batch-of-videos-slides-and-audio.html" target="_blank">Eric Ries&#8217; presentations</a></p>
]]></content:encoded>
			<wfw:commentRss>http://firestarterlabs.com/2009/10/being-a-lean-startup/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

