Category: Startups

Getting Respect

Respect Network (@RespectConnect) is a new kind of corporate animal: a for-profit company that is also a collection of developers and other interested parties (including nonprofits) gathered around common goals and principles. Chief among the latter is OIX‘s Respect Trust Framework, which is “designed to be self-reinforcing through use of a peer-to-peer reputation system.” Every person and organization agreeing to the framework is a peer. Here are the five principles to which all members agree:

Promise We will respect each other’s digital boundaries

Every Member promises to respect the right of every other Member to control the Member Information they share within the network and the communications they receive within the network.

Permission We will negotiate with each other in good faith

As part of this promise, every Member agrees that all sharing of Member Information and sending of communications will be by permission, and to be honest and direct about the purpose(s) for which permission is sought.

Protection We will protect the identity and data entrusted to us

As part of this promise, every Member agrees to provide reasonable protection for the privacy and security of Member Information shared with that Member.

Portability We will support other Members’ freedom of movement

As part of this promise, every Member agrees that if it hosts Member Information on behalf of another Member, the right to possess, access, control, and share the hosted information, including the right to move it to another host, belongs to the hosted Member.

Proof We will reasonably cooperate for the good of all Members

As part of this promise, every Member agrees to share the reputation metadata necessary for the health of the network, including feedback about compliance with this trust framework, and to not engage in any practices intended to game or subvert the reputation system.

The Respect Network’s founding partners are working, each in their own way, to bring the Respect Trust Framework into common use. I like it as a way to scaffold up a market for VRM tools and services.

This summer Respect Network launched a world tour on which I participated as a speaker and photographer. (Disclosures: Respect Network paid my way, and The Searls Group, my consultancy, has had a number of Respect Network partners as clients. I am also on the board of Flamingo and  Customer Commons, a nonprofit. I don’t however, play favorites. I want to see everybody doing VRM succeed, and I help all of them every way I can. ) We started in London, then hit San Francisco, Sydney and Tel Aviv before heading home to the U.S. Here’s the press coverage:

In the midst of that, Respect Network also announced crowd funding of this button:

respect-connect-button

It operates on the first  promise of the Respect Trust Framework: We will respect each others’ digital boundaries. Think of it as a safe alternative to the same kind of button by Facebook.

The campaign also launched =names (“equals names”) to go with the Respect Connect button, and much else, eventually. These names are yours alone, unlike, say, your Twitter @ handle, which Twitter owns.

There is a common saying: “If you’re not paying for it, you’re the product” In respect of that, =names cost something (like domain names), though not much. Selling =names are CSPs: Cloud Service Providers. There are five so far (based, respectively, in Las Vegas, Vienna, London, New York/Jerusalem and Perth):

bosonweb-logo danube_clouds-logo paoga-logo emmett_global-logo onexus-logo

They  are substitutable. Meaning you can port your =name and data cloud from one to the other as easily as you port your phone number from one company to another. (In fact the company that does this in the background for both your =name and your phone number is Neustar, another Respect Network partner.) You can also self-host your own personal cloud. Mine =name is =Doc, and it’s managed through Danube Clouds. (I actually got it a few years back. The tech behind =names has been in the works for awhile.)

The tour was something of a shakedown cruise. Lots was learned along the way, and everybody involved is re-jiggering their products, services and plans to make the most of what they picked up. I’ll share some of my own learnings for ProjectVRM in the next post.

 

 

Turning the customer journey into a virtuous cycle

Traditional CRM typically looks at customers this way:CRM cycleIt’s a cycle. One of the reasons we started ProjectVRM is that actual customers are hard to find in the CRM business. We are “leads” for Sales, “cases” in Support, “leads” again in Marketing. At the Orders stage we are destinations to which products and invoices are delivered. That’s it.

Oracle CRM, however, has a nice twist on this (and thanks to @nitinbadjatia of Oracle for sharing it*):

Oracle Twist

Here we see the “customer journey” as a path that loops between buying and owning. The blue part — OWN, on the right — is literally the customer’s own-space. As the text on the OWN loop shows, the company’s job in that space is to support and serve. As we see here…

… the place where that happens is typically the call center.

Now let’s pause to consider the curb weight of “solutions” in the world of interactivity between company and customer today. In the BUY loop of the customer journey, we have:

  1. All of advertising, which Magna Global expects to pass $.5 trillion this year
  2. All of CRM, which Gartner pegs at $18b)
  3. All the rest of marketing, which has too many segments for me to bother looking up

In the OWN loop we have a $0trillion greenfield. This is where VRM started, with personal data lockers, stores, vaults, services and (just in the last few months) clouds.

Now look around your home. What you see is mostly stuff you own. Meaning you’ve bought it already. How about basing your relationships with companies on those things, rather than over on the BUY side of the loop, where you are forced to stand under a Niagara of advertising and sales-pitching, by companies and agencies trying to “target” and “acquire” you. From marketing’s traditional point of view (the headwaters of that Niagara), the OWN loop is where they can “manage” you, “control” you, “own” you and “lock” you in. To see one way this works, check your wallets, purses, glove compartments and kitchen junk drawers for “loyalty” cards that have little if anything to do with genuine loyalty.

But what if the OWN loop actually belonged to the customer, and not to the CRM system? What if you had VRM going there, working together with CRM, at any number of touch points, including the call center?

This is more than a simple dream. One of the coolest things to happen in the VRM development world is this insight, based on actual technology: everything you own can have its own cloud, and each can live inside your personal cloud. Your stuff doesn’t need to have embedded smarts. You can put your things’ smarts inside clouds of their own. Manufacturers can also include clouds along with everything they sell. Inside that cloud can go all the touchpoint contact data required for a genuine relationship, plus useful extras such as service manuals and shortcuts to product updates.

This means the product itself becomes the platform for relationship between the customer and everybody on the sell side, from manufacturer to distributor to retailer to service company. As I explained in this HBR post, that platform — the product’s cloud — is the level table where all those parties sit, at the grace of the customer. Because it’s the customer’s space.

One tablecloth for that platform is the TalkTag. It’s a simple QR code, like the one on the right. The pioneering company here is Kynetx, through its SquareTag service. It’s a simple way to give anything you have a cloud of its own. Scanning a TalkTag is one way to visit a thing’s cloud, which is also a programmable space. If your thing is lost, you can program it to provide contact information through somebody’s smartphone when they scan it. (Which I have done, and it works.)

You can also program it to, say, notify the call center when you scan it. For example, I want the TalkTag I just put on my cable modem to notify Time Warner Cable when I scan it. If Time Warner Cable’s CRM system is listening (which should be easy enough to make happen), it can send back a message to my phone, telling me there is an outage in my neighborhood. Or, in the event that there isn’t an outage, the “I’ve been scanned” message from me to Time Warner Cable can jump past stages in the company’s IVR (Interactive Voice Response) system and get me straight to the right person or automated response. That might be, “You need to download new firmware,” or “We have three new service tiers you might want to know about,” or “We see you haven’t paid your bill.”

I have shared this kind of scenario with two call center companies recently, and they liked it a lot. In fact they like the whole idea of VRM systems on the customers’ side that can lighten the burdens of relationship (and open opportunities) for both sides.

The customer journey — his or her experiences of owning and buying — will include more than just interacting with call centers. We use the things we own in countless ways that might be useful to share with others, including the companies that make and sell stuff — and not just through “social” systems like Facebook and Twitter, over which we have little or no control.

We should also be able to integrate data from products that don’t relate but should. In the Quantified Self world, for example, there is a standing need to synthesize data from many devices and databases. This need  cannot be solved by asking Nike, Fitbit, Withings, RunKeeper and the rest of them to all make their data un-silo’d and combine-able. And doing it in “social media,” whose only business is advertising at us, won’t work either. We need means of our own.

In the VRM world we’ve been saying the user needs to be the point of integration for his or her own data since Joe Andrieu first expressed that insight in 2007. Now, with personal clouds, in 2013, it’s starting to look possible. In fact the personal cloud, and the whole OWN loop, can also be a platform for intentcasting toward the BUY side.

The OWN side is also where all the privacy technology also sits, chiefly because it is distributed. It is here also that we hold the terms, preferences and policies we express when dealing with companies sitting across the tables set between us.

An interesting case that lies between buying and owning is relationships with service organizations, such as utilities. What we own here is own side of an ongoing relationship. Equipment of our own may be in there, or may not be. Either way, the use of a service — in our homes, cars and pockets — is what we at least control, even if we don’t own it.

So clearly we need a common platform for personal clouds, and for the things we put in them. That platform needs to be small, lightweight, distributed and open source. Right now I see one candidate for that: CloudOS, which is the brainbaby of Phil Windley. (Here’s a search for CloudOS and Windley. Lots of stuff there.) If you’ve got some other hacks, point them out in the comments below.

If we look at the customer experience from the company’s side again, this graphic from Joe Pine and Jim Gilmore does a nice job of framing the possibilities:

Across the table set in a personal cloud, customers can feed back good intelligence to every one of the loops in that graphic. And, because that data arrives directly and voluntarily, it has far higher quality than inferential data gathered by marketing’s many surveillance methods.

It also re-frames relationship and loyalty, as real things rather than as words marketing recites inside its own echo chambers. It will reduce marketing’s urge to manipulate, and advertising’s urge to personalize in the absence of conscious and voluntary signals welcoming it. The customer journey will thus turn into a virtuous cycle rather than the arduous one it is today.

It can also create a demand chain that can work in tandem with the supply chain, providing far better feedback at every stage. I could go on, but I want to get this up before the latest in the series of Important Calls that punctuate my life. (And they are all Good Things, trust me.)

Bonus link.

* In the comments below the post that follows this one, Ray Wang points to Esteban Kolsky as the original author of this graphic. As I say in my comment below Ray’s, I did hear that from Nitin Badjatia (of Oracle and formerly of Right Now), but I didn’t remember it when I wrote both posts in a hurry. Again, it is the verbs — BUY and OWN — that make the image especially useful for VRM, because they are the customer’s. I don’t yet know if those verbs are Esteban’s or Right Now/Oracle’s. Let me know and I’ll give credit where due.

VRM help is where you find it

As Dean Landsman tweets here, a lot of suff out there is VRM without saying so. (Which is cool; it doesn’t have to.) The example toward which he points is How can we provide better customer service? Create software that lets customers serve each other, by Ashley Verrill in Gigaom. The summary:

As consumers increasingly turn to social media to both praise and criticize brands, those brands can’t possibliy respond to all the feedback. The solution is to empower customers to speak on their behalf.

Her piece begins,

Recently I was asked a question following a presentation that suddenly made me realize social application developers are missing a big opportunity in customer service. I had just finished speaking at the global HP Social Support Summit, when an audience member took the microphone and asked, “Do you know of any software that lets community members respond on behalf of companies on Twitter, Facebook and other social media platforms?”

I do, and more on that below. Meanwhile, Ashley unpacks the problem requiring this kind of question:

The current customer service model is moribund

One of the biggest reasons this idea struck me is that the current model just isn’t working. In one study I conducted, major brands such as Coca-Cola and Wells Fargo responded just 14 percent of the time when they were asked questions via Twitter. This is a big problem when you consider more than half of Twitter users expect a personal response within two hours of sending a question or complaint, according to a report by Oracle last year.

This is a scaling problem that can be partially answered by equipping more employees to respond to requests from customers. Ashley sees customers themselves — “community members” — taking up the rest of the slack:

Existing, active community members can be the perfect candidates to respond for companies on social media for two reasons: For one, they’re already enthusiastic about your products and so can be good brand ambassadors; and two, they’ve proven their zeal for answering questions from other customers already.

Take this HP community member, for example. He spends upwards of 30 unpaid  hours a week responding to queries in their discussion forums. The software I’m suggesting would essentially empower “wb2001″ and thousands of other similar customers like him to respond to questions on social media (in addition to the community that exists already).

This hypothetical technology could still leverage all of the tools that make communities so effective – things like gamification and automated alerts. Also, social listening tools could filter out messages that would be better suited for an employee response. This could include messages from customers that are particularly angry, or questions that would require a technical expert.

This would lead, she concludes, to “empowering your brand advocates to create a sea of new discussions that never would have existed in the first place.”

What would do the empowering, exactly?

Among VRM developers, I see one company that does exactly what the HP audience member asked for. The company is Directly. Here is its mission:

A Better Way To Get Help.

Directly makes it easy to get fast, personal attention from experts who know different companies inside and out. Our community of experts work independently in their own free time. They earn rewards and reputation, and can cash out their rewards or donate them to one of the non-profit causes we support.

  • Our support site helps customers get better customer support — so customers can spend less time dealing with support and more time enjoying their life.
  • Our mortgage site helps homebuyers and homeowners — so more families can buy new homes or stay in the ones they love.

Directly launched publicly in December 2012 with a network that reaches 3.2 million customers monthly and has already helped 35,000 airline, bank, cable and wireless customers with a 97% response rate and an average response time of less than 10 minutes.

So whether you need to evaluate the best options, resolve an issue or just get things done, Directly is a better way to get help straight from the experts who can help.

As for software for making her scenario work, I think it would have to be independent of the world’s HPs, but would work with any or all of them.

For example, let’s say I wish to leverage my expertise with these things:

  • Canon 5D camera
  • 2000 Volkswagen Passat station wagon
  • Sangean ATS-909/Radio Shack DX-398 radio
  • Garmin eTrex Legend HCx GPS
  • Starbucks’ Saeco and Barista espresso machines

Rather than be empowered by each of those companies to speak for them, I might like one standard and non-proprietary way I could provide help for users of all of them. Or that would give customers a way of notifying the marketplace (including the corporate CRM systems, plus help systems such as Directly, plus anybody interested in helping without an intermediator) of a need for help.

Is that way out there yet? There are a zillion fora for a zillion products and services already. Some are hosted by the companies themselves, and some are out in the wild. But all I can name are to some degree centralized. What I’d like to see is something decentralized, but capable of working both with customers and with any of the CRM systems already in place from providers like Salesforce, IBM, SAP, Microsoft Dynamics and the rest of them.

Maybe something like that is out there already. If so, let us know.

Prepping for #VRM Day and #IIW

The 16th IIW (Internet Identity Workshop) is coming up, Tuesday to Thursday, 7-9 May, will be tat the Computer History Museum in Mountain View, CA. As usual, VRM will be a main topic, with lots of developers and other interested folk participating. Also as usual, we will have a VRM planning day on the Monday preceding: 6 May, also at the CHM. So that’s four straight days during which we’ll get to present, whiteboard, discuss and move forward the many projects we’re working on. From the top of my head at the moment:

  • Personal Clouds, including —
    • The Internet of Me and My Things
    • QS (Quantified Self) and Self-Hacking
  • Fully personal wallets, rather than branded ones that work only with payment silos and their partners
  • Intentcasting — where customers advertise their purchase intentions in a secure, private and trusted way, outside of any vendor’s silo
  • Browser add-ons, extensions, related developments
  • Licensing issues
  • Sovereign and administrative identity approaches, including Persona, formerly BrowserID, from Mozilla
  • Legal issues, such as creating terms and policies that individuals assert
  • Tracking and ad blocking, and harmonizing methods and experiences
  • Health Care VRM
  • Devices, such as the freedom box
  • VRM inSovereign vs./+ Administrative identities
    • Real estate
    • Banking (including credit cards, payments, transactions)
    • Retail
  • Personal data pain points, e.g. filling out forms
  • Trust networks
  • Harnessing adtech science and methods for customers, rather than only for vendors

The morning will be devoted to VRM issues, while the afternoon will concentrate on personal clouds.

We still have eight tickets left here. There is no charge to attend.

In the next few days here on the blog we’ll be going over some of the topics above. Input welcome.

 

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

When consumers become media for themselves

I was talking recently with Edi Immonen of Glome about the idea behind it: turning users into publishers. He used the word “media,” but I’m going with “publishers” for now, because that’s the word used in this graphic (one of many like it — all amazing and excellent) from LUMA partners:

That’s the marketer’s view. But how about yours, as the consumer over there on the right. In fact it’s actually more like this:

Because all you do is consume. You have no direct influence on all that intermediary stuff; so it just presses down on you.

But what if you become the publisher — a form of producer, and not just of consumer? Then the system, simplified, would look like this:

This is in alignment with what Tim Berners-Lee designed the Web to look like in the first place, but in in a commercial setting. (Remember that Sir Tim was then working in high energy physics at CERN, looking for ways to share and edit documents across the Internet as it existed at the turn of the ’90s.) It is also what blogging, as originally conceived, also did. If this blog were commercial (which it is not, on purpose), that would be me (or us) on the right.

Now, if we, as publishers, look at our data, or of our personal space — our state as a medium — as a platform for selling and buying stuff, including services, a whole new horizon opens up.

What Edi and his colleagues at Glome envision is a way for you, as a medium, to sell your space (however you chose to define that word) to:

  1. brands with which you already have a relationship;
  2. brands in which you have an interest; or
  3. brands in which you might have an interest.

From the traditional marketing perspective, #3 makes you “qualified lead,” for which the brand should be willing to pay. But that’s a far too reduced view of what you really are, or might be, to that brand.

Think of this marketplace frame from a CRM+VRM perspective. Between those two rectangles, inside the black two-pointed arrow, are cycles of buying and owning, of use and re-use, of live interactions and of long periods of idle time where neither is paying much attention to the other. Lots of stuff can go on within the boundaries of that two-way arrow.

What Glome proposes here is not zero-basing the marketplace, but instead to re-start our thinking, and our work, atop three well-understood existing roles: brand, publisher (or medium) and marketplace. The main re-characterization is of the individual, who is now a publisher or a medium, and not just a consumer.

Obviously much can get disintermediated here, including all the stuff between the marketer and the publisher in the graphic up top.

But much new intermediation is now possible, especially if the individual has a personal cloud through which one (or one’s fourth party) can program interactions, for the individual, among API-based services (in the manner of IFTTT, or using KRL) and the “Internet of things”. (For developers, I believe Singly fits in here too.)

So we are looking here at a whole new market for information and relationships, within the larger marketplace of everything else. This isn’t complicated, really. It’s actually what markets looked like in the first place:

This is the context we meant by “Markets are conversations” in The Cluetrain Manifesto.

LUMAscapes (such as the top one above) brilliantly depict the ecosystems of marketing as they have evolved so far, down different branches of discipline. The tree from which they branch, however, is the old advertising and direct marketing one, now operating inside the Internet . (“Big data” and analytics in marketing are hardly new. They were what direct mail was all about long before it evolved into direct marketing and then spread into online advertising.)

So this is a shout-to —

— as well as all the VRM developers in the world (and it seems there are more every day).

The last graphic above is our new frame. It helps that it’s also the oldest frame.

I also look forward to the day when Terence Kawaja and his colleagues at LUMA partners draw up VRM+CRM and other new ecosystems that are bound to evolve, once enough of us get our heads out of the old marketing frame and into the oldest marketplace one. So this is a shout-out to them too. :-)

VRM taking root in France

I love this tweet from @CaroCondamin

Le concept du Vendor Relationship Management par ProjectVRM http://www.caroline-condamin.com/vrm/  #VRM

Following the links, I see she works for OneCub, a VRM company in France. Here she also includes this simple and handy graphic, which nicely illustrates the reciprocity between CRM and VRM:

Thanks to the good work done by Fing and others in France, when I spoke at an event there last year, all the hands in the room went up when I asked how many were familiar with VRM.

And, even though there is some argument in VRM circles over whether this proposed tax is a good or bad thing, there is no doubt that the spirit behind it is aligned with the one behind VRM development. In fact, this 2oo page report, written in what one source calls “administrative French,” sources The Cluetrain Manifesto and The Intention EconomyHere is Caroline’s post about the proposal. (In Chrome, it translates to English for me.) Anybody interested in the intersection between public interest, policy and market dynamics should read it.

 

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.

Ting rings the opening bell

Here, according to the ProjectVRM wiki, are the ideal characteristics of VRM tools:

  1. VRM tools are personal. As with hammers, wallets, cars and mobile phones, people use them as individuals,. They are social only in secondary ways.
  2. VRM tools help customers express intent. These include preferences, policies, terms and means of engagement, authorizations, requests and anything else that’s possible in a free market, outside any one vendor’s silo or ranch.
  3. VRM tools help customers engage. This can be with each other, or with any organization, including (and especially) its CRM system.
  4. VRM tools help customers manage. This includes both their own data and systems and their relationships with other entities, and their systems.
  5. VRM tools are substitutable. This means no source of VRM tools can lock users in

Note “mobile phones” in #1. Like a car or a wallet, a mobile phone is personal. Ir also supports our independence, helps us express intent, and is substitutable. Bearing all these things (and more) in mind, Ting.com has come to market with the clear intent of doing the best it can to support customers’ VRM intentions.

Go down Joe Andrieu’s list of user driven services

  1. Impulse from the User
  2. Control
  3. Transparency
  4. Data Portability
  5. Service Endpoint Portability
  6. Self Hosting
  7. User Generativity
  8. Improvability
  9. Self-managed Identity
  10. Duty of Care

… and you’ll find that Ting comes about as close as any mobile phone company can come to respecting all those things.

Ting is an MVNO — a Mobile Virtual Network Operator. That means it operates as a phone company, but does not own facilities. Instead it re-sells the raw base offerings (minutes, texts, quantities of data) that it buys from a carrier with facilities. In this case, Sprint. It works everywhere in the U.S. that Sprint does, but it has a much more friendly and sensible set of offerings and pricings than any of the major mobile phone companies. It’s about as gimmick-free as you can get. That is, Ting is the very opposite of what Scott Adams in The Dilbert Future calls a “confusopoly.” Sez Scott,

A confusopoly is a situation in which companies pretend to compete on price, service, and features but in fact they are just trying to confuse customers so no one can do comparison shopping.

Cell [mobile] phone companies are the best example of confusopolies. The average consumer finds it impossible to decipher which carrier has the best deal, so carriers don’t have normal market pressure to lower prices. It’s a virtual cartel without the illegal part.

Ting is a VRM company. Its management and other personnel have been involved in many VRM discussions and events, and a number of VRM folk have been involved in Ting’s beta as well. Our family, for example. So far we’re loving it. The data service especially is surprisingly good. At our kid’s high school in rural New Hampshire, both voice and data service is pretty much perfect.

Here are some of the stories about the Ting launch that have hit so far:

Plus these from Zemanta:

Say howdy to Insidr and Glome

One is , which is “rewriting the Rules of ” by giving you a way to “connect directly to real people who have worked in big companies and are willing to help when the company can’t or won’t.” You post a question, offer a bounty for an answer, and get an answer from an insider at the company. So far those include (copied and pasted from Insidr’s about/learn page):

I asked a question regarding , with which I’ve flown .82 million miles so far. The question had nothing to do with customer service, but rather with looking for a connection inside the airline, with whom I might talk about publishing a book of aerial photos (such as these) taken from United planes, timed to publish about the time  come into service. It’s a long shot, but a fun one.

I think Insidr qualifies as a fourth party (as described this blog post and this ProjectVRM wiki article). That is, one working primarily for the customer, rather than for the vendor. That Insidr is paid by places it on the side of customers financially, which is significant — and novel, in an age when most new Web-based businesses still look for revenue coming from sellers “targeting” customers rather than customers expressing their own intentions, in their own ways.

about Insidr. (I was given a heads-up that TechCrunch might call to get the VRM angle, but that didn’t happen.)

[Update...] I spoke with Antony Brydon, Insidr’s CEO. He made it clear that the term “Insider” is not limited to people working for the company, and in fact is refers to the collection of experts who are proximal to the company rather than inside the company — though it might include those too. He also begs our indulgence of Insidr’s learning process. They’re just getting started.

The other new VRM entry is .  “Stop being a product” says the main copy on the index page. @glomeinc‘s Twitter page says,

Glome Inc@GlomeInc Helsinki, Finland
Media startup aiming to change the way advertisers connect with customers online. Buzzwords: VRM, User controlled data, online privacy, open API:s

The first and only tweet so far there says,

Glome Inc. is officially founded. Stay tuned for private beta invite instructions. #glomeinc #vrm #privacy #changetheworld

I tweeted back,

@GlomeInc Tell us more about your #VRMwork. DM me if you need to keep it private for now.

We’ll see how that goes. Meanwhile, it’s good to know that both companies fly the #VRM flag.

Here’s Zemanta‘s list of Related Articles:

© 2014 ProjectVRM

Theme by Anders NorenUp ↑