ProjectVRM, which I’ve been running as a fellow at Harvard’s Berkman Center has been growing nicely over the past four years, and is on its way toward becoming an independent entity. (It will exist, as always, to support a community of developers and interested parties outside of the project itself.) It’s funny, I remember Jeremie Miller, who encouraged me to choose VRM (before it had that name) as my Berkman project when I started out in late summer of 2006, telling me “it will take five years.” Meaning that’s generally how long any new world-changing development effort spends in the quiet shadows before it breaks out into the open and starts taking off. (If it does at all.) That’s about how long it took for Jeremie’s own Jabber/XMPP efforts. (He predicted five years at the beginning of that too, and he was just a kid then. Wise dude.)
I’ve liked keeping VRM in the shadows, because I felt that code mattered more than anything. Code talks. Buzz walks. And I say that even though I’m not bad at generating buzz when I need to. Now the code base is growing enough that many of us feel a need to start talking about it. Especially to potential partners in the business world.
We’ve described VRM as the “reciprocal” of CRM at various times. It’s much more than that, actually. Its tools that give individuals independence from others, yet useful means for engaging with others — especially organizations, and among those especially sellers. But the core elements are individuals and independence.
I’ve also seen VRM from the start as fundamentally an open source effort, not a commercial one. I also saw open source tools, with their high use-value, having enormous leverage into sale-value for any company selling products or services based on those open tools. This would include, among other things, many fourth-party services — itself another whole new category.
CRM in the meantime has grown to become a $15-billion business. It has also lately enlarged its intrest to include Social CRM. Our friend Paul Greenberg has written extensively on both, and is the driving force behind Destination CRM next week in New York. (Which I hate to miss, but have a prior commitment elsewhere.) Since VRM will be a topic at Destination CRM, and we can get space here at Harvard before the students come back, we put together the workshop to follow at the other end of the same month.
The workshop is for VRM and CRM developers and other interested parties (such as CRM customers) together to start building out the common ground between them. The nature of relationship is to exist between and apart from both parties. Neither controls the other. Both work together, in a common space between the two. We haven’t had that space before. The default on the CRM side (and one that predates CRM itself) is for vendors to control relationships with customers. What VRM proposes is that neither controls the other, but both manage the space between them, in mutually beneficial ways.
The workshop will mostly be an unconference, though there will be some opening briefings by VRM and CRM folks, to set the stage for sessions to follow. Here are a few of the topics and questions I expect will come up. (These are copied over from a post I just put up over on the ProjectVRM blog.) —
- Terms of service. How can we get past the legal hurdles and shackles that inconvenience both buyers and sellers when they get acquainted?
- Privacy policies. How can we reduce the suspicions and frictions that these involve?
- Personal data. What tools, methods and services are being developed for individuals to keep track of data they generate or is being kept by sellers and other parties? What means do we have for sharing or exchanging that data in secure and trustable ways?
- Signaling. What new methods will both individuals and organizations have for notifying each other of interests, intentions, policies, preferences, or changes in any of those? How can we make these common across the industry, rather than different for every organization?
- Self-tracking and personal informatics. What vendor-independent means are being developed for individuals to keep track of their own personal data, and manage it?
- Interactive shopping. The Live Web we saw coming in 2005 is here. So is the mobile one. Combine those facts with the ability to issue personal RFPs (or just to publish your shopping list to trusted retailers and fourth parties), and what do you get?
- Search. What new paradigms for searching are being developed, especially in the context of all the topics above?
- Non-coercive loyalty. What ways are being developed for individuals to express and manage their own forms of loyalty to sellers and other organizations? How can this improve existing loyalty programs?
- Personal RFPs or Advertising in Reverse. How can individual customers notify whole market categories of their intent to purchase a product, safely and securely, without inviting a torrent of promotional jive in response?
- Leveraging base-level protocols, standards and tools. There are hundreds of thousands of free and open source tools, protocols and other goods already in the world, ready to serve as free building materials and guidelines. What can we use of these, and what new ones do we need? What new ones are in development on the VRM side?
- Reducing MLOTT — Money Left On The Table. In our current system, a huge sum of demand goes un-met because of the the means for communicating interest and availability are on the supply side. How (including the means listed above and others) can we equip demand to notify supply of money ready to be spent? In the old days this was seen as “lead generation” by suppliers. But now it’s time to get past that.
- Tie-ins with SCRM. Social CRM is the hottest topic in CRM. How can VRM connect with and through social networking? Important question: Should “social” be restricted to just what can be done through Facebook, Twitter and other commercial services?
- Patient-driven health care. How can individuals be the collection points for their own health data, and the point of origination for what gets done with it?
- API symphonics. The commercial world is increasingly building around a collection of interconnected APIs, or Application Programming Interfaces. Many CRM systems are built around their own APIs. VRM will surely connect into many APIs. How should we be thinking about and guiding evolution here?
- The oppposite of cookies. Sites and companies of all kinds have been keeping track of customers through cookies since the mid-’90s. How can customers do the same with their suppliers?
Feel free to add your own, correct these, or make other recommendations.
More details on the event wiki page.
Comments are now closed.