Category: Transparency

How yours is your car?

Peugeot

I’ve owned a lot of bad cars in my decades.  But some I’ve loved, at least when they were on the road. One was the 1965 Peugeot 404 wagon whose interior you see above, occupied by family dog Christy, guarding the infant seat next to her. You’ll note that the hood is open, because I was working on it at the time, which was constantly while I owned it.

I shot that photo in early 1974, not long after arriving at our new home in Graham, North Carolina. The trip down from our old home in far northern New Jersey was one of the most arduous I’ve ever taken, with frequent stops to fix whatever went wrong along the way, which was plenty.

Trouble started when a big hunk of rusted floor fell away beneath my feet, so I could see the New Jersey Turnpike whizzing by down there, while worrying that the driver’s seat itself might fall to the moving pavement, and my ass with it.

The floor had rusted because rainwater would gather in the air vents between the far side of the windshield and the dashboard, and suddenly splat down on one’s feet, and the floor, soon as the car began to move.  (The floor was prepared for this with a drainage system of tubes laminated between layers of metal, meant to carry downward whatever water fell on top. Great foresight, I suppose. But less prepared was the metal itself, which was determined to rust.)

Later a can attached to the exhaust manifold blew to pieces so sound and exhaust straight from the engine sounded like a machine gun and could be heard to the horizons in all directions, and echoed into the cabin off the pavement through the new hole in the floor. I am sure that the hearing loss I have now began right then.

I replaced the lost metal with an emptied V8 juice can that I filled with steel wool for percussive exhaust damping, and fastened into place with baling wire that I carried just in case of, well, anything. I also always carried a large toolbox, because you never know. If you owned a cheap used car back in those days, you had to be ready for anything.

The car did have its appeals, some of which were detailed by coincidence a month ago by Raphael Orlove in Jalopnik, calling this very model the best wagon he’s ever driven. His reasons were correct—for a working car. The best feature was a cargo area was so far beyond capacious that I once loaded a large office desk into it with room to spare. It also had double shocks on the rear axle, to help handle the load, plus other arcane graces meant for heavy use, such as a device in the brake fluid line to the rear axle that kept the brakes from locking up when both rear wheels were spinning but off the ground. This, I was told, was for drivers on rough dirt roads in Africa.

While the Peugeot 404 was not as weird in its time as the Citroën DS or 2CV (both of which my friend Julius called “triumphs of French genius over French engineering”), it was still weird as shit in some remarkably impractical ways.

For example, screw-on hubcaps. These meant no tire machine could handle changing a tire, and you had to do the job by hand with tire irons and a sledgehammer. I carried those too. For unknown reasons, Peugeot also also hid spark plugs way down inside the valve cover, and fed them electricity through a spring inside a bakelite sleeve that was easy to break and would malfunction even if they weren’t broken.

I could go on, but all that stuff is beside my point, which is that this car was, while I had it, mine. I could fix it myself, or take it to a mechanic friendly to the car’s oddities. While some design features were odd or crazy, there were no mysteries about how the car worked, or how to fix or replace its parts. More importantly, it contained no means for reporting its behavior or use back to Peugeot, or to anybody.

It’s very different today. That difference is nicely unpacked in A Fight Over the Right to Repair Cars Turns Ugly, by @Aarian Marshall in Wired. At issue are right-to-repair laws, such as the one currently raising a fuss in Massachusetts.

See, all of us and our mechanics had a right to repair our own cars for most of the time since automobiles first hit the road. But cars in recent years have become digital as well as mechanical beings. One good thing about this is that lots of helpful diagnostics can be revealed. One bad thing is that many of those diagnostics are highly proprietary to the carmakers, as the cars themselves become so vertically integrated that only dealers can repair them.

But there is hope. Reports Aarian,

…today anyone can buy a tool that will plug into a car’s port, accessing diagnostic codes that clue them in to what’s wrong. Mechanics are able to purchase tools and subscriptions to manuals that guide them through repairs.

So for years, the right-to-repair movement has held up the automotive industry as the rare place where things were going right. Independent mechanics remain competitive: 70 percent of auto repairs happen at independent shops, according to the US trade association that represents them. Backyard tinkerers abound.

But new vehicles are now computers on wheels, gathering an estimated 25 gigabytes per hour of driving data—the equivalent of five HD movies. Automakers say that lots of this information isn’t useful to them and is discarded. But some—a vehicle’s location, how specific components are operating at a given moment—is anonymized and sent to the manufacturers; sensitive, personally identifying information like vehicle identification numbers are handled, automakers say, according to strict privacy principles.

These days, much of the data is transmitted wirelessly. So independent mechanics and right-to-repair proponents worry that automakers will stop sending vital repair information to the diagnostic ports. That would hamper the independents and lock customers into relationships with dealerships. Independent mechanics fear that automakers could potentially “block what they want” when an independent repairer tries to access a car’s technified guts, Glenn Wilder, the owner of an auto and tire repair shop in Scituate, Massachusetts, told lawmakers in 2020.

The fight could have national implications for not only the automotive industry but any gadget that transmits data to its manufacturer after a customer has paid money and walked away from the sales desk. “I think of it as ‘right to repair 2.0,’” says Kyle Wiens, a longtime right-to-repair advocate and the founder of iFixit, a website that offers tools and repair guides. “The auto world is farther along than the rest of the world is,” Wiens says. Independents “already have access to information and parts. Now they’re talking about data streams. But that doesn’t make the fight any less important.”

As Cory Doctorow put it two days ago in Agricultural right to repair law is a no-brainer, this issue is an extremely broad one that basically puts Big Car and Big Tech on one side and all the world’s gear owners and fixers on the other:

Now, there’s new federal agricultural Right to Repair bill, courtesy of Montana Senator Jon Tester, which will require Big Ag to supply manuals, spare parts and software access codes:

https://s3.documentcloud.org/documents/21194562/tester-bill.pdf

The legislation is very similar to the Massachusetts automotive Right to Repair ballot initiative that passed with a huge margin in 2020:

https://pluralistic.net/2020/09/03/rip-david-graeber/#rolling-surveillance-platforms

Both initiatives try to break the otherwise indomitable coalition of anti-repair companies, led by Apple, which destroyed dozens of R2R initiatives at the state level in 2018:

https://pluralistic.net/2021/02/02/euthanize-rentiers/#r2r

It’s a bet that there is more solidarity among tinkerers, fixers, makers and users of gadgets than there is among the different industries who depend on repair price-gouging. That is, it’s a bet that drivers will back farmers’ right to repair and vice-versa, but that Big Car won’t defend Big Ag.

The opposing side in the repair wars is on the ropes. Their position is getting harder and harder to maintain with a straight face. It helps that the Biden administration is incredibly hostile to that position:

https://pluralistic.net/2021/07/07/instrumentalism/#r2r

It’s no coincidence that this legislation dropped the same week as Aaron Perzanowski’s outstanding book “The Right to Repair” — R2R is an idea whose time has come to pass.

https://pluralistic.net/2022/01/29/planned-obsolescence/#r2r

[The next day…]

Cory just added this in a follow-up newsletter and post:

…remember computers are intrinsically universal. Even if manufacturers don’t cooperate with interop, we can still make new services and products that plug into their existing ones. We can do it with reverse-engineering, scraping, bots – a suite of tactics we call Adversarial Interoperability or Competitive Compatibility (AKA “comcom”):

https://www.eff.org/deeplinks/2019/10/adversarial-interoperability

These tactics have a long and honorable history, and have been a part of every tech giant’s own growth…

Read all three of those pieces. There is much to be optimistic about, especially once the fighting is mostly done, and companies have proven knowledge that free customers—and truly free markets—are more valuable than captive ones. That has been our position at ProjectVRM from the start. Perhaps, once #R2R and #comcom start paying off, we’ll finally have one of the proofs we’ve wanted all along.

IoT & IoM next week at IIW

blockchain1

(This post was updated and given a new headline on 20 April 2016.)

In  The Compuserve of Things, Phil Windley issues this call to action:

On the Net today we face a choice between freedom and captivity, independence and dependence. How we build the Internet of Things has far-reaching consequences for the humans who will use—or be used by—it. Will we push forward, connecting things using forests of silos that are reminiscent the online services of the 1980’s, or will we learn the lessons of the Internet and build a true Internet of Things?

In other words, an Internet of Me (#IoM) and My Things. Meaning things we own that belong to us, under our control, and not puppeted by giant companies using them to snarf up data about our lives. Which is the  #IoT status quo today.

A great place to work on that is  IIW— the Internet Identity Workshop , which takes place next Tuesday-Thursday, April 26-28,  at the Computer History Museum in Silicon Valley. Phil and I co-organize it with Kaliya Hamlin.

To be discussed, among other things, is personal privacy, secured in distributed and crypto-secured sovereign personal spaces on your personal devices. Possibly using blockchains, or approaches like it.

So here is a list of some topics, code bases and approaches I’d love to see pushed forward at IIW:

  • OneName is “blockchain identity.”
  • Blockstack is a “decentralized DNS for blockchain applications” that “gives you fast, secure, and easy-to-use DNS, PKI, and identity management on the blockchain.” More: “When you run a Blockstack node, you join this network, which is more secure by design than traditional DNS systems and identity systems. This  is because the system’s registry and its records are secured by an underlying blockchain, which is extremely resilient against tampering and control. In the registry that makes up Blockstack, each of the names has an owner, represented by a cryptographic keypair, and is associated with instructions for how DNS resolvers and other software should resolve the name.” Here’s the academic paper explaining it.
  • The Blockstack Community is “a group of blockchain companies and nonprofits coming together to define and develop a set of software protocols and tools to serve as a common backend for blockchain-powered decentralized applications.” Pull quote: “For example, a developer could use Blockstack to develop a new web architecture which uses Blockstack to host and name websites, decentralizing web publishing and circumventing the traditional DNS and web hosting systems. Similarly, an application could be developed which uses Blockstack to host media files and provide a way to tag them with attribution information so they’re easy to find and link together, creating a decentralized alternative to popular video streaming or image sharing websites. These examples help to demonstrate the powerful potential of Blockstack to fundamentally change the way modern applications are built by removing the need for a “trusted third party” to host applications, and by giving users more control.” More here.
  • IPFS (short for InterPlanetary File System) is a “peer to peer hypermedia protocol” that “enables the creation of completely distributed applications.”
  • OpenBazaar is “an open peer to peer marketplace.” How it works: “you download and install a program on your computer that directly connects you to other people looking to buy and sell goods and services with you.” More here and here.
  • Mediachain, from Mine, has this goal: “to unbundle identity & distribution.” More here and here.
  • telehash is “a lightweight interoperable protocol with strong encryption to enable mesh networking across multiple transports and platforms,” from @Jeremie Miller and other friends who gave us jabber/xmpp.
  • Etherium is “a decentralized platform that runs smart contracts: applications that run exactly as programmed without any possibility of downtime, censorship, fraud or third party interference.”
  • Keybase is a way to “get a public key, safely, starting just with someone’s social media username(s).”
  • ____________ (your project here — tell me by mail or in the comments and I’ll add it)

In tweet-speak, that would be @BlockstackOrg, @IPFS, @OpenBazaar, @OneName, @Telehash, @Mine_Labs #Mediachain, and @IBMIVB #ADEPT

On the big company side, dig what IBM’s Institute for Business Value  is doing with “empowering the edge.” While you’re there, download Empowering the edge: Practical insights on a decentralized Internet of Things. Also go to Device Democracy: Saving the Future of the Internet of Things — and then download the paper by the same name, which includes this graphic here:

ibm-pyramid

Put personal autonomy in that top triangle and you’ll have a fine model for VRM development as well. (It’s also nice to see Why we need first person technologies on the Net , published here in 2014, sourced in that same paper.)

Ideally, we would have people from all the projects above at IIW. For those not already familiar with it, IIW is a three-day unconference, meaning it’s all breakouts, with topics chosen by participants, entirely for the purpose of getting like-minded do-ers together to move their work forward. IIW has been doing that for many causes and projects since the first one, in 2005.

Register for IIW here: https://iiw22.eventbrite.com/.

Also register, if you can, for VRM Day: https://vrmday2016a.eventbrite.com/. That’s when we prep for the next three days at IIW. The main focus for this VRM Day is here.

Bonus link: David Siegel‘s Decentralization.

 

 

 

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:

Where VRM stands in the advertising debate

It’s easy to see why the behavioral advertising business feels threatened lately. Already some of the most popular browser add-ons are for blocking ads and tracking. (Here’s one list.) As of last May, according to ClarityRay, 9.26% of all ads were being blocked by browsers. For tech content, the rate was 17.79% and in one country (Austria) the rate was 22.5%. Ad blocking was highest with Mozilla (17.81%) and lowest with Explorer (3.86%).

Not surprisingly, Microsoft smelled the demand and defaulted Do Not Track in the “on” position with its next version of Explorer. Also not surprisingly, this proved controversial.

And now comes Ad Networks Beware: Firefox to Block Third-Party Cookies: New policy could squeeze online behavioral advertising, by Katy Bachman in AdWeek. She begins,

The Interactive Advertising Bureau lashed out Saturday at a new Firefox policy to block third-party cookies, effectively cutting off ad networks’ ability to track users. That could be put a crimp in the growing online behavioral advertising business, but give privacy advocates a victory in their attempts to give users more control over their online information.

Mike Zaneis (@MikeZaneis), the organization’s svp and general counsel tweeted that Mozilla’s new policy was nothing less than “a nuclear first strike against the ad industry.”

Firefox will begin blocking the cookies from third-party ad networks by default beginning with distribution of Firefox version 22 on April 5. The browser would allow cookies from first party websites that users visit, according to Jonathan Mayer, a grad student at Standford University who wrote the patch for Mozilla.

Firefox’s new cookie policy is similar to Apple Safari, but “slightly relaxed,” Mayer said in a blog post.  In practice, both Google Chrome and Microsoft Internet Explorer allow third-party cookies.

The links are mine.

For a good picture of the debate at work, read the whole thread below Mike’s tweet. In it you’ll see how hard it is to draw lines we don’t want others to cross. If we’re Mike and the IAB, we want to draw the line as far out as our self-reguatory principles for online behavioral advertising allow. That line is inclusive of (presumably) harmless forms of tracking. If you’re Chris Saghoian (@csaghoian), one of the creators of Do Not Track (and a voice in that thread), the line not to cross is the personal one that surrounds one’s private spaces. Among those is the vehicle called a browser, in which one would like to drive around the Web enjoying car-like independence.

Here in the VRM world, we are in the second camp. But we’d rather leave the fighting up to others, and instead extend an olive branch toward cooperative development of tools that shake hands and work together across both kinds of lines. That’s what I did at the last link, in September. Since then I’ve enjoyed a positive back-channel conversation that I’d like to keep moving forward.

Also in play are regulatory urgings. This was behind George Simpson‘s Suicide by Cookies, at MediaPost. He begins there by framing up a problem:

Evidon measured sites across the Internet and found the number of web-tracking tags from ad servers, analytics companies, audience-segmenting firms, social networks and sharing tools up 53% in the past year. (The ones in Mandarin were probably set by the Chinese army.) But only 45% of the tracking tools were added to sites directly by publishers. The rest were added by publishers’ partners, or THEIR partners’ partners.

Then he builds the correct forecast of regulatory squeezery, and concludes with this:

I have spent the better part of the last 15 years defending cookie-setting and tracking to help improve advertising. But it is really hard when the prosecution presents the evidence, and it has ad industry fingerprints all over it — every time. There was a time when “no PII” was an acceptable defense, but now that data is being compiled and cross-referenced from dozens, if not hundreds, of sources, you can no longer say this with a straight face. And we are way past the insanity plea.

I know there are lots of user privacy initiatives out there to discourage the bad apples and get all of the good ones on the same page. But clearly self-regulation is not working the way we promised Washington it would.

I appreciate the economics of this industry, and know that it is imperative to wring every last CPM out of every impression — but after a while, folks not in our business simply don’t care anymore, and will move to kill any kind of tracking that users don’t explicitly opt in to.

And when that happens, you can’t say, “Who knew?”

More background on all this can be found at Wharton’s Future of Advertising Program, where they asked a bunch of people “What could/should ‘advertising’ look like in 2020?” I answered here. My bottom lines:

Here is where this will lead by 2020: The ability of individuals to signal their intentions in the marketplace will far exceed the ability of corporations to guess at those intentions, or to shape them through advertising. Actual relationships between people and processes on both sides of the demand-supply relationship will out-perform today’s machine-based guesswork by advertisers, based on “big data” gained by surveillance. Advertising will continue to do what it has always done best, which is to send clear signals of the advertiser’s substance. And it won’t be confused with its distant relatives in the direct response marketing business.

The follow-up question was, “What do we need to do now for this future?” My answer to that one:

Three things.

First, make sharper distinctions between brand and direct response advertising — distinctions that make clear that the latter is a different breed, with different virtues, methods and metrics.

Second, follow and encourage the development of tools that give individuals more independence and ability to engage.

Third, do more research on the first two, so we have better tracking of trends as they develop.

Our job with ProjectVRM is the last two.

VRM at IIW

VRM was a hot topic at IIW last week, with at least one VRM or VRM-related breakout per session — and that was on top of the VRM workshop held at Ericsson on Monday, April 30, the day before IIW started. (Thanks to Nitin Shah and the Ericsson folks for making the time and space available, in a great facility.) Here’s a quick rundown from the #IIW14 wiki:

Tuesday, May 1, Session 1

Tuesday, May 1,Session 2

Tuesday, May 1, Session 3

Tuesday, May 1,Session 4

Tuesday, May 1,Session 5

Wednesday, May 2, Session 1

Wednesday, May 2,Session 2

Wednesday, May 2,Session 3

Wednesday, May 2,Session 4

Wednesday, May 2,Session 5

Thurssday, May 3,Sessions 1-5

On Friday, May 4, I also visited with Jeremie Miller, Jason Cavnar and the Locker Project / Singly team in San Francisco. Very impressed with what they’re up to as well.

Bonus IIW linkage:

Link roundup

The hot edge of VRM right now is in South Africa, where TrustFabric (@TrustFabric, also mention ed in the prior post) is answering that country’s approach to personal privacy concerns with TrustFabric Connect. Let’s help them out. Note also that they’re helping the rest of us by making their code free (GPL v2) and therefore also open source.

Also on the move is getable, based here in Boston, which has a personal RFP approach. Evan Pritchard points to it here. Commenters to that post correctly point out that Buyosphere and Zaarly are also in the space, though coming at it from different angles. Let’s help all them out too.

Jeremiah Owyang puts VRM squarely in the center of his radar with VRM Systems Put Power in Hands of Buyers –Disrupting Sellers.

Just ran across Sparksheet‘s Freeing the Customer with VRM Part I and Making Business More Human, a pair of interviews from last Fall. Haven’t changed my mind about anything since. (I also get a few seconds at the 3:09 point in the Future of Facebook trailer. Venessa Meimis and friends also give me the final word there, starting at 4:06.)

The older B2B meaning of VRM may start blurring with the newer C2B one, if we follow the thrust of Laura Cecere’s Spice it up? post at Supply Chain Shaman.

‘RM alignments

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

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

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

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

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

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

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

© 2024 ProjectVRM

Theme by Anders NorenUp ↑