Category: open source (Page 4 of 4)

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.

VRM as Agency

Most of us understand agency to mean a kind of company: one that represents other companies, or individuals. Insurance, real estate and advertising agencies come to mind.

In fact agency has a deeper and more important meaning. Namely, the capacity of individuals to act independently, to make choices, and to impose their will in the world. By this meaning, agency is a big deal in sociology, psychology, philosophy, law and many other fields. But it’s missing is business. That’s because we’re accustomed to understanding business as a structural thing:  an instrument of control.

Wikipedia frames this problem well in the opening paragraph of its Structure vs. Agency Debate article:

The debate concerning the primacy of either structure or agency on human behaviour is a central ontological issue in sociology, political science, and the other social sciences. In this context, “agency” refers to the capacity of individuals to act independently and to make their own free choices.[1]Structure“, by contrast, refers to the recurrent patterned arrangements which seem to influence or limit the choices and opportunities that individuals possess.[2] The structure versus agency debate may therefore be understood simply as the issue of socialisation against autonomy.

Limiting individual choices through “patterned arrangements” has been an ideal of big business for a very long time. Choice is an ideal too, provided your product or service provides a choice for customers to not choose competing products or services. Agency-type choice, in which individuals are free to assert their will and their means, doesn’t get much respect.

In fact, most big businesses aren’t interested in customers that have lots of agency — unless those customers aren’t captured yet. Instead big business has long idealized controlling customers. That’s why they talk about “capturing,” “acquiring,” “managing,” “locking in” and “owning” them. And spend billions on systems that help them do that.

These controlling ideals are still with us in the era of “social networking” and “social media.” (Or what one friend calls SEFTTI, for “social every fucking thing there is.”) Sure, Facebook is as social as a kegger (or more so), but it is also a “patterned arrangement that seems to influence or limit the choices and opportunities that individuals possess.”

Personal autonomy on Facebook only goes as far as Facebook lets it go. Same with every other “social” system run by an entity other than yourself. They put a lid on your agency. You are not free.

I’m not saying there’s anything wrong with social systems, or structures, or even with businesses that want to control your choices. I am saying that agency has been AWOL from the market’s table. And bringing it there is what we’re doing with VRM.

I realized that VRM is about agency when I was talking with Iain Henderson the other day. Iain and his company MyDex have been working on creating and deploying personal data stores, or PDSes. These are the means by which individuals manage and  share personal data selectively. In that conversation Iain casually mentioned that the U.K. government was clearly invested in “user agency.” That is, in citizen responsibility for data about themselves and generated by themselves. In this fundamental way, he said, the U.K. government is far ahead of our own here in the U.S. — and the U.K. is therefore a more ideal environment for testing out VRM tools, such as the personal data store. (In fact MyDex’s prototype trials are going on right now, in three U.K. towns.)

What we’ll have, as VRM tools roll out and come into use, is many ways to test concepts such as methodological individualism and action theory. Mostly, however, I think it’s a way to see how much larger, and better, we can make the economy once individual customers are free to express their intentions.

Bonus link — which I put here hoping that somebody can fix it. Since it’s about me and some stuff I’ve said, I’m not the one to do that.

Awake at the wheels

A year ago, at VRooM Boston 2009, , founder and CTO of Zeo — the hot new sleep fitness company — visited questions  about who owns and controlled personal data. Was the sleep data you produce as a customer entirely Zeo’s? Was it yours? Both? Neither? What right should anybody have to use it, and under what conditions?

These kinds of questions aren’t easily answered at a time when mining and selling personal data has turned into a white-hot industry, whether people like it or not. Data about individuals is also easy to rationalize as a corporate asset: something that makes the company itself more valuable.

Since then answers have begun to sort themselves out.

First came Brian, the Cornell student who writes, “I hacked Zeo. And I got paid for it.” Specifically,

I opened Zeo up, soldered to the lines that drive the display, and got my sleep phase output to my PC in real-time! This generated substantial interest from Zeo – and Ben Rubin (Zeo CTO) and I began our discussion on hacking, open source, and Zeo. I was thrilled when I learned that part of my summer would be interning for Zeo creating official ways to get at Zeo data!

Then this month Ben wrote,

Remember everyone’s favorite Zeo-hacker-turned-intern, Brian?

This summer, Brian produced two amazing projects for Zeo: the first – the Zeo Data Decoder – allows you to get at your sleep data without uploading it. The second (the main course, if you will) is the Zeo Raw Data Library.

Use Your Brain

The Zeo Raw Data Library uses the serial port on the back of Zeo (you were wondering about that unused port, weren’t you) to pump out two very cool things:

  • Your sleep phase in real time (Wake, REM, Light, Deep every 30 seconds)
  • Your brainwaves!

We hope developers will use the Raw Data Library for cool applications.  Need some ideas?

  • Build a lucid dreaming application that triggers a light or sound when a user enters REM sleep.
  • Wake yourself during REM in the middle of the night and keep a sweet sleep journal.
  • Use brainwaves for cool Brain Computer Interface projects while you are awake.  For inspiration check out interAxon.
  • Visualize your brainwaves while awake for bio-feedback applications like concentration or relaxation.

How do I get my hands on it?!?

Calm down and step away from the brainwave detector…

You can get the documentation, the library to read the RDL, and an example sleep stage and brainwave visualizer over on sourceforge.  Yup; we decided to open source all of that stuff, so feel free to hack/modify to your needs (and share if you like!).  The special firmware (2.6.3R) needed to run the RDL is over here after you fill out a simple form.

We encourage people who are using the RDL to jump on the forums and discuss it.  People are already using the RDL to optimize polyphasic sleep naps and help them lucid dream with Zeo.  Please use the forums for support and also feel free to email us at DeveloperRelations@myZeo.com.  We’ll also do our best to help troubleshoot, but remember that this is an alpha release so there may be bugs.

The Future is Open Wide

We released the Zeo Raw Data Library because

  • It’s your data–we want you to be free to use it any way you like
  • We are really excited to see what people develop that ends up helping others get a better night’s rest

Please let us know what you think in the comments on on the forums.  Hack away!

I just had to post that whole passage because it’s so completely cool.

Next is combinatorial API fun. From Ben’s latest, All Together Now: Zeo Integrates with Digifit,

Where Sleep Quality meets Fitness and Weight

Zeo is proud to announce the first partner using ZQ outside of our own web application:  The Digifit Dashboard for Healthy LivingSM iPhone app.  Digifit is the only Healthcare and Fitness app for the iPhone that integrates heart rate monitoring for tracking cardio fitness. We’re pretty sure Columbus from Zombieland would be happy with this — his #1 Rule for a Zombified America is Cardio!

Now with the new Digifit Dashboard for Healthy Living SM ,users can also track their weight and sleep (using the Withings WiFi Body Scale and Zeo) and see them conveniently within the Digifit dashboard.  We think Digifit founder says it best:

Withings and Zeo are leading edge pioneers in the industry and we are thrilled to partner with them. With the latest upgrade, our Digifit app completes the health triad puzzle by ‘automagically’ tracking the three most important influences on one’s health: exercise, weight and sleep. We do indeed have it All Together Now.

This is close to home for me, because I’m just starting to get into serious fitness work, which started with my Withings scale. Gotta get a Zeo thing now. (Like the one above.) And Digifit.

Ben again:

This is Just the Beginning

Digifit is the first partner to leverage our soon-to-be-released Web API, which allows data from Zeo to flow out to any internet connected service that wants to leverage the power of sleep quality.  We’ll continue to partner with organizations working in athletics, nutrition, general health, and more to help their users leverage the power of sleep fully so stay tuned!

For more on API jazz, follow . I especially like his Prezi here. Gets you thinking about bi-directional or “full duplex” APIs. This tutorial shows how to do context automation with KRL webhooks and the API.

Do we have to “trade off” privacy?

Look up privacy trade-offs and you’ll get more than 150,000,000 results. The assumption in many of those is that privacy is something one can (and often should) trade away. Also that privacy trading is mostly done with marketers and advertisers, the most energetic of which take advantage of social media such as and .

I don’t think this has to be so.

One example of a trade-off story is this one on public radio’s Marketplace program, which I heard this evening. It begins with the case of Shea Sylvia, a FourSquare user who got creeped out by an unwelcome call from a follower who knew her location. Marketplace’s Sally Herships says,

There are millions of Sylvias out there, giving away their private information for social reasons. More and more, they’re also trading it in for financial benefits, like coupons and discounts. Social shopping websites like Blippy and Swipely let shoppers post about what they buy. But first they turn over the logins to their e-mail accounts or their credit card numbers, so their purchases can be tracked online.

Later, there’s this (the voice is Herships again):

Alessandro Acquisti researches the economics of privacy at Carnegie Mellon, and he says the value we put on privacy can easily shift. In other words, if giving away your credit card information or even your location in return for a discount or a deal seems normal, it must be OK.

ALESSANDRO ACQUISTI: Five years ago, if someone told you that there’d be lots of people going online to show, to share with strangers their credit card purchases, you probably would have been surprised, you probably would thought, “No, I can’t believe this. I wouldn’t have believed this.”

But Acquisti says, when new technologies are presented as the norm, people accept them that way. Like social shopping websites.

HERSHIPS: So the more we use sites like Blippy, the more we’ll use sites like Blippy?

ACQUISTI: Or Blippy 2.0.

Which Acquisti says will probably be even more invasive, because as time passes, we’re going to care less and less about privacy.

Back in Kansas City Shea Sylvia is feeling both better and worse. She thinks the phone call she got that night at the restaurant was probably a prank. But it was a wake up call.

What we’re dealing with here is an evanescent norm. A fashion. A craze. I’ve indulged in it myself with FourSquare, and at one point was the “mayor” of ten different places, including the #77 bus on Mass Ave in Cambridge. (In fact, I created that location.) Gradually I came to believe that it wasn’t worth the hassle of “checking in” all over the place, and was worth nothing to know Sally was at the airport, or Bill was teaching a class, or Mary was bored waiting in some check-out line, much as I might like all those people. The only time FourSquare came in handy was when a friend intercepted me on my way out of a stop in downtown Boston, and even then it felt strange.

The idea, I am sure, is that FourSquare comes to serve as a huge central clearing house for contacts between companies selling stuff and potential buyers (that’s you and me) wandering about the world. But is knowing that a near-infinite number of sellers can zero in on you at any time a Good Thing? And is the assumption that we’re out there buying stuff all the time not so wrong as to be insane?

Remember that we’re the product being sold to advertisers. The fact that our friends may be helping us out might be cool, but is that the ideal way to route our demand to supply? Or is it just one that’s fun at the moment but in the long term will produce a few hits but a lot of misses—some of which might be very personal, as was the case with Shea Silvia? (Of course I might be wrong about both assumptions. What I’m right about is that FourSquare’s business model will be based on what they get from sellers, not from you or me.)

The issue here isn’t how much our privacy is worth to the advertising mills of the world, or to intermediaries like FourSquare. It’s how we maintain and control our privacy, which is essentially priceless—even if millions of us give it away for trinkets or less. Privacy is deeply tied with who we are as human beings in the world. To be fully human is to be in control of one’s self, including the spaces we occupy.

An excellent summary of our current privacy challenge is this report by Joy L. Pitts (developed as part of health sciences policy development process at the Institute of Medicine, the health arm of the National Academy of Sciences). It sets context with these two quotes:

“The makers of the Constitution conferred the most comprehensive of rights and the right most valued by all civilized men—the right to be let alone.”

—Justice Louis Brandeis (1928)

“You already have zero privacy anyway. Get over it.”

—Scott McNealy, Chairman and CEO of Sun Microsystems (1999)

And, in the midst of a long, thoughtful and well-developed case, it says this (I’ve dropped the footnotes, which are many):

Privacy has deep historical roots. References to a private domain, the private or domestic sphere of family, as distinct from the public sphere, have existed since the days of ancient Greece.  Indeed, the English words “private” and “privacy” are derived from the Latin privatus, meaning “restricted to the use of a particular person; peculiar to oneself, one who holds no public office.” Systematic evaluations of the concept of privacy, however, are often said to have begun with the 1890 Samuel Warren and Louis Brandeis article, “The Right of Privacy,” in which the authors examined the law’s effectiveness in protecting privacy against the invasiveness of new technology and business practices (photography, other mechanical devices and newspaper enterprises). The authors, perhaps presciently, expressed concern that modern innovations had “invaded the sacred precincts of private and domestic life; and . . . threatened to make good the prediction that ‘what is whispered in the closet shall be proclaimed from the house-tops.’” They equated the right of privacy with “the right to be let alone” from these outside intrusions.

Since then, the scholarly literature prescribing ideal definitions of privacy has been “extensive and inconclusive.” While many different models of privacy have been developed, they generally incorporate concepts of:

  • Solitude (being alone)
  • Seclusion (having limited contact with others)
  • Anonymity (being in a group or in public, but not having one’s name or identity known to others; not being the subject of others’ attention)
  • Secrecy or reserve (information being withheld or inaccessible to others)

In essence, privacy has to do with having or being in one’s own space.

Some describe privacy as a state or sphere where others do not have access to a person, their information, or their identity. Others focus on the ability of an individual to control who may have access to or intrude on that sphere. Alan Westin, for example, considered by some to be the “father” of contemporary privacy thought, defines privacy as “the claim of individuals, groups or institutions to determine for themselves when, how and to what extent information about them is communicated to others.” Privacy can also be seen as encompassing an individual’s right to control the quality of information they share with others.

In the context of personal information, concepts of privacy are closely intertwined with those of confidentiality and security. Privacy addresses “the question of what personal information should be collected or stored at all for a given function.” In contrast, confidentiality addresses the issue of how personal data that has been collected for one approved purpose may be held and used by the organization that collected it, what other secondary or further uses may be made of it, and when the permission of the individual is required for such uses.Unauthorized or inadvertent disclosures of data are breaches of confidentiality. Informational security is the administrative and technological infrastructure that limits unauthorized access to information. When someone hacks into a computer system, there is a breach of security (and also potentially, a breach of confidentiality). In common parlance, the term privacy is often used to encompass all three of these concepts.

Take any one of these meanings, or understandings, and be assured that it is ignored or violated in practice by large parts of today’s online advertising business—for one simple reason (I got from long ago): Individuals have no independent status on the Web. Instead we have dependent status. Our relationships (and we have many) are all defined by the entities with which we choose to relate via the Web. All those dependencies are silo’d in the systems of sellers, schools, churches, government agencies, social media, associations, whatever. You name it. You have to deal with all of them separately, on their terms, and in their spaces. Those spaces are not your spaces. (Even if they’re in a place called . Isn’t it weird to have somebody else using the first person possessive pronoun for you? It will be interesting to see how retro that will seem after it goes out of fashion.)

What I’m saying here is that, on the Web, we do all our privacy-trading in contexts that are not out in the open marketplace, much less in our own private spaces (by any of the above definitions). They’re all in closed private spaces owned by the other party—where none of the rules, none of the terms of engagement, are yours. In other words, these places can’t be private, in the sense that you control them. You don’t. And in nearly all cases (at least here in the U.S.), your “agreements” with these silos are contracts of adhesion that you can’t break or change, but the other party can—and often does.

These contexts have been so normative, for so long, that we can hardly imagine anything else, even though we have that “else” out here in the physical world. We live and sleep and travel and get along in the physical world with a well-developed understanding of what’s mine, what’s yours, what’s ours, and what’s none of those. That’s because we have an equally well-developed understanding of bounded spaces. These differ by culture. In her wonderful book , Polly Platt writes about how French —comfortable distances from others—are smaller than those of Americans. The French feel more comfortable getting close, and bump into each other more in streets, while Americans tend to want more personal space, and spread out far more when they sit. Whether she’s right about that or not, we actually have personal spaces on Earth. We don’t on the Web, and in Web’d spaces provided by others. (The Net includes more than the Web, but let’s not get into that here. The Web is big enough.)

So one reason that privacy trading is so normative is that dependency requires it. We have to trade it, if that’s what the sites we use want, regardless of how they use whatever we trade away.

The only way we can get past this problem (and it is a very real one) is to create personal spaces on the Web. Ones that we own and control. Ones where we set the terms of engagement. Ones where we decide what’s private and what’s not.

In the VRM development community we have a number of different projects and companies working on exactly this challenge.  is pure open source and has a self-explanatory name. Others (, and others) are open in many ways as well, and are working together to create (or put to use) common code, standards, protocols, terminologies and other conventions on which all of us can build privacy-supporting solutions. You’ll find links to some of the people involved in those efforts (among others) in Personal Data Stores, Exchanges, and Applications, a new post by  (of Switchbook). There’s also the One example is the and at . (For more context on that, check out Iain Henderson’s unpacking of the .) There’s also our own work at ProjectVRM and , which has lately centered on developing -like legal tools for both individuals and companies.  What matters most here is that a bunch of good developers are working on creating spaces online that are as natural, human, personal—and under personal control—as the ones we enjoy offline.

Once we have those, the need for privacy trade-offs won’t end. But they will begin to make the same kind of down-to-Earth sense they do in the physical world. And that will be a huge leap forward.

Cooperation vs. Coercion

We think of markets as competitive places: arenas, battlegrounds, playing fields, boxing rings. Which they are, if you look at them from the standpoint of vendors. As buyers, we do want vendors to compete, of course. But we also want them to cooperate — with us. From our perspective, markets are places where we shop, meet and do business. We want the freedom to do that, and we don’t want sellers taking any of that away, even if they think doing that makes them better competitors.

For decades, if not for a century or more, taking customers’ freedoms away has been something of a virtue for vendors. It’s not for nothing that marketers talk about “acquiring,” “capturing,” “owning” and “managing” customers as if they were slaves or cattle. In the old industrial economy, this made sense. It was easier to serve managed customers than free ones. You could limit the variables you addressed. Even today we sometimes like having our choices restricted, and gladly make the Faustian bargain of captivity. But even here we see the downsides, which go beyond lack of choice. Being captive may seem safe in some ways, but it also makes us vulnerable to a single source of goods on which we have no choice but to depend.

On the sell side, there are two problems. One is the burden of management itself, which should be easier if customers were also carrying some of the load. The other is intelligence. When all you know is what you learn from your captive customers (say, through your loyalty program), you don’t know enough. There is far more happening in the marketplace than you can learn and crunch only in your own exclusive ways.

What we need now is for vendors to discover that free customers are more valuable than captive ones. For that we need to equip customers with better ways to enjoy and express their freedom, including ways of engaging that work consistently for many vendors, rather than in as many different ways ways as there are vendors — which is the “system” (that isn’t) we have now.

There are lots of VRM development efforts working on both the customer and vendor sides of this challenge. In this post I want to draw attention to the symbols that represent those two sides, which we call r-buttons, two of which appear above. Yours is the left one. The vendor’s is the right one. They face each other like magnets, and are open on the facing ends.

These are designed to support what Steve Gillmor calls gestures, which he started talking about back in 2005 or so. I paid some respect to gestures (though I didn’t yet understand what he meant) in The Intention Economy, a piece I wrote for Linux Journal in 2006. (That same title is also the one for book I’m writing for Harvard Business Press. The subtitle is What happens when customers get real power.) On the sell side, in a browser environment, the vendor puts some RDFa in its HTML that says “We welcome free customers.” That can mean many things, but the most important is this: Free customers bring their own means of engagement. It also means they bring their own terms of engagement.

Being open to free customers doesn’t mean that a vendor has to accept the customer’s terms. It does mean that the vendor doesn’t believe it has to provide all those terms itself, through the currently defaulted contracts of adhesion that most of us click “accept” for, almost daily. We have those because from the dawn of e-commerce sellers have assumed that they alone have full responsibility for relationships with customers. Maybe now that dawn has passed, we can get some daylight on other ways of getting along in a free and open marketplace.

The gesture shown here —

— is the vendor (in this case the public radio station KQED, which I’m just using as an example here) expressing openness to the user, through that RDFa code in its HTML. Without that code, the right-side r-button would be gray. The red color on the left side shows that the user has his or her own code for engagement, ready to go. (I unpack some of this stuff here.)

Putting in that RDFa would be trivial for a CRM system. Or even for a CMS (content management system). Next step: (I have Craig Burton leading me on this… he’s on the phone with me right now…) RESTful APIs for customer data. Check slide 69 here. Also slides 98 and 99. And 122, 124, 133 and 153.

If I’m not mistaken, a little bit of RDFa can populate a pop-down menu on the site’s side that might look like this:

All the lower stuff is typical “here are our social links” jive. The important new one is that item at the top. It’s the new place for “legal” (the symbol is one side of a “scale of justice”) but it doesn’t say “these are our non-negotiable terms of service (or privacy policies, or other contracts of adhesion). Just by appearing there it says “We’re open to what you bring to the table. Click here to see how.” This in turn opens the door to a whole new way for buyers and sellers to relate: one that doesn’t need to start with the buyer (or the user) just “accepting” terms he or she doesn’t bother to read because they give all advantages to the seller and are not negotiable. Instead it is an open door like one in a store. Much can be implicit, casual and free of obligation. No new law is required here. Just new practice. This worked for Creative Commons (which neither offered nor required new copyright law), and it can work for r-commerce (a term I just made up). As with Creative Commons, what happens behind that symbol can be machine, lawyer or human-readable. You don’t have to click on it. If your policy as a buyer is that you don’t want to to be tracked by advertisers, you can specify that, and the site can hear and respond to it. The system is, as Renee Lloyd puts it, the difference between a handcuff and a handshake.

Giving customers means for showing up in the marketplace with their own terms of engagement is a core job right now for VRM. Being ready to deal with customers who bring their own terms is equally important for CRM. What I wrote here goes into some of the progress being made for both. Much more is going on as well. (I’m writing about this stuff because these are the development projects I’m involved with personally. There are many others.)

What I want to make clear here is that symbols are necessary. We need graphic representations of states and actions, and what’s possible for both. And we need ones that are not encumbered by anybody’s intellectual property claims. That’s why r-buttons are free for the using. Everybody is also free to use something else, if you think it’s better. I don’t care. I just know we need symbols, and these are some we’ve been using while we’ve been developing stuff.

In the next few weeks there will be a number of  occasions for VRM and CRM folks to get together, to talk, to start building toward each other, and to start training company legal departments in the new ways of open markets — cooperative ways, rather than just coercive ones. Looking forward to seeing how that all goes.

Work toward free and open markets

I just posted three long VRM pieces on my blog:

  1. R-buttons and the Open Marketplace
  2. ListenLog
  3. EmanciPay

They’re really one long post in three parts. Together they unpack the thinking behind my own development work at ProjectVRM here at the Berkman Center, and the three different components of that work. (It’s been a fun four-year-long learning by doing process.)

All this has been going on, of course, in the midst of a growing and active development community that’s also working on many other things, most of which overlap with these three.

See what you think.

Additional note… Those posts should have been on this site; but it’s past three in the morning here in Paris, where my upstream bandwidth is lousy (making the posting of graphics a glacial process) and I made the mistake of misreading my WordPress dashboard, and posting on my blog the first of those pieces. So, rather than start over I continued there. After I figure out how to cross-post the same items here, I’ll do that.

‘RM alignments

In the next several months we’ll start seeing VRM getting respect as a counterpart to CRM — in some cases with a social angle as SRM and sCRM get into the mix. For more on that, here’s Bob Pike on Social Customer Relationship Management:

Forrester predicts the era of Social Commerce, the future of the social Web as I see it, starts to embrace a corporate philosophy and supporting infrastructure that migrates away from CRM and even sCRM to one of Social Relationship Management or SRM. This will usher in the fifth era as observed by Forrester. And, SRM is also acutely cognizant of and in harmony with VRM (Vendor Relationship Management).

VRM is the opposite of CRM, capsizing the concept of talking at or marketing to customers and shifting the balance of power in relationships from vendors to consumers. As such, systems are created to empower consumer participation and sentiment and improve products and services with every engagement.

Should we think the unthinkable and finally adopt a set of new rules which are aligned to actually what is happening this new world of social collaboratio online? Yes I do think so.

And here’s John Lewis on The Manageability of Information:

Nowadays the science of selling has gone much further with ‘relationships selling” as distinct from “transactional selling” and is even being inverted in the form of “soft selling” or should that now be “soft buying”.  It goes beyond selling, organisations have CRM (Customer Relationship Management) processes and systems and are now starting to realise that they need to provide their customers with access to VRM (Vendor Relationship Management) processes and, possibly, systems. There had always been some people who understood it, but there was a development of a general realisation that “selling” and other related areas are manageable!

I believe here John is talking about VRM in a B2B context, where it has been used for many years. Still, it speaks to the need for customers to interact with companies that have transparent and available processes.

Newer posts »

© 2024 ProjectVRM

Theme by Anders NorenUp ↑