[projectvrm] Roadmap to VRM Utopia

[Mark Lizar < >]

Excellent points and idea to progress a Roadmap. 

On 16 May 2011, at 15:07, Devon Loffreto wrote:

 Science/Tech/Law/Entrepreneurs don't always get it right... even though they want to... and conscious evolution requires forethought in advance of effort... so don't undervalue idea sharing. We are here to share-take-riff on the ideas of one another. Creativity by committee rarely works... but there are Individual creators in the midst. Time is not something you are going to speed up by being impatient with it. My $.02

Devon

Along with excellent guidance 

On 15 May 2011, at 14:07, Katherine Warman Kern wrote:

Let's discuss specifically, what the individual customer will have to contribute to enjoy all the benefits, what actions come first vs later, and the barriers to taking action.

Then let's consider how each feature and benefit will relate to motivating those actions. For example, some features and benefits are more important to:

-  reassuring

-  maintaining participation

-  differentiating from other choices

-  peaking curiosity to learn more 

-  compelling each action necessary for an individual to enjoy the defining promise of this community.

Roadmap steps

1. Taking the time to start a roadmap with idea sharing.   

2. Talking the time to start the roadmap understanding what the customer will have to contribute. 

 Providing the customer with confidence enabling the customer to contribute. 

On Mon, May 16, 2011 at 7:38 AM, Katherine Warman Kern < "> "> > wrote:

What would give you confidence in sharing info, not just for fun, but because it could be a valuable asset?

- having more complete information to make wiser decisions

    +1 +1

     > enabling me to identify and choose what is personally new, relevant and credible

The more transaction information you are able to open (e.g. digitally opening receipts, and loyalty cards) the more complete information will be.   Open Loyalty is about being able to take your data out of data silo;s and aggregate the information shared. 

- receiving opportunities for business ventures and productive relationships to form

     +1 +1

     > revealing peers (friends or strangers) receptive to what I care about and businesses who want to do something about it.

- being introduced to people i should know via my trust networks

     +1 +1

     > interacting without risking unwanted invasion of my "personal space," my personal identity being stolen, or my comments being hijacked for unintended purposes.

Ability to interact in non-identifying - e.g. identities based of interests and other attributes

- getting paid

    +1

(from the customer perspective)

I think the scope of 'getting paid' should perhaps be expanded to getting value,e.g. barter and trade, crowdsourcing,  guitar lessons for math lessons etc. 

For the infrastructure, or the service development and provision - getting paid is very important. +1 having money to develop the service infrastructure 

This process will set priorities that may not be the same as thinking about them from strictly an operating point of view.  But since the result starts from the customer's perspective, it will be aligned with the fundamental principle behind VRM.

Starting with the  customer Experience would the next step be evolving the description of what should it be? 

Some (operating) ideas that I have for structuring the community effort would be to create inter-related WG's - E.g.:

- Creating a core operating infrastructure & Services Group

- Creating a series of sub-groups

-- VRM Services - Listing and assessing - (allocating participants to sub groups)

-- Customers

-- Vendors

-- Suppliers

-- Rights/Independence Services/Architecture

- Mark