<?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"

			>

	<channel>
		<title>Make It Right  &#187;  Topic: Product Change Isn&#039;t Easy</title>
		<atom:link href="/what-we-know/laboratory/forums/topic/product-change-isnt-easy/feed/" rel="self" type="application/rss+xml" />
		<link>https://makeitright.org/what-we-know/laboratory/forums/topic/product-change-isnt-easy/feed/</link>
		<description></description>
		<pubDate></pubDate>
		<generator>http://bbpress.org/?v=2.1.2</generator>
		<language></language>

		
														
					
				<item>
					<guid>https://makeitright.org/what-we-know/laboratory/forums/topic/product-change-isnt-easy/#post-2401</guid>
					<title><![CDATA[Product Change Isn&#039;t Easy]]></title>
					<link>https://makeitright.org/what-we-know/laboratory/forums/topic/product-change-isnt-easy/#post-2401</link>
					<pubDate>Fri, 09 Nov 2012 03:22:24 +0000</pubDate>
					<dc:creator>Cesar Rodriguez</dc:creator>

					<description>
						<![CDATA[
						<p>The other day I was doing a final walkthrough in a recently completed home. As I walked in and out of rooms, it dawned on me that we are in a bit a rut on the products that we are using. I stopped and thought about how this happened. </p>
<p>At the beginning, we were trying out all kinds of new products, from glass infused wood to wireless lighting systems; again why is this not our norm today? Switching from product A to product B should be easy, right? </p>
<p>Well it&#8217;s not as easy as you might think. Let&#8217;s consider the following example &#8211; switching from our current wireless lighting system to a traditional system,  the following would have to take place: </p>
<p>* engineering review<br />
* architectural review  and new drawings<br />
* training our General Contractors in proper installation procedures<br />
* setting up a new vendor to handle delivery<br />
* additional new products needed to  accommodate finishing details<br />
* familiarize our homeowners with the new technology (staff time)<br />
* risk assessment </p>
<p>All of these come at a cost and can slow down progress and make it difficult to standardize details. So how do we counter this? </p>
<p>We focus on a product selection and design process that insures the benefits offset the challenges. For example, a few months back we were contacted by a manufacture making a SIP out of magnesium. The claims of the manufacturer are:</p>
<p>*no need for an exterior sheeting<br />
*no need for drywall<br />
*minimal training for General Contractors<br />
*minimal changes that impact the homeowner  </p>
<p>The cost to implement this type of innovation would save more than the cost to change our standardized process. If you find yourself in a similar situation, design a process that collects new product data, reviews the performance of existing products and allows for ease of transition from old to new product. </p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>https://makeitright.org/what-we-know/laboratory/forums/topic/product-change-isnt-easy/#reply-2444</guid>
					<title><![CDATA[Reply To: Product Change Isn&#039;t Easy]]></title>
					<link>https://makeitright.org/what-we-know/laboratory/forums/topic/product-change-isnt-easy/#reply-2444</link>
					<pubDate>Tue, 13 Nov 2012 05:01:49 +0000</pubDate>
					<dc:creator>troyle</dc:creator>

					<description>
						<![CDATA[
						<p>Great post, Cesar! Are you on the lookout for new products at Greenbuild this week?</p>
						]]>
					</description>

					
					
				</item>

					
		
	</channel>
	</rss>

