<?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>The Arena Blog &#187; Product Strategy</title>
	<atom:link href="http://blog.arenasolutions.com/category/product-strategy/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.arenasolutions.com</link>
	<description>On product design, development &#38; manufacturing</description>
	<lastBuildDate>Wed, 08 Feb 2012 23:20:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>When should your contract manufacturer handle purchasing, inventory and assembly?</title>
		<link>http://blog.arenasolutions.com/outsource-purchasing-inventory-and-assembly/</link>
		<comments>http://blog.arenasolutions.com/outsource-purchasing-inventory-and-assembly/#comments</comments>
		<pubDate>Thu, 01 Sep 2011 18:32:32 +0000</pubDate>
		<dc:creator>Alex Gammelgard</dc:creator>
				<category><![CDATA[Outsourced Manufacturing]]></category>
		<category><![CDATA[Product Strategy]]></category>
		<category><![CDATA[Supply Chain]]></category>

		<guid isPermaLink="false">http://blog.arenasolutions.com/?p=3588</guid>
		<description><![CDATA[For organizations moving from prototype to production, there are a lot of decisions that must be made about how to source parts and build the product. A major part of this process is deciding what can be done in-house, and what must be outsourced. (And who are the partners, and how closely can they be [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.arenasolutions.com/outsource-purchasing-inventory-and-assembly/istock-purchase-order/" rel="attachment wp-att-3593"><img class="alignright size-full wp-image-3593" title="istock purchase order" src="http://blog.arenasolutions.com/wp-content/plugins/autothumb/image.php?src=/wp-content/uploads/2011/09/istock-purchase-order.jpg&amp;aoe=1&amp;q=100&amp;w=426&amp;h=282&amp;hash=ce42b01758b2ede1e2e1dc5b65ec12e7" alt="" /></a>For organizations moving from prototype to production, there are a lot of decisions that must be made about how to source parts and build the product. A major part of this process is deciding what can be done in-house, and what must be outsourced. (And who are the partners, and how closely can they be brought into the fold and how will they work together . . . )</p>
<p>Most companies outsource in some capacity—whether it’s working with an external call center on the sales side, or paying a team in China to manufacture the whole thing—but deciding what to outsource can be tough. While it may be an easy decision to outsource something like custom part manufacturing, when it comes to core business processes like purchasing, inventory management and assembly, the decision gets a bit trickier.</p>
<h2>The benefits of outsourcing purchasing, inventory and assembly</h2>
<p>If you are thinking about outsourcing major processes like purchasing, inventory and assembly, there are definitely benefits to this approach. In offloading some of these processes to a contract manufacturer (CM), you free your in-house team up to focus on design and engineering. In many cases, this is a smart move because it allows your in-house team to develop strength in specific areas. Because purchasing and inventory is resource-intensive, assembling and training a team to manage it in-house can distract from product maintenance, development and other organizational priorities.</p>
<p>For some companies, outsourcing purchasing, inventory and assembly leads to significant cost savings. You may be able to reduce sourcing and shortage issues—since your contract manufacturer team is building the product, it can be synergistic to task them with finding and purchasing the parts as well. Plus, when you outsource the purchasing and inventory piece to a contract manufacturer, there is considerable potential for cost-reduction. Contract manufacturers often do similar work for multiple customers using the same components—if your parts get lumped in a volume purchase, economies of scale can save you some money.</p>
<h2>When does outsourcing purchasing, inventory and assembly make sense?</h2>
<p>While there are benefits in outsourcing purchasing, inventory and assembly, it’s not the right decision for everyone.</p>
<p>To help you decide how much of your production process you should outsource, start by asking yourself the following questions:</p>
<ul>
<li><strong>What is your company trying to do?</strong> (If you are trying to develop core competencies or a competitive advantage in a certain area, you probably shouldn’t outsource it!</li>
<li><strong>How important is it to protect your IP?</strong> Can you take chances with an unknown supply chain partner—is there someone you trust?</li>
<li><strong>What are your priorities as an organization?</strong> Does outsourcing more to a CM free you up to focus on competitive differentiators and core competencies, or are the additional management responsibilities distracting?</li>
<li><strong>What is your tolerance for dependency?</strong> When you outsource major parts of your manufacturing process, you become more reliant on vendors and can increase your vulnerability.</li>
<li><strong>What is the cost of purchasing errors and rework?</strong> Are you willing to risk occasional miscommunications and errors by working with an external team?</li>
<li><strong>What is your system for managing BOMs and change</strong>—some of the outsourcing risks can be mitigated if you have an air-tight solution for collaborating with outside partners.</li>
<li><strong>How efficient are you operationally?</strong> Can your in-house team manage purchasing, or are they too focused on other business aspects?</li>
<li><strong>What’s your budget?</strong> (Everything has a cost!)</li>
</ul>
<p>Once you get an idea of your business reality, you can begin to weigh your options, and decide if outsourcing purchasing, inventory and assembly is right for you.</p>
<h2>A final word on outsourcing partnerships</h2>
<p>If you ultimately decide to turn over purchasing, inventory management or assembly to a vendor, make sure you only work with people you trust! As with any outsourcing decision, selecting reliable vendors who supplement your internal skill sets and industry knowledge is key.</p>
<h2>For more information</h2>
<p><a href="../../../../../is-there-a-one-size-fits-all-manufacturing-strategy/">Is there a one-size-fits-all manufacturing strategy?</a></p>
<p><a href="http://www.arenasolutions.com/pdxviewer/">Share BOMs more effectively with the PDX file standard</a></p>
<p><a href="../../../../../how-small-manufacturers-can-establish-better-outsourcing-relationships-pt-1/">How small manufacturers can establish better outsourcing relationships Pt. 1</a></p>
<p><a href="../../../../../how-small-manufacturers-can-establish-better-outsourcing-relationships-pt-2/">How small manufacturers can establish better outsourcing relationships Pt. 2</a></p>
<p><a href="http://www.arenasolutions.com/manufacturing-outsourcing.html">Tips and resources for managing your outsourcing relationships</a></p>
<p><a href="http://www.arenasolutions.com/resources/whitepapers/dl/scaling-your-business.html">5 steps to scaling your business when your competition stumbles</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.arenasolutions.com/outsource-purchasing-inventory-and-assembly/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Documenting fixtures and jigs—why it’s forgotten, and why it matters</title>
		<link>http://blog.arenasolutions.com/documenting-fixtures-and-jigs/</link>
		<comments>http://blog.arenasolutions.com/documenting-fixtures-and-jigs/#comments</comments>
		<pubDate>Thu, 28 Apr 2011 19:24:57 +0000</pubDate>
		<dc:creator>Alex Gammelgard</dc:creator>
				<category><![CDATA[Document Control]]></category>
		<category><![CDATA[Manufacturing]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Product Strategy]]></category>

		<guid isPermaLink="false">http://blog.arenasolutions.com/?p=2320</guid>
		<description><![CDATA[I wrote a bit on Tuesday about the importance of documenting part information during the design process, and today I’d like to talk about another type of documentation that is commonly overlooked in organizations&#8212;the documentation of fixtures and jigs. We talk to many people working in high-functioning manufacturing departments who document everything thoroughly and consistently [...]]]></description>
			<content:encoded><![CDATA[<p><a rel="attachment wp-att-2322" href="http://blog.arenasolutions.com/documenting-fixtures-and-jigs/t-slots-on-the-table-of-a-milling-machine/"><img class="alignleft size-full wp-image-2322" title="T-Slots on the table of a milling machine" src="http://blog.arenasolutions.com/wp-content/plugins/autothumb/image.php?src=/wp-content/uploads/2011/04/istock-fixture.jpg&amp;aoe=1&amp;q=100&amp;w=310&amp;h=205&amp;hash=ae126278ecba9faefac00659efa32f61" alt="" /></a>I wrote a bit on <a href="../../../../../why-engineers-who-hate-documenting-their-designs-should-do-it-anyway/">Tuesday</a> about the importance of documenting part information during the design process, and today I’d like to talk about another type of documentation that is commonly overlooked in organizations&#8212;the documentation of fixtures and jigs.</p>
<p>We talk to many people working in high-functioning manufacturing departments who document everything thoroughly and consistently except for the fixtures they use to make their product. Big mistake!</p>
<p>Failing to document your fixtures and jigs can cause huge problems down the road, so you need to make it a regular part of your process.</p>
<h2>Why do manufacturers forget to document their fixtures?</h2>
<p>Fixtures are important—they are the tools with which you build your product. So why do so many organizations forget to document them?</p>
<p>The most common reason is that fixtures can be built over time as needed, and are usually seen as “tools” and not “products”&#8212;because of this, many organizations forget to assign formal processes for them.</p>
<p>The perception that fixtures are a secondary concern begins early in an organization’s life. When a company first starts up things happen fast, and no one has time to worry about developing formal documentation processes for fixtures—especially if there are only a few people in the company. At this stage in the game things are very tactical, so plans and processes are implemented as an after-thought in the mad scramble to get products built and out the door.</p>
<p>In an ideal world, documentation for fixtures would be adopted immediately, or at least incorporated into the process as soon as your head is above water, but once things begin to stabilize fixture documentation usually takes a back-seat to hiring additional support and building out product lines. At this point a precedent has been set, and fixtures are typically forgotten until they break or need to be replaced.</p>
<h2>So you don’t document your fixtures and jigs—what’s the worst that can happen?</h2>
<p>Consider this scenario.</p>
<p>Something changes with your contract manufacturer and your only viable option is to leave. Of course your CM isn’t happy, but you’ve done the research and a continued partnership just doesn’t make sense. As you make the transition you do your best to capture all the information your new CM will need, but right after the papers have been signed you realize you’re not sure how to build an important fixture. (Or what more commonly happens is that you don’t realize the oversight until your fixtures break a few months or years down the road!)</p>
<p>Now this is a bad situation with two choices—reverse engineer the fixture, or crawl back to your former CM and hope they can help you recreate it.</p>
<p>The last thing you want is your engineering team out on the floor with calipers trying to reverse engineer a fixture—at $70-$100 an hour, this is expensive labor! An even worse possibility is that you can’t convince your old CM to help you out (even at a premium) so production stops.</p>
<p>If you’ve never experienced this personally, you probably know someone who has. It’s a high price to pay for something that is completely avoidable—if you document your fixtures and jigs.</p>
<h2>If you’re still not convinced you need to document your fixtures . . .</h2>
<p>With proper fixture and jig documentation, not only can you avoid line delays or stops, but you can find opportunities to eliminate waste in your manufacturing line, and become a more lean and efficient organization. And if you’re trying to decrease defects by implementing a Six Sigma or lean manufacturing strategy, the best place to start is with your fixtures—proper documentation allows you to see if there are errors or inefficiencies associated with your fixtures so you can make a change.</p>
<p>Even if you outsource your manufacturing, reviewing your processes, and keeping documentation up-to-date should be an in-house competency. Think of it this way—manufacturing is the only part of business where saving a dollar is making a dollar, so putting resources in place to understand and refine how your products get to market is a great way to improve your margins.</p>
<h2>For more information on documenting your fixtures:</h2>
<ul>
<li><a href="http://www.arenasolutions.com/jig-fixture-design.html">Why You Should Document Fixture and Jig Designs</a></li>
<li><a href="http://www.arenasolutions.com/finding-electronic-components.html">Tips For Finding &amp; Documenting Electronic Components</a></li>
<li><a href="http://www.arenasolutions.com/resources/dispatches/complete-bill-of-material.html">Everything Goes Boom: 3 tips for a complete AND correct BOM</a></li>
</ul>
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 889px; width: 1px; height: 1px; overflow: hidden;"><!--[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> <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="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" 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" Name="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]--><!--[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-top:0in; 	mso-para-margin-right:0in; 	mso-para-margin-bottom:10.0pt; 	mso-para-margin-left:0in; 	line-height:115%; 	mso-pagination:widow-orphan; 	font-size:11.0pt; 	font-family:"Calibri","sans-serif"; 	mso-ascii-font-family:Calibri; 	mso-ascii-theme-font:minor-latin; 	mso-hansi-font-family:Calibri; 	mso-hansi-theme-font:minor-latin;} --> <!--[endif]--><span style="font-size: 11pt; line-height: 115%; font-family: &amp;amp;amp;"><a href="http://www.arenasolutions.com/jig-fixture-design.html">http://www.arenasolutions.com/jig-fixture-design.html</a></span></div>
]]></content:encoded>
			<wfw:commentRss>http://blog.arenasolutions.com/documenting-fixtures-and-jigs/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Be ready when opportunity knocks: 5 steps manufacturers can take to prepare for growth</title>
		<link>http://blog.arenasolutions.com/manufacturing-growth-steps/</link>
		<comments>http://blog.arenasolutions.com/manufacturing-growth-steps/#comments</comments>
		<pubDate>Wed, 12 Jan 2011 13:00:35 +0000</pubDate>
		<dc:creator>RoseAnne Moises</dc:creator>
				<category><![CDATA[Business Strategy]]></category>
		<category><![CDATA[Operations]]></category>
		<category><![CDATA[Product Strategy]]></category>
		<category><![CDATA[Supply Chain]]></category>

		<guid isPermaLink="false">http://blog.arenasolutions.com/?p=1502</guid>
		<description><![CDATA[Most manufacturers strive for growth and expansion, looking for opportunities to gain greater market share and see their products succeed. But the truth is, today&#8217;s opportunities for expansion often come at unexpected times and in unexpected ways. And if a company is not well-equipped with the organizational, product development and manufacturing processes to capitalize on [...]]]></description>
			<content:encoded><![CDATA[<p>Most manufacturers strive for growth and expansion, looking for opportunities to gain greater market share and see their products succeed. But the truth is, today&#8217;s opportunities for expansion often come at unexpected times and in unexpected ways. And if a company is not well-equipped with the organizational, product development and manufacturing processes to capitalize on them, those opportunities can go just as quickly as they come.</p>
<p><em>How can you be ready to answer when opportunity knocks?</em> <strong>Start preparing now.</strong> When we look at our customers who’ve successfully capitalized on opportunities for growth, what we see are companies that think about what it takes to scale and ready themselves even before the need arises. Based on the successes we&#8217;ve observed, Arena recently published <a href="http://www.arenasolutions.com/resources/whitepapers/dl/scaling-your-business.html">an article that offers manufacturing businesses a step-by-step template for building a solid foundation for scaling</a> their businesses in 2011 and beyond.</p>
<p>The steps are summarized below. You can also download a <a href="http://www.arenasolutions.com/images/pdf/rc_docs/whitepapers/Arena_WP_Five_Steps_to_Growth.pdf"><strong>free one-page checklist of the 5 steps manufacturers can take to prepare for growth</strong></a>.</p>
<h2><em style="font-family:georgia; color:#999999; font-weight:normal;">Step 1:</em> Know your products</h2>
<p>If you’re a manufacturer, your product is the core of your business. Most manufacturers are used to thinking of their products holistically (i.e. as a complete final product) but it’s just as important to think about the collection of individual parts that come together to create those products. Thus, having control over part data is vital to your products’ success.</p>
<h3>Know your parts</h3>
<p>To establish control, you must first know your master parts list, which should encompass all the details you need to order, build, receive and qualify your parts. Creating a centralized system that manages this information is helpful, especially when the information has to be shared across many departments of your company. Arena offers four tips on how to establish control over your master parts list (see <a href="http://www.arenasolutions.com/resources/whitepapers/dl/scaling-your-business.html">the article</a> for a detailed explanation):</p>
<ol>
<li><em>Remove duplicate part numbers</em></li>
<li><em>Reduce the noise of inactive parts</em></li>
<li><em>Document your parts well</em></li>
<li><em>Find alternatives and multiple sources</em></li>
</ol>
<h3>Know your BOMs</h3>
<p>Aside from knowing your master parts list, you must also understand your product bill of materials (BOM), the DNA of your product. It shows how each part is associated to the whole and how all the parts work together. Revisions and changes in parts and specifications are inevitable during the product development process, and your BOM needs to reflect these changes. It can be chaotic without full control over the information in your BOM. An accurate, up-to-date BOM, on the other hand, minimizes miscommunication and misinformation. To establish control over your product bill of materials, you must:</p>
<ol>
<li><em>Control product revisions</em></li>
<li><em>Track product compliance</em></li>
<li><em>Locate cross-product commonalities</em></li>
<li><em>Identify substitute parts</em></li>
</ol>
<p>These steps are described in more detail in the article (and yes, full disclosure, Arena does offer <a href="http://www.arenasolutions.com/product/index.html">software that helps manufacturers centralize their product data and capture complete BOMs</a>).</p>
<h3>Know your key components</h3>
<p>The last part of knowing your product is knowing your key components, so you can proactively find solutions before an issue brings down your line.  To identify the parts that represent significant risks to production, manufacturers should closely monitor long lead times, expensive components or assemblies and single sources.</p>
<h2><em style="font-family:georgia; color:#999999; font-weight:normal;">Step 2:</em> Know your supply chain</h2>
<p>Although control over every phase of your manufacturing process might seem ideal, the truth is that it simply isn’t an option for most businesses. Instead, most manufacturers rely on a network of partners and suppliers to get their products designed and manufactured.  For your supply chain to be efficient and stable, it is important to know the status of your partners and suppliers, as well as the state of your relationships with them.</p>
<ul>
<li><em>Check your sources.</em> Periodically checking in with your suppliers and partners minimizes the miscommunication that can lead to problems in the later manufacturing phases. Checking in also helps ensure that everyone is working with clean, accurate information and that no changes or revisions go unnoticed. Keeping a close eye on component lifecycles, custom part manufacturers and supply stability will also help you evaluate whether a potential supply chain setback will be a major or minor one.</li>
<li><em>Evaluate your sourcing relationships</em>. The better your relationship is with your partners, the more likely they’ll make choices that help you both succeed. Good relationships establish open communication paths, mutual understanding and respect. The Arena article advises companies to have detailed contracts with their key suppliers and CMs are in place and also to regularly evaluate the performance and relationships of their vendors.</li>
</ul>
<h2><em style="font-family:georgia; color:#999999; font-weight:normal;">Step 3:</em> Know your processes</h2>
<p>Manufacturers know that it takes systematic and sometimes complex processes to build a good working product. Evaluate your process documentation, yields and rework and repeatable processes to make sure your assembly process is efficient, clear-cut and ready to grow.</p>
<h2><em style="font-family:georgia; color:#999999; font-weight:normal;">Step 4:</em> Know your business</h2>
<p>The success of your product is determined by more than just the outcome of the assembly process; it also requires support from the rest of your organization.</p>
<p>To determine if your company is ready to get your product into the hands of customers:</p>
<ul>
<li><em>Evaluate full product impact.</em> The article describes it as thinking through both “what-if” and “and-then” scenarios, in other words considering what would need to change in order to grow and how those changes would affect your business. Doing so will help you be ready to scale your organization, adapt to changes, confront any problems quickly and effectively and balance different stakeholders’ needs.</li>
<li><em>Know your financial health. </em>Understanding your cash flow situation can help you make better decisions about when to spend or invest. Don’t hesitate to consult a professional to help you explore your financial options and think through when and how to expand. It’s also important to know your company’s contractual commitments with suppliers so you can be ready to renegotiate or seek out alternative options if an obstacle arises.</li>
</ul>
<h2><em style="font-family:georgia; color:#999999; font-weight:normal;">Step 5:</em> Look for opportunities</h2>
<p>Once you’re better prepared for growth, you can more successfully plan for the future. Be on the defense: identify risks and be ready to respond to changes quickly and effectively. But don’t be afraid to play offense: look for business opportunities and follow up on them when possible. With proactive planning, you’ll be prepared to capitalize on market opportunities, even when they’re most unexpected.</p>
<p>For more information, <a href="http://www.arenasolutions.com/resources/whitepapers/dl/scaling-your-business.html">read the complete article on the 5 steps manufacturers can take to prepare for growth</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.arenasolutions.com/manufacturing-growth-steps/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Making experimentation part of product development</title>
		<link>http://blog.arenasolutions.com/making-experimentation-part-of-product-development/</link>
		<comments>http://blog.arenasolutions.com/making-experimentation-part-of-product-development/#comments</comments>
		<pubDate>Tue, 04 Jan 2011 13:00:18 +0000</pubDate>
		<dc:creator>Jennifer Bomze</dc:creator>
				<category><![CDATA[Business Strategy]]></category>
		<category><![CDATA[Industry News & Trends]]></category>
		<category><![CDATA[Product Development]]></category>
		<category><![CDATA[Product Strategy]]></category>

		<guid isPermaLink="false">http://blog.arenasolutions.com/?p=1617</guid>
		<description><![CDATA[A recent Harvard Business Review (HBR) blog post makes the case for experimentation as a key part of the product development process. Authors H. James Wilson and Kevin Desouza cite a December 2010 Babson Executive Education survey of 149 senior executives, in which 51% of respondents say that “experimentation is now their organization&#8217;s preferred approach [...]]]></description>
			<content:encoded><![CDATA[<p><!-- p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Helvetica} p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Helvetica; min-height: 13.0px} span.s1 {text-decoration: underline ; color: #0000ff} span.Apple-tab-span {white-space:pre} ol.ol1 {list-style-type: decimal} -->A recent <a href="http://blogs.hbr.org/research/2010/12/while-he-was-at-amazon.html">Harvard Business Review (HBR) blog post</a> makes the case for experimentation as a key part of the product development process. Authors H. James Wilson and Kevin Desouza cite a December 2010 Babson Executive Education survey of 149 senior executives, in which 51% of respondents say that “experimentation is now their organization&#8217;s preferred approach to understanding and acting on potential opportunity.” Among executives at the highest growth firms, the percentage doing experimentation was even higher at 61%, suggesting a possible link between experimentation and &#8220;higher revenue performance.&#8221;</p>
<p>In the post, Wilson and Desouza discuss the other benefits of experimenting (decision-making informed by data, not just gut feelings) and the increasing ease of experimentation as affordable tools come “out of the R&amp;D labs into the mainstream.” They also describe the three types of experimentation that their research has shown to be the “most accessible” for organizations:</p>
<ol>
<li>Prototyping</li>
<li>Simulation</li>
<li>A/B Testing</li>
</ol>
<p>The <a href="http://blogs.hbr.org/research/2010/12/while-he-was-at-amazon.html">HBR blog post</a> examines each type of experimentation in more detail and includes links to additional information about experimentation tools and real-life experimentation examples.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.arenasolutions.com/making-experimentation-part-of-product-development/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>More of a good thing: Extending your product line without inventing a brand new product</title>
		<link>http://blog.arenasolutions.com/more-of-a-good-thing-extending-your-product-line-without-inventing-a-brand-new-product/</link>
		<comments>http://blog.arenasolutions.com/more-of-a-good-thing-extending-your-product-line-without-inventing-a-brand-new-product/#comments</comments>
		<pubDate>Tue, 13 Jul 2010 15:00:38 +0000</pubDate>
		<dc:creator>Kathy Davies</dc:creator>
				<category><![CDATA[Arena Customers & Partners]]></category>
		<category><![CDATA[Business Strategy]]></category>
		<category><![CDATA[Product Design]]></category>
		<category><![CDATA[Product Strategy]]></category>

		<guid isPermaLink="false">http://blog.arenasolutions.com/?p=1132</guid>
		<description><![CDATA[Marc wrote recently about the motorized bicycle that is the latest addition to the Volkswagen product line and a way for the company to extend its brand into an adjacent market. And while innovation is often at the heart of new product development, it is worth pointing out that building a product line can be [...]]]></description>
			<content:encoded><![CDATA[<p>Marc wrote recently about <a href="http://blog.arenasolutions.com/brand-mobility-volkswagen-shows-it’s-not-only-about-cars/">the motorized bicycle that is the latest addition to the Volkswagen product line</a> and a way for the company to extend its brand into an adjacent market. And while innovation is often at the heart of new product development, it is worth pointing out that building a product line can be done without new invention. By varying peripheral product features, cosmetic details or packaging it is possible to use your existing technology and quickly expand your product line to reach new markets. Take <a href="http://www.camelbak.com/">Camelbak</a>:</p>
<p><a href="http://blog.arenasolutions.com/wp-content/uploads/2010/07/camelback1.png"><img class="alignright size-full wp-image-1169" title="camelback" src="http://blog.arenasolutions.com/wp-content/plugins/autothumb/image.php?src=/wp-content/uploads/2010/07/camelback1.png&amp;aoe=1&amp;q=100&amp;w=443&amp;h=269&amp;hash=a6df6af625155f81bba5e1be62b6cbde" alt="" /></a>The company, an Arena customer, started making hands-free hydration systems for mountain bikers and motocross riders, “allowing them to drink without taking their hands off of the handlebars in technical terrain.” Since then “Camelbaks” have become popular for use while hiking, running, snowboarding and skiing in addition to cycling. They typically consist of a capped pouch of water with a long tube and bite valve, enclosed in some wearable form factor.</p>
<p>From this simple concept, Camelbak has built an incredible range of similar but specialized products: more than 90 hydration pack styles for recreational and military use. The company dominates the market through good use of technology (easy-to-use bite valve, rugged materials, easy opening and leakproof cap) and a willingness to customize its product for new sports or situations. Camelbak makes  a pack for refilling other packs (the Squadpak, 25L capacity) for use by a military unit, packs specifically designed for women, packs for use while skiing in sub-zero temperatures, packs for use under body armor and even a variety of “mini” packs (50 oz) for kids.</p>
<p>Another strategy is the purely cosmetic. Take <a href="http://www.envirosax.com/">Envirosax</a>. These reusable shopping bags fold up into compact snap close packages. Envirosax has built its brand by offering a wide array of colors and graphics. Same bag design – different looks to appeal to different market segments.</p>
<p style="text-align: center;"><a href="http://blog.arenasolutions.com/wp-content/uploads/2010/07/envirosax.png"><img class="size-full wp-image-1171 aligncenter" title="envirosax" src="http://blog.arenasolutions.com/wp-content/plugins/autothumb/image.php?src=/wp-content/uploads/2010/07/envirosax.png&amp;aoe=1&amp;q=100&amp;w=568&amp;h=126&amp;hash=edbc1af6ecdecdcdb8fba529e074986f" alt="" /></a></p>
<p>You can also vary packaging and pricing. In addition to slight product differences, <a href="http://www.superfeet.com/">Superfeet</a> uses color, pricing and packaging changes to sell its insoles to multiple market segments. The packaging and pricing for the product targeted at women differs from that aimed at athletes, “on their feet” professionals (doctors, nurses) or industrial workers. Inside the box you will find the same core product, with minor tweaks for the specific user segment.</p>
<p>These three companies have built on their primary product offering and diversified into adjacent markets without inventing a whole new product. Their strategy isn’t for everyone, but it might be worth considering whether your technology can be reused in new form factors or colors or marketed in a new way to appeal to other user groups. Who knows, variation on a theme might lead to your own empire.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.arenasolutions.com/more-of-a-good-thing-extending-your-product-line-without-inventing-a-brand-new-product/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Brand mobility: Volkswagen shows it’s not only about cars</title>
		<link>http://blog.arenasolutions.com/brand-mobility-volkswagen-shows-it%e2%80%99s-not-only-about-cars/</link>
		<comments>http://blog.arenasolutions.com/brand-mobility-volkswagen-shows-it%e2%80%99s-not-only-about-cars/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 15:00:02 +0000</pubDate>
		<dc:creator>Marc Escobosa</dc:creator>
				<category><![CDATA[Business Strategy]]></category>
		<category><![CDATA[Cool Products]]></category>
		<category><![CDATA[Product Strategy]]></category>

		<guid isPermaLink="false">http://blog.arenasolutions.com/?p=1030</guid>
		<description><![CDATA[According to Marty Neumeier in his excellent book, The Brand Gap, a brand, simply put, is “a person’s gut feeling about a product, service or organization.” But all too often, when considering a product roadmap, companies become hemmed in by what they perceive to be their expertise without realizing just how many things can contribute [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-medium wp-image-1037" title="VW electric bike" src="http://blog.arenasolutions.com/wp-content/plugins/autothumb/image.php?src=/wp-content/uploads/2010/06/Picture-1-300x215.png&amp;aoe=1&amp;q=100&amp;w=300&amp;h=215&amp;hash=7899a15fdd2cdff30f144000a13639c0" alt="VW electric bike" />According to Marty Neumeier in his excellent book, <a href="http://www.amazon.com/Brand-Gap-Expanded-Marty-Neumeier/dp/0321348109">The Brand Gap</a>, a brand, simply put, is <a href="http://www.slideshare.net/coolstuff/the-brand-gap">“a person’s gut feeling about a product, service or organization.”</a> But all too often, when considering a product roadmap, companies become hemmed in by what they perceive to be their expertise without realizing just how many things can contribute to people’s gut feelings. In so doing, they lose out on lateral opportunities in nearby market segments with perfect brand overlap.</p>
<p>Consider Volkswagen’s recently unveiled concept for a motorized, foldable bicycle. When announcing its first ever two-wheeler at the <a href="http://www.china-autoshow.com/2010bjx/En/">Auto China 2010</a> exhibition in April, VW’s chief of research and development, Dr. Ulrich Hackenberg was quick to point out that Volkswagen&#8217;s &#8220;focus on mobility&#8221; extends well beyond cars. The implication is that VW intends to take advantage of the room under its brand promise for more integrated solutions for getting you around, regardless of whether an automobile is involved.</p>
<p>At the same time, VW is careful to not distance the concept too far from its core brand values. The bike’s 12.5 mile range is clearly designed for short day trips (after having driven somewhere perhaps?) and with a top speed of 12 mph or so, it’s certainly not intended as a replacement for a car. And then, as if to leave no doubt about the symbiotic relationship between the bike and its cars, they show how the bike folds up to fit neatly into your VW’s spare tire compartment.</p>
<p><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="600" height="360" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0">
<param name="allowFullScreen" value="true" />
<param name="allowscriptaccess" value="always" />
<param name="src" value="http://www.youtube.com/v/MJUx8W4t360&amp;hl=en_US&amp;fs=1&amp;" />
<param name="allowfullscreen" value="true" /><embed type="application/x-shockwave-flash" width="600" height="360" src="http://www.youtube.com/v/MJUx8W4t360&amp;hl=en_US&amp;fs=1&amp;" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
<p>Next time you are planning your product roadmap, consider what adjacent customer experiences are there for the taking if you just expand your product offerings into them.</p>
<p>Read more on <a href="http://green.autoblog.com/2010/04/28/volkswagen-bik-e-replaces-spare-tire-with-electric-mobility-devi/">Autoblog Green</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.arenasolutions.com/brand-mobility-volkswagen-shows-it%e2%80%99s-not-only-about-cars/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Listen up! The web is speaking. (Is it your product they&#8217;re discussing?)</title>
		<link>http://blog.arenasolutions.com/listen-up-the-web-is-speaking/</link>
		<comments>http://blog.arenasolutions.com/listen-up-the-web-is-speaking/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 16:00:28 +0000</pubDate>
		<dc:creator>Kathy Davies</dc:creator>
				<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Product Strategy]]></category>

		<guid isPermaLink="false">http://blog.arenasolutions.com/?p=275</guid>
		<description><![CDATA[Anyone building products for the public or handling product service should check out this blog post chronicling a woman’s battle for appropriate customer service with a washing machine company—and how her public complaints to social networking sites got results. Her story is both hilarious and a great object lesson about the power of social media in [...]]]></description>
			<content:encoded><![CDATA[<p>Anyone building products for the public or handling product service should check out <a href="http://www.dooce.com/2009/08/28/containing-capital-letter-or-two">this blog post</a> chronicling a woman’s battle for appropriate customer service with a washing machine company—and how her public complaints to social networking sites got results. Her story is both hilarious and a great object lesson about the power of social media in the marketplace.</p>
<p>Every day, thousands of bloggers post about the minutiae of their lives, including their interactions with the products that your company builds. Some bloggers have hundreds, thousands or even hundreds of thousands of followers, and their stories carry weight in a way that no advertising campaign can—they are the judgment of the masses for the masses. Twitter, Facebook and blogs give the market a new outlet for complaints, accolades and general product feedback. An influential blogger can make or break a product. Think Oprah’s Book Club, only on the internet—those books sell, baby!</p>
<p>If you’re not already monitoring what’s being said online about your product, service or company, you may wish to start. You can choose from a proliferation of <a href="http://mashable.com/2008/12/24/free-brand-monitoring-tools/">free</a> and <a href="http://mashable.com/2008/12/29/brand-reputation-monitoring-tools/">paid</a> tools that search social networks, groups, blogs, boards and other consumer-generated media (CGM) platforms for names or keywords associated with your product.</p>
<p>When you’re ready, you can start engaging in the conversation too. Participate in the networks and social media platforms relevant to your market or try a tool like <a href="http://getsatisfaction.com/">GetSatisfaction.com</a>, which provides a venue for dialogue between customers with questions or problems and other customers and company representatives.</p>
<p>At Arena, our marketing team monitors internet activity by setting Google and Twitter alerts and using web analytics tools. We also have <a href="http://forums.arenasolutions.com/">discussion forums</a> where customers can talk to each other and a presence on <a href="http://www.facebook.com/pages/Arena-Solutions/243976072650">Facebook</a>, <a href="http://twitter.com/arenasolutions">Twitter</a> and <a href="http://www.linkedin.com/groups?about=&amp;gid=1961565&amp;trk=anet_ug_grppro">LinkedIn</a>. Feel free to check out what we’re doing as an example…just know that we’re still figuring it out too!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.arenasolutions.com/listen-up-the-web-is-speaking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;We have this product idea&#8230;it&#8217;s going to change the world!&#8221;</title>
		<link>http://blog.arenasolutions.com/we-have-this-product-idea-its-going-to-change-the-world/</link>
		<comments>http://blog.arenasolutions.com/we-have-this-product-idea-its-going-to-change-the-world/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 16:00:06 +0000</pubDate>
		<dc:creator>Helen Shaughnessy</dc:creator>
				<category><![CDATA[Innovation]]></category>
		<category><![CDATA[New Product Development]]></category>
		<category><![CDATA[Product Strategy]]></category>

		<guid isPermaLink="false">http://blog.arenasolutions.com/?p=366</guid>
		<description><![CDATA[When I was a design consultant, potential clients would tell us all about how their cool new products were going to take over the market. Sometimes a company&#8217;s product really was cool and new&#8211;though it was doubtful it was going to make its mark in the manner envisioned. Occasionally a company was so enamored with [...]]]></description>
			<content:encoded><![CDATA[<p>When I was a design consultant, potential clients would tell us all about how their cool new products were going to take over the market.</p>
<p>Sometimes a company&#8217;s product really was cool and new&#8211;though it was doubtful it was going to make its mark in the manner envisioned. Occasionally a company was so enamored with its ideas and its technology that its team was unable to step back and see other potential uses or markets for the product.</p>
<p>Heather Fleming from Catapult Design has put together a list of <a href="http://catapultdesign.org/recent-blogs/5-lies">5 justifications people tell themselves</a> when developing technology and products for people in need. Many apply to product development in general, not just product development for the third world.</p>
<p>Maintaining perspective when designing a new product is important. Projects can be so exciting and full of discovery that it is easy to get carried in new directions. It takes discipline, but by periodically evaluating your work, you can make sure the product you&#8217;re developing still meets the needs of the market, the goals for the project and the objectives of your company. It&#8217;s the difference between developing great products and developing products that could have been great if only&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.arenasolutions.com/we-have-this-product-idea-its-going-to-change-the-world/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Exactly who said this was a good idea?</title>
		<link>http://blog.arenasolutions.com/exactly-who-said-this-was-a-good-idea/</link>
		<comments>http://blog.arenasolutions.com/exactly-who-said-this-was-a-good-idea/#comments</comments>
		<pubDate>Wed, 23 Dec 2009 23:30:46 +0000</pubDate>
		<dc:creator>Joe Lipple</dc:creator>
				<category><![CDATA[New Product Development]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Product Strategy]]></category>

		<guid isPermaLink="false">http://blog.arenasolutions.com/?p=81</guid>
		<description><![CDATA[My Pragmatic Marketing mug stares at me every morning with the same stark reminder: Your opinion, although interesting, is irrelevant. It’s a nice grounding statement, and more constructive than my Onion mug. But my mug delivers more than caffeinated goodness—it delivers a message that I need to step back whenever I get excited about a [...]]]></description>
			<content:encoded><![CDATA[<p>My <a title="Pragmatic Marketing mug" href="http://www.cafepress.com/pragmaticmarket.56372820">Pragmatic Marketing mug</a> stares at me every morning with the same stark reminder:</p>
<blockquote><p>Your opinion, although interesting, is irrelevant.</p>
</blockquote>
<p><img class="size-full wp-image-86 alignright" style="margin-left:20px; margin-bottom:30px;" title="mug" src="http://blog.arenasolutions.com/wp-content/plugins/autothumb/image.php?src=/wp-content/uploads/2009/12/mug.jpg&amp;aoe=1&amp;q=100&amp;w=240&amp;h=240&amp;hash=bfe8b1e9e3ad68d6b43febe76cf2ecf8" alt="mug" /><br /> It’s a nice grounding statement, and more constructive than my <a title="Onion mug" href="http://store.theonion.com/product/you-are-dumb-mug,22/">Onion mug</a>. But my mug delivers more than caffeinated goodness—it delivers a message that I need to step back whenever I get excited about a new idea, technology or cool feature and ask, “Does anybody else care?” Or, more specifically, “Will anyone pay money for this?”</p>
<p>After all, we don’t want to end up with the software equivalent of <a href="http://www.smuckers.com/products/category.aspx?groupId=2&amp;categoryId=4">Smuckers Goober</a>, <a href="http://www.asontv.com/household/whizzer-cordless-scissors.html">Whizzers cordless power scissors</a>, or the <a href="http://www.amazon.com/JL421-Badonkadonk-Land-Cruiser-Tank/dp/B00067F1CE">JL421 Badonkadonk Land Cruiser/Personal Tank</a>. (Although I’ll admit that each of these products fascinates me in some way (cough, cough, Christmas present)….)</p>
<p>All product companies face the same challenge: coming up with what to build—which means figuring out which market problems to solve and for whom. Our product happens to be software, but the challenge is still there—and our approach to gathering and processing market intelligence is one that can be used by product companies of all types.</p>
<p>It’s a process that can be summed up in 3 steps:</p>
<ol>
<li> <a href="http://blog.arenasolutions.com/3-steps-to-getting-cheap-easy-and-relevant-product-feedback-step-1-go-get-it/">Go get it.</a></li>
<li> <a href="http://blog.arenasolutions.com/3-steps-to-getting-cheap-easy-and-relevant-product-feedback-step-2-share-it/">Share it.</a></li>
<li> <a href="http://blog.arenasolutions.com/product-feedback-part3/">Live it.</a></li>
</ol>
<p>I promise to expand on those steps in future posts <em>[UPDATE: now available--use links above]</em>, but as long as we’re on the subject of Christmas presents for me, I’ve been wondering: How did the <a href="http://www.amazon.com/iCarta-iPod-Stereo-Tissue-Holder/dp/B000HWX1J8">iPod Dock/Toilet Paper Holder</a> make it off the sketchpad and into the market anyway?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.arenasolutions.com/exactly-who-said-this-was-a-good-idea/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Interested in products? You’ve come to the right place.</title>
		<link>http://blog.arenasolutions.com/interested-in-products-youve-come-to-the-right-place/</link>
		<comments>http://blog.arenasolutions.com/interested-in-products-youve-come-to-the-right-place/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 12:00:32 +0000</pubDate>
		<dc:creator>Jennifer Bomze</dc:creator>
				<category><![CDATA[Arena]]></category>
		<category><![CDATA[Innovation]]></category>
		<category><![CDATA[Product Strategy]]></category>

		<guid isPermaLink="false">http://blog.arenasolutions.com/?p=39</guid>
		<description><![CDATA[Welcome to the official blog of Arena Solutions. If you haven’t heard of Arena, the quick version is this: Arena serves small and mid-size manufacturers by providing on-demand software (also known as software-as-a-service or a SaaS solution) for managing bills of materials (BOMs), the engineering change process and supplier communication. In other words, we help [...]]]></description>
			<content:encoded><![CDATA[<p>Welcome to the official blog of Arena Solutions. If you haven’t heard of Arena, the quick version is this: Arena serves small and mid-size manufacturers by providing on-demand software (also known as software-as-a-service or a SaaS solution) for managing bills of materials (BOMs), the engineering change process and supplier communication.</p>
<p>In other words, we help companies get their products to market.</p>
<p>To make sure we give them help that’s actually, well, helpful, we’re constantly trying to understand everything we can about what it takes to design, develop, manufacture and ship great products.</p>
<p>That’s how we’ve ended up here—with a blog about all things product. We all know there’s no magic formula for building a winning product, so we won’t pretend we can offer one. But what we can offer are observations, opinions, research, learnings, experience and maybe even some wild imaginings from time to time.</p>
<p>We’ll talk about strategies, processes &amp; tactics, particularly the ones that help successful companies do their thing. We’ll share our observations on global trends, market demographics and industry news, and we hope you’ll share yours too. We’ll point out problems when we see them, propose solutions when we have them and ask for your opinions on it all. We’ll highlight successes AND snafus, as there’s a lot to be learned from both.</p>
<p>Innovation? If you’re a small or mid-size manufacturer, innovation is most likely at the heart of your products and the core of your strategy, so we’ll be talking a lot about that too. The discussion may sometimes veer toward the academic (it is a meaty topic, after all), but real-world examples will abound. We love cool products, and we’ll share them when we find them. We may even throw in the occasional what-were-they-thinking examples of innovation gone wrong…just for good measure.</p>
<p>Let us know what you think.</p>
<p>Please join the conversation and help us make the blog a valuable source of information and a lively forum for discussion.</p>
<p>Now let’s talk product.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.arenasolutions.com/interested-in-products-youve-come-to-the-right-place/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

