Main Page: Difference between revisions

From Project VRM
Jump to navigation Jump to search
(→‎Site/Blog: added a missing space)
 
(508 intermediate revisions by more than 100 users not shown)
Line 1: Line 1:
== About VRM ==
[https://cyber.harvard.edu/lists/info/projectvrm Here's a shortcut to the ProjectVRM list]. More details are under #10, below.


VRM stands for '''Vendor Relationship Management'''. VRM  tools provide customers with both ''independence'' from vendors and ''better ways of engaging'' with vendors. The same tools can also support individuals' relations with schools, churches, government entities and other kinds of organizations.
== Site/Blog ==


In a narrow sense, VRM is the reciprocal — the customer side — of CRM (or [http://en.wikipedia.org/wiki/Customer_Relationship_Management Customer Relationship Management]). VRM tools provide customers with the means to bear their side of the relationship burden. They relieve CRM of the perceived need to "capture," "acquire," "lock in," "manage," and otherwise employ the language and thinking of slave-owners when dealing with customers. With VRM operating on the customer's side, CRM systems will no longer be alone in trying to improve the ways companies relate to customers. Customers will be also be involved, as fully empowered participants, rather than as captive followers.
ProjectVRM's three sites are this wiki, a [https://cyber.harvard.edu/lists/info/projectvrm mailing list], and a Wordpress blog. The wiki and the list are hosted by the [https://cyber.harvard.edu Berkman Klein Center] at [https://harvard.edu/ Harvard University]. The blog was hosted at Harvard from 2007 to 2023. It is now independently maintained at what had been the shortlink for the Harvard blog: [http://projectvrm.org projectvrm.org].


VRM development projects are listed below.
== About VRM ==


== Project VRM ==
VRM stands for [http://en.wikipedia.org/wiki/Vendor_Relationship_Management '''Vendor Relationship Management''']. VRM  tools provide customers with both
# ''independence'' from vendors, and
#''better ways of engaging'' with vendors.


[http://projectvrm.org ProjectVRM] is a research and development project of [http://cyber.law.harvard.edu the Berkman Center for Internet & Society] at Harvard University. It was created by [http://en.wikipedia.org/wiki/Doc_Searls Doc Searls], a fellow at the Center, to encourage VRM development and to conduct research on its premises and its progress.  
The same tools can also support individuals' relations with schools, churches, government entities and other kinds of organizations.


When the project began in 2006, Doc saw it as "a way to fulfill the promise of [http://www.smslaan.org Sms lån][http://cluetrain.com ''The Cluetrain Manifesto'']'s Prime Clue": [http://www.diamondlinks.net link building services]
For individuals, VRM tools and services provide or increase personal autonomy and agency.


[[Image:Not-1.gif]]
For vendors and other service providers, VRM is the customer-side counterpart of CRM (or [http://en.wikipedia.org/wiki/Customer_Relationship_Management Customer Relationship Management]) and other systematic means for engaging individuals.


Doc believed that customer reach would only exceed vendor grasp if customers had the tools for the job. So Doc created ProjectVRM to support the creation and building of those tools.  
In commercial contexts, VRM tools provide customers — that's all of us — with ways to operate with full agency in the marketplace. This includes the ability to control and permit the use of personal data, to aassert intentions in ways that can be understood and respected, and to protect personal privacy. VRM tools also provide ways for each of us to bear bear our own side of relationship burdens, and to have the same kind of scale across many vendors as vendors have across many customers. (An example of scale: being able to change one's address, phone number or last name, for every entity with which a customer deals, ''in one move''.)


Since then the VRM community has grown to include many development projects, companies, allied associations and individuals, in addition to ProjectVRM itself. The community's work is outlined in this wiki, and discussed on its [http://cyber.law.harvard.edu/projectvrm/Mailing_list mailing list], its [http://blogs.law.harvard.edu/vrm blog] and in workshops and other events.
VRM relieves vendors of the perceived need to "capture," "acquire," [http://en.wikipedia.org/wiki/Vendor_lock-in "lock in,"] "manage," and otherwise employ the language and thinking of slave-owners when dealing with customers. With VRM operating on the customer's side, CRM systems will no longer be alone in trying to improve the ways companies relate to customers. Customers will be also be involved, as fully empowered participants, rather than as captive followers.


Read more about ProjectVRM on the [[About | About Page]].
== VRM Principles ==


== VRM and the Economy ==
VRM development work is based on the belief that ''free customers (and citizens) are more valuable than captive ones'' — to themselves, to vendors, and to the larger economy. To be free,


The economic goal of VRM is to improve relationships between Demand and Supply by providing new and better ways for the former to engage with and drive the latter.  
#Customers must enter relationships with vendors as '''independent actors'''.
#Customers must be the '''points of integration for their own data'''.
#Customers must have '''control of data they generate and gather'''. This means they must be able to share data selectively and voluntarily.
#Customers must be able to '''proffer their own terms of engagement'''—and to have auditable records of all contracts to which both sides agree.
#Customers must be '''free to express their demands and intentions outside of any one company's control'''.


This is not possible when all the tools of engagement are provided by suppliers, and all those tools are different. For example, most customers today carry around up to dozens of "loyalty" cards and key-ring tags, each with its own vendor-provided means for controlling interactions and providing benefits. These inconvenience both buyers and sellers, and limit the intelligence that can be gathered and put to use by either party. What if buyers had the ability to advertise their shopping lists to the sellers with which they have relationships? What if buyers were able to establish and maintain loyalty on their own terms and in their own ways? What if customers' ability to express preferences and advertise demand were improved to the point where sellers could reduce money wasted on advertising and other forms of guesswork? What if it were quick and easy for customers to say what they'll pay for what they want, on their own terms (and to pay on the spot, if the terms are mutually agreeable)? VRM tools and services will answer these and many other questions that could not be asked before the Internet came along — and cannot be asked, as long as sellers continue to hold all the relationship cards.
== VRM Goals ==
 
== VRM Principles ==


VRM development work is based on the belief that ''free customers are more valuable than captive ones'' — to themselves, to vendors, and to the larger economy. To be free —
In the "Markets Are Relationships" chapter of the [http://www.cluetrain.com/Cluetrain_10/index.html 10th Anniversary edition] of ''The Cluetrain Manifesto'', Doc Searls writes this about the goals of VRM efforts:


#Relationships must be voluntary.
#'''Provide tools for individuals to manage relationships with organizations'''. These tools are personal. That is, they belong to the individual in the sense that they are under the individual's control. They can also be social, in the sense that they can connect with others and support group formation and action. But they need to be personal first.
#Customers must enter relationships with vendors as independent actors.
#'''Make individuals the collection centers for their own data''', so that transaction histories, health records, membership details, service contracts, and other forms of personal data are no longer scattered throughout a forest of silos.
#Customers must be the points of integration for their own data.
#'''Give individuals the ability to share data selectively''', without disclosing more personal information than the individual allows.
#Customers must have control of data they generate and gather. They must be able to share data selectively, voluntarily, and control the terms of its use.
#'''Give individuals the ability to control how their data is used by others''', and for how long. At the individual's discretion, this may include agreements requiring others to delete the individual's data when the relationship ends.
#Customers must be able to assert their own terms of engagement and service.  
#'''Give individuals the ability to assert their own terms of service''', reducing or eliminating the need for organization-written terms of service that nobody reads and everybody has to "accept" anyway.
#Customers must be free to express their demands and intentions outside of any one company's control.
#'''Give individuals means for expressing demand in the open market''', outside any organizational silo, without disclosing any unnecessary personal information.
#'''Make individuals platforms for business''' by opening the market to many kinds of third party services that serve buyers as well as sellers
#'''Base relationship-managing tools on open standards and open APIs (application program interfaces)'''. This will support a rising tide of activity that will lift an infinite variety of business boats plus other social goods.


VRM research work probes the willingness and ability of customers to assert and enjoy  independence from vendors -- and of vendors' willingness and ability to value and engage with independent customers. It also follows changes in the marketplace as VRM tools come into use.
== VRM Tools ==


== VRM Goals ==
These are ideal characteristics of VRM tools:


In the "Markets Are Relationships" chapter of the [http://www.cluetrain.com/Cluetrain_10/index.html 10th Anniversary edition] of ''The Cluetrain Manifesto'', Doc Searls writes this about the purposes of VRM efforts:
#'''VRM tools are personal'''. As with hammers, wallets, cars and mobile phones, people use them as individuals,. They are social only in secondary ways.
#'''VRM tools help customers express intent'''. These include preferences, policies, terms and means of engagement, authorizations, requests and anything else that’s possible in a free market, outside any one vendor’s silo or ranch.
#'''VRM tools help customers engage'''. This can be with each other, or with any organization, including (and especially) its CRM system.
#'''VRM tools help customers manage'''. This includes both their own data and systems and their relationships with other entities, and their systems.
#'''VRM tools give customers scale across multiple vendors'''. This means customers can express an intent, or save a setting, or change an entry in a form (e.g. phone number or email address), across many different vendor systems, with one action."
#'''VRM tools are substitutable'''. They don't lock individuals into any company's silo.


#Provide tools for individuals to manage relationships with organizations. These tools are personal. That is, they belong to the individual in the sense that they are under the individual's control. They can also be social, in the sense that they can connect with others and support group formation and action. But they need to be personal first.
== VRM Development Work ==
#Make individuals the collection centers for their own data, so that transaction histories, health records, membership details, service contracts, and other forms of personal data are no longer scattered throughout a forest of silos.
#Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.
#Give individuals the ability to control how their data is used by others, and for how long. At the individual's discretion, this may include agreements requiring others to delete the individual's data when the relationship ends.
#Give individuals the ability to assert their own terms of service, reducing or eliminating the need for organization-written terms of service that nobody reads and everybody has to "accept" anyway.
#Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.
#Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers.
#Base relationship-managing tools on open standards, open APIs (application program interfaces), and open code. This will support a rising tide of activity that will lift an infinite variety of business boats, plus other social goods.


== VRM Terminology ==
The list is too long to put here. So go to the [[VRM Development Work]] page.
Like any new market concept, VRM requires the introduction of a handful of new terms. The community is currently (October 2010) using this wiki to develop Wikipedia entries for the following terms. Feel free to help us by reviewing and editing the following pages (or our [[Wikipedia Article Discussion]] page):
* [[Personal data service]]
* [[Personal data server]]
* [[Personal data store]]
* [[Personal data ecosystem]]
* [[Personal Cloud]]


We encourage discussion of these definitions on the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]. Please add other terms you feel are important to harmonize within VRM and with related communities.
We also have a [[Cooperative_Work]] page.


== VRM Development Work ==
== VRM Research ==


Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:
ProjectVRM is a D&R — Development and Reserch — project. Development has always come first. For more on VRM research, see our [[Research]] page.
*[http://azigo.com Azigo]
*[http://connect.me Connect.me]
*[[EmanciPay]]
*[[FCRA: Access to credit data]]
*[[GRM: Government Relationship Management]]
*[http://wiki.eclipse.org/Higgins_2.0 Higgins]
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup at Kantara]
*[http://kynetx.com Kynetx], which also does [http://hvr.me HoverMe]
*[[ListenLog]]
*[http://www.vrm.cl/ myinfo.cl]
*[http://mydex.org/ MyDex]
*[http://newgov.us/ NewGov.us]
*[http://www.paoga.com/ Paoga]
*[http://pegasuspublic.wikispaces.com/ Pegasus]
*[http://personal.com Personal.com]
*[http://personaldataecosystem.org/ Personal Data Ecosystem]
*[[Personal RFP]]
*[http://projectdanube.org/ ProjectDanube]
*[http://www.projectnori.org/ Project Nori]
*[http://www.gofrugal.com/pos/point-of-sale.html Project Management]
*[http://www.qiycorporate.com/ QIY]
*[[r-button]]
*[http://sing.ly/ Singly]
*[http://www.socialnori.org/ Social Nori]
*[http://www.switchbook.com/ SwitchBook]
*[http://telehash.org Telehash]
*[http://www.trustfabric.com/ TrustFabric]
*[http://kantarainitiative.org/confluence/display/uma/ UMA]
*[http://www.vrmhub.net VRM Hub]
*[http://www.vrmlabs.net VRM Labs]
*[http://www.banyanproject.com/ The Banyan Project]
*[https://github.com/quartzjer/Locker#readme The Locker Project]
*[http://themineproject.org/ The Mine! Project]
*[http://code.google.com/p/webfinger/ webfinger]


== ProjectVRM Committees ==
Also, after more than a dozen years at this, it is clear that Amara's Law applies: We tend to overestimate in the short term and underestimate in the long.


*[[Vision Committee]]
At this writing (September, 2022), Doc Searls, who started and runs ProjectVRM, is (with his wife Joyce) a [https://ostromworkshop.indiana.edu/about/visiting-scholars/index.html?keyword=&typeDefault=Visiting%20Scholars&letter=S visiting scholar] with the [https://ostromworkshop.indiana.edu/ Ostrom Workshop] at Indiana University, working on a VRM project called the [https://customercommons.org/a-new-way/ Byway], which will be researched closely as it rolls out in Bloomington, Indiana, home of the university. This is the first time Doc is working directly on a VRM development project, rather than just encouraging many projects.
*[[Marketing Committee]]
*[[Standards Committee]]
*[[Organization Committee]]
*[[Usage Committee]]
*[[Compliance Committee]]
*[[Steering Committee]]


== ProjectVRM Resources ==
== ProjectVRM Resources ==
Line 116: Line 74:
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]
* [[VRM FAQ]]
* [[VRM FAQ]]
* VRM [Twitter stream http://twitter.com/vrm]
* @VRM [Twitter stream http://twitter.com/vrm]


Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.
Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.
== Privacy Manifesto ==
ProjectVRM hosts the draft of a [[Privacy Manifesto]] that lives on this wiki, and which has also appeared in earlier versions elsewhere, such as [https://medium.com/@dsearls/a-privacy-manifesto-e475d4d8792a here on Medium].


== VRM Events ==
== VRM Events ==


Also see [http://cyber.law.harvard.edu/projectvrm/Events Events] page.
=== Regular Events ===
ProjectVRM events take place once or twice per year:
 
The two events where the VRM community is gathered and maintained both happen in the same weeks, at the same location, twice per year, Spring and Fall. Those are VRM Day and [http://iiworkshop.org IIW, the Internet Identity Workshop]. VRM Day happens on the Monday preceding IIW, which happens the next three days (Tuesday through Thursday), at the [http://computerhistory.org Computer History Museum] in Mountain View, California, which is at the center of Silicon Valley, midway between its two main airports (SFO, for San Francisco and SJC, for San Jose).
 
The purpose of VRM day is to prep for the following three days at IIW. Note that IIW is an unconference, so its topics are whatever those participating choose. VRM is always one of the main topics.
 
=== Upcoming Events ===
=== Upcoming Events ===
2011
 
* [http://iiw13.eventbrite.com/ IIW XIII (2011-B)] November, 2011, Mountain View, CA]
2022
 
* VRM Day 2022b


=== Past Events ===
=== Past Events ===
2022
* VRM Day 2022a
2021
* VRM Day 2021a
* VRM Day 2021b
2020
* [https://www.eventbrite.com/e/vrmme2b-day-2020a-tickets-100546832282# VRM/Me2B Day 2020a]
* VRM/Me2B Day 2020b
2019
* VRM Day 2019a
* VRM Day 2019b
2018
* [http://vrmday2018b.eventbrite.com/ VRM Day] on Monday, 22 October, at the [http://chm.org Computer History Museum] in Mountain View, CA.
* [https://iiw27.eventbrite.com/ Internet Identity Workshop — IIW] on Tuesday-Thursday, 23-25 October, at the [http://chm.org Computer History Museum] in Mountain View, CA.
2017
* VRM Day 2017b
* VRM Day 2017a
2016
* [https://www.ctrl-shift.co.uk/personal-information-economy-2016/ Personal Information Economy 2016: Achieving Growth Through Trust] on Thursday, 29th September 2016 from 08.30 to 17.00 (GMT), Kings Place, 90 York Way, London, N1 9AG. (Doc Searls is one of the speakers, and many VRM community members will attend.)
* [http://vrmday2016b.eventbrite.com/ VRM Day] on Monday, 24 October, at the [http://chm.org Computer History Museum] in Mountain View, CA.
* [https://iiw23.eventbrite.com/ Internet Identity Workshop — IIW] on Tuesday-Thursday, 25-27 October, at the [http://chm.org Computer History Museum] in Mountain View, CA.
* [http://mydata2016.org/ MyData2016] 31 August to 2 September 2016, in Helsinki, Finland. (Doc Searls and Sean Bohan spoke there.)
* [http://vrmday2016a.eventbrite.com/ VRM Day] on Monday, 25 April, at the [http://chm.org Computer History Museum] in Mountain View, CA.
* [http://mesinfos.fing.org/self-data-the-european-pims-lanscape/ Self-Data: The European PIMS Landscape], part of  [http://fing.org/ FING]'s [http://mesinfos.fing.org/ Mesinfos] work.
* [https://iiw22.eventbrite.com/ Internet Identity Workshop — IIW] on Tuesday-Thursday, 26-28 April, at the [http://chm.org Computer History Museum] in Mountain View, CA.
2015
* [http://www.eventbrite.com/e/vrm-day-2015a-tickets-15523363799?aff=erelexporg VRM Day] on Monday, 6 April
* [http://www.internetidentityworkshop.com/ Internet Identity Workshop] #20, (7-9 April) at the [http://chm.org Computer History Museum] in Mountain View, CA.
* VRM Day on Oct 26
* [http://www.internetidentityworkshop.com/ Internet Identity Workshop] #21, (27-29 October) at the [http://chm.org Computer History Museum] in Mountain View, CA.
2014
* [http://www.eventbrite.com/e/vrm-day-2014b-tickets-12888143785 VRM Day 2014b], on 27 October, in advance of the Internet Identity Workshop, at the [http://chm.org Computer History Museum] in Mountain View, CA.
* [http://iiw.idcommons.net/IIW_19_Notes Internet Identity Workshop (Notes)] #19, (28-30 October) at the [http://chm.org Computer History Museum] in Mountain View, CA.
* [http://VRMday2014a.eventbrite.com VRM Day 2014a] 5 May at the [http://chm.org Computer History Museum] in Mountain View, CA. Free.
* [http://iiw.idcommons.net/IIW_18_Notes Internet Identity Workshop (Notes)] #18, 6-8 May at the [http://chm.org Computer History Museum] in Mountain View, CA.
2013
* [http://data-tuesday.com/calendrier/prochain-data-tuesday/ Data Tuesday] "VRM : le contrôle des données aux utilisateurs !" au 12/14, rue Henri Barbusse – 92110 Clichy
* [[VRM Day 2013a]] , in advance of IIW, below, 6 May in Mountain View, CA.
* [http://www.internetidentityworkshop.com/ Internet Identity Workshop #16], 7-9 May at the Computer History Museum in Mountain View, CA. IIW is where #VRM in some ways began and where it remains a huge part of what gets worked on there.
* [https://identityworkshop.eu/ European Workshop on Trust & Identity], 12-13 February, Vienna, Austria. The focus is on identity, but VRM is sure to come up.
* [http://www.id-conf.com/ European Identity & Cloud Conference], 14 -17 May, Munich, Germany. Kuppinger-Cole, which puts on the conference, has a focus on [http://www.kuppingercole.com/report/advisorylifemanagementplatforms7060813412 life management platforms], which are highly relevant to VRM.
* [http://www.internetidentityworkshop.com/ Internet Identity Workshop #17], 22-24 October at the Computer History Museum in Mountain View, CA.
2012
* [http://www.picnicnetwork.org/festival PICNIC Festival 2012], at the EYE Film Institute, Amsterdam, Netherlands. September 17-18, 2012. Register [http://www.picnicnetwork.org/register-picnic-festival-12 here]. Big fun annual event. Doc will speak there.
* VRM pre-IIW meeting/worshop. Location TBD. October 22, 2012. Interested VRooMers gather to catch up and prep for the next three days at IIW.
* [http://www.internetidentityworkshop.com/ Internet Identity Workshop] #15, Computer History Museum, Mountain View, CA. October 23-25, 2012. Register [http://iiw15.eventbrite.com/ here]. This is very much a VRM workshop, since it's an unconference where many VRooMers show up and hold sessions of their own choosing.
* [http://datavenu.com/ Datavenu], at the [http://www.csom.umn.edu/Carlson School of Management], [http://www.umn.edu/ University of Minnesota], Minneapolis, MN. On August 7-8, 2012. Register [http://datavenu.com/?page_id=24 here]. First VRooMy event in Minnesota, organized by Barb Bowen. Kaliya, Doc and Phil are speakers.
* [http://schedule.sxsw.com/2012/events/event_IAP13611 Are Free Customers More Valuable Than Captive Ones?], by [http://doc.searls.com Doc Searls] at [http://sxsw.com/interactive South by Southwest Interactive], Austin, Texas, March 9-13.
* [http://www.newdigitaleconomics.com/events/ STL Partners Executive Brainstorm], San Francisco, March 27-28.
* [http://www.eventbrite.com/event/3333006111 Pre-IIW VRM workshop] at Ericsson, 200 Holger Way (Zanker & 237), San Jose, CA 95134, 9am-5pm April 30. Our usual meeting, with a special welcome for newbies.
* [http://www.id-conf.com/eic2012/ European Identity and Cloud Conference], Munich, April 17-20. Craig Burton, Phil Windley Drummond Reed, Kim Cameron, Doc Searls and other VRM'ers will be there
* [http://www.mashupevent.com/event/intention-economy Intention Economy Mashup Event] London, Innovation Warehouse, 1 East Poultry Avenue, London. EC1A 9PT 4:30-9:30pm, Monday, 23 April Put on by Tony Fish, Sam Sethi and Iain Henderson. Named after Doc's new book, which will be almost out then. Doc will speak there.
* [http://vrm-crm.eventbrite.com/ VRM and CRM Inter-op London 2012] London , EC1A 9PT Tuesday, April 24, 2012 from 9:00 AM to 1:00 PM (GMT) Hosted by Iain Henderson, with a special invite to CRM professionals.
* [http://www.internetidentityworkshop.com/ IIW14 Internet Identity Workshop #14], Mountain View, CA, May 1-3. The venerable unconference where there are many VRM breakout sessions.
2011
2011
*[http://www.internetidentityworkshop.com/iiw-12/ IIW #12], May 3-5, Mountain View, CA
*[http://www.cvent.com/events/conversational-commerce-conference/event-summary-f70a703bbabf4cda930c1412dee2bf4f.aspx Conversational Commerce Conference], February 2-3, San Francisco
*[http://www.cvent.com/events/conversational-commerce-conference/event-summary-f70a703bbabf4cda930c1412dee2bf4f.aspx Conversational Commerce Conference], February 2-3, San Francisco
* [http://impact.kynetx.com/ IMPACT/2011], March 22-23, Salt Lake City, UT
* [http://impact.kynetx.com/ IMPACT/2011], March 22-23, Salt Lake City, UT
* VRM Gathering at [[SXSW Interactive 2011]] (date TBD)
* VRM Gathering at [[SXSW Interactive 2011]]
* [http://iiw12.eventbrite.com/ IIW XII (2011-A)] May 3-5, 2011, Mountain View, CA
* [http://iiw12.eventbrite.com/ IIW XII (2011-A)] May 3-5, 2011, Mountain View, CA
* [http://iiw13.eventbrite.com/ IIW XIII (2011-B)] October 18-20, 2011, Mountain View, CA]


2010
2010
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge, MA
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge, MA.


2009
2009
Line 142: Line 184:
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA.


2008
2008
Line 148: Line 190:
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University


Other meetings and workshops take place before and during [http://www.internetidentityworkshop.com/ Internet Identity Workshops] in Mountain View, California, each Fall and Spring.  Also see [http://cyber.law.harvard.edu/projectvrm/Events Events] page for some past events.


[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.
== ProjectVRM Participation ==
 
We have two mailing lists:
 
* Our main [[Mailing list]]. You can subscribe and view the archive [https://cyber.law.harvard.edu/lists/info/projectvrm here].
* Our geeks-only [https://cyber.law.harvard.edu/lists/info/opensourcevrm Open Source VRM developers list], which hasn't taken off, but we want to at least save the link, should it want to


Other meetings and workshops take place before and during [http://www.internetidentityworkshop.com/ Internet Identity Workshops] in Mountain View, California, each Fall and Spring. VRM is also a topic at [http://kynetximpactspring2010.eventbrite.com/ Kynetx Impact] conferences.
You can edit this wiki by:
* registering up at the top of this page
* sending e-mail to the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list] asking to be enabled as an editor (to combat the spam problem). Be sure you provide your actual handle (username)


== ProjectVRM Participation ==
[https://twitter.com/#!/dsearls/vroomers Here is a list of "VRooMers" on Twitter.]


Sign up for the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]. Or edit this wiki by signing up at the top of this page.
We encourage you to use the hashtag #VRM when blogging or tweeting about the topic.

Latest revision as of 11:40, 3 March 2024

Here's a shortcut to the ProjectVRM list. More details are under #10, below.

Site/Blog

ProjectVRM's three sites are this wiki, a mailing list, and a Wordpress blog. The wiki and the list are hosted by the Berkman Klein Center at Harvard University. The blog was hosted at Harvard from 2007 to 2023. It is now independently maintained at what had been the shortlink for the Harvard blog: projectvrm.org.

About VRM

VRM stands for Vendor Relationship Management. VRM tools provide customers with both

  1. independence from vendors, and
  2. better ways of engaging with vendors.

The same tools can also support individuals' relations with schools, churches, government entities and other kinds of organizations.

For individuals, VRM tools and services provide or increase personal autonomy and agency.

For vendors and other service providers, VRM is the customer-side counterpart of CRM (or Customer Relationship Management) and other systematic means for engaging individuals.

In commercial contexts, VRM tools provide customers — that's all of us — with ways to operate with full agency in the marketplace. This includes the ability to control and permit the use of personal data, to aassert intentions in ways that can be understood and respected, and to protect personal privacy. VRM tools also provide ways for each of us to bear bear our own side of relationship burdens, and to have the same kind of scale across many vendors as vendors have across many customers. (An example of scale: being able to change one's address, phone number or last name, for every entity with which a customer deals, in one move.)

VRM relieves vendors of the perceived need to "capture," "acquire," "lock in," "manage," and otherwise employ the language and thinking of slave-owners when dealing with customers. With VRM operating on the customer's side, CRM systems will no longer be alone in trying to improve the ways companies relate to customers. Customers will be also be involved, as fully empowered participants, rather than as captive followers.

VRM Principles

VRM development work is based on the belief that free customers (and citizens) are more valuable than captive ones — to themselves, to vendors, and to the larger economy. To be free,

  1. Customers must enter relationships with vendors as independent actors.
  2. Customers must be the points of integration for their own data.
  3. Customers must have control of data they generate and gather. This means they must be able to share data selectively and voluntarily.
  4. Customers must be able to proffer their own terms of engagement—and to have auditable records of all contracts to which both sides agree.
  5. Customers must be free to express their demands and intentions outside of any one company's control.

VRM Goals

In the "Markets Are Relationships" chapter of the 10th Anniversary edition of The Cluetrain Manifesto, Doc Searls writes this about the goals of VRM efforts:

  1. Provide tools for individuals to manage relationships with organizations. These tools are personal. That is, they belong to the individual in the sense that they are under the individual's control. They can also be social, in the sense that they can connect with others and support group formation and action. But they need to be personal first.
  2. Make individuals the collection centers for their own data, so that transaction histories, health records, membership details, service contracts, and other forms of personal data are no longer scattered throughout a forest of silos.
  3. Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.
  4. Give individuals the ability to control how their data is used by others, and for how long. At the individual's discretion, this may include agreements requiring others to delete the individual's data when the relationship ends.
  5. Give individuals the ability to assert their own terms of service, reducing or eliminating the need for organization-written terms of service that nobody reads and everybody has to "accept" anyway.
  6. Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.
  7. Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers
  8. Base relationship-managing tools on open standards and open APIs (application program interfaces). This will support a rising tide of activity that will lift an infinite variety of business boats plus other social goods.

VRM Tools

These are ideal characteristics of VRM tools:

  1. VRM tools are personal. As with hammers, wallets, cars and mobile phones, people use them as individuals,. They are social only in secondary ways.
  2. VRM tools help customers express intent. These include preferences, policies, terms and means of engagement, authorizations, requests and anything else that’s possible in a free market, outside any one vendor’s silo or ranch.
  3. VRM tools help customers engage. This can be with each other, or with any organization, including (and especially) its CRM system.
  4. VRM tools help customers manage. This includes both their own data and systems and their relationships with other entities, and their systems.
  5. VRM tools give customers scale across multiple vendors. This means customers can express an intent, or save a setting, or change an entry in a form (e.g. phone number or email address), across many different vendor systems, with one action."
  6. VRM tools are substitutable. They don't lock individuals into any company's silo.

VRM Development Work

The list is too long to put here. So go to the VRM Development Work page.

We also have a Cooperative_Work page.

VRM Research

ProjectVRM is a D&R — Development and Reserch — project. Development has always come first. For more on VRM research, see our Research page.

Also, after more than a dozen years at this, it is clear that Amara's Law applies: We tend to overestimate in the short term and underestimate in the long.

At this writing (September, 2022), Doc Searls, who started and runs ProjectVRM, is (with his wife Joyce) a visiting scholar with the Ostrom Workshop at Indiana University, working on a VRM project called the Byway, which will be researched closely as it rolls out in Bloomington, Indiana, home of the university. This is the first time Doc is working directly on a VRM development project, rather than just encouraging many projects.

ProjectVRM Resources

Conference Call archive and audio links can be found at the Community Portal page.

Privacy Manifesto

ProjectVRM hosts the draft of a Privacy Manifesto that lives on this wiki, and which has also appeared in earlier versions elsewhere, such as here on Medium.

VRM Events

Regular Events

The two events where the VRM community is gathered and maintained both happen in the same weeks, at the same location, twice per year, Spring and Fall. Those are VRM Day and IIW, the Internet Identity Workshop. VRM Day happens on the Monday preceding IIW, which happens the next three days (Tuesday through Thursday), at the Computer History Museum in Mountain View, California, which is at the center of Silicon Valley, midway between its two main airports (SFO, for San Francisco and SJC, for San Jose).

The purpose of VRM day is to prep for the following three days at IIW. Note that IIW is an unconference, so its topics are whatever those participating choose. VRM is always one of the main topics.

Upcoming Events

2022

  • VRM Day 2022b

Past Events

2022

  • VRM Day 2022a

2021

  • VRM Day 2021a
  • VRM Day 2021b

2020

2019

  • VRM Day 2019a
  • VRM Day 2019b

2018

2017

  • VRM Day 2017b
  • VRM Day 2017a

2016

2015

2014

2013

2012

2011

2010

  • VRM+CRM 2010 August 26-27 Harvard University, Cambridge, MA.

2009

2008

Other meetings and workshops take place before and during Internet Identity Workshops in Mountain View, California, each Fall and Spring. Also see Events page for some past events.

ProjectVRM Participation

We have two mailing lists:

You can edit this wiki by:

  • registering up at the top of this page
  • sending e-mail to the Project VRM mailing list asking to be enabled as an editor (to combat the spam problem). Be sure you provide your actual handle (username)

Here is a list of "VRooMers" on Twitter.

We encourage you to use the hashtag #VRM when blogging or tweeting about the topic.

Retrieved from "http://cyber.harvard.edu/projectvrm/?title=Main_Page&oldid=6622"