by Paula Thornton
August 18, 2009 at 2:33 pm
· Filed under Event Announcements
Of recent, we as a blogging team, agreed to focus more on actual E2.0 implementations and related adoption issues. I’m now insisting on diverging from that.
We repeatedly mention that 2.0 is not about the technology. If that’s truly the case, then the advice should not be about the adoption of the same technologies for which this is not about (bear with me…at some point there ARE technologies involved, but it’s focusing on those technologies and not on the REST of the stuff that goes on where failure begins).
Let’s talk about examples I’ve come across in the past 30 minutes, where companies are not applying the principles of 2.0 thinking, in all the everyday little things that go on. While these examples may be more Web 2.0 in focus, the analogies can readily be transferred to Enterprise 2.0 scenarios. Exercising related 2.0 thinking at all levels, makes the actions second nature — hopefully, enough that we can stop focusing on the topic at all (that’s the goal).
Amazon and TD Ameritrade Send Relationship Spam
I’ve been a customer of Amazon long enough to remember the annual Christmas gifts and letters that we got from them as customers. Clearly, Amazon led the way in many 2.0 principles and practices even before we codified the term and the focus (shortening the distance to done = 1-click ordering). But Amazon has gotten big and lazy in their attention to detail (which is likely to happen when dealing with the volumes of relationships and touchpoints they have stewardship over). Amazon is not alone in this. In the same 30 minutes I had interactions with two companies (remember, EVERY interaction is a critical point for which relationship equity can be added upon) and they both failed at exactly the same thing: dead end emails.
As I pointed out in my response to TD Ameritrade (which will likely not find its way to any human eyes, and if it does it will be promptly ignored as ‘noise’ — understanding the value of noise is a topic I’ve covered in the past), sending an email which is asking/prompting for action, or even might incidentally be the impetus for action, is a PRIME opportunity for investing in a little relationship equity — furthering the relationship by adding to the interaction. Let me repeat that last part again: “furthering the relationship by adding to the interaction” — think of expanding the relationship chain in the ways many businesses look to expand their strategic focus along a supply chain (clearly the latter is of less value without the former). Replace this notion with what in 1.0 was referred to as stickiness (stickiness is dead).
I got an email from both Amazon and TD Ameritrade. Amazon wrote to tell me that another book I had just posted, had sold and that I needed to fulfill the order. How does Amazon “further the relationship by adding to the interaction”? — by word and not by deed.
“1. Go to your Seller Account by clicking “Your Account” at the top of any Amazon.com page, then clicking “Your Seller Account” on the right side of the page, under Marketplace.”
Instead of reading those instructions (which are relevant and great for mobile and JAWS), I could be clicking on a link that would DO all of that for me — and shorten the distance to done (I went to their site and quickly pointed this out to them — even though I had to invest considerably more of my precious time — which they’d already eaten into, to give them valuable feedback…which again, will likely fall on the machine room floor). It’s an email: “Luke, Use the Force.”
TD Ameritrade regularly sends confirmations of trades by email (something I signed up for in lieu of the paper version — never mind that the email contains NONE of the detail the paper version does). But there’s a significant distinction here — this is an institutional account. I’m not initiating the trades — my personal advisor is. So the most relevant scenario to be initiated by this receipt of an email is that I likely would like to see what it is that has been transacted on my behalf. [insert silence]…TD Ameritrade sends the emails, but treats them like spam. I just delete them. Why? I can never remember HOW to get to my account, I’m not in it enough (my advisor is). The email could easily shorten that distance for me. But, it does not.
Suddenly, I feel like a revivalist and have the urge to say, “Brothers and Sisters…” — we have to start with the little things. It’s actually less about transparency (although that is important) than it is first about sincerity. Where’s the sincerety in sending out a message that is not designed to BE a conversation?
2.0 IS first and foremost the means by which to converse — one with another (even vicariously). Can we start there and then add the other stuff? Seriously, at the top of your E2.0 initiative ‘list’, should be assessing the reality and start fixing that first. In doing so, you will learn so much more about what’s truly relevant to be done, for real 2.0 success.
Learn first to ‘apply’ 2.0. Exercise the craft as an apprentice and earn your way into mastery.
Permalink
18 Tweets
You shouldn’t be clicking on links in emails that seem to be coming from places like Ameritrade as they could be phishing. These companies are trying to train you not to expect to be able to do that. The Amazon one sounds perfect in that it walks you through the process of going to their site yourself and finding the info you need, rather than clicking on a link that could do anything.
Jeremy: Perhaps there’s more to the context here that you’re missing. These are emails that I receive ALL the time — as a course of doing business.
If we stifle ourselves over unfounded fears (and a failure to step forward intelligently) we will fail to move forward at all.
Ah, but I see that your profession is risk management. The more analytical side of me would suggest that you are in the business of ‘fear mongering’ (or gravitated there to alleviate your own personal fears, thinking that there’s such a thing as ‘control’ — which there is not).
Paula,
Actually, my business is *advising those* who perform risk management around information security. We actually typically take the position that our clients are *too concerned* about information risks, as you are doing here. See for example this recent post in our blog:
http://irec.wordpress.com/2009/06/10/do-we-spend-too-much-to-protect-information/
I also argue in favor of password usability in the blog:
http://irec.wordpress.com/2009/07/08/5-properties-of-passwords-that-must-be-managed-to-reduce-risk/
Anyway, putting my personal psychology and biases aside, I think I failed to make my point clear.
As far as you’re concerned I don’t care how you make your personal risk management decisions. What I meant was: *from the POV of the companies,* phishing is a well-founded problem that they bear real costs of every day. Reminders to them about usability such as your original post are probably needed, but they are probably not keeping links out of their email because they are “big and lazy” or failing to “think 2.0″, but because they are trying to train their customers that real emails from them will not contain links in order to help their customers spot phishing emails, which in turn lowers the companies’ risks. Whether the negative impact to the customer is less or more than the positive impact from reduced phishing is a legitimate question, but it is not helpful to reduce the decision to laziness.
Stickiness is dead. Learn to “apply” 2.0 principles first. http://twurl.nl/cey1g7 #e2.0 #CRM2.0
This comment was originally posted on Twitter
@DonPeppers In a ‘deep’ way (=nearly buried), I honored you today. New post http://twurl.nl/cey1g7. Solo link leads to 1999 piece…
This comment was originally posted on Twitter
Applying 2.0 – Enterprise 2.0 scenarios, Amazon and TD Ameritrade – #e20 http://bit.ly/4didT0
This comment was originally posted on Twitter
 |
VMNplusAugust 18th, 2009 at 3:38 pm |
Applying 2.0: Of recent, we as a blogging team, agreed to focus more on actual E2.0 implementations and related .. http://bit.ly/2RUf93
This comment was originally posted on Twitter
Applying 2.0 – Of recent, we as a blogging team, agreed to focus more on actual E2.0 implementations and related ad http://ow.ly/15Lw5Z
This comment was originally posted on Twitter
some businesses “not applying the principles of 2.0 thinking” http://bit.ly/XjgiD If I were a biz, 2.0 doesn’t cut it, I want all 10’s.
This comment was originally posted on Twitter
Applying 2.0 http://snipr.com/qhvtq
This comment was originally posted on Twitter
RT @aponcier Applying 2.0 http://snipr.com/qhvtq
This comment was originally posted on Twitter
Good blog post from FastForward – Applying Web 2.0 – http://bit.ly/10L5xA
This comment was originally posted on Twitter
@EricPosner tks RT @aponcier Applying 2.0 http://snipr.com/qhvtq
This comment was originally posted on Twitter
Solid piece on Applying 2.0 by @rotkapchen #yam http://digg.com/u1B18H
This comment was originally posted on Twitter
.@sniukas Ah, that Trust equation is missing one I just wrote about…sincerity http://twurl.nl/cey1g7 #smchat
This comment was originally posted on Twitter
#smchat imprtnce of sincerity in 2.0comms via @rotkapchen: Where’s the sincerity in sendng msgs not designed 2 BE a convo? http://ow.ly/kCFP
This comment was originally posted on Twitter
Applying 2.0 wisdom from @rotkapchen http://bit.ly/10L5xA
This comment was originally posted on Twitter
RT @BillIves: Applying 2.0 wisdom from @rotkapchen http://bit.ly/10L5xA
This comment was originally posted on Twitter
@tamar Had to snicker…brand evangelizer…close relative to my revivalist persona that snuck out at the end? http://twurl.nl/hwggav
This comment was originally posted on Twitter
 |
sniukasAugust 20th, 2009 at 2:02 am |
RT @rotkapchen @sniukas Ah, that Trust equation is missing one I just wrote about…sincerity http://twurl.nl/cey1g7 #smchat
This comment was originally posted on Twitter
 |
rpolomAugust 20th, 2009 at 9:34 am |
Applying 2.0 by Paula Thornton http://bit.ly/10L5xA #Enterprise 2.0
This comment was originally posted on Twitter
» Subscribe to the RSS feed for these comments
HTML-Tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Additional comments powered by BackType