Category: r-button (Page 1 of 2)

We’re done with Phase One

Here’s a picture that’s worth more than a thousand words:

maif-vrm

He’s with MAIF, the French insurance company, speaking at MyData 2016 in Helsinki, a little over a month ago. Here’s another:

sean-vrm

That’s Sean Bohan, head of our steering committee, expanding on what many people at the conference already knew.

I was there too, giving the morning keynote on Day 2:

cupfu1hxeaa4thh

It was an entirely new talk. Pretty good one too, especially since  I came up with it the night before.

See, by the end of Day 1, it was clear that pretty much everybody at the conference already knew how market power was shifting from centralized industries to distributed individuals and groups (including many inside centralized industries). It was also clear that most of the hundreds of people at the conference were also familiar with VRM as a market category. I didn’t need to talk about that stuff any more. At least not in Europe, where most of the VRM action is.

So, after a very long journey, we’re finally getting started.

In my own case, the journey began when I saw the Internet coming, back in the ’80s.  It was clear to me that the Net would change the world radically, once it allowed commercial activity to flow over its pipes. That floodgate opened on April 30, 1995. Not long after that, I joined the fray as an editor for Linux Journal (where I still am, by the way, more than 20 years later). Then, in 1999, I co-wrote The Cluetrain Manifesto, which delivered this “one clue” above its list of 95 Theses:

not

And then, one decade ago last month, I started ProjectVRM, because that clue wasn’t yet true. Our reach did not exceed the grasp of marketers in the world. If anything, the Net extended marketers’ grasp a lot more than it did ours. (Shoshana Zuboff says their grasp has metastacized into surveillance capitalism. ) In respect to Gibson’s Law, Cluetrain proclaimed an arrived future that was not yet distributed. Our job was to distribute it.

Which we have. And we can start to see results such as those above. So let’s call Phase One a done thing. And start thinking about Phase Two, whatever it will be.

To get that work rolling, here are a few summary facts about ProjectVRM and related efforts.

First, the project itself could hardly be more lightweight, at least administratively. It consists of:

Second, we have a spin-off: Customer Commons, which will do for personal terms of engagement (one each of us can assert online) what Creative Commons (another Berkman-Klein spinoff) did for copyright.

Third, we have a list of many dozens of developers, which seem to be concentrated in Europe and Australia/New Zealand.  Two reasons for that, both speculative:

  1. Privacy. The concept is much more highly sensitive and evolved in Europe than in the U.S. The reason we most often get goes, “Some of our governments once kept detailed records of people, and those records were used to track down and kill many of them.” There are also more evolved laws respecting privacy. In Australia there have been privacy laws for several years requiring those collecting data about individuals to make it available to them, in forms the individual specifies. And in Europe there is the General Data Protection Regulation, which will impose severe penalties for unwelcome data gathering from individuals, starting in 2018.
  2. Enlightened investment. Meaning investors who want a startup to make a positive difference in the world, and not just give them a unicorn to ride out some exit. (Which seems to have become the default model in the U.S., especially Silicon Valley.)

What we lack is research. And by we I mean the world, and not just ProjectVRM.

Research is normally the first duty of a project at the Berkman Klein Center, which is chartered as a research organization. Research was ProjectVRM’s last duty, however, because we had nothing to research at first. Or, frankly, until now. That’s why we were defined as a development & research project rather than the reverse.

Where and how research on VRM and related efforts happens is a wide open question. What matters is that it needs to be done, starting soon, while the “before” state still prevails in most of the world, and the future is still on its way in delivery trucks. Who does that research matters far less than the research itself.

So we are poised at a transitional point now. Let the conversations about Phase Two commence.

 

 

 

Save

Save

Save

Save

Save

Save

Save

VRM development work

I’ll be having a brown bag lunch today with a group of developers, talking about VRM and personal clouds, among other stuff that’s sure to come up. To make that easier, I’ve copied and pasted the current list from the VRM developers page of the ProjectVRM wiki. If you’d like to improve it in any way, please do — either on the wiki itself, or by letting us know what to change.

While there are entire categories that fit in the larger VRM circle — quantified self (QS) and personal health records (PHRs) are two that often come up — we’ve tried to confine this list to projects and companies that directly address the goals (as well as the principles) listed on the main page of the wiki.


Here is a partial list of VRM development efforts. (See About VRM). Some are organizations, some are commercial entities, some are standing open source code development efforts.

SOFTWARE and SERVICES
Intentcasting
AskForIt † – individual demand aggregation and advocacy
Body Shop Bids † – intentcasting for auto body work bids based on uploaded photos
Have to Have † – “A single destination to store and share everything you want online”
Intently † – Intentcasting “shouts” for services, in the U.K.
Innotribe Funding the Digital Asset Grid prototype, for secure and accountable Intentcasting infrastructure
OffersByMe † – intentcasting for local offers
Prizzm †- social CRM platform rewarding customers for telling businesses what they want, what they like, and what they have problems with
RedBeacon † – intentcasting locally for home services
Thumbtack † – service for finding trustworthy local service providers
Trovi intentcasting; matching searchers and vendors in Portland, OR and Chandler, AZ†
Übokia intentcasting†
Zaarly † intentcasting to community – local so far in SF and NYC
Browser Extensions
Abine † DNT+, deleteme, PrivacyWatch: privacy-protecting browser extentions
Collusion Firefox add-on for viewing third parties tracking your movements
Disconnect.me † browser extentions to stop unwanted tracking, control data sharing
Ghostery † browser extension for tracking the trackers
PrivacyScore † browser extensions and services to users and site builders for keeping track of trackers
Databases
InfoGrid – graph database for personal networking applications
ProjectDanube – open source software for identity and personal data services
Messaging Services and Brokers
Gliph †- private, secure identity management and messaging for smartphones
Insidr † – customer service Q&A site connecting to people who have worked in big companies and are willing to help when the company can’t or won’t
PingUp (was Getabl) †- chat utility for customers to engage with merchants the instant customers are looking for something
TrustFabric † – service for managing relationships with sellers
Personal Data and Relationship Management
Azigo.com † – personal data, personal agent
ComplainApp † – An iOS/Android app to “submit complaints to businesses instantly – and find people with similar complaints”
Connect.Me † – peer-to-peer reputation, personal agent
Geddup.com † – personal data and relationship management
Higgins – open source, personal data
The Locker Project – open source, personal data
Mydex †- personal data stores and other services
OneCub †- Le compte unique pour vos inscriptions en ligne (single account for online registration)
Paoga † – personal data, personal agent
Personal.com † – personal data storage, personal agent
Personal Clouds – personal cloud wiki
Privowny † – privacy company for protecting personal identities and for tracking use and abuse of those identities, building relationships
QIY † – independent infrastructure for managing personal data and relationships
Singly † – personal data storage and platform for development, with an API
Transaction Management
Dashlane † – simplified login and checkout
Trust-Based or -Providing Systems and Services
id3 – trust frameworks
Respect Network † – VRM personal cloud network based on OAuth, XDI, KRL, unhosted, and other open standards, open source, and open data initiatives. Respect Network is the parent of Connect.Me.
Trust.cc Personal social graph based fraud prevention, affiliated with Social Islands
SERVICE PROVIDERS OR PROJECTS BUILT ON VRM PRINCIPLES
First Retail Inc. † commodity infrastructure for bi-directional marketplaces to enable the Personal RFP
dotui.com † intelligent media solutions for retail and hospitality customers
Edentiti Customer driven verification of idenity
Real Estate Cafe † money-saving services for DIY homebuyers & FSBOs
Hover.com Customer-driven domain management†
Hypothes.is – open source, peer review
MyInfo.cl (Transitioning from VRM.cl) †
Neustar “Cooperation through trusted connections” †
NewGov.us – GRM
[1] † – Service for controlling one’s reputation online
Spotflux † malware, tracking, unwanted ad filtration through an encrypted tunnel
SwitchBook † – personal search
Tangled Web † – mobile, P2P & PDS
The Banyan Project– community news co-ops owned by reader/members
TiddlyWiki – a reusable non-linear personal Web notebook
Ting † – customer-driven mobile virtual network operator (MVNO – a cell phone company)
Tucows †
VirtualZero – Open food platform, supply chain transparency
INFRASTRUCTURE
Concepts
EmanciPay – dev project for customer-driven payment choices
GRM: Government Relationship Management – subcategory of VRM
ListenLog – personal data logging
Personal RFP – crowdsourcing, standards
R-button – UI elements for relationship members
Hardware
Freedom Box – personal server on free software and hardware
Precipitat, WebBox – new architecture for decentralizing the Web, little server
Standards, Frameworks, Code bases and Protocols
Datownia † – builds APIs from Excel spreadsheets held in Dropbox
Evented APIs – new standard for live web interactivity
KRL (Kinetic Rules Language) – personal event networks, personal rulesets, programming Live Web interactions
Kynetx † – personal event networks, personal rulesets
https://github.com/CSEMike/OneSwarm Oneswarm] – privacy protecting peer-to-peer data sharing
http://www.mozilla.org/en-US/persona/ Mozila Persona] – a privacy-protecting one-click email-based way to do single sign on at websites
TAS3.eu — Trusted Architecture for Securely Shared Services – R&D toward a trusted architecture and set of adaptive security services for individuals
Telehash – standards, personal data protocols
Tent – open decentralized protocol for personal autonomy and social networking
The Mine! Project – personal data, personal agent
UMA – standards
webfinger – personal Web discovery, finger over HTTP
XDI – OASIS semantic data interchange standard
PEOPLE
Analysts and Consultants
Ctrl-SHIFT † – analysts
Synergetics † – VRM for job markets
VRM Labs – Research
HealthURL – Medical
Consortia, Workgroups
Fing.org – VRM fostering organization
Information Sharing Workgroup at Kantara – legal agreements, trust frameworks
Pegasus – eID smart cards
Personal Data Ecosystem Consortium (PDEC) – industry collaborative
Meetups, Conferences, and Events
IIW: Internet Identity Workshop – yearly unconference in Mountain View
VRM Hub – meeting in LondonNOTES:
† Indicates companies. Others are organizations, development projects or both. Some development projects are affiliated with companies. (e.g. Telehash and The Locker Project with Singly, and KRL with Kynetx.)
A – creating standard
B – Using other standards
1 – EventedAPI

Let’s turn Do Not Track into a dialog

Do Not Track (DNT), by resembling Do Not Call in name, sounds like a form of prophylaxis.  It isn’t. Instead it’s a request by an individual with a browser not to be tracked by a website or its third parties. As a request, DNT also presents an interesting opportunity for dialogue between user and site, shopper and retailer, or anybody and anything. I laid out one possibility recently in my Inkwell conversation at The Well. Here’s a link to the page, and here’s the text of the post:

The future I expect is one in which buyers have many more tools than they have now, that the tools will be theirs, and that these will enable buyers to work with many different sellers in the same way.

One primitive tool now coming together is “Do Not Track” (or DNT): http://en.wikipedia.org/wiki/Do_Not_Track It’s an HTTP header in a user’s browser that signals intention to a website. Browser add-ons or extensions for blocking tracking, and blocking ads, are also tools, but neither constitute a social protocol, because they are user-side only. The website in most cases doesn’t know ad or tracking blocking being used, or why. On the other hand, DNT is a social gesture. It also isn’t hostile. It just expresses a reasonable intention (defaulted to “on” in the physical world) not to be followed around.

But DNT opens the door to much more. Think of it as the opening to dialog:

User: Don’t track me.
Site: Okay, what would you like us to do?
User: Share the data I shed here back to me in a standard form, specified here (names a source).
Site: Okay. Anything else?
User: Here are my other preferences and policies, and means for matching them up with yours to see where we can agree.
Site: Good. Here are ours.
User: Good. Here is where they match up and we can move forward.
Site: Here are the interfaces to our CRM (Customer Relationship Management) system, so your VRM (Vendor Relationship Management) system can interact with it.
User: Good. From now on my browser will tell me we have a working relationship when I’m at your site, and I can look at what’s happening on both sides of it.

None of this can be contemplated in relationships defined entirely by the sellers, all of which are silo’d and different from each other, which is what we’ve had on the commercial Web since 1995. But it can be contemplated in the brick & mortar world, which we’ve had since Ur. What we’re proposing with VRM is nothing more than bringing conversation-based relationships that are well understood in the brick-and-mortar world into the commercial Web world, and weaving better marketplaces in the process.

A bit more about how the above might work:
http://blogs.law.harvard.edu/vrm/2012/02/23/how-about-using-the-no-track-button-we-already-have/

And a bit more about what’s wrong with the commercial Web (so far, and it’s not hard to fix) here:
http://blogs.law.harvard.edu/vrm/2012/02/21/stop-making-cows-stop-being-calves /

So, to move forward, consider this post a shout-out to VRM developers, to the Tracking Protection Working Group at the W3C, to browser developers, to colleagues at Berkman (where Chris Soghoian was a fellow, about at the time he helped think up DNT) — and to everybody with the will and the ways to move forward on this thing.

And hey: it’s also our good luck that the next IIW is coming up at the Computer History Museum in Mountain View, from October 23rd to 25th. IIW is the perfect place to meet and start hashing out DNT-D (I just made that up: DNT-Dialog) directions. IIW is an unconference: no keynotes, panelists or vendor booths. Participants vet and choose their own topics and break out into meeting rooms and tables. It’s an ideal venue for getting stuff done, which always happens, and why this is the 15th of them.

Meanwhile, let’s get in touch with each other and start making it happen.

Let’s fix the car rental business

Lately Ron Lieber (@ronlieber), the Your Money editor and columnist for the New York Times, has been posting pieces that expose a dysfunction in the car rental marketplace — one that is punishing innovators that take the sides of customers. The story is still unfolding, which gives us the opportunity to visit and think through some VRM approaches to the problem.

Ron’s first piece is a column titled “A Rate Sleuth Making Rental Car Companies Squirm,” on February 17, and his second is a follow-up column, “Swatting Down Start-Ups That Help Consumers,” on April 6. Both stories are about , a start-up that constantly researches and re-books car rentals for you, until you get the lowest possible price from one of them. That company wins the business, at a maximized discount. The others all lose. This is good for the customer, if all the customer cares about is price. It’s bad for the agencies, since the winner is the one that makes the least amount of money on the rental.

In the second piece, Ron explains,

The customer paid nothing for the service, and AutoSlash got a commission from Travelocity, whose booking engine it rented. This was so delightful that it felt as if it might not last, and I raised the possibility that participating companies like Hertz and Dollar Thrifty would bail out, as Enterprise and the company that owns Avis and Budget already had. I encouraged readers to patronize the participants in the meantime to reward them for playing along. Well, they’ve stopped playing. In the last couple of weeks, Hertz and the company that owns both Dollar and Thrifty have turned their backs on AutoSlash — and for good reason, according to Hertz: AutoSlash seems to have been using discount codes that its customers were not technically eligible for.

On its site, AutoSlash put things this way (at that last link):

We’re disappointed that these companies have now chosen to reverse course and adopt this anti-consumer position, after having participated in this site since its launch in mid-2010. Apparently, with more customers booking reservations through our service, they felt they could no longer support our consumer-friendly model of automatically finding the best discount codes and re-booking when rates drop. AutoSlash will not waver in our objective to help people get a great deal on their rentals. We have exciting product plans on the horizon to make our site even more useful to you..

On the same day as his second column, Ron ran a blog post titled “AutoSlash, AwardWallet, MileWise and the Travel Bullies,” in which he points to airlines as another business with the same problems — and the same negative responses to rate-sleuths:

American Airlines and Southwest Airlines have made it clear that they do not want any third party Web site taking customers’ AAdvantage or Rapid Rewards frequent flier balances and putting them on a different site where people can view them alongside those from other loyalty programs. This comes at a loss of convenience to customers, and the airlines make all sorts of specious arguments about why this is necessary. Meanwhile, sites like  and  are less useful than they would be otherwise without a full lineup of airline account information available. But there’s a the bigger question here: Why can’t the big travel players simply fix their archaic business models and add these nifty features to their Web sites and stop spending energy ganging up on start-ups who unmask their flaws?

The answer comes from , of Dilbert fame. By Scott’s definition, the big travel players are a “confusopoly.” They see what Ron calls a “flaw” — burying the customer in a snowstorm of discounts intended both to entice and to confuse — as a feature, rather than a bug. Here’s Scott:

A confusopoly is any group of companies in a particular industry that intentionally confuses customers about their pricing plans and products. Confusopolies do this so customers don’t know which one of them is offering the best value. That way every company gets a fair share of the confused customers and the industry doesn’t need to compete on price. The classic examples of confusopolies are phone companies, insurance companies, and banks.

Car rental agencies are clearly confusopolies. So are airlines. Dave Barry explains how it is that no two passengers on one airplane pay the same price for a seat:

Q. So the airlines use these cost factors to calculate a rational price for my ticket?
A. No. That is determined by Rudy the Fare Chicken, who decides the price of each ticket individually by pecking on a computer keyboard sprinkled with corn. If an airline agent tells you that they’re having “computer problems, ” this means that Rudy is sick, and technicians are trying to activate the backup system, Conrad the Fare Hamster.

There are a few exceptions. One is , which competes through relatively simple seat pricing and unconfusing policies (e.g. no seat assignments and “bags fly free”). But even Southwest plays confusing games. For example, I just went to Southwest to make sure the URL was right (it used to be iflyswa.com, as I recall), and got intercepted by a promo offer, for a gift card. So, for research purposes, I filled it out. That got me to this page here:

Note that there is no place to take the last step. The “Your Info Below” space is blank. Everywhere I click, nothing happens. Fun. (Is it possible this isn’t from Southwest at all? Maybe somebody from Southwest can weigh in on that.)

So, a confusopoly.

What can we do? Governments fix monopolies by breaking them up. But confusopolies come pre-broken. That’s how they work. There is no collusion between Hertz and Budget, or between United and American. They are confusing on purpose, and independently so. No doubt they have their confusing systems fully rationalized, but that doesn’t make the confusion less real for the customer, or less purposeful for the company.

Let’s look a bit more closely at three problems endemic to the car rental business, and contribute to the confusopoly.

  1. Cars, like airlines and their seats, have become highly generic, and therefore commoditized. Even if there is a difference between a Chevy Cruze and a Ford Focus, the agencies mask it by saying what you’ll get is some model of some maker’s car, “or similar.” (I’ve always thought one of the car makers ought to just go ahead and make a car just for rentals, and brand it the “Similar.”)
  2. The non-price differentiators just aren’t different enough. For example, I noticed that Enterprise lately forces its workers to go out of their way to be extra-personal. They come out from behind the counter, shake your hand, call you by name, ask about your day, and so on. Which is all nice, but not nicer for most of us than a lower price than the next agency.
  3. The agencies’ CRM (Customer Relationship Management) systems don’t have enough to work with. While Enterprise is singled out here and here for having exceptional CRM, all these systems today operate entirely on the vendors’ side. Not on yours or mine. Each of is silo’d. How each of us relates to any one agency doesn’t work with the others. This is an inconvenience for us, but not for the agencies, at least as far as they know. And, outside their own silo’d systems, they can’t know much, except maybe through intelligence they buy from “big data” mills. But that data is also second-hand. No matter how “personalized” that data is, it’s about us, not directly by us or from us, by our own volition, and from systems we control.

A few years ago I began to see these problems as opportunities. I thought, Why not build new tools and systems for individual customers, so they can control their own relationships, in common and standard ways, with multiple vendors?  And, What will we call the result, once we have that control? My first answer to those questions came in a post for in March, 2006, titled The Intention Economy. Here are the money grafs from that one:

The Intention Economy grows around buyers, not sellers. It leverages the simple fact that buyers are the first source of money, and that they come ready-made. You don’t need advertising to make them. The Intention Economy is about markets, not marketing. You don’t need marketing to make Intention Markets. The Intention Economy is built around truly open markets, not a collection of silos. In The Intention Economy, customers don’t have to fly from silo to silo, like a bees from flower to flower, collecting deal info (and unavoidable hype) like so much pollen. In The Intention Economy, the buyer notifies the market of the intent to buy, and sellers compete for the buyer’s purchase. Simple as that. The Intention Economy is built around more than transactions. Conversations matter. So do relationships. So do reputation, authority and respect. Those virtues, however, are earned by sellers (as well as buyers) and not just “branded” by sellers on the minds of buyers like the symbols of ranchers burned on the hides of cattle.

The Intention Economy is about buyers finding sellers, not sellers finding (or “capturing”) buyers. In The Intention Economy, a car rental customer should be able to say to the car rental market, “I’ll be skiing in Park City from March 20-25. I want to rent a 4-wheel drive SUV. I belong to Avis Wizard, Budget FastBreak and Hertz 1 Club. I don’t want to pay up front for gas or get any insurance. What can any of you companies do for me?” — and have the sellers compete for the buyer’s business.

Thanks to work by the VRM (Vendor Relationship Management) development community, The Intention Economy is now a book, with the subtitle When Customers Take Charge, due out from Harvard Business Review Press on May 1. (You can pre-order it from Amazon, and might get it sooner that way.)

Having sellers compete for a buyer’s business (to serve his or her signaled intent) is what we now call a Personal RFP. (Scott Adams calls it “broadcast shopping.”) What it requires are two things that are now on their way. One is tools. The other is infrastructure. As a result of both, we will see emerge a new class of market participant: the . It’s a role AutoSlash can play, if it’s willing to play a new game rather than just gaming the old one.

The new game is serving as a real agent of customers, rather than just as a lead-generating system for third parties such as Travelocity, or a pest for second parties such as Hertz, Dollar and Thrifty. Fourth parties are businesses that side with customers rather than with vendors or third parties. Think of them as third parties that work for you and me. In this post, of (a VRM developer), represents the four parties graphically: Fourth parties can also serve as agents for improving actual relationships (rather than coercive ones). The two magnets are “r-buttons” (explained most recently here), which represent the buyer and the seller, and (as magnets) depict both attraction and openness to relationship. They are simple symbols one can also type, like this:  ⊂ ⊃. (The ⊂ represents you, or the buy side, while the ⊃ represents vendors and their allied third parties, or the sell side.) Here is another way of laying these out, with some names that have already come up: 4 parties As of today AutoSlash presents itself as an agent of the customer, but business-wise it’s an accessory to a third party, Travelocity. While Travelocity could be a fourth party as well, it is still too tied into the selling systems of the car rental agencies to make the move. (If I’m wrong, tell me how.) Now, what if AutoSlash were to join a growing young ecosystem of VRM companies and projects working on the customer’s side? Here is roughly how that looks today: AutoSlash is over there on the right, on the sell side. On the buy side, in the fourth party quadrant, are , , , MyDex, and . All provide ways for individuals to manage their own data, and (actually in some cases, potentially in others) relationships with second and third parties, on behalf of the customer. If you look at just the right two quadrants, on the ⊃ side, the car rental agencies fired AutoSlash for breaking their system. That’s one more reason for AutoSlash to come over to the ⊂ side and start operating unambiguously as a pure fourth party.

I believe that’s what already does. While their service is superficially similar to AutoSlash’s (they book you the lowest prices), they clearly work for you (⊂) as a fourth party and not for the agencies (⊃) as a third party. What makes them unambiguously a fourth party is the fact that you pay them. Here are their rates.

For controlling multiple relationships, however, you still need tools other than straightforward one-category services (such as AutoSlash and RentalCarMagic). One circle around those tools is what KuppingerCole calls Life Management Platforms. Another, from Peter Vander Auwera of SWIFT is The Programmable Me These (among much more) will be the subject of sessions at the European Identity and Cloud Conference (EIC) this week in Munich. (I’ll be flying there shortly from Boston.) I’ll be participating in those. So will Phil Windley of Kynetx, who has detailed a concept called the “Personal Event Network,” aka the “Personal Cloud.” Links, in chronological order:

  1. Ways, Not Places
  2. Protocols and Metaprotocols: What is a Personal Event Network?
  3. KRL, Data and Personal Clouds
  4. Personal Clouds as General Purpose Computers
  5. Personal Clouds Need a Cloud Operating System
  6. The Foundational Role of Identity in Personal Clouds
  7. Data Abstractions for Richer Cloud Experiences
  8. A Programming Model for Personal Clouds
  9. Federating Personal Clouds

This is thinking-in-progress about work-in-progress, by a Ph.D. computer scientist and college professor as well as an entrepreneur and a very creative inventor. (By the way, KRL and its rules engine are open source. That’s cool too.)

If I have time later I’ll unpack some of this, and start knitting the connections between what Phil’s talking about and what others (especially Martin Kuppinger of KuppingerCole, who will be writing and posting more about Life Management Platforms) are also bringing to the table here.

In particular I will bring up the challenge of fixing the car rental agency market. What can we do, not only for the customer and for his or her fourth parties (the ⊂ side) but for everybody on the third and second party (⊃) side?

And what changes will have to take place on the ⊃ side once they find they need to truly differentiate, in distinctive and non-gimmicky ways? What effect will that have on the car makers as well?

When I started down this path, back in 2006, I had a long conversation with a top executive at one of the car rental companies. What sticks with me is that these guys don’t have it easy. Among other things, he told me that the car companies mostly don’t like the car rental business because it turns drivers off to many of the cars they rent, and the car companies don’t make much money on the cars either. Can that be fixed too? I don’t know, but I’d like customers and their fourth parties to help.

How about through true personalization, in response to actual demand by individual customers, such as I suggested in 2006?

How about through new infrastructural approaches, such as the ?

Hertz, Budget’s and Enterprise’s own CRM and loyalty systems are not going to go away. Nor will the ways they all have of identifying us, and authenticating us. How can we embrace those, even as we work to obsolete them?

There are two worlds overlapping here: the one we have, and the one we’re building that will transcend and subsume the one we have.

The one we have is a “free market” with a “your choice of captor” model. It is for violating this model that AutoSlash was fired as a third party by the car rental agencies.

The one we’re building is a truly free market, in which free customers prove more valuable than captive ones. We need to make the pudding that proves that principle.

And we’re doing that. But it’s not a simple, an easy, or even a coordinated process. The good thing is, it’s already underway, and has been for some time.

Looking forward to seeing you at EIC in Munich, and/or at the other events that follow, in London and Mountain View:

Meanwhile, a last word, in respect to what Bart Stevens says below. Clearly the car rental business needs to move out of the confusopoly model, and to differentiate on more than price. To some degree they already do, but price is the primary driver for most customers. (And I’d welcome correction on that, if it’s wrong.) We have a lot to learn from each other.

Your actual wallet vs./+ Google’s and Apple’s

Now comes news that Apple has been granted a patent for the iWallet. Here’s one image among many at that last link:

iwallet

Note the use of the term “rules.” Keep that word in mind. It is a Good Word.

Now look at this diagram from Phil Windley‘s Event Channels post:

event channels

Another term for personal event network is personal cloud. Phil visits this in An Operating System for Your Personal Cloud, where he says, “In contrast a personal event network is like an OS for your personal cloud. You can install apps to customize it for your purpose, it canstore and manage your personal data, and it provides generalized services through APIsthat any app can take advantage of.” One of Phil’s inventions is the Kinetic Rules Language, or KRL, and the rules engine for executing those rules, in real time. Both are open source. Using KRL you (or a programmer working for you, perhaps at a fourth party working on your behalf, can write the logic for connecting many different kinds of events on the Live Web, as Phil describes here).

What matters here is that you write your own rules. It’s your life, your relationships and your data. Yes, there are many relationships, but you’re in charge of your own stuff, and your own ends of those relationships. And you operate as  free, independent and sovereign human being. Not as a “user” inside a walled garden, where the closest thing you can get to a free market is “your choice of captor.”

Underneath your personal cloud is your personal data store (MyDex, et. al.), service (Higgins), locker (Locker Project / Singly), or vault (Personal.com). Doesn’t matter what you call it, as long as it’s yours, and you can move the data from one of these things into another, if you like, compliant with the principles Joe Andrieu lays out in his posts on data portability, transparency, self-hosting and service endpoint portability.

Into that personal cloud you should also be able to pull in, say, fitness data from Digifit and social data from any number of services, as Singly demonstrates in its App Gallery. One of those is Excessive Mapper, which pulls together checkins with Foursquare, Facebook and Twitter. I only check in with Foursquare, which gives me this (for the U.S. at least):

Excessive Mapper

The thing is, your personal cloud should be yours, not somebody else’s. It should contain your data assets. The valuable nature of personal data is what got the World Economic Forum to consider personal data an asset class of its own. To help manage this asset class (which has enormous use value, and not just sale value), a number of us (listed by Tony Fish in his post on the matter) spec’d out the Digital Asset Grid, or DAG…

DAG

… which was developed with Peter Vander Auwera and other good folks at SWIFT (and continues to evolve).

There are more pieces than that, but I want to bring this back around to where your wallet lives, in your purse or your back pocket.

Wallets are personal. They are yours. They are not Apple’s or Google’s or Microsoft’s, or any other company’s, although they contain rectangles representing relationships with various companies and organizations:

Still, the container you carry them in — your wallet — is yours. It isn’t somebody else’s.

But it’s clear, from Apple’s iWallet patent, that they want to own a thing called a wallet that lives in your phone. Does Google Wallet intend to be the same kind of thing? One might say yes, but it’s not yet clear. When Google Wallet appeared on the development horizon last May, I wrote Google Wallet and VRM. In August, when flames rose around “real names” and Google +, I wrote Circling Around Your Wallet, expanding on some of the same points.

What I still hope is that Google will want its wallet to be as open as Android, and to differentiate their wallet from Apple’s through simple openness.  But, as Dave Winer said a few days ago

Big tech companies don’t trust users, small tech companies have no choice. This is why smaller companies, like Dropbox, tend to be forces against lock-in, and big tech companies try to lock users in.

Yet that wasn’t the idea behind Android, which is why I have a degree of hope for Google Wallet. I don’t know enough yet about Apple’s iWallet; but I think it’s a safe bet that Apple’s context will be calf-cow, the architecture I wrote about here and here. (In that architecture, you’re the calf, and Apple’s the cow.) Could also be that you will have multiple wallets and a way to unify them. In fact, that’s probably the way to bet.

So, in the meantime, we should continue working on writing our own rules for our own digital assets, building constructive infrastructure that will prove out in ways that require the digital wallet-makers to adapt rather than to control.

I also invite VRM and VRooMy developers to feed me other pieces that fit in the digital assets picture, and I’ll add them to this post.

How about using the ‘No Track’ button we already have?

left r-buttonright r-buttonFor as long as we’ve had economies, demand and supply have been attracted to each other like a pair of magnets. Ideally, they should match up evenly and produce good outcomes. But sometimes one side comes to dominate the other, with bad effects along with good ones. Such has been the case on the Web ever since it went commercial with the invention of the cookie in 1995, resulting in a calf-cow model in which the demand side — that’s you and me — plays the submissive role of mere “users,” who pretty much have to put up with whatever rules websites set on the supply side.

Consistent with Lord Acton’s axiom (“Power corrupts; absolute power corrupts absolutely”) the near absolute power of website cows over user calves has resulted in near-absolute corruption of website ethics in respect to personal privacy.

This has been a subject of productive obsession by Julia Anguin and her team of reporters at The Wall Street Journal, which have been producing the What They Know series (shortcut: http://wsj.com/wtk) since July 30, 2010, when Julia by-lined The Web’s New Gold Mine: Your Secrets. The next day I called that piece a turning point. And I still believe that.

Today came another one, again in the Journal, in Julia’s latest, titled Web Firms to Adopt ‘No Track’ Button. She begins,

A coalition of Internet giants including Google Inc. has agreed to support a do-not-track button to be embedded in most Web browsers—a move that the industry had been resisting for more than a year.

The reversal is being announced as part of the White House’s call for Congress to pass a “privacy bill of rights,” that will give people greater control over the personal data collected about them.

The long White House press release headline reads,

We Can’t Wait: Obama Administration Unveils Blueprint for a “Privacy Bill of Rights” to Protect Consumers Online

Internet Advertising Networks Announces Commitment to “Do-Not-Track” Technology to Allow Consumers to Control Online Tracking

Obviously, government and industry have been working together on this one. Which is good, as far as it goes. Toward that point, Julia adds,

The new do-not-track button isn’t going to stop all Web tracking. The companies have agreed to stop using the data about people’s Web browsing habits to customize ads, and have agreed not to use the data for employment, credit, health-care or insurance purposes. But the data can still be used for some purposes such as “market research” and “product development” and can still be obtained by law enforcement officers.

The do-not-track button also wouldn’t block companies such as Facebook Inc. from tracking their members through “Like” buttons and other functions.

“It’s a good start,” said Christopher Calabrese, legislative counsel at the American Civil Liberties Union. “But we want you to be able to not be tracked at all if you so choose.”

In the New York Times’ White House, Consumers in Mind, Offers Online Privacy Guidelines Edward Wyatt writes,

The framework for a new privacy code moves electronic commerce closer to a one-click, one-touch process by which users can tell Internet companies whether they want their online activity tracked.

Much remains to be done before consumers can click on a button in their Web browser to set their privacy standards. Congress will probably have to write legislation governing the collection and use of personal data, officials said, something that is unlikely to occur this year. And the companies that make browsers — Google, Microsoft, Apple and others — will have to agree to the new standards.

No they won’t. Buttons can be plug-ins to existing browsers. And work has already been done. VRM developers are on the case, and their ranks are growing. We have dozens of developers (at that last link) working on equipping both the demand and the supply side with tools for engaging as independent and respectful parties. In fact we already have a button that can say “Don’t track me,” plus much more — for both sides. Its calle the R-button, and it looks like this: ⊂ ⊃. (And yes, those symbols are real characters. Took a long time to find them, but they do exist.)

Yours — the user’s — is on the left. The website’s is on the right. On a browser it might look like this:

r-button in a browser

Underneath both those buttons can go many things, including preferences, policies, terms, offers, or anything else — on both sides. One of those terms can be “do not track me.” It might point to a fourth party (see explanations here and here) which, on behalf of the user or customer, maintains settings that control sharing of personal data, including the conditions that must be met. A number of development projects and companies are already on this case. All the above falls into a category we call EmanciTerm. Much has been happening as well around personal data stores (PDSes), also called “lockers,” “services” and “vaults.” These include:

Three of those are in the U.S., one in Austria, one in France, one in South Africa, and three in the U.K. (All helping drive the Midata project by the U.K. government, by the way.) And those are just companies with PDSes. There are many others working on allied technologies, standards, protocols and much more. They’re all just flying below media radar because media like to look at what big suppliers and governments are doing. Speaking of which… 🙂

Here’s Julia again:

Google is expected to enable do-not-track in its Chrome Web browser by the end of this year.

Susan Wojcicki, senior vice president of advertising at Google, said the company is pleased to join “a broad industry agreement to respect the ‘Do Not Track’ header in a consistent and meaningful way that offers users choice and clearly explained browser controls.”

White House Deputy Chief Technology Officer Daniel Weitzner said the do-not-track option should clear up confusion among consumers who “think they are expressing a preference and it ends up, for a set of technical reasons, that they are not.”

Some critics said the industry’s move could throw a wrench in a separate year-long effort by the World Wide Web consortium to set an international standard for do-not-track. But Mr. Ingis said he hopes the consortium could “build off of” the industry’s approach.

So here’s an invitation to the White House, Google, the 3wC, interested BigCos (including CRM companies), developers of all sizes and journalists who are interested in building out genuine and cooperative relationships between demand and supply::::

Join us at IIW — the Internet Identity Workshop — in Mountain View, May 1-3. This is the unconference where developers and other helpful parties gather to talk things over and move development forward. No speakers, no panels, no BS. Just good conversation and productive work. It’s our fourteenth one, and they’ve all been highly productive.

As for the r-button, take it and run with it. It’s there for the development. It’s meaningful. We’re past square one. We’d love to have all the participation we can get, from the big guys as well as the little ones listed above and here.

To help get your thinking started, visit this presentation of one r-button scenario, by Adam Marcus of MIT. Here’s another view of the same work, which came of of a Google Summer of Code project through ProjectVRM and the Berkman Center:

(Props to Oshani Seneviratne and David Karger, also both of MIT, and Ahmad Bakhiet, of Kings College London, for work on that project.)

If we leave fixing the calf-cow problem entirely up to the BigCos and BigGov, it won’t get fixed. We have to work from the demand side as well. In economies, customers are the 100%.

Here are some other stories, mostly gathered by Zemanta:

All look at the symptoms, and supply-side cures. Time for the demand side to demand answers from itself. Fortunately, we’ve been listening, and the answers are coming.

Oh, and by the way, Mozilla has been offering “do not track” for a long time. Other tools are also available:

Toward a new symbiosis between Demand and Supply

I’m listening and watching with fascination to Keith Scovell‘s Shopper Power videos. In these Keith describes progress being made in a VRM direction by retailers and their upstream suppliers, detailing efforts made by Starbucks, Hallmark, CVS, Tesco/Homeplus, Frito-Lay, Reese’s and other companies — all recognizing that customers’ range of control over interactions in retail environments is increasing dramatically, and will increase a great deal more.

I haven’t watched all of Keith’s videos yet, but I’m taking notes as I do, and I recommend that others do the same, if they’re interested in how increasingly empowered and independent customers relate to vendors — especially at the retail level in the brick & mortar world. And how clueful vendors are working on better ways of interacting with those customers.

It’s interesting that Keith is coming from the CPG — Consumer Packaged Goods — industry, and not CRM, which is most commonly posed as the counterpart to VRM. Yet I think that CPG, and retailing in general, is the more direct counterpart of VRM. Talking about where the rubber meets the road here. Keith talks about market signals, which go in both directions. One purpose of VRM is to provide better means for signaling, as well as for engaging over the longer term.

Four things are important to point out as developers on both sides get acquainted:

  1. Customers will become more independent. That is, they will have their own ways of expressing demand, loyalty, brand preferences and terms of engagement. Many of today’s solutions on the vendors’ side — loyalty cards, for example — are both coercive and inconvenient, as customers are required to carry around many of these things, all with their own proprietary and silo’d systems. New tools and systems will emerge on the customer’s side to provide both independence and better means of engagement. And those tools and systems will be personal, not just social.
  2. VRM tools will not only provide or support that independence, but common means for engaging many vendors the same way. For example, they will provide ways for a customer to change his or her address one time for many vendors rather than many times for many vendors.
  3. The new market ecosystem will be symbiotic one between demand and supply. Not a coercive or competitive one. That means the best customers and the best vendors will be caring about each other and watching out for each others’ best interests. This will actually reduce need on the vendors’ side for discounts, coupons and other gimmicks, which often clutter and confuse an otherwise smooth relationship with customers, and which have other hard costs as well.
  4. New user interface elements will be required.

For that last two reasons I’ve flanked the text above between two r-buttons. Keith visits QR codes and other handy signaling devices already being used in the retail environment. But it’s still early, so we still lack are user interface (UI) elements that represent actions and states within relationships between buyers and sellers. As work in the VRM development community goes on the demand side moves toward work Keith and others are doing on the supply side, the two magnets will place a new force field over the marketplace: one that brings mutual interests into alignment, even as competition and other familiar market interactions continue as they always have.

Prototyping a new business model for everything

For IIW next week, and I have been working on a prototype demonstrating , using on the  app from .  The description at the EmanciPay link is minimal so far, but the model has a great deal of promise, because what it puts forward is a new business model for all kinds of stuff: easy voluntary payments from anybody for anything, to escrow accounts where the money can be picked up by the intended recipient with no strings attached. The first target is public radio (as it has been, ever since the earliest ProjectVRM meetings at the ), but it could easily apply to and other media as well.

We still need financial institutions to weigh in and take up a new business model for themselves, and it would be cool if some of them showed up at IIW next week for that, but in any case we’re taking one small step in the direction of a major sea change in the way markets for media work.

I’ve been making test contributions to different public radio stations, using the EmanciPay prototype. Craig has hacked a way for this to show up in my Twitter stream. You can see those here.

IIW dev job: ListenLog

Craig Burton has a nice tutorial on developing VRM applications, using ListenLog as both an example and a challenge for next week at IIW.

ListenLog is the brainchild of Keith Hopper and the collaborative result of efforts by folks from NPR, PRX and other public radio institutions, as well as the Berkman Center and volunteers from the VRM community. It’s a form of self-tracking (see The Quantified Self for more on what that’s about), and also part of a larger effort that includes EmanciPay.

You’ll already find it on the Public Radio Player for iPhone, which is free and a great app. If you’re using an iPhone, download it, then go (as the tutorial says) to the settings and turn on logging. What you’ll have is your own growing pile of personal data, that you control. (No, it’s not yet in your all-purpose personal data store, locker or vault, but that’s another step and we can talk about that too. It is, for sure, in your Personal Data Ecosystem.)

Here’s where the tutorial pauses, for now:

to be done

One of our jobs next week is fulfilling those needs. This is light-duty hacking of the sort we can do around a table in one afternoon. (For those of us who can hack. Alas, the only code I know is Morse.)

Here’s where moving forward on this will lead:

  1. Better knowledge for listeners about what they actually value.
  2. Necessary groundwork for EmanciPay, which is a new listener-driven business model for public radio — and for everything else thats available for free but worth more than that.
  3. More money for public radio (because the old models won’t go away).
  4. More money for every business that produces free goods that are worth more than that. (For example music, newspapers, magazines, blogs and so on.)
  5. Experience and modeling for other similar projects.

Should be fun work.

Bonus thought: This might also work as something that ties in with the Knight-Mozilla News Innovation Challenge. (Keith will be there, I think.) Hey, let’s connect the two. Should be fun. Just tweeted this as well.

Knight News Challenge entry for EmanciPay

Below is a copy of our entry to the Knight News Challenge. It actually hadn’t crossed my mind to put one together until last Monday, when I saw that they have a category for sustainability. It says here,

Sustainability: Considers new economic models supporting news and information. New ways of conducting and consuming journalism may require new ways of paying for it. We’re open to ideas for generating revenue as well as ways to reduce costs.

EmanciPay is exactly that.

Three years ago, when ProjectVRM was new, we applied and made it to the second round. Back then EmanciPay was still called PayChoice. (We changed it because we wanted a better name with a URL we could buy, which we did.) Sustainability wasn’t front-burner for Knight then, I guess. Now it is. And, in the meantime, much VRM development has been going in the sustainability direction, including work behind the r-button (some context here). Special thanks for that goes to David Karger, Oshani Seneviratne and Adam Marcus of CSAIL at MIT,  our Google Summer of Code student, Ahmad Bakhiet of Kings College London and Renee Lloyd (a fellow veteran Berkman Center fellow) for their good work on that.

That work is built on code Adam and Oshani had already done on Tipsy, which has its own Knight News Challenge entry as well. (This is all open source stuff, so it can be leveraged many ways.) I met Adam and Oshani through David Karger, who I met through Keith Hopper of NPR, a stalwart contributor to the VRM community from the beginning. Keith is the brainfather of ListenLog, an application you’ll find in your Public Radio Player, from PRX, which is run by Jake Shaprio (another Berkman vet, and a star with the band Two Ton Shoe). When I ran the idea of applying again past Jake (who has an exceptional track record at winning these kinds of things), he said “Go for it,” so we did.

Another VRM effort in the Knight News Challenge  is Tom StitesBanyan Project. Tom has forgotten more about journalism, and its business, than most of us will ever know, and has been hard at work on Banyan for the last several years, rounding up good people and good ideas into one coherent system that could use support. Here’s the Banyan application to the News Challenge. It seems not to appear on the roster at the KNC site right now. I’m told that’s just a glitch. So check it out at that last link in the meantime.

Meanwhile, here are the parts of the EmanciPay entry that matter:

Project Title:

EmanciPay:
a user-driven system for generating revenue and managing relationships
Requested amount from Knight News Challenge:

$325,000

Describe your project:

EmanciPay is the first user-driven revenue model for news and information media. With EmanciPay, users can easily pay whatever they like, whenever they like, however they like — on their own terms and not just those controlled by the media’s supply side.

EmanciPay will also provide means for building genuine two-way relationships between the consumers and producers of media, rather than the confined relationships defined by each organization’s default subscription and membership systems .

EmanciPay is among a number of VRM (Vendor Relationship Management) tools that have been in development for the last several years, with guidance from ProjectVRM, which is led by Doc Searls at Harvard’s Berkman Center for Internet & Society. Here is a list of VRM development projects.

Starting early this year, Doc and other members of the VRM community have been working on EmanciPay with developers at MIT/CSAIL and Kings College London. The MIT/CSAIL collaboration is led by David Karger and ties in with work he and others are doing with Haystack. This work includes developing a UI called r-button for offering payment and for creating and managing relationships between users and producers.

The r-button is the first Web UI element that allows a site to signal openness to the user’s own terms of engagement. Toward this end work has also begun on terms-matching, which will allow engagement to go forward without the user being forced to “accept” terms on a site’s take-it-or-leave-it basis — thus eliminating a major source of friction in the marketplace. (Note: These one sided agreements are increasingly coming under fire by courts and regulators, thus creating a higher risk profile for organizations using them. EmanciPay seeks to lower or eliminate that risk altogether.)

As with Creative Commons, terms will be expressed in text and symbols that can be read easily by both software and people.

While there is no limit to payment choice options with EmanciPay, we plan to test these one at a time. The first planned trials are with Tipsy, which is itself the subject of another Knight News Challenge application, here. (Note: EmanciPay is not a micropayments system. It is a way for users to choose whatever amounts and methods of payment they like, whenever they like, with maximum ease.)

ProjectVRM has also been working with PRX and other members of the public radio community on ListenLog (the brainchild of Keith Hopper at NPR), which can currently be found on the Public Radio Player, an iPhone app that has been downloaded more than 2 million times, so far.

Other VRM development efforts, on identity and trust frameworks, and personal data stores (PDSes), will also be brought in to help with EmanciPay.

The plan now is to step up code development, get the code working in the world, test it, improve it, work with media and their CRM suppliers, and drive it to ubiquity.

How will your project improve the delivery of news and information to geographic communities?:

Two ways.

The first is with a new business model. Incumbent local and regional media currently have three business models: paid delivery (subscriptions and newsstand sales), advertising, and (in the case of noncommercial media) appeals for support. All of these have well-known problems and limitations. They are also controlled in a top-down way by the media organization, and cannot be managed from the user’s side, using tools native to the user. Thus they lack insight into what buyers really want. Accordingly, what we propose is a new supplementary system that makes it as easy as possible for anybody to pay anything for whatever they like, whenever they like, without going through the friction of becoming a “member” or otherwise coping with existing payment systems.

The second is a system for creating and sustaining relationships between the consumers and producers of news and information. EmanciPay is one among a larger box of VRM (vendor relationship management) tools by which individual consumers of news can also participate in the news development process. These tools are based on open source code and open standards, so they can be widely adopted and adapted to meet local needs.

CRM software companies, many of which supply CRM (customer relationship management) systems to media organizations, are also awaiting VRM developments. (The cover and much of a recent CRM Magazine were devoted to VRM.)

What unmet need does your proposal answer?:

EmanciPay meets need for maximum freedom and flexibility in paying for news and information, and for a media business model that does not depend only on advertising or the frictions of subscriptions and membership systems.

Right now most news and information is already free of charge on the Web, whether or not it costs money to subscribe or to buy those goods on newsstands. Meanwhile, paying for those goods voluntarily today ranges from difficult to impossible. Even the membership systems of public broadcasting exclude vast numbers of people who would contribute “if it was easy”.

EmanciPay will make it easy for consumers of news to become customers of news. It will allow customers to pay for what they want, when they want, in ways they want, and to initiate actual relationships with the news organizations they pay — on users’ own terms as well as those of news organizations.

How is your idea new?:

Equipping individuals with their own digital tools for exerting and controlling their means of engagement with suppliers is a new idea. So is basing those tools on open source and open standards.

There have also been no tools for expressing terms of engagement that match up with — and reform — those of sellers, rather than just submitting to what are known in law as contracts of adhesion: ones in which the dominant party is free to change what they please while the submissive party is nailed to whatever the dominant party dictates. Contracts of adhesion have been pro forma on the Web since the invention of the cookie in 1995, and EmanciPay is the first system developed to replace them. This system is entirely new, and is being developed by legal experts on the ProjectVRM team, aided by friends at Harvard Law School and other interested institutions. Once in place, its implications and reformations are likely to exceed even those of Creative Commons, because they address the demand as well as the supply side of the marketplace — and (like Creative Commons) do not require changes in standing law.

EmanciPay is also new in the sense that it is distributed, and does not require an intermediary. As with email (the protocols of which are open and distributed, by design), EmanciPay supports any number of intermediary services and businesses providing services to assist it.

What will you have changed by the end of the project?:

First, we will have changed the habits and methods by which people pay for the media goods they receive, starting with news and information.

Second, we will have established a new legal framework for agreements between buyers and sellers on the Web and in the networked world.

Third, we will have introduced to the world an intention economy, based on the actual intentions of buyers, rather than on guesswork by sellers about what customers might buy. (The latter is the familiar “attention economy” of advertising and promotion.)

Fourth, we will have introduced relationship systems that are not controlled by sellers, but instead are controlled and driven by the individuals who are each at the centers of their own relationships with many different entities. Thus relationships will be user-driven and not just organization-driven.

What terms best describe your project?:

Bold, original, practical, innovative and likely to succeed.

(I left out stuff where I was asked to flatter myself. Not my style; but hey, they made me do it.)

So far the place has 207 views and 20 ratings. It would help us if you could view it too, and rate it kindly. Recommendations going forward are welcome too.

And do the same for Tipsy and Banyan.

« Older posts

© 2023 ProjectVRM

Theme by Anders NorenUp ↑