<?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>Shipulski On Design &#187; VOC</title>
	<atom:link href="http://www.shipulski.com/category/voc/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.shipulski.com</link>
	<description>Innovation, Product Development, Design</description>
	<lastBuildDate>Sun, 05 Feb 2012 14:30:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>It&#8217;s a tough time to be a CEO</title>
		<link>http://www.shipulski.com/2009/10/13/its-a-tough-time-to-be-a-ceo/</link>
		<comments>http://www.shipulski.com/2009/10/13/its-a-tough-time-to-be-a-ceo/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 00:22:58 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[A/B Data]]></category>
		<category><![CDATA[CEO]]></category>
		<category><![CDATA[Recession]]></category>
		<category><![CDATA[Top Line Growth]]></category>
		<category><![CDATA[VOC]]></category>
		<category><![CDATA[Engineering Capability]]></category>
		<category><![CDATA[Engineering Mindset]]></category>
		<category><![CDATA[Product Development Engine]]></category>
		<category><![CDATA[Sales Tools]]></category>

		<guid isPermaLink="false">http://www.shipulski.com/?p=331</guid>
		<description><![CDATA[2009 is a tough year, especially for CEOs. CEOs have a strong desire to do what it takes to deliver shareholder value, but that’s coupled with a deep concern that tough decisions may dismantle the company in the process. Here is the state-of-affairs: Sales are down and money is tight.  There is severe pressure to cut [...]]]></description>
			<content:encoded><![CDATA[<p>2009 is a tough year, especially for CEOs.</p>
<p>CEOs have a strong desire to do what it takes to deliver shareholder value, but that’s coupled with a deep concern that tough decisions may dismantle the company in the process.</p>
<p>Here is the state-of-affairs:</p>
<p style="padding-left: 30px;">Sales are down and money is tight.  There is severe pressure to cut costs including those that are linked to sales – marketing budgets, sales budgets, travel &#8211; and things that directly impact customers – technical service, product manuals, translations, and warranty.</p>
<p style="padding-left: 30px;">Pricing pressure is staggering.  Customers are exerting their buying power &#8211; since so few are buying they want to name their price (and can).  Suppliers, especially the big ones, are using their muscle to raise prices.</p>
<p style="padding-left: 30px;">Capacity utilization is ultra-low, so the bounce-back of new equipment sales is a long way off.</p>
<p style="padding-left: 30px;">Everyone wants to expand into new markets to increase sales, but this is a particularly daunting task with competitors hunkering down to retain market share, cuts in sales and marketing budgets, and hobbled product development engines.</p>
<p style="padding-left: 30px;">There is a desire to improve factory efficiency to cut costs (rather than to increase throughput like in 2008), but no one wants to spend money to make money &#8211; payback must be measured in milliseconds.</p>
<p>So what’s a CEO to do? <span id="more-331"></span></p>
<p>Focus on product.  Selling into new markets requires new products; even with full marketing and sales budgets, new products are required.  But, hobbled product development engines aren’t going to get it done – they can’t even do what they used to, never mind do more with high levels of innovation.  Here are some steps that can get things on track.</p>
<p>First, some investment must be made to understand the new markets.  They’re called new markets because they’re new – previous experience is not valid and new experience must be created.  So get some experience by watching customers use the leading products and talking directly with them about what they like and what they don’t.  A list of new functions and features is the desired outcome, along with a sale price and target cost.</p>
<p>The new features, functions, and cost target are the input to the product development engine.  The existing product with the strongest overlap with the new features and functions is used as the platform for the new design.  To make a splash, functionality and cost must be improved at the same time (remember, customers are naming their price).  Hopefully the engineering team has the chops to do the new work.  If not, some investment must be made to bolster their capability in the new areas.  Don’t skimp here or the new product will come out wrong (if at all) falling short of functionality and cost goals.</p>
<p>There is another deliverable from the product development engine.  The engine must create A/B performance data from which data-driven sales tools are created.  The best product in the new market is chosen as the baseline product (A) and tested to define the performance specification (maybe 20% better than the baseline product).  The new product (B) is tested under the same test protocol and its performance is plotted relative to the performance specification (20% better than the baseline product [product A]).  If the product development engine does its job, the new produce will have a competitive advantage over the best product in the market, with more function and less cost.</p>
<p>Some investment is needed to develop (and translate?) the data-driven sales tools and some spending is needed to get the sales force (and their new tools) in front of customers.  Don’t forget the sales tracking systems.</p>
<p>Improving the product development engine is vital.  Designing higher functioning products with low cost signatures is not natural for engineers, so care must be taken when defining the challenge.  And the morale of the engineering teams is likely low due to the recent cost cutting.  They may not be in the right frame of mind to accept their challenge, so a thoughtful delivery makes a difference.  A modest training plan to develop their capability goes a long way to putting them in the right frame of mind.</p>
<p>There is no free lunch here, and little new thinking.  Solid blocking-and-tackling is needed from marketing, sales, engineering, and manufacturing along with improved capability in engineering.  Even in a recession, this approach can grow sales in new markets, especially when coupled with strong focus.</p>
<p>Next time you see your CEO, give a smile, a hand shake, and a thank you.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.shipulski.com/2009/10/13/its-a-tough-time-to-be-a-ceo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Assess Design Alternatives With Axiomatic Design</title>
		<link>http://www.shipulski.com/2009/09/07/assess-design-alternatives-with-axiomatic-design/</link>
		<comments>http://www.shipulski.com/2009/09/07/assess-design-alternatives-with-axiomatic-design/#comments</comments>
		<pubDate>Mon, 07 Sep 2009 17:02:46 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[Axiomatic Design]]></category>
		<category><![CDATA[VOC]]></category>
		<category><![CDATA[Design Alternatives]]></category>
		<category><![CDATA[Design Spaces]]></category>
		<category><![CDATA[Functional Domain]]></category>
		<category><![CDATA[Physical Domain]]></category>
		<category><![CDATA[Process Domain]]></category>

		<guid isPermaLink="false">http://www.shipulski.com/?p=222</guid>
		<description><![CDATA[Al Hamilton, of Axiomatic Design Solutions, wrote a good article on how Axiomatic Design can be used to evaluate multiple design alternatives. Here is an excerpt from the article:   Axiomatic design breaks the design process into four domains, shown in Figure 1.  The customer domain can be thought of as the voice of the [...]]]></description>
			<content:encoded><![CDATA[<p><em><strong>Al Hamilton, of Axiomatic Design Solutions</strong></em>, wrote a good <a href="http://www.realinnovation.com/content/c080721a.asp">article </a>on how Axiomatic Design can be used to evaluate multiple design alternatives.</p>
<p>Here is an excerpt from the article:</p>
<blockquote><p> </p>
<p style="text-align: center;"><a href="http://www.shipulski.com/wp-content/uploads/2009/09/four-design-spaces-from-Als-article.jpg"><img class="size-full wp-image-223  aligncenter" title="Four Design Spaces of Axiomatic Design" src="http://www.shipulski.com/wp-content/uploads/2009/09/four-design-spaces-from-Als-article.jpg" alt="Four Design Spaces of Axiomatic Design" width="457" height="194" /></a></p>
<p>Axiomatic design breaks the design process into four domains, shown in Figure 1.  The customer domain can be thought of as the voice of the customer (VOC).</p>
<ol>
<li>The functional domain is initially populated by mapping the VOC into independent measurable functions. High-level functions are driven by the customer; lower-level functions are driven by design choices. Every function must be measurable.</li>
<li>The physical domain is the domain of physics, chemistry, math and algorithms.</li>
<li>The process domain is where the specifics of how the design parameters identified in the physical domain will be implemented.</li>
</ol>
<p>Dr. Mike Shipulski, director of engineering at Hypertherm, a manufacturer of plasma cutting systems, has made extensive use of axiomatic design. Shipulski observes, &#8220;By first defining the functions we are to achieve, we align our problem solving on the right areas and broaden possible design opportunities. With axiomatic design, we have a framework for avoiding problems that are often detected only during system-level testing.&#8221;</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.shipulski.com/2009/09/07/assess-design-alternatives-with-axiomatic-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

