<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Some users do not like the single version of the truth</title>
	<atom:link href="http://virtualdutchman.com/2009/12/02/some-users-do-not-like-the-single-version-of-the-truth/feed/" rel="self" type="application/rss+xml" />
	<link>http://virtualdutchman.com/2009/12/02/some-users-do-not-like-the-single-version-of-the-truth/</link>
	<description>Global mid-market observations of the world now called PLM</description>
	<lastBuildDate>Tue, 24 Jan 2012 07:16:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Asset Lifecycle Management using a PLM system &#171; Jos Voskuil&#8217;s Weblog</title>
		<link>http://virtualdutchman.com/2009/12/02/some-users-do-not-like-the-single-version-of-the-truth/#comment-530</link>
		<dc:creator><![CDATA[Asset Lifecycle Management using a PLM system &#171; Jos Voskuil&#8217;s Weblog]]></dc:creator>
		<pubDate>Mon, 01 Mar 2010 22:30:24 +0000</pubDate>
		<guid isPermaLink="false">http://josvoskuil.wordpress.com/?p=658#comment-530</guid>
		<description><![CDATA[[...] March 1, 2010 in Asset Lifecycle Management, ISO 15926, MRO, Observations, PLM, Tag numbering &#124; Tags: ALM, Asset Lifecycle Management, MRO, PLM, ROI     Although I am still active most of my time in ‘classical’ PLM, some of the projects I am involved with also deal with Asset Lifecycle Management. In general PLM focuses on a product development process, starting from a conceptual phase, going through planning, development and production. The PLM system serves as a collaboration and information backbone for all product IP (Intellectual Property). One of the main capabilities a PLM system provides is a ‘single version of the truth’. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] March 1, 2010 in Asset Lifecycle Management, ISO 15926, MRO, Observations, PLM, Tag numbering | Tags: ALM, Asset Lifecycle Management, MRO, PLM, ROI     Although I am still active most of my time in ‘classical’ PLM, some of the projects I am involved with also deal with Asset Lifecycle Management. In general PLM focuses on a product development process, starting from a conceptual phase, going through planning, development and production. The PLM system serves as a collaboration and information backbone for all product IP (Intellectual Property). One of the main capabilities a PLM system provides is a ‘single version of the truth’. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Samantha</title>
		<link>http://virtualdutchman.com/2009/12/02/some-users-do-not-like-the-single-version-of-the-truth/#comment-528</link>
		<dc:creator><![CDATA[Samantha]]></dc:creator>
		<pubDate>Fri, 26 Feb 2010 22:22:49 +0000</pubDate>
		<guid isPermaLink="false">http://josvoskuil.wordpress.com/?p=658#comment-528</guid>
		<description><![CDATA[Craig has pretty much said it all.  

In terms of change management a bottom-up approach is necessary to ensure that users will accept the new solution and use it as it&#039;s intended.  They are ultimately the ones who will be using it everyday in support of their jobs, so their feedback is important. 

When using a top down approach, it&#039;s hard to achieve the same kind of success because the direction and authority is streaming down from the top with little to no input from users and may result in the failure to reach the overall objectives, such as achieving a &#039;single version of the truth&#039; because of low employee buy-in and resistance.  

I just found this blog through Oleg. Pretty sweet...I&#039;ll be back!

Samantha
Datastay Corp.

&lt;em&gt;Thanks Samantha for your feedback. I believe the challenge in the mid-market is always between bottom-up with enough top-down guidance/push. Enjoy future readings and looking forward to your inputs

Best regards


Jos&lt;/em&gt;]]></description>
		<content:encoded><![CDATA[<p>Craig has pretty much said it all.  </p>
<p>In terms of change management a bottom-up approach is necessary to ensure that users will accept the new solution and use it as it&#8217;s intended.  They are ultimately the ones who will be using it everyday in support of their jobs, so their feedback is important. </p>
<p>When using a top down approach, it&#8217;s hard to achieve the same kind of success because the direction and authority is streaming down from the top with little to no input from users and may result in the failure to reach the overall objectives, such as achieving a &#8216;single version of the truth&#8217; because of low employee buy-in and resistance.  </p>
<p>I just found this blog through Oleg. Pretty sweet&#8230;I&#8217;ll be back!</p>
<p>Samantha<br />
Datastay Corp.</p>
<p><em>Thanks Samantha for your feedback. I believe the challenge in the mid-market is always between bottom-up with enough top-down guidance/push. Enjoy future readings and looking forward to your inputs</p>
<p>Best regards</p>
<p>Jos</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Senior</title>
		<link>http://virtualdutchman.com/2009/12/02/some-users-do-not-like-the-single-version-of-the-truth/#comment-434</link>
		<dc:creator><![CDATA[Craig Senior]]></dc:creator>
		<pubDate>Fri, 04 Dec 2009 16:30:48 +0000</pubDate>
		<guid isPermaLink="false">http://josvoskuil.wordpress.com/?p=658#comment-434</guid>
		<description><![CDATA[When users choose to do other than what WE are supposed to do, where are their team leaders/managers in all this. As a leader, when we decide that WE are doing something a new way, that&#039;s it. We communicate the plan, give training/briefings, monitor conformance, and monitor performance, getting feedback on what is working and not working.

The new way must yield benefits in improved quality and efficiency, understanding that we sometimes might do more work up front to reduce even more work downstream.

Sometimes, leaders must handhold transactions through the first few to ensure conformity and to capture process blockages firsthand because users will often find a defect and workaround that goes unreported, osmosing into &quot;how we do things.&quot;

I found that after people understanding that to improve, we must change and we experience one or two improvements where they see and experience the benefit, they are more apt to adopt future improvements.

You must have an accomodating change process where user feedback is acted upon immediately. How about rewarding people for submitting feedback, so that we reinforce the behaviour we want?

In response to feedback, perform root cause analysis to determine why the defect occurred and on the next improvement, the cause is considered and the failure event is prevented.

&lt;em&gt;Thanks Craig, 

I agree with your approach -it is all about the management taking the ownership of the change and do their best efforts to accomodate the changes 

Best Regards

Jos
&lt;/em&gt;]]></description>
		<content:encoded><![CDATA[<p>When users choose to do other than what WE are supposed to do, where are their team leaders/managers in all this. As a leader, when we decide that WE are doing something a new way, that&#8217;s it. We communicate the plan, give training/briefings, monitor conformance, and monitor performance, getting feedback on what is working and not working.</p>
<p>The new way must yield benefits in improved quality and efficiency, understanding that we sometimes might do more work up front to reduce even more work downstream.</p>
<p>Sometimes, leaders must handhold transactions through the first few to ensure conformity and to capture process blockages firsthand because users will often find a defect and workaround that goes unreported, osmosing into &#8220;how we do things.&#8221;</p>
<p>I found that after people understanding that to improve, we must change and we experience one or two improvements where they see and experience the benefit, they are more apt to adopt future improvements.</p>
<p>You must have an accomodating change process where user feedback is acted upon immediately. How about rewarding people for submitting feedback, so that we reinforce the behaviour we want?</p>
<p>In response to feedback, perform root cause analysis to determine why the defect occurred and on the next improvement, the cause is considered and the failure event is prevented.</p>
<p><em>Thanks Craig, </p>
<p>I agree with your approach -it is all about the management taking the ownership of the change and do their best efforts to accomodate the changes </p>
<p>Best Regards</p>
<p>Jos<br />
</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joy Garon</title>
		<link>http://virtualdutchman.com/2009/12/02/some-users-do-not-like-the-single-version-of-the-truth/#comment-433</link>
		<dc:creator><![CDATA[Joy Garon]]></dc:creator>
		<pubDate>Thu, 03 Dec 2009 20:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://josvoskuil.wordpress.com/?p=658#comment-433</guid>
		<description><![CDATA[Great post Jos - I have seen small companies achieve the &#039;single version of the truth&#039;. In these cases the management team did an excellent job of educating their entire team and keeping them on track by acting on feedback and maintaining continuous process improvement for the PDM/PLM system itself.
Cheers, Joy]]></description>
		<content:encoded><![CDATA[<p>Great post Jos &#8211; I have seen small companies achieve the &#8216;single version of the truth&#8217;. In these cases the management team did an excellent job of educating their entire team and keeping them on track by acting on feedback and maintaining continuous process improvement for the PDM/PLM system itself.<br />
Cheers, Joy</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oleg Shilovitsky</title>
		<link>http://virtualdutchman.com/2009/12/02/some-users-do-not-like-the-single-version-of-the-truth/#comment-432</link>
		<dc:creator><![CDATA[Oleg Shilovitsky]]></dc:creator>
		<pubDate>Wed, 02 Dec 2009 23:10:40 +0000</pubDate>
		<guid isPermaLink="false">http://josvoskuil.wordpress.com/?p=658#comment-432</guid>
		<description><![CDATA[Jos,
As you said to create &quot;a single point of truth&quot; is not easy, but assuming everybody on board and... wow! We succeeded to create one. What comes to my mind next - yes, change in your system. How to make this change fast without going to the next complex round of implementation? This is the key question from my standpoint. Some of my thought about that is here - http://plmtwine.com/2009/06/18/my-slice-of-plm-single-version-of-truth/.

Best, Oleg


&lt;em&gt;Oleg hi, yes creating a single version of the truth is the same as maintaining it - and you have to analyze what are the cost of maintenance and what is the ROI. Not documenting a modification in an as-built environment can be almost harmless in a beer brewery but killing in a nuclear plant &lt;/em&gt;]]></description>
		<content:encoded><![CDATA[<p>Jos,<br />
As you said to create &#8220;a single point of truth&#8221; is not easy, but assuming everybody on board and&#8230; wow! We succeeded to create one. What comes to my mind next &#8211; yes, change in your system. How to make this change fast without going to the next complex round of implementation? This is the key question from my standpoint. Some of my thought about that is here &#8211; <a href="http://plmtwine.com/2009/06/18/my-slice-of-plm-single-version-of-truth/" rel="nofollow">http://plmtwine.com/2009/06/18/my-slice-of-plm-single-version-of-truth/</a>.</p>
<p>Best, Oleg</p>
<p><em>Oleg hi, yes creating a single version of the truth is the same as maintaining it &#8211; and you have to analyze what are the cost of maintenance and what is the ROI. Not documenting a modification in an as-built environment can be almost harmless in a beer brewery but killing in a nuclear plant </em></p>
]]></content:encoded>
	</item>
</channel>
</rss>

