Category: VRM (page 1 of 20)

If your voice comes from a company, you don’t have one

Got this in my email today:

Oracle pitch

I’m sure Oracle Service Cloud is good at what it does. Such as:

  • Deliver an integrated customer experience while equipping employees with the right tools
  • Drive and meet consumer expectations in the new omni-channel world
  • Adapt their service to customer needs by researching and considering their demographics

The problem is that this assumes customers have no voices of their own, and need to be given one. And, since every company has its own way to give customers voices, the customer turns into a Tower of Babble, speaking with many different voices to many different companies.

For example, today at a medical center I had to give exactly the same personal information to two different systems operating in the same office — and this was information already known to countless other systems with which I’ve had dealings over the years. Why? “Because we’re using two different CRM systems.”

You can look at the problem here as one of scale. Systems such as Oracle’s give companies scale: one way to deal with many different customers. Likewise, customers need one way to deal with many different companies, regardless of what CRM systems they run. This is a fundamental VRM challenge. And it’s one that should be good for CRM too. Win-Win.

You can see how it would work if you imagine being able to  change your phone number or email address, for every company you deal with, in one move. Lots of VRM developers are working on that, but we aren’t there yet.

It helps that we already have the Internet, which bridges many networks (why it’s called internet), along with email, phones and other things that give us one way to deal with many different entities.

But we don’t yet have voices of our own (meaning scale), or we wouldn’t see headlines like the one above.

Giving our voices scale isn’t a CRM job. It’s a VRM job. It also has to be done in a way that speaks directly to the Oracle Service Clouds of the world, engaging what they already have in place.

I know people at Oracle and its competitors who are ready and eager to see VRM developments that speak — literally and figuratively — to their corporate systems. They know VRM is going to make their jobs a lot easier and cause a lot more business to happen and improve.

Conversations are happening, and that’s good. But we also need more development in the direction of convergence. Expect to see reports on that in coming months.

Privacy isn’t about secrecy and freedom isn’t about license. Both are about agency.

Agency is the power to act with effect in the world. We have agency when we type on a keyboard, hammer a nail, ride a horse or drive a car.  Here’s a dictionary definition:

a·gen·cy (ā′jən-sē)
noun.

  1. The condition of being in action; operation.
  2. The means or mode of acting; instrumentality.

It is derived from agere: Latin for to do.

We are built to do a lot: with our brains, our opposable thumbs, our lack of fur, our capacity to sweat and to learn — and our strange ability to walk or run on two feet instead of four (almost ceaselessly, at least when we are young and fit) — we can do an amazing variety of things with our bodies.

For what we can’t do, we invent tools and machines. These extend our agency outward through technology. A hammer becomes another length of arm. With one in our hand, we have the power to drive nails with a metal fist. A car gives us an engine and wheels, so we can zoom down roads at dozens of miles (or kilometers) per hour. A plane gives us engines and wings, so we can fly far and high.  Each expands our agency to distant horizons of effect and experience in the world.

Infrastructure and services expand what each and all of us can do as well. But at the base of human capacity is the individual’s ability to do stuff in the world. Or, in a word, agency.

Which brings me to the second world we built alongside the physical one we all share. That second world is the Internet: a Giant Zero shaped by an oddly simple protocol: TCP/IP. Never mind how it works. Just note what it does: reduce to zero the functional distance between everything and everybody on it. Also the cost.

As a way to expand human agency, the Internet has no rivals. It gives all our voices, all our ideas, all our actions, worldwide scale. Any of us can speak, write, publish and much more, across any distance, at levels of inconvenience and cost that veer toward zero.

And we’ve been doing that, routinely, ever since the Internet assumed its current form. (That happened in April 1995, when the NSFnet‘s backbone — one network within the Internet — was decommissioned and commercial activity, which the NSFnet forbade, could begin to flourish across the whole Net.)

The Net has an end-to-end architecture. Every body and every thing is an end point, and the Net’s protocol does its best to move data between any and all of those. This is what Paul Baran, one of the Net’s fathers, described as a distributed design, rather than a centralized or decentralized one. Here is how he illustrated the difference, way back in 1962:

Paul Baran, On Distributed Communications Networks, 1962

And that became the Net’s basic design. Or at least its ideal.

Yet, for the sake of convenience — especially in the early days of the Net, when most of us were still on dial-up — we defaulted to a client-server architecture for deploying servers and services. With client-server, each server is a central point, which makes the Net, in a practical sense, a decentralized thing, rather than a distributed one.

And yet the distributed nature of the Net persists, grounding our agency in the world it defines.

Conflicts between centralized, decentralized and distributed capacities on the Net — and uneven development of tools and services enlarging our agency — are behind many of our crises on the Net today.

Take privacy for example. It’s a huge issue. Survey after survey (e.g. from Pew, TRUSTe and Customer Commons) say that 90% and more of us are concerned about personal privacy on the Net, don’t trust many service providers, or lie and hide to obscure personal identity. Advertising and tracking blockers are the most popular browser extensions, and with good reason: we are still naked on the Net.

That’s because the Net, like nature in the physical world, doesn’t come with privacy installed. We have to make it for ourselves. In the physical world we did it by inventing clothing and shelter. In the virtual world we still don’t have either. Tracking blockers are fig leaves at best. They also all work differently. We are still in early times.

Since we have no privacy yet (other than by staying off the Net, or by isolating ourselves on it by declining to accept cookies and staying away from services such as Google’s and Facebook’s), we tend to think about privacy in terms of secrets: things we don’t want others to know about us. But think instead about what we do to create privacy in the physical world, with clothing and shelter. Both do more than cover our bodies and and our lives. We express both. We also express with them. Our clothing and shelter send signals about ourselves. They speak of our tastes, our gender, our status, our memberships. Most of these speakings are subtle, but many are not. What matters is that they all valve our exposure to others. Buttons and zippers on our clothes speak of what can, can’t and shouldn’t be opened by others, without permission. Doors, shades and shutters on our homes do the same.

All of those things facilitate our agency. We need the same in the networked world.

The main difference is that we’ve had thousands of years to work them out in the physical world, and just twenty in the networked one. In the history of civilization, and even of business, this is close to nothing. We’re barely started.

There will, inevitably, emerge a symbiosis between centralized, decentralized and distributed capacities. Brian Behlendorf uses the term “minimum viable centralization” to label what we’re looking for here. Meanwhile we have maximum viable centralization on a network that is also distributed by design. Just like the humans on it.

We are seeing today a collapse of intermediary institutions. Publishing (e.g. blogs) Hospitality (e.g. Airbnb), dispatch (e.g. Uber), broadcast (e.g. Meerkat and Periscope) and payments (e.g.  Bitcoin) come quickly to mind, and many more are coming along. Yet through all of those there must remain some degree of trust in the graces that institutions — governments and companies — alone can provide. How can their minimum viable agencies help us enlarge our own? That’s the main challenge for the coming years.

The question we need to ask, as we address that challenge through VRM, is this: What is best done by the individual, and what is best done by the institution — and how an the two work together?

To answer that, agency must be key. Without it we’ll only get more centralized BS to distrust.

 

 

 

Declaration of Customer Independence

I published one of these five years ago, way ahead of its time, which I believe has now come. (Evidence:  @BenGrubb‘s victory over Telstra.*)

So here we go again:

Declaration

We hold these truths to be self-evident: that all customers are born free, that they are endowed by their creator with innate abilities to relate, to converse and and to transact — on their own terms, and in their own ways. When sellers have labored long and hard to restrict those freedoms, and to ignore and insult the capacities enjoyed naturally by customers — by speaking, for example, of “targeting,” “capturing,” “acquiring,” “retaining,” “managing,” “locking in” and “owning” customers as if they were slaves  — and when sellers work to inconvenience customers to the exclusive benefit of sellers themselves, for example through “loyalty programs” that require customers to carry around cards that thicken’ wallets and slow checkout in stores, it is the right of customers to obsolete the coercive systems to which both sellers and customers have become accustomed. We do this by providing ourselves with new tools for leveraging our native human powers, for the good of ourselves and sellers alike.

We therefore resolve to construct relationships in which we, the customers, control our own data, hold rights to metadata about ourselves, express loyalty at our own grace, deal in common and standard ways with all sellers and other second and third parties, protect our private persons and spaces, assert fair terms and means of engagement that work in mutually constructive ways for both ourselves and the other parties we engage, for the good of all.

We make this Declaration as free and independent persons, each with full agency, ready to form agreements, make choices, assert commitments, transact business, and otherwise function in the free and open environment we call The Marketplace.

To this we pledge our lives, our fortunes, and our precious time and attention.

Comments and improvements welcome.

*Read the whole thing. It matters. Hugely.

By the way, I’ll be in New Zealand and Australia the week after next, keynoting Identity 2015 in Wellington and Customer Tech X in Melbourne, where I will also be on a number of panels. I’ll also be in Sydney for one day before heading back. Hope I can also hook up with some  of the growing number of VRM companies there. There are many on the VRM Developers List. (More on a separate post later.)

Of vaults and honey pots

Personal Blackbox (pbb.me) is a new #VRM company — or so I gather, based on what they say they offer to users: “CONTROL YOUR DATA & UNLOCK ITS VALUE.”

So you’ll find them listed now on our developers list.

Here is the rest of the text on their index page:

pbbWheel

PBB is a technology platform that gives you control of the data you produce every day.

PBB lets you gain insights into your own behaviors, and make money when you choose to give companies access to your data. The result? A new and meaningful relationship between you and your brands.

At PBB, we believe people have a right to own their data and unlock its benefits without loss of privacy, control and value. That’s why we created the Personal Data Independence Trust. Take a look and learn more about how you can own your data and its benefits.

In the meantime we are hard at work to provide you a service and a company that will make a difference. Join us to participate and we will keep you posted when we are ready to launch.

That graphic, and what seems to be said between the lines, tells me Personal Blackbox’s customers are marketers, not users.  And, as we so often hear, “If the service is free, you’re the product being sold.”

But, between the last paragraph and this one, I ran into Patrick Deegan, the Chief Technology Officer of Personal Blackbox, at the PDNYC meetup. When I asked him if the company’s customers are marketers, he said no — and that PBB (as it’s known) is doing something much different that’s not fully explained by the graphic and text above, and is tied with the Personal Data Independence Trust, about which not much is said at the link to it. (At least not yet. Keep checking back.) So I’ll withhold judgement about it until I know more, and instead pivot to the subject of VRM business models, which that graphic brings up for me.

I see two broad ones, which I’ll call vault and honey pot.

The vault model gives the individual full control over their personal data and what’s done with it, which could be anything, for any purpose. That data primarily has use value rather than sale value.

The honey pot model also gives the individual control over their personal data, but mostly toward providing a way to derive sale value for that data (or something similar, such as bargains and offers from marketers).

The context for the vault model is the individual’s whole life, and selective sharing of data with others.

The context for the honey pot model is the marketplace for qualified leads.

The vault model goes after the whole world of individuals. Being customers, or consumers, is just one of the many roles we play in that world. Who we are and what we do — embodied in our data — is infinitely larger that what’s valuable to marketers. But there’s not much money in that yet.

But there is in the honey pot model, at least for now. Simply put, the path to market success is a lot faster in the short run if you find new ways to help sellers sell.  $zillions are being spent on that, all the time. (Just look at the advertising coming along with that last link, to a search).

FWIW, I think the heart of VRM is in the vault model. But we have a big tent here, and many paths to explore. (And many metaphors to mix.)

Toward VRooMy privacy policies

Canofworms1In The nightmare of easy and simple, T.Rob unpacks the can of worms that is:

  1. one company’s privacy policy,
  2. provided by another company’s automatic privacy policy generating system, which is
  3. hosted at that other company, and binds you to their privacy policy, which binds you to
  4. three other companies’ privacy policies, none of which assure you of any privacy, really. Then,
  5. the last of these is Google’s, which “is basically summed up as ‘we own your ass'” — and worse.

The company was GeniCan — a “smart garbage can” in the midst of being crowdfunded. GeniCan, like so many other connected devices, lives in the Internet of Things, or IoT. After exploring some of the many ways that IoT is already FUBAR in the privacy realm, T.Rob offers some constructive help:

The VRM Version
There is a possible version of this device that I’d actually use.  It would be the one with the VRM-ypersonal cloud architecture.  How does that work?  Same architecture I described in San Francisco:

  • The device emits signed data over pub/sub so that secondary and tertiary recipients of data can trust it.

  • By default, the device talks to the vendor’s service so users don’t need any other service or device to make it work.

  • The device can be configured to talk to a service of the user’s choosing instead of, or in addition to that of the manufacturer.

  • The device API is open.

Since privacy policy writing for IoT is pretty much a wide-open greenfield, that provides a helpful starting point. It will be good to see who picks up on it, and how.

How Staples can make things easy for real

Staples likes to make things easy. s0105150_sc7Or so their button says.

But rebates in general are hard — on both the store and the customer. And at that Staples is no exception.

For example, yesterday at a Staples store I bought a couple reams of Staples paper for our printer. I probably would have bought the Staples brand anyway, simply because it’s cheaper. But I also couldn’t ignore the after-rebate price: $1.50 less for each ream, or $3.00 total. So I asked at the cash register if what I paid included the rebate. No, I was told. The rebate is in the electronic receipt I’d get by email. I could send in for the rebate online after getting the email.

When I got home the receipt was waiting in my email inbox. Among many other promotions in the email, it said this about my rebate:

Screen Shot 2015-04-02 at 12.18.33 AM

When I clicked on the link I got to this:

Screen Shot 2015-04-02 at 12.19.34 AM

When I clicked on “SELECT FORM” I got this:

Screen Shot 2015-04-02 at 12.22.06 AM

For $3, fulling out something like that, and mailing it in, is worse than a waste. So I clicked on the “right here” link, which led me here:

Screen Shot 2015-04-02 at 12.24.13 AM

So I clicked on the center one. That got me here:

Screen Shot 2015-04-02 at 12.26.49 AM

So: what was the Easy Rebate ID? All I saw, so far, was a “Rebate offer number,” on the email and back at the page that the email link brought up. So I entered it in the form and hit “NEXT.” That got me this:

Screen Shot 2015-04-02 at 12.29.23 AM

After going “Hmmm… ” I scrolled down and saw this:

Screen Shot 2015-04-02 at 12.31.45 AM

Sure enough, at the bottom of the very long email with the rebate jive on it, was this:

Mail Attachment

I entered that number, and it worked.  Hitting “NEXT” then took me here:

Screen Shot 2015-04-02 at 12.37.02 AM

When I clicked on NEXT again, I got to a page where I could register for a rebate account (by filling out a form that mined way too much personal information) or sign in. I have a Staples loyalty account; so, hoping that this might also be the rebate account, I hit “Sign in.”

I would show you the page this went to, if I could have copied it. But I couldn’t. The page had the same “Staples Easy Rebates” header, and under it just two words: “Error occurred.” When I paged down to see if there was more, the page disappeared and I was delivered back to Square Zero: the “Welcome to the Staples Rebate Center” page.

Since everything I already entered was lost, and I had no faith that entering it again would yield a different result, I gave up.

In retail parlance, this is called “breakage.” Within rebate systems, some level of breakage is a virtue. You (the retailer) don’t want everybody getting a rebate. You want as few people as possible asking for the rebate, and as few as possible succeeding at navigating an intentionally complicated series of required steps for getting the rebate. Most customers know this, of course, but every once in awhile some of us want to see if we get lucky.

This is not a good “customer experience.”In what marketers love to call “the customer journey,” it’s a wasteful and annoying side trip to an outer circle of retail hell.

So here’s a message from one customer to every retailer running a rebate program:

Any system that rationalizes breakage as a virtue is broken itself, for the simple reason that it pisses off customers. And if you want to piss off any percentage of customers — even good ones — some of the time, your whole store is broken.

So here’s a bottom line I invite Staples to consider:

Rebates save money if your time has no value. This principle applies equally to customers and companies offering rebates.

As a loyal customer of Staples — a company I’ve always liked (partly because of the “easy” promise, which they’ve been making for many years — my advice is to calculate all the overhead involved in all the promotional gimmickry used to drive sales and “loyalty” that isn’t. Include time wasted at the cash register every time the employee has to ask for a loyalty card  or a phone number to recover the customer’s account, and to explain how a rebate works, plus other extraneous bullshit that has that takes time and incurs labor costs for purposes that have nothing to do with why the customer is standing at the checkout counter, just wanting to pay for goods and  get the hell out of the store. Also include the inconvenience to the customer of having to carry around a card, and the corresponding administrative overhead required to manage all this complicated work, and the computing and network technology required to sustain it (and how that gets broken too). Multiply those by all the employees and customers inconvenienced by it. Then add all of it up. Be real about what percentage of your total overhead it accounts for. Remember to include the real costs to customer loyalty of pissing some of them off on purpose.

Then kill the whole thing and subtract the savings from the prices of the goods in the store. Publicize it. Hey, hold a public execution of all the added-up costs to company and customers. Talk about it as real savings, which it is. Publish papers and place editorials explaining why you’re done with the game of kidding yourselves and your customers. I know plenty of good PR firms that would be glad to help you out with this — and maybe even cut you a deal, because they’re tired of bullshitting too.

In Silicon Valley they call this “disruption.” It’s a great way to stand out, and to reposition both Staples and all of retailing.

And your customers will love it.

Don’t trust me on this. Trust  Trader Joe’s. They don’t have a loyalty program, rebates or any other gimmicks. They never have discount prices. They don’t keep any data on any customers, because they don’t want the overhead, or to complicate anybody’s life. Their marketing research — no kidding — consists of this: talking to customers. That’s it. And what’s the result? Customers love them.*

Now you might say, “Yes, but Trader Joe’s is a special case. So are companies like Apple — another company customers seem to love. They only sell their own private label goods. They don’t operate in the world of co-op advertising, dealer premiums, display allowances, buyback allowances, push money, spiffs, forward buying, variable trade spending and trade deals, manufacturer coupons and all the other variables that retailers like Staples, which carry goods from hundreds of different suppliers, need to deal with constantly. And what about customers constantly hunting bargains, and comparison shopping? They want deals, and we have to compete for them.”

Sure. But why make it more complicated than it has to be?

If you really want to make things easy, for yourself and your customers, kill the bullshit. Be the no-bullshit company. Nothing would make you stand out more.

Nothing is easier, for everybody in retailing, than no bullshit at all. Or more rewarding, because customers appreciate absent bullshit at least as much as they appreciate present bargains. Especially bargains that come with labor costs — for them.

Source: The Intention Economy, pp. 223-228.

Preparing for the 3D/VR future

Look in the direction that meerkatMeerkat and periscopeappPeriscope both point.

If you’ve witnessed the output of either, several things become clear about their evolutionary path:

  1. Stereo sound is coming. So is binaural sound, with its you-are-there qualities.
  2. 3D will come too, of course, especially as mobile devices start to include two microphones and two cameras.
  3. The end state of both those developments is VR, or virtual reality. At least on the receiving end.

The production end is a different animal. Or herd of animals, eventually. Expect professional gear from all the usual sources, showing up at CES starting next year and on store shelves shortly thereafter. Walking around like a dork holding a mobile in front of you will look in 2018 like holding a dial-phone handset to your head looks today.

I expect the most handy way to produce 3D and VR streams will be with  glasses like these:

srlzglasses

(That’s my placeholder design, which is in the public domain. That’s so it has no IP drag, other than whatever submarine patents already exist, and I am sure there are some.)

Now pause to dig @ctrlzee‘s Fast Company report on Facebook’s 10-year plan to trap us inside The Matrix. How long before Facebook buys Meerkat and builds it into Occulus Rift? Or buys Twitter, just to get Periscope and do the same?

Whatever else happens, the rights clearing question gets very personal. Do you want to be broadcast and/or recorded by others or not? What are the social and device protocols for that? (The VRM dev community has designed one for the glasses above. See the ⊂ ⊃ in the glasses? That’s one. Each corner light is another.)

We should start zero-basing the answers today, while the inevitable is in sight but isn’t here yet. Empathy is the first requirement. (Take the time to dig Dave Winer’s 12-minute podcast on the topic. It matters.) Getting permission is another.

As for the relevance of standing law, almost none of it applies at the technical level. Simply put, all copyright laws were created in times when digital life was unimaginable (e.g. Stature of Anne, ASCAP), barely known (Act of 1976), or highly feared (WIPO, CTEA, DMCA).

How would we write new laws for an age that has barely started? Or why start with laws at all? (Nearly all regulation protects yesterday from last Thursday. And too often its crafted by know-nothings.)

We’ve only been living the networked life since graphical browsers and ISPs arrived in the mid-90’s. Meanwhile we’ve had thousands of years to develop civilization in the physical world. Which means that, relatively speaking, networked life is Eden. It’s brand new here, and we’re all naked. That’s why it’s so easy anybody to see everything about us online.

How will we create the digital equivalents of the privacy technologies we call clothing and shelter? Is the first answer a technical one, a policy one, or both? Which should come first? (In Europe and Australia, policy already has.)

Protecting the need for artists to make money is part of the picture. But it’s not the only part. And laws are only one way to protect artists, or anybody.

Manners come first, and we barely have those yet, if at all. None of the big companies that currently dominate our digital lives have fully thought out how to protect anybody’s privacy. Those that come closest are ones we pay directly, and are financially accountable to us.

Apple, for example, is doing more and more to isolate personal data to spaces the individual controls and the company can’t see. Google and Facebook both seem to regard personal privacy as a bug in online life, rather than a feature of it. (Note that, at least for their most popular services, we pay those two companies nothing. We are mere consumers whose lives are sold to the company’s actual customers, which are advertisers.)

Bottom line: the legal slate is covered in chalk, but the technical one is close to clean. What do we want to write there?

We’ll be talking about this, and many other things, at VRM Day (6 April) and IIW (7-9 April) in the Computer History Museum in downtown Silicon Valley (101 & Shoreline, Mountain View).

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.

VRM Day and IIW XX

The most important weeks on the VRM calendar are those when IIW — the Internet Identity Workshop — takes place. There are two per year, in Spring and Fall, and they are hosted by Kaliya Hamlin,  Phil Windley and myself at the Computer History Museum in Silicon Valley.

The next is April 7-9. Leading into it is VRM Day, which is on April 6.

IIW is an unconference, which means there are no speakers or panels, and sponsors (which we appreciate hugely) just cover our meals, snacks and barista. All the topics of the workshop are vetted and posted the start of each of IIW’s three days, and every topic is discussed in breakout sessions spread across the venue’s many rooms and tables.

IIW is ideal for pushing topics and dev work forward. VRM has many topics, of course: intentcasting, personal data management (aka clouds, vaults, lockers, stores, services, etc.), VRM-meets-CRM (including CX, CE and other two- and three-letter acronyms), IoT, intelligent assistants, the Indie Web (and indie everything), emerging and wannabe standards and shared code bases, and all the other kinds of things listed on the ProjectVRM wiki development page.

This next one will be our XXth. All of them are important, but this one will be especially so, because we will be sorting out how various VRM projects fit together, compete, support each other, and engage systems on the big vendor and enterprise side.

In fact that topic will be the main focus of VRM Day, where we will vet a VRM framework document based on a maturity model that will give everybody a way to show how far along they are in different development areas.

This is the document VRM developers will share with analysts, enterprises and big vendors who need to know how real VRM is becoming, and who plays what roles in the emerging market space.

Here is the link to register for VRM Day.

And here is the one for IIW XX.

Look forward to seeing you there.

Older posts

© 2015 ProjectVRM

Theme by Anders NorenUp ↑