<?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: What it Means to Outsource the Development of Your Product</title>
	<atom:link href="http://freshout.us/notebook/outsourcing-product-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://freshout.us/notebook/outsourcing-product-development/</link>
	<description>Web application design and development agency!</description>
	<lastBuildDate>Mon, 01 Apr 2013 22:27:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: MideastYouth</title>
		<link>http://freshout.us/notebook/outsourcing-product-development/comment-page-1/#comment-293</link>
		<dc:creator>MideastYouth</dc:creator>
		<pubDate>Mon, 23 Jan 2012 02:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://freshout.us/?p=2150#comment-293</guid>
		<description>I really need to hand it to Navid here. Everything noted above is spot on. The idea means nothing if the execution doesn&#039;t compliment it. Micro-managing with the pretense or false assumption that the client knows everything has the potential of killing the project before it even begins. The client&#039;s job is to provide a concept or the problem to be solved and trust the product team to come up with various ways in which this can be solved, and then picking the best approach that sticks. Yes, handing over a project to a team is very risky. But if you spent enough time getting to know the team and their quality work, you can relax. Outsourcing (to the right team) doesn&#039;t mean the client loses control. It means being open to bigger, stronger and more ambitious opportunities that they wouldn&#039;t have come up with on their own. In a nutshell: You&#039;re doing yourself a favor.

Those who made a habit out of wanting to be part of every UI or development decision end up being a hindrance, not to mention it&#039;s demotivational for the rest of the team. Feedback is one thing but the long docs and detailed slideshows is a gunshot to &#039;innovation.&#039; Innovation comes with big risks. Innovative products come from people who let go of the traditional and embraced the new and unique. The fact will always remain that on most occasions the product team will know better than you purely because of the amount of experience they have gained in the field working with other startups and learning a lot of lessons along the way while gaining top-notch skills that can be used to your advantage. 

Being a client of Freshout now for about 2 years, I consider it a place where mere ideas come alive in the form of beautiful, amazingly functional products and apps. This isn&#039;t a testimonial. It&#039;s an experience that we are grateful for. I really can&#039;t imagine where we would&#039;ve been if we hadn&#039;t made that initial contact a few years ago. It was clear that this was a team that is extremely capable, extremely innovative, and most importantly understanding of exactly what you&#039;re trying to achieve by taking what could&#039;ve been a failed idea to something 10 times fresher and more unique. We&#039;ve matured because of it, and became much more trusting of their valuable contributions and inputs.

To conclude, the most important thing is that product design and development is not an &quot;expense,&quot; it&#039;s an investment. The quality of our latest projects (CrowdVoice, Mideast Tunes, and Ahwaa) were so good that it invited more people to donate to our projects, which allowed us to invest directly into improvements of current work or newer projects.

Again, while this may read like a testimonial, it&#039;s just noted here to evidence that if more clients did this we do feel that the web would be a better place. For us, Freshout makes that possible every day. We don&#039;t think there&#039;s any team out there with the passion and skills that these guys have. I&#039;m super confident in just giving them an idea and having them go at it, knowing that the end result will be nothing short of amazing. They&#039;re irreplaceable and we treasure them. If you can&#039;t say that about your dev team, it&#039;s time to make a serious investment and look elsewhere (unless you don&#039;t care enough about your idea or startup.)</description>
		<content:encoded><![CDATA[<p>I really need to hand it to Navid here. Everything noted above is spot on. The idea means nothing if the execution doesn&#8217;t compliment it. Micro-managing with the pretense or false assumption that the client knows everything has the potential of killing the project before it even begins. The client&#8217;s job is to provide a concept or the problem to be solved and trust the product team to come up with various ways in which this can be solved, and then picking the best approach that sticks. Yes, handing over a project to a team is very risky. But if you spent enough time getting to know the team and their quality work, you can relax. Outsourcing (to the right team) doesn&#8217;t mean the client loses control. It means being open to bigger, stronger and more ambitious opportunities that they wouldn&#8217;t have come up with on their own. In a nutshell: You&#8217;re doing yourself a favor.</p>
<p>Those who made a habit out of wanting to be part of every UI or development decision end up being a hindrance, not to mention it&#8217;s demotivational for the rest of the team. Feedback is one thing but the long docs and detailed slideshows is a gunshot to &#8216;innovation.&#8217; Innovation comes with big risks. Innovative products come from people who let go of the traditional and embraced the new and unique. The fact will always remain that on most occasions the product team will know better than you purely because of the amount of experience they have gained in the field working with other startups and learning a lot of lessons along the way while gaining top-notch skills that can be used to your advantage. </p>
<p>Being a client of Freshout now for about 2 years, I consider it a place where mere ideas come alive in the form of beautiful, amazingly functional products and apps. This isn&#8217;t a testimonial. It&#8217;s an experience that we are grateful for. I really can&#8217;t imagine where we would&#8217;ve been if we hadn&#8217;t made that initial contact a few years ago. It was clear that this was a team that is extremely capable, extremely innovative, and most importantly understanding of exactly what you&#8217;re trying to achieve by taking what could&#8217;ve been a failed idea to something 10 times fresher and more unique. We&#8217;ve matured because of it, and became much more trusting of their valuable contributions and inputs.</p>
<p>To conclude, the most important thing is that product design and development is not an &#8220;expense,&#8221; it&#8217;s an investment. The quality of our latest projects (CrowdVoice, Mideast Tunes, and Ahwaa) were so good that it invited more people to donate to our projects, which allowed us to invest directly into improvements of current work or newer projects.</p>
<p>Again, while this may read like a testimonial, it&#8217;s just noted here to evidence that if more clients did this we do feel that the web would be a better place. For us, Freshout makes that possible every day. We don&#8217;t think there&#8217;s any team out there with the passion and skills that these guys have. I&#8217;m super confident in just giving them an idea and having them go at it, knowing that the end result will be nothing short of amazing. They&#8217;re irreplaceable and we treasure them. If you can&#8217;t say that about your dev team, it&#8217;s time to make a serious investment and look elsewhere (unless you don&#8217;t care enough about your idea or startup.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  freshout.us/notebook/outsourcing-product-development/feed/ ) in 0.19391 seconds, on May 19th, 2013 at 3:35 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on May 19th, 2013 at 4:35 pm UTC -->