Category: open source (Page 1 of 4)

Syndication and the Live Web Economy

This is from a December 2009 newsletter called Suitwatch, which I wrote for Linux Journal, and was 404’d long ago. (But I kept the original.) I’m re-posting it here because I think syndication may be the most potent power any of us have in the Internet age—and because the really simple kind, RSS, has been with us since before I wrote this piece. (I also think RSS has VRM implications as well, but I’ll leave those for another post.) My only edits here were to remove arcana and anachronisms that are pointless today. This graphic illustrates how entrenched and widespread RSS already is:


Until recently, the verb “syndication” was something big publishers and agencies did. As a kid, I recognized “© King Features Syndicate” was the one unfunny thing about Blondie or Dennis the Menace. All it meant to me was that some kind of Business was going on here.

Now millions of individual writers syndicate their own work, usually through RSS (Really Simple Syndication). Publishers and other large organizations do too. This article is syndicated. So are updates to product manuals, changes to development wikis, updates on SourceForge, and searches of keywords. You name it: if there’s something that updates frequently on the Web, there’s a better chance every minute that the new stuff is syndicated if it isn’t already.

Far as I know, not many sources are making money with it. Lots, however, are making money because of it. The syndicated world may not look like an economy yet. But trust me, it is.

At this early stage in its long future history, syndication is primarily a feature of blogging, which is primarily the product of too many people to count. Blogging is not about large-scale things. It’s about human beings who have no scale other than themselves. Only you can be good at being you, and nobody else is the same as you. Syndication does more to expand individual human potential than anything since the invention of type. Or perhaps ever. The syndicated world economy is the one that grows around unleashed personal powers of expression, productivity, creation, distribution, instruction, influence, leadership, whatever.

In a loose sense, syndication is one side of the conversation. Think about conversation in the best sense of the word: as the way people teach and learn from each other, the way topics start and move along. Syndication makes that happen in huge ways.

The notion that “markets are conversation”, popularized by The Cluetrain Manifesto, was borrowed from this case I used to make for a form of marketing that was far more natural and powerful than the formal kind:

  1. Markets are conversation, and
  2. Conversation is fire. Therefore,
  3. Marketing is arson.

If you want to set fires, start conversations that tend to keep going. Nothing does the latter better than syndication.

There are three reasons why we still don’t hear as much about syndication as we should (and will). First, it’s still new. Second, it didn’t come from The Big Guys. (It came from Dave Winer, father of RSS — Really Simple Syndication.) Third, it points toward a value system not grounded only in exchange — one especially suited for the Net, a deeply ironic worldwide environment where everybody is zero distance apart.

But let’s park the value system until later and talk about next week. That’s when I’ll be in San Francisco for Syndicate. It’s the second in a series of conferences by that name. The first was in New York last Spring.

Since I’m the conference chair (disclosure: it’s a paying gig), and since I’ll be giving both the introductory talk and the closing keynote, Syndication is on the front burner of my mind’s stove.

There are others subjects there as well, some of which will be visited in sessions at the show. RSS, for starters. And tagging—a practice so new it’s not even close to having standards of the sort we find at OASIS, the IETF, and the W3C. Instead, it has emerging standards, like the ones we find at microformats.org.

Like syndication, tagging is a long-tail activity. Something individuals do. Along with blogging and syndication, it helps outline a new branch of the Net we’re starting to call the Live Web — as opposed to the Static Web with “sites” that are “built” and tend not to change.

The World Live Web is the title of my December Linux For Suits column in Linux Journal. In it, I note that the directoryless nature of everything on the Web falls in the Unix file path east of the domain name. Every path to a document (or whatever) is a piece of straw in the static Web’s haystack. Google and Yahoo help us find needles in that haystack, but their amazing success at search also tends to confirm the haystack nature of the Static Web itself.

The Live Web is no less webby than the Static Web. They’re both parts of the same big thing. But the Live Web is new and very different. It cannot be understood in Static Web terms.

In that piece, I also observed that blogs, as continuing projects by human authors, leave chronological trails. These give the Live Web something of a structure: a chronological one that goes /year/month/day/date/post, even if that’s not the way each post’s URL is composed. There is an implicit organizational structure here, and it’s chronological.

Tagging, by which individuals can assign categorical tags of their own to everything from links to bookmarks to photos, has given the Live Web an ad hoc categorical structure as well.

So that’s what we’re starting to see emerge here: chronology and category. Rudimentary, sure, but real. And significant.

But not organized. New practices, and new ideas, are coming along too fast.

What matters, above all, is user-in-charge: a form of personal agency in the connected world. That’s a concept so key to everything else that’s happening on the Web, even on the Static one, that we may need a new word for it.

Or an old one, like independencelibertysovereignty, or autonomy. That’s my inner Libertarian, choosing those. If your sensibilities run a bit more to the social side, you may prefer words like actualization or fulfillment. Point is, the Big Boys aren’t in charge anymore. You are. I am. We are.

There’s an economy that will grow around us. I think free software and open-source practices (see various books and essays by Richard M. Stallman and Eric S. Raymond) put tracks in the snow that point in the direction we’re heading, but the phenomenon is bigger than that.

It’s also bigger than Google and Yahoo and Microsoft and IBM and Sun and Red Hat and Apple and the rest of the companies people (especially the media) look to for Leadership. For all the good those companies do in the world, the power shift is underway and is as certain as tomorrow’s dawn. The Big Boys will need to take advantage of it. We’ll need them to, as well.

This power shift is what I’d like to put in front of people’s attention when they come to Syndicate next week, or when they follow the proceedings in blogs and other reports.

Now more than ever, power is personal. Companies large and small will succeed by taking advantage of that fact. And by watching developments that aren’t just coming from The Usual Suspects. Including the Usual Economic Theories.

For example, not everything in an economy is about exchange, or the value chain, or about trade-offs of this for that. Many values come out of effort and care made without expectation of return. Consider your love for your parents, spouses, children, friends, and good work. Consider what you give and still get to keep. Consider debts erased by forgiveness. Consider how knowledge grows without its loss by anyone else.

Sayo Ajiboye, the Nigerian minister who so blew my mind in conversations we had on a plane nearly five years ago (Google them up if you like), taught me that markets are relationships, and not just conversations. Relationships, he said, are not just about exchange. They cannot be reduced to transactions. If you try, you demean the relationships themselves.

Also, in spite of the economic framings of our talk about morality and justice (owing favors, paying for crimes, just desserts), there is a deeper moral system that cannot be understood in terms of exchange. In fact, when you bring up exchange, you miss the whole thing. (Many great teachers have tried in futility to make this point, and I’m probably not doing any better.) Whatever it is, its results are positive. Growth in one place is not matched by shrinking in another. Value in both systems is created. But in the latter one, the purpose is not always, or exclusively, exchange, or profit. At least not from the activity itself. There are because effects at work. And we’re only beginning to understand them, much less practice them in new ways.

Toward that end, some questions…

Where did the Static Web, much less the Live Web, come from? What is it for? What are we doing with it? Whatever the answers, nothing was exchanged for them. (No, not even the record industry, the losses of which owe to their own unwillingness to take advantage of new opportunities opened by the Net.)

Nor was anything exchanged for Linux, which has grown enormously.

As Greg Kroah-Hartman said recently on the Linux-Elitists list,

Remember, Linux is a species, and we aren’t fighting anyone here, we are merely evolving around everyone else, until they aren’t left standing because the whole ecosystem changed without them realizing it.

Yes, we have living ends.

Our radical hack on the whole marketplace

In Disruption isn’t the whole VRM story, I visited the Tetrad of Media Effects, from Laws of Media: the New Science, by Marshall and Eric McLuhan. Every new medium (which can be anything from a stone arrowhead to a self-driving car), the McLuhans say, does four things, which they pose as questions that can have multiple answers, and they visualize this way:

tetrad-of-media-effects

The McLuhans also famously explained their work with this encompassing statement: We shape our tools and thereafter they shape us.

This can go for institutions, such as businesses, and whole marketplaces, as well as people. We saw that happen in a big way with contracts of adhesion: those one-sided non-agreements we click on every time we acquire a new login and password, so we can deal with yet another site or service online.

These were named in 1943 by the law professor Friedrich “Fritz” Kessler in his landmark paper, “Contracts of Adhesion: Some Thoughts about Freedom of Contract.” Here is pretty much his whole case, expressed in a tetrad:

contracts-of-adhesion

Contracts of adhesion were tools industry shaped, was in turn shaped by, and in turn shaped the whole marketplace.

But now we have the Internet, which by design gives everyone on it a place to stand, and, like Archimedes with his lever, move the world.

We are now developing that lever, in the form of terms any one of us can assert, as a first party, and the other side—the businesses we deal with—can agree to, automatically. Which they’ll do it because it’s good for them.

I describe our first two terms, both of which have potentials toward enormous changes, in two similar posts put up elsewhere: 

— What if businesses agreed to customers’ terms and conditions? 

— The only way customers come first

And we’ll work some of those terms this week, fittingly, at the Computer History Museum in Silicon Valley, starting tomorrow at VRM Day and then Tuesday through Thursday at the Internet Identity Workshop. I host the former and co-host the latter, our 24th. One is free and the other is cheap for a conference.

Here is what will come of our work:
personal-terms

Trust me: nothing you can do is more leveraged than helping make this happen.

See you there.

 

“Disruption” isn’t the whole VRM story

250px-mediatetrad-svg

The vast oeuvre of Marshall McLuhan contains a wonderful approach to understanding media called the tetrad (i.e. foursome) of media effects.  You can apply it to anything, from stone tools to robots. McLuhan unpacks it with four questions:

  1. What does the medium enhance?
  2. What does the medium make obsolete?
  3. What does the medium retrieve that had been obsolesced earlier?
  4. What does the medium reverse or flip into when pushed to extremes?

I suggest that VRM—

  1. Enhances CRM
  2. Obsoletes marketing guesswork, especially adtech
  3. Retrieves conversation
  4. Reverses or flips into the bazaar

Note that many answers are possible. That’s why McLuhan poses the tetrad as questions. Very clever and useful.

I bring this up for three reasons:

  1. The tetrad is also helpful for understanding every topic that starts with “disruption.” Because a new medium (or technology) does much more than just disrupt or obsolete an old one—yet not so much more that it can’t be understood inside a framework.
  2. The idea from the start with VRM has never been to disrupt or obsolete CRM, but rather to give it a hand to shake—and a way customers can pull it out of the morass of market-makers (especially adtech) that waste its time, talents and energies.
  3. After ten years of ProjectVRM, we still don’t have a single standardized base VRM medium (e.g. a protocol), even though we have by now hundreds of developers we call VRM in one way or another. Think of this missing medium as a single way, or set of ways, that VRM demand can interact with CRM supply, and give every customer scale across all the companies they deal with. We’ve needed that from the start. But perhaps, with this handy pedagogical tool, we can look thorugh one framework toward both the causes and effects of what we want to make happen.

I expect this framework to be useful at VRM Day (May 1 at the Computer History Museum) and at IIW on the three days that follow there.

Save

The new frontier for CRM is CDL: Customer Driven Leads

cdlfunnelImagine customers diving, on their own, straight down to the bottom of the sales funnel.

Actually, don’t imagine it. Welcome it, because it’s coming, in the form of leads that customers generate themselves, when they’re ready to buy something. Here in the VRM world we call this intentcasting. At the receiving end, in the  CRM world, they’re CDLs, or Customer Driven Leads.

Because CDLs come from fully interested customers with cash in hand, they’re worth more than MQLs (Marketing Qualified Leads) or  SQLs (Sales Qualifed Leads), both of which need to be baited with marketing into the sales funnel.

CDLs are also free.  When the customer is ready to buy, she signals the market with an intentcast that CRM systems can hear as a fresh CDL. When the CRM system replies, an exchange of data and permissions follows, with the customer taking the lead.

It’s a new dance, this one with the customer taking the lead. But it’s much more direct, efficient and friendly than the old dances in which customers were mere “targets” to be “acquired.”

The first protocol-based way to generate CDLs for CRM is described in At last, a protocol to connect VRM and CRM, posted here in August. It’s called JLINC. We’ll be demonstrating it working on a Salesforce system on VRM Day at the Computer History Museum in Silicon Valley, on Monday, October 24. VRM Day is free, but space is limited, so register soon, here.

We’ll also continue to work on CDL development  over the next three days in the same location, at the IIW, the Internet Identity Workshop. IIW is an unconference that’s entirely about getting stuff done. No keynotes, no panels. Just working sessions run by attendees. This next one will be our 23rd IIW since we started them in 2005. It remains, in my humble estimation, the most leveraged conference I know. (And I go to a lot of them, usually as a speaker.)

As an additional temptation, we’re offering a 25% discount on IIW to the next 20 people who register for VRM Day. (And it you’ve already reigstered, talk to me.)

Iain Henderson, who works with JLINC Labs, will demo CDLs on Salesforce. We also invite all the other CRM companies—IBM, Microsoft Dynamics, SAP, SugarCRM… you know who you are—to show up and participate as well. All CRM systems are programmable. And the level of programming required to hear intentcasts is simple and easy.

See you there!

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

At last, a protocol to connect VRM and CRM

person-entity

We’ve been waiting a long time for a protocol to connect VRM (customers’ Vendor Relationship Management) with CRM (vendors’ Customer Relationship Management).

Now we have one. It’s called JLINC, and it’s from JLINC Labs. It’s also open source. You’ll find it at Github, here. It’s still early, at v.0.3. So there’s lots of opportunity for developers and constructive hackers of all kinds to get involved.

Specifically, JLINC is a protocol for sharing data protected by the terms under which it is shared, such as those under development by Customer Commons and the Consent and Information Sharing Working Group (CISWG) at Kantara.

The sharing instance is permanently recorded in a distributed ledger (such as a blockchain) so that both sharer and recipient have a permanent record of what was agreed to. Additionally, both parties can build up an aggregated view of their information sharing over time, so they (or their systems) can learn from and optimize it.

The central concept in JLINC is an Information Sharing Agreement (ISA). This allows for—

  1. the schema related to the data being shared so that the data can be understood by the recipient without prior agreement
  2. the terms associated with the data being shared so that they can be understood by the recipient without prior negotiation
  3. the sharing instance, and any subsequent onward sharing under the same terms, to be permanently recorded on a distributed ledger of subsequent use (compliance and analytics)

To test and demonstrate how this works, JLINC built a demonstrator to bring these three scenarios to life. The first one tackled is Intentcasting , a long-awaited promise of VRM. With an Intencast, the customer advertises her intention to buy something, essentially becoming a qualified lead. (Here are all the ProjectVRM blog posts here with the Intentcasting tag.)

Obviously, the customer can’t blab her buying intention out to the whole world, or marketers would swarm her like flies, suck up her exposed data, spam her with offers, and sell or give away her data to countless other parties.

With JLINC, intention data is made available only when the customer’s terms are signed. Those terms specify permitted uses. Here is one such set (written for site visiting, rather than intentcasting):

UserSubmittedTerms2ndDraft

These say the person’s (first party’s) data is being shared exclusively with the second party (the site), for no limit in time, for the site’s use only, provided the site also obey the customer’s Do Not Track signal. I’m showing it because it lays out one way terms can work in a familiar setting

For JLINC’s intentcasting demonstration, terms were limited to second party use only, and a duration of thirty days. But here’s the important part: the intentcast spoke to a Salesforce CRM system, which was able to—

  1. accept or reject the terms, and
  2. respond to the intentcast with an offer,
  3. while the handshake between the two was recorded in a blockchain both parties could access

This means that JLINC is not only a working protocol, but that there are ways for VRM tools and systems to use JLINC to engage CRM systems. It also means there are countless new development opportunities on both sides, working together or separately.

Here’s another cool thing:  the two biggest CRM companies, Salesforce and Oracle, will hold their big annual gatherings in the next few weeks. This means JLINC and VRM+CRM can be the subjects of both conversation and hacking at either or both events. Specifically, here are the dates:

  1. Oracle’s OpenWorld 2016 will be September 18-22.
  2. Salesforce’s Dreamforce 2016  will be October 4-7.

Both will be at the Moscone Center in San Francisco.

Conveniently, the next VRM Day and IIW will both also happen, as usual, at the end of October:

  1. VRM Day will be October 24.
  2. Internet Identity Workshop (IIW’s XXIIIth) will be October 25-27.

Both will take place at the Computer History Museum, in downtown Silicon Valley. And JLINC, which was launched at the last VRM Day, is sure to be a main topic of discussion, starting at VRM Day and continuing through IIW, which I consider the most leveraged conference in the world, especially for the price.

If all goes well, we’ll have some examples of VRM+(Oracle and/or Salesforce) CRM to show off at Demo Day at IIW.

Love to see other CRM vendors show up too. You listening, SugarCRM? (I spoke about VRM+CRM at SugarCon in 2011. Here’s my deck from that talk. What we lacked then, and since, was a protocol for that “+”. Now we have it. )

Big HT to Iain Henderson of both JLINC Labs and Customer Commons, for guiding this post, as well as conducting the test that showed, hey, it can be done!

 

 

 

 

Save

The Castle Doctrine

home castle

The Castle doctrine has been around a long time. Cicero (106–43 BCE) wrote, “What more sacred, what more strongly guarded by every holy feeling, than a man’s own home?” In Book 4, Chapter 16 of his Commentaries on the Laws of England, William Blackstone (1723–1780 CE) added, “And the law of England has so particular and tender a regard to the immunity of a man’s house, that it stiles it his castle, and will never suffer it to be violated with impunity: agreeing herein with the sentiments of ancient Rome…”

Since you’re reading this online, let me ask, what’s your house here? What sacred space do you strongly guard, and never suffer to be violated with impunity?

At the very least, it should be your browser.

But, unless you’re running tracking protection in the browser you’re using right now, companies you’ve never heard of (and some you have) are watching you read this, and eager to use or sell personal data about you, so you can be delivered the human behavior hack called “interest based advertising.”

Shoshana Zuboff, of Harvard Business School, has a term for this:surveillance capitalism, defined as “a wholly new subspecies of capitalism in which profits derive from the unilateral surveillance and modification of human behavior.”

Almost across the board, advertising-supported publishers have handed their business over to adtech, the surveillance-based (they call it “interactive”) wing of advertising. Adtech doesn’t see your browser as a sacred personal space, but instead as a shopping cart with ad space that you push around from site to site.

So here is a helpful fact: we don’t go anywhere when we use our browsers. Our browser homes are in our computers, laptops and mobile devices. When we “visit” a web page or site with our browsers, we actually just request its contents (using the hypertext protocol called http or https).

In no case do we consciously ask to be spied on, or abused by content we didn’t ask for or expect. That’s why we have every right to field-strip out anything we don’t want when it arrives at our browsers’ doors.

The castle doctrine is what hundreds of millions of us practice when we use tracking protection and ad blockers. It is what called the new Brave browser into the marketplace. It’s why Mozilla has been cranking up privacy protections with every new version of Firefox . It’s why Apple’s new content blocking feature treats adtech the way chemo treats cancer. It’s why respectful publishers will comply with CHEDDAR. It’s why Customer Commons is becoming the place to choose No Trespassing signs potential intruders will obey. And it’s why #NoStalking is a good deal for publishers.

The job of every entity I named in the last paragraph — and every other one in a position to improve personal privacy online — is to bring as much respect to the castle doctrine in the virtual world as we’ve had in the physical one for more than two thousand years.

It should help to remember that it’s still early. We’ve only had commercial activity on the Internet since April 1995. But we’ve also waited long enough. Let’s finish making our homes online the safe places they should have been in the first place.

 

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:

The answer is #CFT: Clouds For Things

My last post asked, How do you maximize the help that companies and customers give each other? My short answer is in the headline above. Let me explain.

The house where I’m a guest in London has clouds for all its appliances. All the clouds are physical. Here they are:

House cloud

Here is a closer look at some of them:

House cloud closeup

Each envelope contains installation and instruction manuals, warranty information and other useful stuff. For example, today I used an instruction manual to puzzle out what these symbols on the kitchen’s built-in microwave oven mean:

knob

Now let’s say I didn’t have the directions handy. How would I find them? Obviously, on the Web, right? I mean, you’d think.

So I went to the site of Atag, the oven’s maker.  From eyeballing the microwave, I gathered that the one in the kitchen is  this one: the Combi-Microwave MA4211B. On the Atag website I found it buried in Kitchen Appliances —> Collection —> Microwaves, where it might also be the MA4211A or MA4211T. Hard to tell. Directions for its use appeared to be under Quality and Service —> Visit ATAG Service Support. There I found this:

atagservice

When I clicked on “Download the User Manual,” I got this:

atagusermanual

For “type number” I guessed MA4211B, entered it in the search field and got this:

atagresults

I got the same results clicking on both:

atagdownloadchoice

Nothing actually downloaded, and the Acrobat Reader information was useless to me. So I clicked on “No.” That got me this:

atagfail

I then hit “I want to stop.” That looped me back to the search panel, three screenshots up from here.

In other words, a complete fail. Since the copyright notice is dated 2007 — eight years ago — I assume this fail is a fossil.

There are three reasons for this fail, and why its endemic to the entire service industry:

  1. The company bears the full burden of customer service.
  2. Every company serves customers differently.
  3. There is no single standard or normalized way for companies and customers to inform each other online.

What’s missing is a way to give customers scale — for the good of both themselves and the companies they deal with. Customers have scale with cash, credit cards, telephony, email and many other tools and systems. But not yet with a mechanism for connecting to any company and exchanging useful information in a standard way.

We’ve  been moving in that direction in the VRM development community, by working on personal data services, stores, lockers, vaults and clouds. Those are all important and essential efforts, but they have not yet converged around common standards, protocols and customer experiences. Hence, scale awaits. What this house models, with its easily-accessed envelopes for every appliance, is a kind of scale: a simple and standardized way of dealing with many different suppliers — a way that is the customer’s own.

Now let’s imagine a simple  digital container for each appliance’s information: its own cloud. In form and use, it would be as simple and standard as a file folder. It would arrive along with the product, belong to the customer*, and live in the customer’s own personal data service, store, locker, vault, cloud or old-fashioned hard drive.  Or, customers could create them for themselves, just like the owner of the house created those file folders for every appliance. Put on the Net, each appliance  would join the Internet of Things, without requiring any native intelligence on the things themselves.

There, on the Net, companies could send product updates and notifications directly into the clouds of each customer’s things. And customers could file suggestions for product improvements, along with occasional service requests.

This would make every product’s cloud a relationship platform: a conduit though which the long-held dreams of constant product improvement and maximized customer service can come true.

Neither of those dreams can come true as long as every product maker bears the full responsibility for intelligence gathering and customer support — and does those  differently than every other company. The only way they can come true is if the customers and their things have one set of standard ways to stay in touch and help each other. That’s what clouds for things will do. I see no other way.

So let’s get down to it, starting with a meme/hashtag representing Clouds For Things : #CFT.

Next, #VRM developers old and new need to gather around standard code, practices and protocols that can make #CFT take off.  Right now the big boys are sucking at that, building feudal fiefdoms that give us the AOL/Compuserve/Prodigy of things, rather than the Internet of Things.  For the whole story on this mess, read Bruce Sterling‘s e-book/essay The Epic Struggle for the Internet of Things, or the chunks of it at BoingBoing and in this piece I wrote here for Linux Journal.

We have a perfect venue for doing the Good Work required for both IoT and CFT — with IIW, which is coming up early this spring: 7-9 April. It’s an inexpensive unconference in the heart of Silicon Valley, with no speakers or panels. It’s all breakouts, where participants choose the topics and work gets done. Register here.

We also have a lot of thinking and working already underway. The best documented work, I believe, is by Phil Windley (who calls CFTs picos, for persistent compute objects). His operating system for picos is CloudOS. His holdings-forth on personal clouds are here. It’s all a good basis, but it doesn’t need to be the only one.

What matters is that #CFT is a $trillion market opportunity. Let’s grab it.

* I just added this, because I can see from Johannes Ernst’s post here that I didn’t make it clear enough.

 

 

 

 

 

« Older posts

© 2024 ProjectVRM

Theme by Anders NorenUp ↑