VPEC-T Google Group

Locard-Wittgenstein Principle

2009-11-23T23:46:35Z

Wittenstein converted Locard's exchange principle of forensics (Every
Contact Leaves a Trace) into a principle of psychology (Every Event
leaves a Trace in the Memory).

For VPEC-T, assuming we can identify Memory with Content, this
principle appears to have important implications for the relationship

VPEC-T and abstract problem solving

2009-10-15T08:43:26Z

In Nigel's Open Group presentation in April 2009, referring to the
Criminal Justice System case study, he said "A Policy-Event-Content
analysis pattern taken from Supply Chain Logistics could be applied to
the information flows between government departments"

This is presumably justified by an abstract similarity between the PEC

VPEC-T and Gregory Bateson

2009-10-15T02:49:10Z

Looking for something else (as one does), I came across a biography of
the great systems thinking pioneer Gregory Bateson, which contained
some material that looked particularly interesting for VPEC-T.

***

In Bateson’s usage, systems are always formed by at least two sites,
and they interact through exchanges of information or messages. In

Re: Seeing VPEC-T everywhere

2009-10-06T21:53:04Z

When the only tool you have is a hammer, every problem is a fingernail
(ouch).

But seriously, I suspect that we need lenses/filters to look at problems
through. So we build an armory of techniques and approaches. The most recent
weapons in the armory are probably the first that we try. Of course if that

Seeing VPEC-T everywhere

2009-10-06T14:24:38Z

Just saw a post called "The five dysfunctions of a team". Apparently
this is the title of a new book.

[link]

So I immediately thought it would be a good idea to try and map these
against VPEC-T.

In summary, the five are as follows.

Re: VPEC-T Re: - from analysis to design

2009-10-05T11:00:26Z

Policy is an interesting dimension. Like most of the VPEC-T dimensions it
applies at many levels. So for example, we can see policy being applied in a
granular sense - within a node in a value network. Policy being almost rule
based. "We have a policy that people with a credit score of less than 600

Re: VPEC-T Re: - from analysis to design

2009-10-04T22:32:59Z

Need to find the time, but John Holland's book (Hidden Order) is a
classic reference on complexity.

Re: VPEC-T Re: - from analysis to design

2009-10-04T22:30:55Z

Richard,
I think this is where VPEC-T provides the opportunity to take a more a
holistic (I remember your comments on TOGAF 9) approach to design. i.e.
the key elements of design at the enterprise level are surely the
policies and relationship systems rather than the technical structure.
This starts to sound like social engineering and I guess in some senses

Re: VPEC-T Re: - from analysis to design

2009-10-04T21:40:36Z

VPEC-T certainly fits with the way I have been doing design, at the
enterprise level, very well.

The essence is to consider the context diagram of something that you are
going to deploy as an information system. The events are the business events
(POST or PUT) that the IS will either absorb or emit. The business events

Re: VPEC-T - from analysis to design

2009-10-04T15:47:52Z

Thanks Nigel.

I take the point about PEC being used as an IS design technique, but I
guess I was looking for something that "solved" the V and T as well as
the PEC issues.

I accept the relevance of Adoption Engineering, but I had seen this as
a separate lens rather than as a part of VPEC-T.

Re: VPEC-T - from analysis to design

2009-10-04T11:25:04Z

[link]

(1 hour 11 mins - worth spending if considering Next Practice IMO)

This video by John Holland PhD might help get nto how VPEC-T works in
the design space:
Complex Adaptive and #vpect work well together: V: Agent Goals/Values,
Policy: Light-constraints, Lever-points, Events: Adaptive behavior

Re: VPEC-T - from analysis to design

2009-10-04T09:17:39Z

VPEC-T was originally conceived as a tool to help business analysis
and to help with traceability into design and further still, to
operation. The P-E-C part came about first as a Design Pattern based
around federated information systems - Trading Partners in a Supply
Chain for example. It emerged from the design of a asynchronous

VPEC-T - from analysis to design

2009-10-02T22:26:34Z

I've just run a couple of Next Practice bootcamps featuring the VPEC-T
lens, and I thought I'd share the reaction I got from the
participants.

There was general acceptance of VPEC-T as a diagnostic lens - for
understanding problems, analysing requirements and identifying risks.
What the participants found more difficult was to see VPEC-T as a

VPEC-T on the Lenscraft wiki

2009-10-01T22:06:07Z

I have split the VPEC-T page on the Lenscraft wiki into multiple
pages. I should welcome any help in improving these pages (or anything
else on the Lenscraft wiki for that matter).

[link]

I have created a VPEC-T blog page. This filters some relevant blogs
using the VPEC-T category. If I've missed any, please let me know.

Re: VPEC-T and complementary lenses

2009-10-01T11:26:42Z

Re:Anti-pattern - A way we might've tried to achieve the same result
in the past or 'Bad Habit' that we're in that has proven to not work.

I like the added column to TRANSFORMATION. Could we start to build a
Use Pattern repository somewhere - could this be a service of the Next
Practice Institute?