Adrian Apthorp has mentioned Business Capability Maps to me.
http://www.forrester.com/Research/Document/Excerpt/0,7211,43049,00.html
They are closely related to some work I did with him for DHL a few
years ago.
From the description, it made me wonder if VPEC-T should include
outcomes and become VPEC-TO. OK, Nigel, desired Outcomes are another
way of saying Values, but Values are from the wide variety of
perspectives of all the different players involved. That was, I
believe, one of the major insights of VPEC-T. There, the business
seems to just be jostling with all the other players.
But the outcomes in Business Capability Maps appear to be Values to
the business specifically. Might it be worth having business outcomes
as an explicitly recognized sub-set of VPEC-T's Values?
O would clearly be just a subset of V (all the intended outcomes), so
perhaps should not be promoted to appear in the name in caps. VoPEC-
T? Nah! Even more geeky.
There may be advantages in demonstrating to the business that business
outcomes have a special place in the pecking order.
I haven't yet found a description of Business Capability Maps (as I'm
not about to stump up $499 to Forrester) to see how closely they are
related to Business Domain Models, so perhaps I'm running down a wild
path into the for(r)est.
Roy