Do You Trust On An Illogical Level?

// October 12th, 2007 // Brain Dump

[Time To Read: ~20min.]

This whole ongoing ordeal with LinkedIn and a comment my mother made a couple weeks ago regarding a disastrous launch of a CMS by a major Canadian company, got me thinking about some of these sites we seem to be using more and more…

Are we trusting these sites far more than we logically should be?

My first example is the Canadian company I mentioned earlier. This particular company decided that they would re-launch a particular division back last year (at least), yet through some of the most bizzare business practices, they have run exceedingly over budget, they have developed a CMS on the backend that makes one wonder “why bother?”, and they have nearly destroyed the most valuable commodity in business – trust.

See, this company had built into their old site a system where users could setup an account, and store certain information that could be referenced whenever the user wished. For some, vast quantities of information were stored within the system based on a certain level of trust in the company providing the service.

When the company decided to transition from the old system to the new system there was an undiscovered bug which mean that when the data was migrated, not everything went as smoothly as expected, and significant amounts of information were lost.

The result is now that this “new” site has been launched, users are logging into their respective accounts and discovering that information they have been adding to for years is no longer available.

Is the information lost forever? Well, it is anyones guess at this point. Theory would indicate that the information is still in the old system database… If it is not, then the information is lost forever and there will be a user backlash like they never thought possible. Now, on the other hand, if the information does still exist, someone has to locate it, verify it, and write some sort of process for moving over this data from the old to the new, yet skipping that which has already been moved. This will now take more time, and cost more money – added onto a project which in my best guess has already spent over $100,000 in WASTED WAGES that should have been avoided, and could have been avoided far too easily.

The key to this one is that Company A setup a system for users to store information and traded trust for user loyalty.

Where it gets quite interesting is that the re-launch of the site was originally planned for early this past year. After many, many, many delays the site was finally launched complete with loss of data. The users noticed it immediately and began the flood of emails to the front line individuals who add to and maintain the content of the site. The truly sad thing is that the trust level between company and client has been seriously damaged, yet it didn’t have to be this way!

For a little over a month the new system was on a development server while an immense mountain of bugs were frantically being worked out. The information had been migrated from the old system (which was still the public facing site) and it was discovered early on that not all the information had been migrated. Users were still using the old site, adding in information yet completely unaware that in 4 weeks time they would suddenly be faced with a new system complete with missing information.

Given the lack of marketing of this re-launch, my guess is that the plan was to suddenly launch the new site and all the users would be in the “Ooooh! Aaaah!” state and happy with the new site….

The front line individuals noticed that the information had not been moved to the new site early on (weeks before the actual launch), yet were unable to express the importance of having this information, the long term effect if it wasn’t there at the launch, and the fact that it needed to be high on the priority list.

The actual development team were doing their best at tackling challenges, however, without an actual project manager (I kid you not!), a language barrier, and the fact that they were running at about 150% capacity for months – it really doesn’t come as a big surprise that this became such a huge issue once the site was launched.

In terms of the site functionality, yes, it is a relatively small issue, HOWEVER, when looking at the long term impact on the company as a whole it then becomes a massive issue.

So is this now perfect 20/20 hindsight? For some it no doubt is – for others it is a situation filled with immense frustration which should have been EASILY avoided, and could have been.

Ok, so the information was moved over from the old system to the new system 4 weeks before the new system actually went live. It was also discovered (doesn’t matter by whom!) at that time, that not all of the information was migrated. With the re-re-re-re-re-scheduled launch of the new site now weeks away, why didn’t anyone let the users know that it would be a good idea to make a backup of their information because the site will be re-launched by X Date and that they cannot guarantee that everything will move over 100%?

This would have given their users weeks of time to go in to the old system (which was still being used), and make a copy of their information IN THE EVENT that something like this did happen. The reality is that it already DID happen and now they’re playing catch-up.

It truly baffles the mind. Here we have a large company, providing a service to their clients, their clients trusting the company, trusting the service, and in the blink of an eye, information that the client deemed worthy, stored on the company system (that they provided) is now gone with some of this information being irreplaceable.

So who is at fault? Both. That’s right, both parties are equally stupid, but for different reasons.

The front-line team knew that this information wasn’t migrated in its entirety and did everything in their power to express to the development team how critical this information was. Heck, the site has re-launched and they’re STILL making their case as to the importance of this issue.

Where it gets messy for the company is that they developed this information system and then promoted it to their clients as a safe and effective way for storing and organizing their information. They put their trust on the line in exchange for loyalty. We’re talking TRUST here people. The absolute, number one, and most valuable commodity in business! Through a history of action, it was implied that the information was going to be there and that their system could be trusted.

On the other hand, the users should have their heads checked as well… If you are using a system, provided by someone else, that you are not paying for, with no guarantees or service level agreement in place, and you simply trust a company with your information because they SEEM trustworthy – don’t bother crying when they lose your information and you don’t have a backup.

We are putting an incredible amount of trust in various companies every single day when we really need to be stopping to take a look at what is going on.

LinkedIn for example has suspended my account because of a stupid picture, and no, I’m not going on another diatribe about their horrible customer service. All I will say is that it is now the 5th day, 4 emails have been sent to them, and I finally got one back today saying that the restriction has been lifted, yet, it has not.

Back to my point.. LinkedIn dropped the heavy hammer on my account over something quite trivial, yet thankfully, if I was to be completely banned from the system, yes it would be an annoyance, however, I do have a backup of all +400 contacts.

Do I trust them? No. Can I trust that their site will always be accessible? Can I trust that I will always have access to my contacts? Can I trust that my information will not be wiped off their servers for whatever reason? Can I even trust that they will be in operation, tomorrow, next week, next month, or next year? No. Can you?

I believe at this point we are all getting better at guarding certain personal information, and companies are being forced to be better with it legally. Great, so I’m comfortable with Company X having a reasonable amount of my personal information. I might even go as far as to say that I trust they won’t sell it when they say they won’t. But does this mean implicit trust across the board?

Direct from the LinkedIn User Agreement:

You agree that LinkedIn may, with or without cause, immediately terminate your LinkedIn account and access to the LinkedIn Service without prior notice.

It’s pretty standard stuff, yet when we begin to place large value on the service provided (which is the goal for the company), and it is suddenly yanked out from under us – we have placed more trust in them than is logically deserved.

I’m going to cut this post there because at this point I think it is my biggest one yet. It could also split off and go down the customer service path far too easily. The big “take away” after all of this is simply: be aware of the level of trust you place in the companies you deal with. You are allowed to trust, and you should be able to trust, however, when something happens and you suffer a loss because you believed something that wasn’t necessarily true, it is you that gets to pick up whatever pieces are left.

Photo by blairware

Popularity: 21% [?]

7 Responses to “Do You Trust On An Illogical Level?”

  1. [...] Amrit Dangol wrote an interesting post today onHere’s a quick excerptWe’re talking TRUST here people. The absolute, number one, and most valuable commodity in business! Through a history of action, it was implied that the information was going to be there and that their system could be trusted. … [...]

  2. [...] Read the rest of this great post here [...]

  3. unwesenNo Gravatar says:

    Very briefly, this is the exact reason why I don’t think those web-based applications like Google apps will really fly. Google may be one of the few companies out there that throw enough money at the problem of storing gigantic amounts of data safely, but to most companies, the level of engineering required to pull something like that off goes way above their budget.

    A web based office suite built on services like Amazon’s S3 might work out better, I suppose, but then that’s not free anymore. You’re charged a service fee (for S3), which isn’t even very high. But compare that to how much you pay once for a downloadable office suite, and it’s rather expensive.

    It might be that enough of these services are developed in the mid to long term to make very cheap and very reliable online storage feasible, but that’ll be too late for the web 2.0 hype to still be in effect.

    Let me amend my statement above: this generation of web apps won’t fly, and the next… I still doubt it.

  4. TullyNo Gravatar says:

    I do see your point, and I have to agree. On the other hand, what is more important, the app that created the information, or the information itself? Really, if Google wants to develop online applications, great, go nuts. It is who is controlling my information that becomes the issue.

    Applications can be changed pretty quickly and easily regardless of whether it’s online or offline. The ultimate challenge would be if you’re using a Google App, storing your information on their server (securely with no concern there), but what happens when they pull the service, or your data gets lost, or they get bought and no longer provide the app or access to your data? Sure, not likely to happen to Google (anything is possible tho), however, what about small companies?

    Given the immediate termination without notice clauses that we all agree to with any online service, there is the possibility that such a thing could take place. At any time. We trust them with our information, yet that information could be gone right now….

  5. unwesenNo Gravatar says:

    Well, I’ve been mixing two points up really.

    Your concern with your post was with your data, not so much with the service LinkedIn provides around your data, if I understand correctly.

    I’m taking the engineering perspective, unfortunately, and am trying to say that in the case of LinkedIn, the two are inseparable.

    All I’m trying to say (and I don’t think I was that clear before), was that the two should be separate, because while that doesn’t solve the trust issue you talk about, it makes it slightly less likely to matter.

    The companies providing web apps (such as the LinkedIn website) could die like mayflies, your data would still be “safe” on the servers provided by people specialized in storing data reliably. You can trust those web app providers, mostly because they can’t mess up your data.

    On the other hand, you place that trust into people who work on nothing but the problem of reliably storing your data. On the one hand, that’s a single point of failure (if they go bust, all your data is gone), but on the other hand, they know what they’re doing (unlike most web app providers).

    The matter of trust still remains, it just becomes a bit clearer who you can or should trust to what level, and why.

  6. Ah, I see now. The post was actually about the service we use, and the data we store. Really, if the service disappears (or cuts us off) our data is somewhat lost as well.

    For the CMS example, yes, when looking at the actual data itself it is the responsibility of those in charge with the data store management.

    I think it comes down to accessibility vs. availability. Most technology companies wave the big availability flag which although crucial, is not the important one. From a user point of view, accessibility is the only thing that matters. If the data is available (as in the linkedin case), yet completely unacessible…

    We’ll explain it this way:

    Avail.(1) + Access.(1) = Happy Customer (2)
    Avail.(0) + Access.(1) = Upset Customer (1)
    Avail.(1) + Access.(0) = Frustrated Customer (1)
    Avail.(0) + Access.(0) = No Customer (0)

    I think the reality is that in order for services like LinkedIn to work, we have to trust both the service accessibility, as well as the data availability. Sure, large companies put quite a bit of funding into data storage, yet it is still part of that company. If the data is lost (for whatever reason), what recourse do you have? You used their system, you stored it there, yeah they lost it, but didn’t you have a backup?

    I think it’s a grey area of responsibility too…

    (is it a good thing when comments run as long as the original lengthly post?) ;)

  7. unwesenNo Gravatar says:

    It’s a good thing when there are long comments :)

    Can’t add more, though, I agree with what you’re saying!

Leave a Reply

CommentLuv badge
PHVsPjxsaT48c3Ryb25nPndvb3ByYV9hdXRvX3RhZ19jb21tZW50YXRvcnM8L3N0cm9uZz4gLSBZRVM8L2xpPjxsaT48c3Ryb25nPndvb3ByYV90cmFja19hZG1pbjwvc3Ryb25nPiAtIE5PPC9saT48bGk+PHN0cm9uZz53b29wcmFfd2Vic2l0ZV9pZDwvc3Ryb25nPiAtIDIwMjQwNjc4NDk8L2xpPjxsaT48c3Ryb25nPndvb19hYm91dDwvc3Ryb25nPiAtIDwvbGk+PGxpPjxzdHJvbmc+d29vX2Fib3V0bGluazwvc3Ryb25nPiAtICM8L2xpPjxsaT48c3Ryb25nPndvb19hZHNfcm90YXRlPC9zdHJvbmc+IC0gdHJ1ZTwvbGk+PGxpPjxzdHJvbmc+d29vX2FkX2ltYWdlXzE8L3N0cm9uZz4gLSBodHRwOi8vd3d3Lndvb3RoZW1lcy5jb20vYWRzL3dvb3RoZW1lcy0xMjV4MTI1LTEuZ2lmPC9saT48bGk+PHN0cm9uZz53b29fYWRfaW1hZ2VfMjwvc3Ryb25nPiAtIGh0dHA6Ly93d3cud29vdGhlbWVzLmNvbS9hZHMvd29vdGhlbWVzLTEyNXgxMjUtMi5naWY8L2xpPjxsaT48c3Ryb25nPndvb19hZF9pbWFnZV8zPC9zdHJvbmc+IC0gaHR0cDovL3d3dy53b290aGVtZXMuY29tL2Fkcy93b290aGVtZXMtMTI1eDEyNS0zLmdpZjwvbGk+PGxpPjxzdHJvbmc+d29vX2FkX2ltYWdlXzQ8L3N0cm9uZz4gLSBodHRwOi8vd3d3Lndvb3RoZW1lcy5jb20vYWRzL3dvb3RoZW1lcy0xMjV4MTI1LTQuZ2lmPC9saT48bGk+PHN0cm9uZz53b29fYWRfdXJsXzE8L3N0cm9uZz4gLSBodHRwOi8vd3d3Lndvb3RoZW1lcy5jb208L2xpPjxsaT48c3Ryb25nPndvb19hZF91cmxfMjwvc3Ryb25nPiAtIGh0dHA6Ly93d3cud29vdGhlbWVzLmNvbTwvbGk+PGxpPjxzdHJvbmc+d29vX2FkX3VybF8zPC9zdHJvbmc+IC0gaHR0cDovL3d3dy53b290aGVtZXMuY29tPC9saT48bGk+PHN0cm9uZz53b29fYWRfdXJsXzQ8L3N0cm9uZz4gLSBodHRwOi8vd3d3Lndvb3RoZW1lcy5jb208L2xpPjxsaT48c3Ryb25nPndvb19hbHRfc3R5bGVzaGVldDwvc3Ryb25nPiAtIGRlZmF1bHQuY3NzPC9saT48bGk+PHN0cm9uZz53b29fY3VzdG9tX2Nzczwvc3Ryb25nPiAtIDwvbGk+PGxpPjxzdHJvbmc+d29vX2N1c3RvbV9mYXZpY29uPC9zdHJvbmc+IC0gPC9saT48bGk+PHN0cm9uZz53b29fZmVlZGJ1cm5lcl91cmw8L3N0cm9uZz4gLSBodHRwOi8vZmVlZHMyLmZlZWRidXJuZXIuY29tL0xvZ2ljYWxFbW90aW9uczwvbGk+PGxpPjxzdHJvbmc+d29vX2dvb2dsZV9hbmFseXRpY3M8L3N0cm9uZz4gLSA8c2NyaXB0IHR5cGU9XCJ0ZXh0L2phdmFzY3JpcHRcIj4NCnZhciBnYUpzSG9zdCA9ICgoXCJodHRwczpcIiA9PSBkb2N1bWVudC5sb2NhdGlvbi5wcm90b2NvbCkgPyBcImh0dHBzOi8vc3NsLlwiIDogXCJodHRwOi8vd3d3LlwiKTsNCmRvY3VtZW50LndyaXRlKHVuZXNjYXBlKFwiJTNDc2NyaXB0IHNyYz1cJ1wiICsgZ2FKc0hvc3QgKyBcImdvb2dsZS1hbmFseXRpY3MuY29tL2dhLmpzXCcgdHlwZT1cJ3RleHQvamF2YXNjcmlwdFwnJTNFJTNDL3NjcmlwdCUzRVwiKSk7DQo8L3NjcmlwdD4NCjxzY3JpcHQgdHlwZT1cInRleHQvamF2YXNjcmlwdFwiPg0KdHJ5IHsNCnZhciBwYWdlVHJhY2tlciA9IF9nYXQuX2dldFRyYWNrZXIoXCJVQS0xODEyNDE5LTFcIik7DQpwYWdlVHJhY2tlci5fdHJhY2tQYWdldmlldygpOw0KfSBjYXRjaChlcnIpIHt9PC9zY3JpcHQ+PC9saT48bGk+PHN0cm9uZz53b29faG9tZTwvc3Ryb25nPiAtIHRydWU8L2xpPjxsaT48c3Ryb25nPndvb19ob21lX2FyY2hpdmVzPC9zdHJvbmc+IC0gaHR0cDovL3d3dy50dWxseS5jYS9ibG9nLzIwMDkvPC9saT48bGk+PHN0cm9uZz53b29faG9tZV9mbGlja3JfY291bnQ8L3N0cm9uZz4gLSA1PC9saT48bGk+PHN0cm9uZz53b29faG9tZV9mbGlja3JfdXJsPC9zdHJvbmc+IC0gaHR0cDovL3d3dy5mbGlja3IuY29tL3Bob3Rvcy93aWxsaWFtdHVsbHkvPC9saT48bGk+PHN0cm9uZz53b29faG9tZV9mbGlja3JfdXNlcjwvc3Ryb25nPiAtIDkzNDkxNzFATjA3PC9saT48bGk+PHN0cm9uZz53b29faG9tZV9saWZlc3RyZWFtPC9zdHJvbmc+IC0gMTI8L2xpPjxsaT48c3Ryb25nPndvb19ob21lX3Bvc3RzPC9zdHJvbmc+IC0gNjwvbGk+PGxpPjxzdHJvbmc+d29vX2xvZ288L3N0cm9uZz4gLSBodHRwOi8vd3d3LnR1bGx5LmNhL2Jsb2cvd3AtY29udGVudC90aGVtZXMvbG9nby10cmFucy5wbmc8L2xpPjxsaT48c3Ryb25nPndvb19tYWlucmlnaHQ8L3N0cm9uZz4gLSBmYWxzZTwvbGk+PGxpPjxzdHJvbmc+d29vX21hbnVhbDwvc3Ryb25nPiAtIGh0dHA6Ly93d3cud29vdGhlbWVzLmNvbS9zdXBwb3J0L3RoZW1lLWRvY3VtZW50YXRpb24vaXJyZXNpc3RpYmxlLzwvbGk+PGxpPjxzdHJvbmc+d29vX25hdjwvc3Ryb25nPiAtIGZhbHNlPC9saT48bGk+PHN0cm9uZz53b29fc2hvcnRuYW1lPC9zdHJvbmc+IC0gd29vPC9saT48bGk+PHN0cm9uZz53b29fdGFiczwvc3Ryb25nPiAtIHRydWU8L2xpPjxsaT48c3Ryb25nPndvb190aGVtZW5hbWU8L3N0cm9uZz4gLSBJcnJlc2lzdGlibGU8L2xpPjxsaT48c3Ryb25nPndvb192aWRlbzwvc3Ryb25nPiAtIHRydWU8L2xpPjwvdWw+