<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>product lifecycle on Bald Engineer</title><link>https://www.baldengineer.com/tag/product-lifecycle</link><description>Recent content in product lifecycle on Bald Engineer</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 20 Jun 2018 03:07:13 +0000</lastBuildDate><atom:link href="https://www.baldengineer.com/tag/product-lifecycle/index.xml" rel="self" type="application/rss+xml"/><item><title>IoT: Intelligent Outsourcing</title><link>https://www.baldengineer.com/iot-intelligent-outsourcing.html</link><pubDate>Wed, 28 Mar 2018 20:37:14 +0000</pubDate><guid isPermaLink="false">https://www.baldengineer.com/?p=7066</guid><description>&lt;p&gt;Whether you are developing a WiFi-enabled coffee maker, a sensor to detect rainfall, or a livestock tracking drone, an IoT device will follow the same product development cycle.&lt;/p&gt;&#10;&lt;p&gt;A common mistake that engineers will make is trying to own the development at each stage, at least up until &amp;ldquo;deliver.&amp;rdquo; Who can blame us? The idea of delegating any part of our new product introduction can be daunting. Delegating, or outsourcing can be a powerful tool. It allows you to focus on the elements of your process that only you can do. Let others handle the rest. If your core contribution is the machine learning algorithm, then focus your effort there. Spending time designing the enclosure, or negotiating with suppliers, or even laying out the printed circuit board is a waste. Let the people who excel in each of those areas apply their expertise to your product.&lt;/p&gt;</description></item></channel></rss>