Comments on: Rethinking enterprise issues. http://www.gilyehuda.com/2009/08/12/rethinking-enterprise-issues/ A blog about collaboration, trust, open source, workplace, and community behaviors. Wed, 08 Feb 2012 09:19:08 +0000 hourly 1 http://wordpress.org/?v=3.1.4 By: Paula Thornton http://www.gilyehuda.com/2009/08/12/rethinking-enterprise-issues/comment-page-1/#comment-4862 Paula Thornton Thu, 27 Aug 2009 06:53:17 +0000 http://www.gilyehuda.com/?p=607#comment-4862 <span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Elder Experience Vid plays better here RT @gyehuda: isn't @melissaatbif great. I shared some thoughts about it here http://bit.ly/JTvk5</span></span> Elder Experience Vid plays better here RT @gyehuda: isn’t @melissaatbif great. I shared some thoughts about it here http://bit.ly/JTvk5

]]> By: Rotkapchen http://www.gilyehuda.com/2009/08/12/rethinking-enterprise-issues/comment-page-1/#comment-1942 Rotkapchen Wed, 26 Aug 2009 23:59:13 +0000 http://www.gilyehuda.com/?p=607#comment-1942 "What do you think of this?" Hmmm...exactly what we do and say in Experience Design all the time : ) Welcome to our reality. “What do you think of this?” Hmmm…exactly what we do and say in Experience Design all the time : )

Welcome to our reality.

]]> By: Jordan Frank http://www.gilyehuda.com/2009/08/12/rethinking-enterprise-issues/comment-page-1/#comment-1903 Jordan Frank Mon, 17 Aug 2009 18:22:42 +0000 http://www.gilyehuda.com/?p=607#comment-1903 I like the concept, but you are missing one important clause: memory same people + same process + memory = different results Had the group blogged about their status and issues as they were confronted, and also blogged their lessons learned - then they'd have had the opportunity to learn from past issues and overcome them. That may or may not be an issue of process per se, but rather how they operate within the process. A team with experience is more likely to outperform against other teams, so using memory is generally far better than just tossing new people on a process. In a PM role I saw a huge change for the better when the same people reorganized and got much better results. That was, I suppose, a process change but one that involved same people and good memory. The KUKA customer story on our site shows a nice example of an issue-awareness e2.0 deployment. It's a good best practice for anyone seeking process improvement to follow I like the concept, but you are missing one important clause: memory

same people + same process + memory = different results

Had the group blogged about their status and issues as they were confronted, and also blogged their lessons learned – then they’d have had the opportunity to learn from past issues and overcome them. That may or may not be an issue of process per se, but rather how they operate within the process. A team with experience is
more likely to outperform against other teams, so using memory is generally far better than just tossing new people on a process.

In a PM role I saw a huge change for the better when the same people reorganized and got much better results. That was, I suppose, a process change but one that involved same people and good memory.

The KUKA customer story on our site shows a nice example of an issue-awareness e2.0 deployment. It’s a good best practice for anyone seeking process improvement to follow

]]>