<?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>Key Tech Blog &#187; reduce</title>
	<atom:link href="http://www.keytechinc.com/blog/index.php/tag/reduce/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.keytechinc.com/blog</link>
	<description>Key Tech&#039;s take on Engineering, the World, and everything else.</description>
	<lastBuildDate>Mon, 06 Feb 2012 20:55:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>The symbiosis of modeling and prototyping</title>
		<link>http://www.keytechinc.com/blog/index.php/2010/the-symbiosis-of-modeling-and-prototyping/</link>
		<comments>http://www.keytechinc.com/blog/index.php/2010/the-symbiosis-of-modeling-and-prototyping/#comments</comments>
		<pubDate>Tue, 23 Feb 2010 12:00:22 +0000</pubDate>
		<dc:creator>Chad Schneider</dc:creator>
				<category><![CDATA[Engineering]]></category>
		<category><![CDATA[Lab-on-a-chip]]></category>
		<category><![CDATA[Manufacturing]]></category>
		<category><![CDATA[Microfluidics]]></category>
		<category><![CDATA[Problem Solving]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[obstacles]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[product development]]></category>
		<category><![CDATA[reduce]]></category>
		<category><![CDATA[resource]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[tool]]></category>

		<guid isPermaLink="false">http://www.keytechinc.com.php5-6.dfw1-2.websitetestlink.com/blog/?p=518</guid>
		<description><![CDATA[Prototypes are essential to testing system performance. However, due to the current technological constraints of creating microscale prototypes, compromises in the characteristics of the prototype usually must be made, which can lead to unforeseen, expensive problems on the production line. Fortunately, basic, fundamental models of significant aspects of the system (first-principles modeling) can be “calibrated” through the use of focused CFD models and empirical data. The result is improved models that allow the designer to bridge the knowledge gap between paper and production.]]></description>
			<content:encoded><![CDATA[<p>Prototypes are essential to testing system performance. However, due to the current technological constraints of creating microscale prototypes, compromises in the characteristics of the prototype usually must be made, which can lead to unforeseen, expensive problems on the production line. Fortunately, basic, fundamental models of significant aspects of the system (first-principles modeling) can be “calibrated” through the use of focused CFD models and empirical data. The result is improved models that allow the designer to bridge the knowledge gap between paper and production.</p>
<p>Read more about the <a href="http://www.micromanufacturing.com/past_editions/pdf/Jan-Feb2010.pdf" target="_blank">symbiosis of modeling and prototyping</a> (PDF) for designing microscale parts in an article I wrote that was published in MICROmanufacturing Magazine this month, page 33 (Jan/Feb 2010, Volume 3, Issue 1).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.keytechinc.com/blog/index.php/2010/the-symbiosis-of-modeling-and-prototyping/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Multi-Tasking Hurts Your Brain</title>
		<link>http://www.keytechinc.com/blog/index.php/2009/multi-tasking-hurts-your-brain/</link>
		<comments>http://www.keytechinc.com/blog/index.php/2009/multi-tasking-hurts-your-brain/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 12:43:40 +0000</pubDate>
		<dc:creator>Jenny Regan</dc:creator>
				<category><![CDATA[Engineering]]></category>
		<category><![CDATA[Problem Solving]]></category>
		<category><![CDATA[Staff]]></category>
		<category><![CDATA[reduce]]></category>
		<category><![CDATA[user]]></category>

		<guid isPermaLink="false">http://www.keytechinc.com/blog/?p=425</guid>
		<description><![CDATA[New research shows that multi-tasking reduces your productivity and impairs your cognitive ability, permanently.]]></description>
			<content:encoded><![CDATA[<p><span style="font-family:Verdana; font-size:10pt">Yikes. New technology and busy schedules are making it increasingly more difficult to focus on one task at a time. And, even if you&#8217;re well-practiced, it may not be surprising that multi-tasking reduces productivity. But, new research shows it also may impair your cognitive ability, permanently.  In the August 24 edition of <a href="http://www.pnas.org/content/106/37/15583.abstract?sid=ce74d4c4-6e72-4e00-b773-148c54034709"><em>The Proceedings of the National Academy of Sciences</em></a><em> (Abstract), </em>Clifford Nass and others at Stanford have shown that multi-tasking reduces productivity, and also cognitive ability.<br />
</span></p>
<p><span style="font-family:Verdana; font-size:10pt">They found that, when test subjects are in situations where there are multiple sources of information coming from the external world or emerging out of memory, they&#8217;re less able to filter out what&#8217;s not relevant to their current goal.  That failure to filter slows them down because they are unable to ignore irrelevant information.  Frequent multi-tasking, such as keeping up with incoming email while reviewing a document and listening to music, may actually decrease your ability to filter through information later, even when you are not multi-tasking.<br />
</span></p>
<p><span style="font-family:Verdana; font-size:10pt">A few years ago I attended a course at MIT Sloan on Product Portfolio Management, taught by Dr. Rebecca Henderson.  Part of the material Dr. Henderson presented included results from research on engineer productivity as a function of the number of projects the engineer was juggling at once.  On reading the recent Stanford research, it struck me that media multi-tasking is probably not that different from juggling multi-project activities, and that proper management of multiple simultaneous projects should include focusing on one thing at a time, as recommended  by the Stanford group.  The MIT-cited productivity data looked something like the plot below, showing that productivity peaks at about two assigned projects, and falls rapidly away as the assigned projects approach 4 and beyond.  It probably goes without saying that the best people on a team will end up with the most projects.  If possible, don&#8217;t let that number of projects exceed 2 or 3.<br />
</span></p>
<p><span style="font-family:Verdana; font-size:10pt">Now, back to my other tasks…</span></p>
<p><span style="font-family:Verdana; font-size:10pt"> </span></p>
<div id="attachment_426" class="wp-caption aligncenter" style="width: 336px"><img class="size-full wp-image-426" title="Multi-tasking as a function of productivity" src="http://www.keytechinc.com/blog/wp-content/uploads/2009/10/Multi-taskingPlot.jpg" alt="Research results on an engineer's productivity as a function of the number of projects they're working on." width="326" height="291" /><p class="wp-caption-text">Research results on an engineer&#39;s productivity as a function of the number of projects they&#39;re working on.</p></div>
]]></content:encoded>
			<wfw:commentRss>http://www.keytechinc.com/blog/index.php/2009/multi-tasking-hurts-your-brain/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Discussion on Micro-Design &amp; Manufacturing Costs</title>
		<link>http://www.keytechinc.com/blog/index.php/2009/a-discussion-on-micro-design-manufacturing-costs/</link>
		<comments>http://www.keytechinc.com/blog/index.php/2009/a-discussion-on-micro-design-manufacturing-costs/#comments</comments>
		<pubDate>Mon, 19 Oct 2009 12:03:16 +0000</pubDate>
		<dc:creator>Conrad Laskowski</dc:creator>
				<category><![CDATA[Engineering]]></category>
		<category><![CDATA[Lab-on-a-chip]]></category>
		<category><![CDATA[Microfluidics]]></category>
		<category><![CDATA[Problem Solving]]></category>
		<category><![CDATA[Product Design]]></category>
		<category><![CDATA[conserve]]></category>
		<category><![CDATA[cost]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Manufacturing]]></category>
		<category><![CDATA[micro]]></category>
		<category><![CDATA[partners]]></category>
		<category><![CDATA[reduce]]></category>
		<category><![CDATA[technology]]></category>

		<guid isPermaLink="false">http://www.keytechinc.com/blog/?p=400</guid>
		<description><![CDATA[A good designer must often think like a manufacturer.  The question, “Can this be made?” is asked over and over again during the design process.  Shortly thereafter, the question also becomes, “Can this be made cheaply?”]]></description>
			<content:encoded><![CDATA[<p>A good designer must often think like a manufacturer.  The question, “Can this be made?” is asked over and over again during the design process.  Shortly thereafter, the question also becomes, “Can this be made <em>cheaply</em>?”  It may be true that in the Field of Dreams <em>if you build it, he will come, </em>but in the World of Consumers <em>if you build it cheaply</em>, <em>he will come</em>… <em>along with his friends, family, and colleagues.</em></p>
<p>The traditional way to make a product cheaper has always been subtraction – in essence, minimizing the size and complexity of a device without sacrificing its performance.  Size and complexity reductions can drive down costs on materials, packaging, and shipping, while also favoring higher-throughput production and the use of disposable parts – an increasingly important consideration in biomedical applications.  With that said, the simpler and smaller approach is not without limitations, and these limitations are being tested now by “hugely small” applications.</p>
<p>In the case of micro-electromechanical systems (MEMS), microfluidic chips, nano-sensing technology, and numerous other scale-intensive fields, reduced size is actually a profound contributor to increased complexity.  And while these innovative fields show tremendous promise for the future, they currently pose costly manufacturing hurdles as a consequence.  The cost of prototyping and manufacturing micro-parts should be carefully weighed when considering whether or not to pursue an otherwise-avoidable micro-approach.  As of now, these costs can quickly consume the benefits of implementing questionable technology since this often requires several iterations of low-volume custom components.  Lab-on-a-chip devices are a good example prone to this paradoxical limbo.  Even a relatively straightforward microfluidic component can require robust interfaces and innovative prototyping and assembly processes to ensure proper functionality.  Before long, the microfluidic system isn’t so “micro” anymore – in size or cost.</p>
<p>So what can designers and our manufacturing comrades do to advance the cost effectiveness of these emerging technologies?  For starters, let’s abandon <em>subtraction</em> and opt for <em>addition</em>;  additional measures to define and achieve design tolerances, additional manufacturing techniques for creating repeatable micron and sub-micron parts, additional design features for ease of alignment during assembly, additional quality assurance measures to assess as-built dimensions, and – most importantly – additional communication between manufacturers and designers for continued success on the field of dreams we now find ourselves playing.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.keytechinc.com/blog/index.php/2009/a-discussion-on-micro-design-manufacturing-costs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disruptive Innovation</title>
		<link>http://www.keytechinc.com/blog/index.php/2009/disruptive-innovation/</link>
		<comments>http://www.keytechinc.com/blog/index.php/2009/disruptive-innovation/#comments</comments>
		<pubDate>Mon, 12 Oct 2009 11:20:38 +0000</pubDate>
		<dc:creator>Chad Schneider</dc:creator>
				<category><![CDATA[Engineering]]></category>
		<category><![CDATA[Problem Solving]]></category>
		<category><![CDATA[Product Design]]></category>
		<category><![CDATA[component selection]]></category>
		<category><![CDATA[conserve]]></category>
		<category><![CDATA[cost]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[innovation]]></category>
		<category><![CDATA[medical]]></category>
		<category><![CDATA[medical devices]]></category>
		<category><![CDATA[Microfluidics]]></category>
		<category><![CDATA[reduce]]></category>
		<category><![CDATA[resource]]></category>
		<category><![CDATA[technology]]></category>

		<guid isPermaLink="false">http://www.keytechinc.com/blog/?p=386</guid>
		<description><![CDATA[Designing medical devices can be an expensive undertaking. It can cost thousands of dollars for a traditional setup to make microfluidic chips or a centrifuge to isolate the components of a multi-constituent sample. Luckily, the creative minds that are focused on solving complex, technical problems don't stop working when there's a tight budget.]]></description>
			<content:encoded><![CDATA[<p>Designing medical devices can be an expensive undertaking. It can cost thousands of dollars for a traditional setup to make microfluidic chips or a centrifuge to isolate the components of a multi-constituent sample. Luckily, the creative minds that are focused on solving complex, technical problems don&#8217;t stop working when there&#8217;s a tight budget.</p>
<p>In <em>The Innovator&#8217;s Prescription</em>, Clayton Christensen discusses how disruptive solutions are the evolutions that take the status quo to the next level. They may or may not be technical leaps, but they are new business models that take Blue-Chip titans by surprise, knocking them from #1 and leaving them trying to catch up. Think Canon taking printing business from Xerox by moving it from the giant mega-machine to the desktop. Christensen&#8217;s book specifically addresses the business models of health-care, but many of the concepts can be easily transported to other industries.</p>
<p>Here are two examples of the DIY mentality creating some disruptive, and hopefully game-changing, solutions to common problems.</p>
<p><strong>Michelle Khine</strong> is an Assistant Professor at UC Irvine working on microfluidics and nanotechnologies. As part of their research, she and her team developed a technique to create microfluidic chips quickly and cheaply using Shrinky Dinks®, an oven, and a printer. Although she was just trying to get her lab up and running quickly, she ended up creating a breakthrough technology that resulted in her being named one of MIT&#8217;s TR35, an award given to top innovators under 35 years old. Yes, the toys of childhood are now the research tools of the future. So, if your boss asks you why you have Rock &#8216;Em Sock &#8216;Em Robots on your desk, you can point to this.</p>
<p><em>Technology Review 2009 &#8211; <a href="http://www.techreview.com/tr35/Profile.aspx?Cand=T&amp;TRID=764" target="_blank">A children&#8217;s toy inspires a cheap, easy production method for high-tech diagnostic chips</a><br />
</em></p>
<p><strong>Chemistry students</strong> at Harvard University devised a $2 device to separate plasma from blood using an egg-beater and a few other parts. The resulting plasma is more than sufficient to detect diseases such as Hepatitis B and cystercosis. While not quite ready for the major laboratories, the device would be useful to doctors in remote locations without the financial resources to send blood off to a lab for testing.</p>
<p><a href="http://www.eurekalert.org/pub_releases/2008-10/rsoc-ec101508.php" target="_blank">$2 egg-beater could save lives in developing countries</a></p>
<div class="wp-caption aligncenter" style="width: 252px"><img title="$2 Device Separates Plasma From Whole Blood" src="http://www.keytechinc.com/blog/wp-content/uploads/2009/10/100709_1143_DisruptiveI1.png" alt="$2 Device Separates Plasma From Whole Blood" width="242" height="363" /><p class="wp-caption-text"> </p></div>
<p style="text-align: center;">
<p>Photo credit: <a href="http://www.eurekalert.org/multimedia/pub/10352.php?from=123606" target="_blank">Malancha Gupta</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.keytechinc.com/blog/index.php/2009/disruptive-innovation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Designing for a Lower Carbon Footprint</title>
		<link>http://www.keytechinc.com/blog/index.php/2009/designing-for-a-lower-carbon-footprint/</link>
		<comments>http://www.keytechinc.com/blog/index.php/2009/designing-for-a-lower-carbon-footprint/#comments</comments>
		<pubDate>Tue, 08 Sep 2009 13:07:50 +0000</pubDate>
		<dc:creator>Chad Schneider</dc:creator>
				<category><![CDATA[Engineering]]></category>
		<category><![CDATA[Product Design]]></category>
		<category><![CDATA[conserve]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[innovation]]></category>
		<category><![CDATA[medical devices]]></category>
		<category><![CDATA[reduce]]></category>

		<guid isPermaLink="false">http://www.keytechinc.com/blog/?p=328</guid>
		<description><![CDATA[Mechanical Engineering Magazine has a good article for designers about significantly lowering the overall energy impact of our products, based on the vision of Saul Griffith, a mechanical engineer and serial inventor. The good news is that we don’t have to start creating medical devices from bamboo.]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal"><a href="http://memagazine.asme.org/Articles/2009/september/Keeps.cfm">Mechanical Engineering Magazine</a> has a good article for designers about significantly lowering the overall energy impact of our products, based on the vision of Saul Griffith, a mechanical engineer and serial inventor. The good news is that we don’t have to start creating medical devices from bamboo.</p>
<blockquote>
<p class="MsoNormal">Griffith sees three routes to cut the amount of energy embedded in personal possessions. One is to simply have less stuff, though that seems more like poverty than efficiency. Another is to make goods more efficiently. That has a role, Griffith said, but a limited one.</p>
<p>“Through material and design changes, say you can cut in half the energy used to make the object,” Griffith said. “For an object that should have a lifetime of one year, if you just do those material changes and design changes, you can halve the amount of energy over that year.</p>
<p>“But because time is in the denominator of the embodied energy equation for an object, it dominates the equation,” Griffith continued. “The easiest way to get the most out of your objects is to make them last a lot longer.”</p></blockquote>
<p class="MsoNormal">I agree with the sentiment, and, “they just don’t make it like they used to” is true far more than it isn’t. But, can this philosophy of making long-lasting products translate into my work as a medical device designer?</p>
<p class="MsoNormal">My first hurdle, and probably the toughest to overcome, is the efficiency of disposables. Because of sterility requirements that prevent the spread of disease and because disposables provide an attractive long term revenue stream, the medical industry has grown quite fond of the disposable model. Quite often, a device has both a durable portion and a disposable one to reduce overall waste. Perhaps we could design parts for chemical or thermal sterilization instead, but there is considerable inertia in the marketplace that will resist such change.</p>
<ul style="margin-top: 0in;" type="disc">
<li class="MsoNormal">Any new products would      have to overcome the perception that it’s not clean unless it came from      the factory in a sealed bag</li>
<li class="MsoNormal">The marketplace would have      to show that disposables are not an attractive business model</li>
</ul>
<p class="MsoNormal">The second hurdle is the pace of innovation. Products and technologies change so quickly that it’s easy to imagine that something will surely supplant my latest product. However, hospitals and insurance companies are generally not considered “early adopters” and can be especially fickle about buying the latest “thing”, probably because of the accountants that are driven by the bottom line. If a product is guaranteed to last for 10 years instead of 3 years, a 3X higher cost can be easily justified.</p>
<p class="MsoNormal"><!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val="&#45;-" /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="0" Name="Hyperlink" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false"<br />
Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" N<br />
ame="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--><!--  /* Font Definitions */  @font-face 	{font-family:"Cambria Math"; 	panose-1:2 4 5 3 5 4 6 3 2 4; 	mso-font-charset:0; 	mso-generic-font-family:roman; 	mso-font-pitch:variable; 	mso-font-signature:-1610611985 1107304683 0 0 159 0;}  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-unhide:no; 	mso-style-qformat:yes; 	mso-style-parent:""; 	margin:0in; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman","serif"; 	mso-fareast-font-family:"Times New Roman";} .MsoChpDefault 	{mso-style-type:export-only; 	mso-default-props:yes; 	font-size:10.0pt; 	mso-ansi-font-size:10.0pt; 	mso-bidi-font-size:10.0pt;} @page Section1 	{size:8.5in 11.0in; 	margin:1.0in 1.0in 1.0in 1.0in; 	mso-header-margin:.5in; 	mso-footer-margin:.5in; 	mso-paper-source:0;} div.Section1 	{page:Section1;} --><!--[if gte mso 10]> <mce:style><!   /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-priority:99; 	mso-style-qformat:yes; 	mso-style-parent:""; 	mso-padding-alt:0in 5.4pt 0in 5.4pt; 	mso-para-margin:0in; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:10.0pt; 	font-family:"Times New Roman","serif";} --> <!--[endif]--></p>
<p class="MsoNormal">I’m sure there are other considerations that keep designers from developing longer-lasting products, but are they reasonable? Can we work around them by thinking differently? Can we improve the bottom line for the medical device consumers while maintaining the standard of care and reducing our impact on the environment?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.keytechinc.com/blog/index.php/2009/designing-for-a-lower-carbon-footprint/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Happy Earth Day from Key Tech</title>
		<link>http://www.keytechinc.com/blog/index.php/2009/happy-earth-day-from-key-tech/</link>
		<comments>http://www.keytechinc.com/blog/index.php/2009/happy-earth-day-from-key-tech/#comments</comments>
		<pubDate>Wed, 22 Apr 2009 11:34:30 +0000</pubDate>
		<dc:creator>Josh Mull</dc:creator>
				<category><![CDATA[Product Design]]></category>
		<category><![CDATA[conserve]]></category>
		<category><![CDATA[innovation]]></category>
		<category><![CDATA[product development]]></category>
		<category><![CDATA[reduce]]></category>

		<guid isPermaLink="false">http://www.keytechinc.com/blog/?p=159</guid>
		<description><![CDATA[When environmental compliance is a design goal early in the development process, these and many other opportunities exist to create innovative products with green footprints.  On this Earth Day, consider how your next product could be made more environmentally sound with some green design principles.]]></description>
			<content:encoded><![CDATA[<div id="attachment_160" class="wp-caption alignleft" style="width: 190px"><img class="size-full wp-image-160" title="Picture of Earth" src="http://www.keytechinc.com/blog/wp-content/uploads/2009/04/gaia_shine.jpg" alt="Picture of Earth" width="180" height="120" /><p class="wp-caption-text"> </p></div>
<p class="MsoNormal">Today, April 22, is Earth Day.<span> </span>It is a day to pause and think about environmental awareness.<span> </span>For most of us, over the course of a day we use hundreds of different products, everything from pens and pencils, to computers, to cars, and yet few people stop to think about the full lifespan of the products they use and the impact those products have on the environment.<span> </span>Luckily, environmental awareness and conservation are growing factors in product development, and thus the products we use are becoming progressively more “green”.<span> </span></p>
<p class="MsoNormal">When a designer focuses on creating a product that will minimize its impact on the environment, there are a number of factors that can be considered, many of them cheap or cheaper than the alternatives.<span> </span>While these may not all be feasible for every product, with a dedicated effort it is always possible to produce products greener than the ones being made today.<span> </span>A couple areas that can be considered when thinking about green development include:</p>
<ul type="circle">
<li class="MsoNormal"><em>Materials </em> – Choosing materials that are recyclable and reusable goes a long way      towards reducing a product’s impact on the environment.<span> </span>Perhaps a product can be molded out of      recyclable plastic or metal, or used 5-10 times instead of once, both means      which allow for an increased lifespan rather than being dropped into a      landfill.</li>
<li class="MsoNormal"><em>Energy      Consumption </em>– The past decade has been all about devices becoming battery      operated.<span> </span>From a design standpoint,      this has forced development to become increasingly focused on efficient      use of the energy available.<span> </span>Many      of the energy consumption tricks that have been learned in the      battery-operated world can be carried over to other devices, even devices      that do not run on batteries.<span> </span>Making all devices energy efficient reduces the amount of energy      that needs to be produced, makes each device cheaper to operate, and decreases      the depletion of resources from our environment. To this affect, the      European Union has gone as far to begin implementing energy consumption      rules for even plugged-in devices, to help reduce unnecessary energy waste.</li>
<li class="MsoNormal"><em>Energy      Harvesting </em>– A burgeoning field of design is based around energy      harvesting, or the ability to gather energy from localized sources such as      solar energy, vibration, heat, or mechanical motion.<span> </span>These devices then become      self-sustainable, drawing no energy from the electric grid or      batteries.<span> </span>From a green designers      view energy harvesting devices create their own energy, with little to no      waste.<span> </span>Energy harvesting technology      has an exciting future in front of it, with the potential to take many      forms of “waste” energy such as heat or vibrations and turn them into a      positive gain.</li>
</ul>
<p class="MsoNormal">When environmental compliance is a design goal early in the development process, these and many other opportunities exist to create innovative products with green footprints.<span> </span>On this Earth Day, consider how your next product could be made more environmentally sound with some green design principles.</p>
<p class="MsoNormal"><em>Photo credit: <a href="http://www.sxc.hu/photo/1158741" target="_blank">Flávio Takemoto</a></em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.keytechinc.com/blog/index.php/2009/happy-earth-day-from-key-tech/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Avoid Common Obstacles in NPD</title>
		<link>http://www.keytechinc.com/blog/index.php/2009/avoid-common-obstacles-product-development/</link>
		<comments>http://www.keytechinc.com/blog/index.php/2009/avoid-common-obstacles-product-development/#comments</comments>
		<pubDate>Mon, 06 Apr 2009 11:00:31 +0000</pubDate>
		<dc:creator>Ben Lane</dc:creator>
				<category><![CDATA[Product Design]]></category>
		<category><![CDATA[obstacles]]></category>
		<category><![CDATA[pipeline]]></category>
		<category><![CDATA[product development]]></category>
		<category><![CDATA[reduce]]></category>
		<category><![CDATA[resource]]></category>
		<category><![CDATA[risk]]></category>

		<guid isPermaLink="false">http://www.keytechinc.com/blog/?p=96</guid>
		<description><![CDATA[There are many ways to lose focus developing a new product, especially with so many people involved and so much at stake. By taking a disciplined approach, one can avoid many of the common pitfalls that cost money and cause delays.]]></description>
			<content:encoded><![CDATA[<div id="attachment_98" class="wp-caption alignright" style="width: 220px"><img class="size-full wp-image-98" title="broken_bridge" src="http://www.keytechinc.com/blog/wp-content/uploads/2009/03/broken_bridge.jpg" alt="broken_bridge" width="210" height="171" /><p class="wp-caption-text">   </p></div>
<p>There are many ways to lose focus developing a new product, especially with so many people involved and so much at stake. By taking a disciplined approach, one can avoid many of the common pitfalls that cost money and cause delays.</p>
<ol>
<li>Develop a <em>realistic </em>schedule and stick to it. Always keep the critical path in mind and avoid letting non-critical path items slow down the project.</li>
<li>If possible, secure sufficient funding to complete development with some extra padding to cover the unavoidable things that come up. While the product development is best done in phases, raising funding in stages is often very inefficient and more expensive because the development team loses momentum if the timing is off.</li>
<li>Develop a comprehensive specification up front and be disciplined about preventing spec creep throughout the project.</li>
<li>Obtain voice of the customer (VOC) input very early in the project, since it will focus and define the feature set outlined in the product specification.</li>
<li>Perform market research prior to embarking on the development. Developing the marketing plan late in the game inevitably leads to costly last minute changes to the product.</li>
<li>Select the development team carefully, ensuring that members of the team communicate well. If outsourcing only a part of the development, make sure that part is very well defined and verify that the outsource partner has a full understanding of the requirements.</li>
<li>Prepare a detailed project plan that identifies the overall schedule with stage gates. The plan must clearly define the criteria necessary to pass each stage gate.</li>
<li>Identify the high risk aspects of the development and address them first in the project plan, before the bulk of the work gets underway. Wasted work equals wasted money.</li>
<li>Line up manufacturing partners as early as possible and involve them in the design process – include them in team meetings, design reviews, etc.</li>
<li>Communicate, communicate, communicate. Weekly team meetings often seem unnecessary, but keeping everyone on the same page throughout the project will reduce expenses in the long run.</li>
<li>Reduce the risk of safety and environmental testing by considering it early in the design.</li>
</ol>
<p>This list goes to 11!</p>
<p><em>Photo credit: <a href="http://www.sxc.hu/photo/726569" target="_blank">H Assaf</a></em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.keytechinc.com/blog/index.php/2009/avoid-common-obstacles-product-development/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More Ways to Conserve Capital in NPD</title>
		<link>http://www.keytechinc.com/blog/index.php/2009/conserve-capital-new-product-development/</link>
		<comments>http://www.keytechinc.com/blog/index.php/2009/conserve-capital-new-product-development/#comments</comments>
		<pubDate>Mon, 30 Mar 2009 15:00:42 +0000</pubDate>
		<dc:creator>Chad Schneider</dc:creator>
				<category><![CDATA[Product Design]]></category>
		<category><![CDATA[conserve]]></category>
		<category><![CDATA[cost]]></category>
		<category><![CDATA[economy]]></category>
		<category><![CDATA[pipeline]]></category>
		<category><![CDATA[product development]]></category>
		<category><![CDATA[reduce]]></category>
		<category><![CDATA[resource]]></category>

		<guid isPermaLink="false">http://www.keytechinc.com/blog/?p=88</guid>
		<description><![CDATA[The economy has many businesses against the ropes, and the rest are tightening their belts in the face of uncertainty. However, you don’t need to completely halt your new product development (NPD) efforts. Here are five ways to spend less while keeping your pipeline moving.]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal">The economy has many businesses against the ropes, and the rest are tightening their belts in the face of uncertainty. However, you don’t need to completely halt your new product development (NPD) efforts. Here are five ways to spend less while keeping your pipeline moving.</p>
<ol>
<li><strong>Use Resources Efficiently</strong></li>
<p class="MsoNormal">Getting a full time, highly trained engineer to do everything in the product development process may move the project along faster, but it can be more expensive. Instead of paying an engineer to perform every task, such as testing a prototype or drafting a report, maybe a lab technician or college intern can run specific parts of the test and write up the final report under the engineer’s supervision. What they cost in inefficiency they often make up for in reduced overhead.</p>
<li><strong>Plan Ahead</strong></li>
<p class="MsoNormal">Nothing wastes time and money more than having to do things over. There’s certainly plenty of iteration required in product development, but making mistakes by rushing or failing to prepare for likely problems should be avoided by taking the time to plan ahead.</p>
<li><strong>Mind Your Perspective</strong></li>
<p class="MsoNormal">While working on a project, it’s easy to get caught up in the details. At least once a week, step back to look at the big picture. Consider what you (and others) are working on and where it lays on the path between the design specification and the finished product. Is your team working efficiently? Are you spending time on minutia too early in the project? Adding (and rebuilding) the draft angles and fillets required for injection-molding are often unnecessary when using most rapid prototyping techniques.</p>
<li><strong>Look Off-The-Shelf</strong></li>
<p class="MsoNormal">Using commercial off-the-shelf parts (COTS) is a great way to reduce the schedule and cut development costs. Designing products takes time, so if someone has already spent the time and money to build a sub-system, try to take advantage. Look for at least one more supplier so you have options if they raise the price, discontinue the product, or don’t meet expectations as a vendor. Sole-source products should be avoided as much as possible, but you can spare yourself some pain by purchasing stock well ahead of time or negotiating a contract with the supplier. Of course, don’t squeeze a square peg in a round hole just to save a buck, either. If you can’t find anything to meet the requirements, and changing the requirements is out of the question, it’s time to design it yourself.</p>
<li><strong>Conserve Energy</strong></li>
<p class="MsoNormal">We have a responsibility to be environmentally conscious, but efforts to that effect can also make financial sense. Reducing the power requirements for your product can decrease the size, weight, and cost of your power supply. It can also increase the battery life for a product used in the field. Choosing the same materials or components within a product or across product lines makes recycling easier, but it also means you can save money by purchasing raw materials in higher quantities.</p>
</ol>
<div id="attachment_49" class="wp-caption aligncenter" style="width: 220px"><img class="size-medium wp-image-49" title="sunburst" src="http://www.keytechinc.com/blog/wp-content/uploads/2009/02/sunburst-300x215.jpg" alt="Keep your pipeline moving" width="210" height="151" /><p class="wp-caption-text">Keep your pipeline moving. Photo credit: Steve Knight</p></div>
]]></content:encoded>
			<wfw:commentRss>http://www.keytechinc.com/blog/index.php/2009/conserve-capital-new-product-development/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Reducing Risk in New Product Development</title>
		<link>http://www.keytechinc.com/blog/index.php/2009/reduce-risk-product-development/</link>
		<comments>http://www.keytechinc.com/blog/index.php/2009/reduce-risk-product-development/#comments</comments>
		<pubDate>Fri, 27 Feb 2009 16:58:01 +0000</pubDate>
		<dc:creator>Ben Lane</dc:creator>
				<category><![CDATA[Problem Solving]]></category>
		<category><![CDATA[Product Design]]></category>
		<category><![CDATA[cost]]></category>
		<category><![CDATA[economy]]></category>
		<category><![CDATA[pipeline]]></category>
		<category><![CDATA[product development]]></category>
		<category><![CDATA[reduce]]></category>
		<category><![CDATA[risk]]></category>

		<guid isPermaLink="false">http://www.keytechinc.com/blog/index.php/?p=50</guid>
		<description><![CDATA[Early stage gates in the pipeline should examine risk – technical risk, market risk, manufacturing risk, regulatory risk, supply chain risk, etc. A well managed pipeline has procedures in place to identify areas of risk and prioritize the risk for further assessment and evaluation. The process of assessing and addressing risk is an excellent, cost effective means of advancing the product pipeline in lean times.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.keytechinc.com/blog/wp-content/uploads/2009/02/pd_pipeline.jpg" rel="lightbox[50]"><img class="alignright size-medium wp-image-47" title="Product Development Pipeline" src="http://www.keytechinc.com/blog/wp-content/uploads/2009/02/pd_pipeline-300x231.jpg" alt="Product Development Pipeline" width="240" height="185" /></a>Businesses with a constant, full, new product development (NPD) pipeline are traditionally the ones that enjoy long term success and growth<span class="MsoCommentReference"><span><span> </span></span></span>. During an economic downturn &#8211; like the one the world is currently experiencing &#8211; <span> </span>when cash and investment is difficult to secure, businesses must find a way to maintain their pipelines so they are positioned for growth when the economy improves.</p>
<p class="MsoNormal">You can save money and continue working with a smaller budget by implementing stage gates early in the product pipeline to examine risk – technical risk, market risk, manufacturing risk, regulatory risk, supply chain risk, etc. A well managed pipeline has procedures in place to identify areas of risk and evaluate them. The process of assessing and addressing risk is an excellent, cost effective means of advancing the product pipeline in lean times.</p>
<ul>
<li><strong>Technical risk</strong> is assessed with basic proof of concept prototypes and technology research that address specific aspects of the product that are considered high risk.</li>
<li><strong>Market risk</strong> is assessed with targeted market studies, limited voice of the customer (VOC) interviews, and other information gathering efforts focused on reducing risk. For medical products, preliminary research to understand the reimbursement environment for the product may be of particular importance.</li>
<li><strong>Regulatory risk</strong> can be minimized through careful planning of the submittal process and preliminary discussions with regulatory personnel. For products that will be launched into regulated environments (medical, nuclear, etc), regulatory acceptance of the product is critical to product success.</li>
<li><strong>Supply chain risk</strong> is assessed through detailed conversations with manufacturing vendors and suppliers. Risk may be significantly minimized by reducing the number of “single-point failures” required for a product such as a sole-sourced component or highly-specialized service. Trusted vendors often prove to be invaluable resources later in the NPD process and should be involved as early as possible.</li>
</ul>
<p class="MsoNormal">The risk assessment phase of NPD is absolutely critical to maintaining the health of the new product pipeline and preventing unpleasant surprises late in the game when a product is almost ready for release. By attacking and reducing risk early, unfeasible projects are eliminated earlier in the pipeline and feasible projects become easier to forecast. It is also a relatively inexpensive phase, as compared to the balance of the development process. In weak economic times, focusing on this early phase can filter multiple concepts, preparing them for the more costly process of advancing them down the pipeline when the economy improves.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.keytechinc.com/blog/index.php/2009/reduce-risk-product-development/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

