<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rss version="2.0">
  <channel>
  <title>VPEC-T Google Group</title>
  <link>http://groups.google.co.uk/group/vpec-t</link>
  <description>This group is focused on discussing the VPEC-T framework and derived methods such as the &amp;#39;5D lens&amp;#39; and &amp;#39;Threads and Beads&amp;#39;. This is a Public group - Anyone can join, but only members can post messages, view the members list, create pages and upload files. </description>
  <language>en</language>
  <item>
  <title>Information content versus conversation content</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/ee815c24fc3d4f2d/35b58e5fe3186ef5?show_docid=35b58e5fe3186ef5</link>
  <description>
  &amp;quot;Conversational content may look like information. But when it is the &lt;br&gt; product of mediated conversation, content conceals dynamics and &lt;br&gt; relationships: social forces that are by their nature implicit and &lt;br&gt; tacit.&amp;quot; &lt;br&gt; &lt;p&gt;&lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.readwriteweb.com/archives/getting_more_from_conversation_real_time_challenge.php&quot;&gt;[link]&lt;/a&gt;
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/ee815c24fc3d4f2d/35b58e5fe3186ef5?show_docid=35b58e5fe3186ef5</guid>
  <author>
  goo...@veryard.com
  (Richard Veryard)
  </author>
  <pubDate>Thu, 12 Dec 2009 03:28:07 UT
</pubDate>
  </item>
  <item>
  <title>Re: Enterprise KM</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/bfd9a3ff68ca5b90/7b3ff163bf6e90f5?show_docid=7b3ff163bf6e90f5</link>
  <description>
  first, thank you so much to the VPECT community for starting up this &lt;br&gt; dialog so quickly - that alone says alot to me. Second, as I respond &lt;br&gt; here, let me be the first to admit that I have zero experience in &lt;br&gt; VPECT so I am coming from the enterprise KM perspective here (and i &lt;br&gt; hope thats helpful). i&#39;m picking up on the notion that VPECT seems to
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/bfd9a3ff68ca5b90/7b3ff163bf6e90f5?show_docid=7b3ff163bf6e90f5</guid>
  <author>
  johnhov...@gmail.com
  (John Hovell)
  </author>
  <pubDate>Thu, 12 Dec 2009 19:47:17 UT
</pubDate>
  </item>
  <item>
  <title>Re: VPEC-T Locard-Wittgenstein Principle</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/af4cd2ac1f3c590b/b4265a3e0c813f8a?show_docid=b4265a3e0c813f8a</link>
  <description>
  Okay, I accept that &amp;quot;Memory is Content&amp;quot; is a bit simplistic. One way &lt;br&gt; of thinking about memory is as a system in its own right, in which &lt;br&gt; case it HAS content rather than BEING content. &lt;br&gt; &lt;p&gt;How about this possible reformulation. Memory is a repository of &lt;br&gt; memories. (The memories represent the content of the memory.) For the
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/af4cd2ac1f3c590b/b4265a3e0c813f8a?show_docid=b4265a3e0c813f8a</guid>
  <author>
  goo...@veryard.com
  (Richard Veryard)
  </author>
  <pubDate>Wed, 12 Dec 2009 10:01:55 UT
</pubDate>
  </item>
  <item>
  <title>Re: VPEC-T Locard-Wittgenstein Principle</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/af4cd2ac1f3c590b/159f00e93c790090?show_docid=159f00e93c790090</link>
  <description>
  I would contest the assumption that memory is content. This doesn&#39;t seem &lt;br&gt; right. If we ask a question of memory and then express the result (in the &lt;br&gt; context of the question), then we have content. That is the problem with a &lt;br&gt; knowledge repository, by itself it doesn&#39;t represent content. Rather it &lt;br&gt; requires the context of a question and then the result of that question to
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/af4cd2ac1f3c590b/159f00e93c790090?show_docid=159f00e93c790090</guid>
  <author>
  jschlesin...@computer.org
  (John Schlesinger)
  </author>
  <pubDate>Wed, 12 Dec 2009 08:43:32 UT
</pubDate>
  </item>
  <item>
  <title>Re: Enterprise KM</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/bfd9a3ff68ca5b90/601825f9d66792bc?show_docid=601825f9d66792bc</link>
  <description>
  j4ngis wants to look at this from the Knowledge Managers/Maintainer &lt;br&gt; perspective... &lt;br&gt; &lt;p&gt;One of the questions here is whether the knowledge manager is actually &lt;br&gt; interested in the knowledge content per se, or focuses on oiling the &lt;br&gt; wheels. Like a librarian who never actually reads the books in the &lt;br&gt; library herself, merely organizes the catalogue and chases the overdue
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/bfd9a3ff68ca5b90/601825f9d66792bc?show_docid=601825f9d66792bc</guid>
  <author>
  goo...@veryard.com
  (Richard Veryard)
  </author>
  <pubDate>Tue, 12 Dec 2009 22:40:28 UT
</pubDate>
  </item>
  <item>
  <title>Re: Enterprise KM</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/bfd9a3ff68ca5b90/89d680f79799bf39?show_docid=89d680f79799bf39</link>
  <description>
  One might also consider VPEC-T from two different perspectives; &lt;br&gt; Producing &amp;amp; Consuming. &lt;br&gt; Walking through the VPEC-T system (as Richard did above) you can do &lt;br&gt; it from Producing Knowledge perspective and Consuming/using knowledge &lt;br&gt; perspective. And why not also from Knowledge Managers/Maintainer &lt;br&gt; perspective...
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/bfd9a3ff68ca5b90/89d680f79799bf39?show_docid=89d680f79799bf39</guid>
  <author>
  ajangbr...@gmail.com
  (j4ngis)
  </author>
  <pubDate>Tue, 12 Dec 2009 18:54:51 UT
</pubDate>
  </item>
  <item>
  <title>Re: Enterprise KM</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/bfd9a3ff68ca5b90/a004a4dc651d899c?show_docid=a004a4dc651d899c</link>
  <description>
  Chris has talked about the VPEC-T of the KM system. I think it&#39;s worth &lt;br&gt; relating this to the knowledge itself. &lt;br&gt; &lt;p&gt;VALUES. What is (could be) the value of knowledge to the organization, &lt;br&gt; and to the people inside and outside the organization. &lt;br&gt; &lt;p&gt;POLICIES. What are the policies for the creation, sharing and use of
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/bfd9a3ff68ca5b90/a004a4dc651d899c?show_docid=a004a4dc651d899c</guid>
  <author>
  goo...@veryard.com
  (Richard Veryard)
  </author>
  <pubDate>Mon, 11 Nov 2009 19:27:48 UT
</pubDate>
  </item>
  <item>
  <title>Re: Enterprise KM</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/bfd9a3ff68ca5b90/5631f90e147c4f52?show_docid=5631f90e147c4f52</link>
  <description>
  I think KM is a very fertile ground for KM because it has so many &lt;br&gt; constituencies with quite divergent needs. So (as I usually do), I &lt;br&gt; shall start with a story. &lt;br&gt; &lt;p&gt;I joined a new company in May this year. This company has an enormous &lt;br&gt; amount of documentation, discussion threads, program specs, iteration
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/bfd9a3ff68ca5b90/5631f90e147c4f52?show_docid=5631f90e147c4f52</guid>
  <author>
  seabir...@gmail.com
  (Seabird)
  </author>
  <pubDate>Mon, 11 Nov 2009 17:18:03 UT
</pubDate>
  </item>
  <item>
  <title>Enterprise KM</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/bfd9a3ff68ca5b90/675e8a2e5e7ba855?show_docid=675e8a2e5e7ba855</link>
  <description>
  Picked up a tweet from John Hovell @klowey22 &lt;br&gt; &lt;p&gt;VPEC-T mindmap (values, policies, events, content, trust)...wondering &lt;br&gt; how we might apply to enterprise #km &lt;br&gt; &lt;p&gt;--- &lt;br&gt; &lt;p&gt;My first thought was that a lot of enterprise knowledge management &lt;br&gt; focuses on Content. &lt;br&gt; &lt;p&gt;We then have to think about Events and Policies
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/bfd9a3ff68ca5b90/675e8a2e5e7ba855?show_docid=675e8a2e5e7ba855</guid>
  <author>
  goo...@veryard.com
  (Richard Veryard)
  </author>
  <pubDate>Mon, 11 Nov 2009 16:33:53 UT
</pubDate>
  </item>
  <item>
  <title>Locard-Wittgenstein Principle</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/af4cd2ac1f3c590b/8d777b0a66226df3?show_docid=8d777b0a66226df3</link>
  <description>
  Wittenstein converted Locard&#39;s exchange principle of forensics (Every &lt;br&gt; Contact Leaves a Trace) into a principle of psychology (Every Event &lt;br&gt; leaves a Trace in the Memory). &lt;br&gt; &lt;p&gt;For VPEC-T, assuming we can identify Memory with Content, this &lt;br&gt; principle appears to have important implications for the relationship
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/af4cd2ac1f3c590b/8d777b0a66226df3?show_docid=8d777b0a66226df3</guid>
  <author>
  goo...@veryard.com
  (Richard Veryard)
  </author>
  <pubDate>Mon, 11 Nov 2009 23:46:35 UT
</pubDate>
  </item>
  <item>
  <title>VPEC-T and abstract problem solving</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/caac6578117ecaf2/ad2db1d9cbb7c7e2?show_docid=ad2db1d9cbb7c7e2</link>
  <description>
  In Nigel&#39;s Open Group presentation in April 2009, referring to the &lt;br&gt; Criminal Justice System case study, he said &amp;quot;A Policy-Event-Content &lt;br&gt; analysis pattern taken from Supply Chain Logistics could be applied to &lt;br&gt; the information flows between government departments&amp;quot; &lt;br&gt; &lt;p&gt;This is presumably justified by an abstract similarity between the PEC
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/caac6578117ecaf2/ad2db1d9cbb7c7e2?show_docid=ad2db1d9cbb7c7e2</guid>
  <author>
  goo...@veryard.com
  (Richard Veryard)
  </author>
  <pubDate>Thu, 10 Oct 2009 08:43:26 UT
</pubDate>
  </item>
  <item>
  <title>VPEC-T and Gregory Bateson</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/8dc0ea41c3bf8faf/1ec8bc0cde414397?show_docid=1ec8bc0cde414397</link>
  <description>
  Looking for something else (as one does), I came across a biography of &lt;br&gt; the great systems thinking pioneer Gregory Bateson, which contained &lt;br&gt; some material that looked particularly interesting for VPEC-T. &lt;br&gt; &lt;p&gt;*** &lt;br&gt; &lt;p&gt;In Bateson’s usage, systems are always formed by at least two sites, &lt;br&gt; and they interact through exchanges of information or messages. In
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/8dc0ea41c3bf8faf/1ec8bc0cde414397?show_docid=1ec8bc0cde414397</guid>
  <author>
  goo...@veryard.com
  (Richard Veryard)
  </author>
  <pubDate>Thu, 10 Oct 2009 02:49:10 UT
</pubDate>
  </item>
  <item>
  <title>Re: Seeing VPEC-T everywhere</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/00e170711900ccce/bfb4c675f903292a?show_docid=bfb4c675f903292a</link>
  <description>
  When the only tool you have is a hammer, every problem is a fingernail &lt;br&gt; (ouch). &lt;br&gt; &lt;p&gt;But seriously, I suspect that we need lenses/filters to look at problems &lt;br&gt; through. So we build an armory of techniques and approaches. The most recent &lt;br&gt; weapons in the armory are probably the first that we try. Of course if that
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/00e170711900ccce/bfb4c675f903292a?show_docid=bfb4c675f903292a</guid>
  <author>
  seabir...@gmail.com
  (Christopher Bird)
  </author>
  <pubDate>Tue, 10 Oct 2009 21:53:04 UT
</pubDate>
  </item>
  <item>
  <title>Seeing VPEC-T everywhere</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/00e170711900ccce/78e329211b4a52bb?show_docid=78e329211b4a52bb</link>
  <description>
  Just saw a post called &amp;quot;The five dysfunctions of a team&amp;quot;. Apparently &lt;br&gt; this is the title of a new book. &lt;br&gt; &lt;p&gt;&lt;a target=&quot;_blank&quot; rel=nofollow href=&quot;http://www.column2.com/2009/10/the-five-dysfunctions-of-a-team-gartnerbpm/&quot;&gt;[link]&lt;/a&gt; &lt;br&gt; &lt;p&gt;So I immediately thought it would be a good idea to try and map these &lt;br&gt; against VPEC-T. &lt;br&gt; &lt;p&gt;In summary, the five are as follows.
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/00e170711900ccce/78e329211b4a52bb?show_docid=78e329211b4a52bb</guid>
  <author>
  goo...@veryard.com
  (Richard Veryard)
  </author>
  <pubDate>Tue, 10 Oct 2009 14:24:38 UT
</pubDate>
  </item>
  <item>
  <title>Re: VPEC-T Re: - from analysis to design</title>
  <link>http://groups.google.co.uk/group/vpec-t/browse_frm/thread/c05f98ff15b74283/36ebb30630812207?show_docid=36ebb30630812207</link>
  <description>
  Policy is an interesting dimension. Like most of the VPEC-T dimensions it &lt;br&gt; applies at many levels. So for example, we can see policy being applied in a &lt;br&gt; granular sense - within a node in a value network. Policy being almost rule &lt;br&gt; based. &amp;quot;We have a policy that people with a credit score of less than 600
  </description>
  <guid isPermaLink="true">http://groups.google.co.uk/group/vpec-t/browse_frm/thread/c05f98ff15b74283/36ebb30630812207?show_docid=36ebb30630812207</guid>
  <author>
  seabir...@gmail.com
  (Christopher Bird)
  </author>
  <pubDate>Mon, 10 Oct 2009 11:00:26 UT
</pubDate>
  </item>
  </channel>
</rss>
