Category: Demand chain (page 1 of 5)

VRM at MyData2016

mydata2016-image

As it happens I’m in Helsinki right now, for MyData2016, where I’ll be speaking on Thursday morning. My topic: The Power of the Individual. There is also a hackathon (led by DataBusiness.fi) going on during the show, starting at 4pm (local time) today. In no order of priority, here are just some of the subjects and players I’ll be dealing with,  talking to, and talking up (much as I can):

Please let me know what others belong on this list. And see you at the show.

Save

Is Facebook working on a VRM system? Or just another way to do ads?

It’s easy to get caught up in news that WhatsApp is starting to accept advertising (after they said they would never do that), and miss the deeper point of what’s really going on: Facebook setting up a new bot-based channel through which companies and customers can communicate. Like this:

vrmcrmbot

The word balloon is Facebook Messenger. But it could be WhatsApp too. From a VRM perspective, what matters is whether or not “Messenger bots” work as VRM tools, meaning they obey the individual user’s commands (and not just those of Facebook’s corporate customers). We don’t know yet. Hence the question mark.

But before we get to exploring the possibilities here (which could be immense), we need to visit and dismiss the main distractions.

Those start with Why we don’t sell ads, posted on the WhatsApp blog on 18 June 2012. Here are the money grafs from that one:

We knew we could do what most people aim to do every day: avoid ads.
No one wakes up excited to see more advertising, no one goes to sleep thinking about the ads they’ll see tomorrow. We know people go to sleep excited about who they chatted with that day (and disappointed about who they didn’t). We want WhatsApp to be the product that keeps you awake… and that you reach for in the morning. No one jumps up from a nap and runs to see an advertisement.

Advertising isn’t just the disruption of aesthetics, the insults to your intelligence and the interruption of your train of thought. At every company that sells ads, a significant portion of their engineering team spends their day tuning data mining, writing better code to collect all your personal data, upgrading the servers that hold all the data and making sure it’s all being logged and collated and sliced and packaged and shipped out… And at the end of the day the result of it all is a slightly different advertising banner in your browser or on your mobile screen.

Remember, when advertising is involved you the user are the product.

Great stuff. But that was then and this is now. In WhatsApp’s latest post, Looking Ahead for WhatsApp (25 August), we have the about-face:

But by coordinating more with Facebook, we’ll be able to do things like track basic metrics about how often people use our services and better fight spam on WhatsApp. And by connecting your phone number with Facebook’s systems, Facebook can offer better friend suggestions and show you more relevant ads if you have an account with them. For example, you might see an ad from a company you already work with, rather than one from someone you’ve never heard of. You can learn more, including how to control the use of your data, here.

Pretty yucky, huh?

Earlier in the same post, however, WhatsApp says,

we want to explore ways for you to communicate with businesses that matter to you too

Interesting: Mark Zuckerberg said the same thing when he introduced messenger bots, back in April. In the video at that link, Zuck said,

Now that Messenger has scaled, we’re starting to develop ecosystems around it. And the first thing we’re doing is exploring how you can all communicate with businesses.

You probably interact with dozens of businesses every day. And some of them are probably really meaningful to you. But I’ve never met anyone who likes calling a business. And no one wants to have to install a new app for every service or business they want to interact with. So we think there’s gotta be a better way to do this.

We think you should be able to message a business the same way you message a friend. You should get a quick response, and it shouldn’t take your full attention, like a phone call would. And you shouldn’t have to install a new app.

Note the similarities in the set-up:

  1. Zuck:  “how you can all communicate with business.”
  2. WhatsApp: “explore ways for you to communicate with businesses.”

This is, or should be, pure VRM:  a way for a customer to issue a service request, or to intentcast for bids on a new washing machine or a car. In other words, what they seem to be talking about here is a new communication channel between customers and businesses that can relieve  the typical pains of being a customer while also opening the floodgates of demand notifying supply when it’s ready to buy. Back to Zuck:

So today we’re launching Messenger Platform. So you can build bots for Messenger.

By “you” Zuck means the developers he was addressing that day. I assume these were developers working for businesses that avoid customer contact and would rather have robots take over everything possible, because that’s the norm these days. But I could be wrong. He continues,

And it’s a simple platform, powered by artificial intelligence, so you can build natural language services to communicate directly with people. So let’s take a look.

CNN, for example, is going to be able to send you a daily digest of stories, right into messenger. And the more you use it, the more personalized it will get. And if you want to learn more about a specific topic, say a Supreme Court nomination or the zika virus, you just send a message and it will send you that information.

The antecedents of “you” move around here. Could be he’s misdirecting attention away from surveillance. Can’t tell. But it is clear that he’s looking past advertising alone as a way to make money.

Back to the WhatsApp post:

Whether it’s hearing from your bank about a potentially fraudulent transaction, or getting notified by an airline about a delayed flight, many of us get this information elsewhere, including in text messages and phone calls.

This also echoes what Zuck said in April. In both cases it’s about companies communicating with you, not about you communicating with companies. Would bots work both ways?

In “‘Bot’ is the wrong name…and why people who think it’s silly are wrong”, Aaron Batalion says all kinds of functionality now found only in apps will move to bots—Messenger’s in particular. “In a micro app world, you build one experience on the Facebook platform and reach 1B people.”

How about building a one-experience bot so 1B people can reach businesses the same way?

Imagine, for example, that you can notify every company you deal with that your last name has changed, or you’ve replaced a credit card. It would be great to do that in one move. It would also be VRM 101. But, almost ten years into our project, nobody has built that yet. Is Facebook doing it?

Frankly, I hope not, because I don’t want to see VRM trapped inside a giant silo.

That’s why I just put up Market intelligence that flows both ways, over in Medium. (It’s a much-updated version of a post I put up here several years ago.)

In that post I describe a much better approach, based on open source code, that doesn’t require locating your soul inside a large company for which, as WhatsApp put it four years ago, you’re the product.

Here’s a diagram that shows how one person (myself, in this case) can relate to a company whose moccasins he owns:

vrmcrmconduit

The moccasins have their own pico: a cloud on the Net for a thing in the physical world. For VRM and CRM purposes, this one is a relationship conduit between customer and company.

A pico of this type comes in to being when the customer assigns the QR code to the moccasins and scans it. The customer and company can then share records about the product, or notify the other party when there’s a problem, a bargain on a new pair, or whatever. It’s tabula rasa: wide open.

The current code for this is called Wrangler. It’s open source and in Github. For the curious, Phil Windley explains how picos work in Reactive Programming With Picos.

I’ll continue on this theme in the next post. Meanwhile, my main purpose with this one is to borrow interest in where Facebook is going (if I’m guessing right) with Messenger bots, and do it one better in the open and un-silo’d world, while we still have one to hack.

 

 

Save

Save

Save

Save

Save

Save

Save

Save

Save

Save

Save

Save

Save

Why #NoStalking is a good deal for publishers

"Just give me ads not based on tracking me.."

That line, scribbled on a whiteboard at VRM Day recently at the Computer History Museum, expresses the unspoken social contract we’ve always had with ad-supported print publications in the physical world. But we never needed to say it in that world, for the same reason we never needed to say “don’t follow me out of your store,” or “don’t use ink that will give me an infection.” Nobody ever would have considered doing anything that ridiculously ill-mannered.

But following us, and infecting our digital bodies (e.g. our browsers) with microbes that spy on us, is pro forma for ad-supported publishers on the Internet. That’s why Do Not Track was created in 2007, and a big reason why since then hundreds of millions of us have installed ad blockers and tracking protection of various kinds in our browsers and mobile devices.

But blocking ads also breaks that old social contract. In that sense it’s also ill-mannered, though not ridiculously so.

What if we wanted to restore that social contract, for the good of publishers that are stuck in their own ill-mannered death spiral?

The first and easiest way is by running tracking protection alone. There are many ways of doing that. There are settings you can make in some browsers, plus add-ons or extensions from Aloodo, BaycloudDisconnect, the EFF and others.

The second is requesting refined settings from browser makers. That’s  what @JuliaAnguin does in this tweet about the new Brave browser:

Julia Angwin's request to Brave

But why depend on each browser to provide us with a separate setting, with different rules? How about having our own pro forma rule we could express through all our browsers and apps?

We have the answer, and it’s called the NoStalking rule. In fact, it’s already being worked out and formalized at the Kantara Initiative and will live at Customer Commons, where it will be legible at all three of these levels:

3way

It will work because it’s a good one for both sides. Individuals issuing the offer get guilt-free use of the goods they come to the publisher for, and the publisher gets to stay in business — and improve that business by running advertising that is actually valued by its recipients.

The offer can be expressed in one line of code in a browser, and accepted by corresponding code on the publisher’s side. The browser code can be run natively (as, for example, a choice in the Brave menu above) or through an extension such as an ad or tracking blocker. In those cases the blocker would open the valve to non-tracking-based advertising.

On the publisher’s side, the agreement can be automatic. Or simply de facto, meaning the publisher only runs non-tracking based ads anyway. (As does, for example, Medium.) In that case, the publisher is compliant with CHEDDAR, which was outlined by Don Marti (of Aloodo, above) and discussed  both at VRM Day and then at  IIW, in May. Here’s an icon-like image for CHEDDAR, drawn by Craig Burton on his phone:

Sketch - 7

To explain CHEDDAR, Don wrote this on the same whiteboard where the NoStalking term above also appeared:

cheddar

For the A in CHEDDAR, if we want the NoStalking agreement to be accountable from both sides, it might help to have a consent receipt. That spec is in the works too.

What matters most is that individuals get full respect as sovereign actors operating with full agency in the marketplace. That means it isn’t good enough just for sites to behave well. Sites also need to respond to friendly signals of intent coming directly from individuals visiting those sites. That’s why the NoStalking agreement is important. It’s the first of many other possible signals as well.

It also matters that the NoStalking agreement may be the first of its kind in the online world: one where the individual is the one extending the offer and the business is the one agreeing to it, rather than the other way around.

At VRM Day and IIW, we had participants affiliated with the EFF, Mozilla, Privacy Badger, Adblock Plus, Consent Receipt, PDEC (Personal Data Ecosystem Consortium),  and the CISWG (Consent & InfoSharing Working Group), among others. Work has continued since then, and includes people from the publishing, advertising and other interested communities. There’s a lot to be encouraged about.

In case anybody wonders if advertising can work as well if it’s not based on tracking, check out Pedro Gardete: The Real Price of Cheap Talk: Do customers benefit from highly targeted online ads?  by Eilene Zimmerman (@eilenez) in Insights by Stanford Business. The gist:

Now a new paper from Stanford Graduate School of Business professor Pedro Gardete and Yakov Bart, a professor at Northeastern University, sheds light on who is likely to benefit from personalized advertising and identifies managerial best practices.

The researchers found that highly targeted and personalized ads may not translate to higher profits for companies because consumers find those ads less persuasive. In fact, in some cases the most effective strategy is for consumers to keep information private and for businesses to track less of it.

You can also mine the oeuvres of Bob Hoffman and Don Marti for lots of other material that makes clear that the best advertising is actual advertising, and not stalking-based direct marketing that only looks like advertising.

Our next step, while we work on all this,  is to put together an FAQ on why the NoStalking deal is a good one for everybody. Look for that at Customer Commons, where terms behind more good deals that customers offer will show up in the coming months.

How customers can debug business with one line of code

744px-Olive_branch.svg

Four years ago, I posted An olive branch to advertising here. It began,

Online advertising has a couple of big problems that could possibly be turned into opportunities. One is Do Not Track, or DNT. The other is blocking of ads and/or tracking.

Publishers and the advertising business either attacked or ignored Do Not Track, which was too bad, because the ideas we had for making it work might have prevented the problem those businesses now have with ad blocking.

According to the latest PageFair/Adobe study,  the number of people blocking ads passed 200 million last May, with double-digit increases in adoption, worldwide. Tracking protection is also gaining in popularity.

While those solutions provide individuals with agency and scale, they don’t work for publishers. Not yet, anyway.

What we need is a solution that scales for readers and is friendly to publishers and the kind of advertising readers can welcome—or at least tolerate, in appreciation of how ads sponsor the content they want. This is what we have always had with newspapers, magazines, radio and TV in the offline world, none of which ever tracked anybody anywhere.

So now we offer a solution. It’s a simple preference, which readers can express in code, that says this: Just show me ads that aren’t based on tracking me. Equally simple code can sit on the publishers’ side. Digital handshakes can also happen between the two.

This term will live at Customer Commons, which was designed for that purpose, on the model of Creative Commons (which also came out of work done by folks here at the Berkman Center).  This blog post provides some context.

We’ll be working on that term, its wording , and the code that expresses and agrees to it, next week at the Computer History Museum in Silicon Valley. Monday will be VRM Day. Tuesday through Thursday will be IIW—the Internet Identity Workshop (where ProjectVRM was incubated almost ten years ago). VRM Day is mostly for planning the work we’ll do at IIW. VRM Day is free, and IIW is cheap for three days of actually getting stuff done. (It’s by far the most leveraged conference I know, partly because it’s an unconference: no keynotes, panels or sponsor booths. Just breakouts that participants create, choose and lead.)

If you care about aligning publishing and advertising online with what worked for hundreds of years offline — and driving uninvited surveillance out of business itself — come help us out.

This one term is a first step. There will be many more before we customers get the full respect we deserve from ad-funded businesses online. Each step needs to prove to one business category or another that customers aren’t just followers. Sometimes they need to take the lead.

This is one of those times.  So let’s make it happen.

See you next week.

 

 

A good customer experience (#CX)

twc-promiseOn the left is a partial screenshot of an October email pitch to me by Time Warner Cable, here in Manhattan. (It’s also on the Web, here.) On the whole, it looks good: service on demand, on my terms, when I need it.

Or, I thought, maybe. Because I was suspicious. Time Warner Cable’s customer service reputation was awful.  And I’m always on alert for BS. For example, hold time was “reduced” (to what?) and suspected the 24/7 “live agent” was not a human being.

Then there was the “My TWC® app.” Why should I clutter my mobile device with an app from every company I deal with, especially when I hardly ever deal with them?

And then there was the “Ask TWC Virtual Assistant”: http://www.timewarnercable.com/en/suppor…

Hey, if I want a virtual assistant, it should be my employee, not TWC’s, or any other company’s. (Here are the VRM ones.)

But I was game, so I looked for MyTWC on Apple’s App Store, and found nothing there — not by “My TWC”, “TWC” or “Time Warner Cable”.

Then I decided to dig into the TWC site for more. Naturally, I needed a login and password. I didn’t know what those were, and when I tried to recover a login, I got this:

TWC ID System Error
Error Code: EXCEPTION Reference ID: 4FFUT-5327B-RH4L4-2RDQD-N4WET.

So, in case I never registered (I didn’t remember), I tried doing that. The result:

A TWC ID already exists for this account. If you are the primary account holder and did not register for a TWC ID, please contact us. Chat with us.

— with a link under that last sentence.

Before I chatted, I needed to give the agent my full name and phone number, and then choose the topic. My choices:

Topic: *
New TWC ID Help
Reset TWC ID Login

Not especially clear, but I hit the former.

What then followed was the best customer experience I’ve ever had with an ISP. Two chat agents, in succession,  gave me exactly what I was looking for, and more. I quickly recovered the login and password. I got the right link to the app, which I downloaded and installed. Then I found, after asking what speeds I should be getting for the $109/month I’m spending, that it’s 300MBps down and 20MBps up. When I found that my speed (over Ethernet, directly through the router) was 50/5, I was told that my modem (a Motorola SurfBoard SB6121) couldn’t handle the promised speeds. The agent even gave me tech reasons I doubt any robot could give. Then the agent sent me to a page with a list of cable modems that can handle the speeds I’m buying. (Here’s a .pdf version.)  All were about $95 on Amazon and elsewhere. So I ordered the Netgear CM500-100NAS, which seemed to have the most good reviews — helped along the way by  the chat agent, who told me to call back when the unit arrived.

I did that, and booked a technician to show up and help install the thing early the next Monday morning — exactly as promised in the email above. When the guy got here, he not only got the thing set up well, but helped me select a channel on my Apple Time Machine/wifi hotspot that had minimal interference from activity coming from the high-rise next door. (The list of wi-fi signals in the drop-down menu of my laptop can get longer than the screen is high.) And to set up the hot spot so it gave both 5GHz and a 2.4GHz. The former was faster here in my office, while the latter had better range to the other end of the apartment. Here is the final post-tweaking test result in my office, from DSL Reports’ speedtest, which is currently the best in the business:

Screen Shot 2015-12-28 at 10.22.14 AM

Not what I expected.

So hats off to TWC. Well done.

Now for the VRM side of this.

We know from our friends in the CRM, CX, CE, IA and other overlapping customer services worlds on the supply side of business that there is now friendliness toward VRM approaches that standardize and normalize the way each of us connects to the companies that serve us.

How do we meet in a middle? More about that in the next post — and in comments below, if you like.

Helping publishers and advertisers move past the ad blockade

reader-publisher-advertiser

Those are the three market conversations happening in the digital publishing world. Let’s look into what they’re saying, and then what more they can say that’s not being said yet.

A: Publisher-Reader

Publishing has mostly been a push medium from the start. One has always been able to write back to The Editor, and in the digital world one can tweet and post in other places, including one’s own blog. But the flow and power asymmetry is still push-dominated, and the conversation remains mostly a one-way thing, centered on editorial content. (There is also far more blocking of ads than talk about them.)

An important distinction to make here is between subscription-based pubs and free ones. The business model of subscription-supported pubs is (or at least includes) B2C: business-to-customer. The business model of free pubs is B2B: business-to-business. In the free pub case, the consumer (who is not a customer, because she isn’t paying anything) is the product sold to the pub’s customer, the advertiser.

Publishers with paying subscribers have a greater stake — and therefore interest — in opening up conversation with customers. I believe they are also less interested in fighting with customers blocking ads than are the free pubs. (It would be interesting to see research on that.)

B. Publisher-Advertiser

In the offline world, this was an uncomplicated thing. Advertisers or their agencies placed ads in publications, and paid directly for it. In the online world, ads come to publishers through a tangle of intermediaries:

displaylumascape:

Thus publishers may have no idea at any given time what ads get placed in front of what readers, or for what reason. In service to this same complex system, they also serve up far more than the pages of editorial content that attracts readers to the site. Sight unseen, they plant tracking cookies and beacons in readers’ browsers, to follow those readers around and report their doings back to third parties that help advertisers aim ads back at those readers, either on the publisher’s site or elsewhere.

We could explore the four-dimensional shell game that comprises this system, but for our purposes here let’s just say it’s a B2B conversation. That it’s a big one now doesn’t mean it has to be the only one. Many others are possible.

C. Reader-Advertiser

In traditional offline advertising, there was little if any conversation between readers and advertisers, because the main purpose of advertising was to increase awareness. (Or, as Don Marti puts it, to send an economic signal.) If there was a call to action, it usually wasn’t to do something that involved the publisher.

A lot of online advertising is still that way. But much of it is direct response advertising. This kind of advertising (as I explain in Separating Advertising’s Wheat and Chaff) is descended not from Madison Avenue, but from direct mail (aka junk mail). And (as I explain in Debugging adtech’s assumptions) it’s hard to tell the difference.

Today readers are speaking to advertisers a number of ways:

  1. Responding to ads with a click or some other gesture. (This tens to happen at percentages to the right of the decimal point.)
  2. Talking back, one way or another, over social media or their own blogs.
  3. Blocking ads, and the tracking that aims them.

Lately the rate of ad and tracking blocking by readers has gone so high that publishers and advertisers have been freaking out. This is characterized as a “war” between ad-blocking readers and publishers. At the individual level it’s just prophylaxis. At the group level it’s a boycott. Both ways it sends a message to both publishers and advertisers that much of advertising and the methods used for aiming it are not welcome.

This does not mean, however, that making those ads or their methods more welcome is the job only of advertisers and publishers. Nor does it mean that the interactions between all three parties need to be confined to the ones we have now. We’re on the Internet here.

The Internet as we know it today is only twenty years old: dating from the end of the NSFnet (on 30 April 1995) and the opening of the whole Internet to commercial activity. There are sand dunes older than Facebook, Twitter — even Google — and more durable as well. There is no reason to confine the scope of our invention to incremental adaptations of what we have. So let’s get creative here, and start by looking at, then past, the immediate crisis.

People started blocking ads for two reasons: 1) too many got icky (see the Acceptable Ads Manifesto for a list of unwanted types); 2) unwelcome tracking. Both arise from the publisher-advertiser conversation, which to the reader (aka consumer) looks like this:

rotated

Thus the non-conversation between readers blocking ads and both publishers and advertisers (A and C) looks like this:

stophandsignal

So far.

Readers also have an interest in the persistence of the publishers they read. And they have an interest in at least some advertisers’ goods and services, or the marketplace wouldn’t exist.

Thus A and C are conversational frontiers — while B is a mess in desperate need of cleaning up.

VRM is about A and C, and it can help with B. It also goes beyond conversation to include the two other activities that comprise markets: transaction and relationship. You might visualize it as this:

Handshake_icon_GREEN-BLUE.svg

From Turning the customer journey into a virtuous 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?

So here are two questions for the VRM community:

  1. What are we already doing in those areas that can help move forward in A and B?
  2. What can we do that isn’t being done now?

Among things we’re already doing are:

  • Maintaining personal clouds (aka vaults, lockers, personal information management systems, et.al.) from which data we control can be shared on a permitted basis with publishers and companies that want to sell us stuff, or with which we already enjoy relationships.
  • Employing intelligent personal assistants of our own.
  • Intentcasting, in which we advertise our intentions to buy (or seek services of some kind).
  • Terms individuals can assert, to start basing interactions and relationships on equal power, rather than the defaulted one-way take-it-or-leave-it non-agreements we have today.

The main challenge for publishers and advertisers is to look outside the box in which their B2B conversation happens — and the threats to that box they see in ad blocking — and to start looking at new ways of interacting with readers. And look for leadership coming from tool and service providers representing those readers. (For example, Mozilla.)

The main challenge for VRM developers is to provide more of those tools and services.

Bonus links for starters (again, I’ll add more):

Loyalty means nothing if customers don’t have their own ways of expressing it

nomorecards

@jobsworth and I were just pointed by @aainslie to a @ronmiller piece in @TechCrunch titled In The Age of Disruption, Customer Love Is More Important Than Ever.

The headline says it all, and it’s true. But, as with all pieces like this, it’s about what companies can (or should) do, rather than what customers can do.

Think about it. What if customers had their own systematic methods of expressing loyalty? Not silo-provided gimmicks like Facebook’s “like” buttons, but standard tools or systems that every customer could use, as easily as they use their own wallets or phones.

Think about how much better it would be for the whole marketplace if we built loyalty tools and systems where loyalty actually resides: on the customer’s side. What customers express through these tools and systems would be far more genuine and meaningful than any of today’s silo’d and coercive “loyalty programs,” which inconvenience everybody and yield rewards worth less than the time wasted by everybody dealing with them.

If loyalty systems are left entirely up to the sellers of the world, we’ll have as many different systems as we have sellers. Which, of course, is what we already have, and it’s a royal mess.

As it happens, loyalty is one VRM development area where there is nothing going on, so far — or at least nothing that fits the description I just made.

So maybe it’s about time to get started. Looks like a greenfield to me.

Speaking of which, I’ll betcha there is stuff that already exists within CRM systems that could be ported over to the customer side, and then match up with seller-side CRM stuff. Be interesting to hear from CRM folks about that. Here’s the key thing, though: customer VRM loyalty tools need to work with all CRM systems. (Just like, say, browsers, email and other standard customer-side tools also do.)

First we take Oz

Sydneydoc 017-018_combined_medAustralia’s privacy principles are among the few in the world that require organizations to give individuals personal information gathered about them.* This opens the path to proving that we can do more with our own data than anybody else can.

Estimating the size of the personal data management business is like figuring the size of the market for talking or driving. (Note: we can also do more with those than companies can.)

Starting us down this path is  Ben Grubb (@BenGrubb) of the Sydney Morning Herald. Ben requested personal data held by the Australian telco giant Telstra, and found himself in a big fightwhich he won. (Here’s the decision. Telstra is appealing, but they’re still gonna lose.)

Bravo to Ben — not just for whupping a giant, but for showing a path forward for individual empowerment in the marketplace. Thanks to Australia’s privacy principles, and Ben’s illustrative case, the yellow brick road to the VRM future is widest in Oz.

Here (and in New Zealand) we not only have lots of VRM developers (Flamingo, Fourth Party, Geddup, Meeco, MyWave, OneExus, Welcomer and others I’ll insulting by not listing yet), but legal easement toward proving that individuals can do the more with their own data than can the companies that follow us. And proving as well that individuals managing their own data will be good for those companies as well. The data they get will be richer, more accurate,  more contextual, and more useful.

This challenge is not new. It’s as old as our species. The biggest tech revolutions have always been inventions individuals could put to the best use:

  • Stone tools
  • Weaving
  • Smithing
  • Musical instruments
  • Hand-held hunting and fighting tools
  • Automobiles
  • PCs
  • The Internet (which is a node-to-node invention, not an advanced phone or cable company, even though we pay those things for access to it)
  • Mobile phones and tablets
  • Movable type (which would be nowhere without individual authors — and writing tools in the hands of those authors)

There should be symbiosis here. There are things big organizations do best, and things individuals do best. And much that both do best when they work together.

Look at cars, which are a VRM technology: we use them to get around the marketplace, and to help us do business with many companies. They give us ways to be both independent and engaging. But companies don’t drive them. We do. Companies provide parking lots, garages, drive-up windows and other conveniences for drivers. Symbiosis.

So, while Telstra is great at building and managing communication infrastructure and services, its customers will be great at doing useful stuff with the kind of data Ben requested, such as locations, calls and texts — especially after customers get easy-to-use tools and services that help them work as points of integration for their own data, and managers of what gets done with it. There are many VRM developers working toward that purpose, around the world, And many more that will come once they smell the opportunities.

These opportunities are only apparent when you look at the market through your own eyes as a sovereign human being. The same opportunities are mostly invisible when you look at the market from the eye at the top of the industrial pyramid.

Bonus links:


* My understanding is that privacy principles such as the OECD’s and Ontario’s provide guidance but not the full force of law, or means of enforcement. Australia’s differ because they have teeth. See the Determination on page 36 of the Privacy Commissioner’s investigation and decision. Canada’s also has teeth. See the list of orders issued in Ontario. If there are other examples of decisions like this one, anywhere in the world, please let us know.

The most important event, ever

IIW XXIIW_XX_logothe 20th IIW — comes at a critical inflection point in the history of VRM. If you’re looking for a point of leverage on the future of customer liberation, independence and empowerment, this is it. Wall Street-sized companies around the world are beginning to grok what Main Street ones have always known: customers aren’t just “targets” to be “acquired,” “managed,” “controlled” and “locked in.” In other words, Cluetrain was right when it said this, in 1999:

if you only have time for one clue this year, this is the one to get…

Now it is finally becoming clear that free customers are more valuable than captive ones: to themselves, to the companies they deal with, and to the marketplace.

But how, exactly? That’s what we’ll be working on at IIW, which runs from April 7 to 9 at the Computer History Museum, in the heart of Silicon Valley: the best venue ever created for a get-stuff-done unconference. Focusing our work is a VRM maturity framework that gives every company, analyst and journalist a list of VRM competencies, and every VRM developer a context in which to show which of those competencies they provide, and how far along they are along the maturity path. This will start paving the paths along which individuals, tool and service providers and corporate systems (e.g. CRM) can finally begin to fit their pieces together. It will also help legitimize VRM as a category. If you have a VRM or related company, now is the time to jump in and participate in the conversation. Literally. Here are some of the VRM topics and technology categories that we’ll be talking about, and placing in context in the VRM maturity framework:

Designing the VRM future at IIW

A veteran VRooMeriiwxx tells me a design fiction would be a fun challenge for VRM Day and IIW (which will run from April 6-9 at the Computer History Museum in Mountain View, CA).

He describes one as “basically a way of peeking into the near future by demonstrating an imaginary product that doesn’t exist, but could. For example, instead of talking about a possible VRM product, one instead would create a marketing brochure, screen mockups or a fake video advertisement for this imaginary product as a way to help others understand where the world is headed and possibly even further the underlying technologies or driving concepts.”

Coincidentally, the subject of VRM Day (and a focus for the three days that will follow at IIW) is a maturity model framework that will provide every VRM developer the same single sheet (or set of them) on which to show where they stand in developing VRM capabilities into their company, product, code base or whatever else they’re working on. Work has already started on it, and those doing the work will present a first draft of it on VRM Day.

You know the old saying, “all singing from the same song sheet”? The VRM maturity model framework is it. Think of it as a musical score that is starting to be written, for an orchestra will come together. When we’re done with this round, we’ll at least know what the score describes, and give the players of different instruments enough of a framework so they know where they, and everybody else, fits.

By the end of IIW, it should be ready to do several things:

  1. Provide analysts with a single framework for understanding all VRM developers and development, and the coherencies among them.
  2. Give VRM developers a way to see how their work complements and/or competes with other VRM work that’s going on — and guide future developments.
  3. Give each developer a document to use for their own internal and external purposes.
  4. Give CRM, CE. CX and other vendor-side systems a clear picture of what pieces in the VRM development community will connect with their systems, and how, so buyer-side and seller-side systems can finally connect and grow together.

While we do this, it might also be fun to work out a design fiction as a summary document or video. What would the complete VRM solution (which will surely be a collection of them) look like? How would we present it as a single thing?

All of this is food for thinking and re-thinking. Suggestions invited.

Older posts

© 2016 ProjectVRM

Theme by Anders NorenUp ↑