Corrections & Amplifications on RSS
Posted by tloverro in Marketing, Technology on July 13, 2010
Given some of the reactions out there on the blog-o-sphere, I thought I would clarify a few points regarding my post on RSS.
1) When I say “RIP RSS” or anything like it, I am being totally 100% tongue-in-cheek. I would not sanely call a technology that is deployed on nearly every website on earth (proudly including this one!!!) dead without employing large doses of humor and irony.
2) My larger point is that given how widely deployed RSS is on the publisher front, I believe it still has very low awareness on the consumer front, especially among non-technical folks. The folks I am referring to check email, have Facebook accounts, use Google and, by the way, are the majority of internet users. However, unlike you and me, they’ve never read Slashdot, don’t know what PHP is and didn’t have to hack their WINSOCK.DLL to get Mosiac or Netscape working with AOL back in the day. Go out and see for yourself. Ask a bunch of folks who are not technical and have jobs that are not in tech, ages 30-60, what RSS is and whether or not they regularly use it. Do the same for email. Compare and contrast. Is that a high bar? Yes, but I believe RSS has that sort of potential which is why its low awareness frustrates me.
3) I am an avid RSS user. I need RSS to keep on top of things (mostly Achewood, Kottke.org, HackerNews and DF). I have no less than SIX paid and free RSS clients and utilities on my computer, iPhone and iPad. But the fact that I need to email my blog updates to my family and friends is a sign that something has failed. However, I might have misspoken. Perhaps it’s not RSS’ fault. Maybe the problem is that the world has never seen an easy to use, consumer friendly and viral RSS reader and link sharing client. As my commenter KidMercury pointed out, RSS is great at being a backend technology, so maybe the issue is that no one has taken RSS to the next level as a consumer-facing technology.
4) It’s all about potential. The use case for RSS is so simple, ubiquitous and awesome that nearly every one I know needs it from ubergeek Unix admin to luddite. So how should we judge whether or not RSS is being as successful as it should be? I think it should be almost as ubiquitous as email or at least close to it (30%-50%?). with daily usage.
5) You also need to understand where this blog is coming from. I should probably rename this blog “In Defense of Normals.” All of my posts try to look at things from a decidedly non-geeky POV despite being a geek myself. One commenter asked if I also consider Linux a failed technology. Using the same criteria I used for my post on RSS, the answer is “No, Linux is not a failed technology insofar as it wasn’t meant to be a consumer tech, but Linux & Unix on the Desktop (ie in Wal-Mart) have been disasters precisely because they were meant for consumers.” But consider OS X which is kinda like a skin for Unix. Now, that has been a success.
You might think of it this way: RSS has been a huge win on the backend (kinda like Linux & Unix on servers and workstations, etc.) but has failed to capture the public’s attention and imagination (kinda like Linux & Unix on the Desktop) as much as I think it should / has the potential to. What I really want is something brave and new. I want an RSS client that, like OS X, takes an awesome underlying technology and makes it consumer friendly.
RIP RSS: RSS is a Failed Technology
Posted by tloverro in Marketing, Technology on July 12, 2010
REVISED Edition (I wrote the first edition in a bad mood)
RSS is a failure as a consumer-facing technology. That’s right, despite the fact that you can’t live without Google Reader, RSS is an utter, horrible Kin-tastic failure. You should be embarrassed to use it. Your usage of RSS makes you look as outdated as a dude rocking a Rio Diamond 600 for his MP3 player. (Hopefully you can tell at this point that I am being tongue-in-cheek.)
I put RSS in the same ranks as the JooJoo, Palm Foleo and Clippy. No, strike that. RSS is a worse failure than Clippy. Clippy was ambitious. Clippy was designed to possess human-like intelligence. Now’s that a goddamn challenge! RSS was designed to tell users when a website has been updated. If that’s not a fucking simple task, I frankly don’t know what is.
RSS has failed us. How do I know? Normal people have never heard of RSS. FAIL. I don’t need to actually execute a $1,000,000 marketing research survey to tell you the results. RSS users are hairy-ass, geeky tech dudes. RSS hasn’t crossed the canyon because it’s afraid it’ll get sunburnt if it steps outside of a temperature controlled server room.
Really Simple Syndication–if it’s so simple why do I need to email my family to tell them when I wrote a new post on one of my blogs. If it’s sooooooo simple that six year old cats can use it why did I spend a Saturday morning wasting my time installing an email subscription feature on this blog? (BTW, MailChimp seems to be the best solution I have found so far and it still is 1000x too complex to install on a blog for that purpose.)
The time, my friends, has emerged for something to replace RSS. Something that works. Something that will climb that Mount Everest of engineering marvels: letting me know when a website has been updated. And that chosen technology will be so utterly radical both women and men will use it.The ideal solution should making sharing news and following a website both easy and natural. Users shouldn’t have to deal with an RSS unread count that regularly exceed 1,000+ (useless) or be bothered with understanding the differences between HTTP and RSS (complicated). All a user should have to say is “Yes, please!” If it’s not that simple, it will fail.
Telling the Truth vs Marketing
Posted by tloverro in Marketing, Technology on June 18, 2010
So a guy walks into a a fashionable barbershop for a haircut. The barber is a cute young lass. She asks her client who is a wearing a suit and tie if he’s on his lunch break. The young man replies, “No, I was interviewing for a job.” The barberess follows up, “What sort of job are you interviewing for?” The young man says, “I am interviewing with AppliedTechno Corp for a programming position translating backend database protocols such as…these protocols…” STOP.
That is the truth. That’s all quite truthful as delivered [Ed. Please excuse the stereotyping] by someone with an engineering mindset. Lots of detail that doesn’t take into account the mindset of the receiver of the information. Factually correct, but not necessarily suitable for the audience, suitable for a clone of himself. He might feel as if leaving out some of this info was incorrect or it just might not occur to him to do so.
This exemplifies the difference between “telling the truth” which is something scientists and engineers often feel compelled and obligated to do and “marketing.” Individuals with an engineering mindset often think of there as being some epic battle between the truth and marketing: good vs. evil, straight men vs. spin doctors. This isn’s the case at all, at least with good engineers and marketers. I believe engineers and marketers would be better off and more productive if this misunderstanding were cleared up and technologists, scientists and engineers trusted marketers more and saw them less as “evil spindoctors trying to shove crap on an unwitting public” paraphrasing my Kellogg Prof. Julie Hennessy. (On the flip side, marketers also need to learn that engineers are not all socially awkward introverts who look like Bill Gates circa 1978.)
Marketing is not lying anymore than engineering is creating superhuman robots hellbent on taking over the earth. Marketing is telling a story in such a way that your audience can digest and appreciate it. Marketing is the man replying, “I am interviewing for an engineering position at a local startup.” This is truthful. It’s delivered in a concise way that the audience likely understands and appreciates. It’s also much more likely to incite follow up questions from the audience. The woman may have asked “What type of engineer?” or “Which startups?” or “What did you do before?” We call this a dialogue or engaging your audience.
As soon as you can get the brain of your audience to interact with your message, they are much more likely to be interested and remember it (and resultantly use, buy, etc.). She may have had a great conversation with the engineer and then established a relationship for future visits. Instead, she smiled and nodded awkwardly after his geeky sililoquy. They stopped speaking to each other after that.
PS- Who get’s their haircut after an interview. And, yes, this really just happened before me: State Street Barbers in River North, Chicago.
Improving Customer Adoption by Reducing Fear, Uncertainty & Doubt
Posted by tloverro in Marketing, Technology on June 12, 2010
Recently, I had a conversation with a startup around the concept of making it easier for customers to adopt their product. The question is how you reduce the fear, uncertainty and doubt (FUD) for customers around not just buying but integrating your product or service. I’ll demonstrate this by way of example.
EXAMPLE: I am sitting on a Southwest flight last night from LaGuardia to Midway. I am engrossed reading a Wired article on my iPad when a loud noise startles the crap out of me. But oh, it’s just the wing flaps extending in preparation for landing. But are they
normally that loud? Everyone besides me is looking anxiously around as well. Maybe it’s just because I am sitting over the wing? For a few seconds, a wave of fear, uncertainty and doubt crosses my mind.
Keep in mind. I am an experienced flier. At one point, a United pilot on the JFK-SFO run would call me by my first name. Yet, my experience on my flight was soured by a few seconds of panic. Even though flaps successfully deploying is a good thing and Southwest didn’t do a damed thing wrong, Southwest’s brand was subconsciously tarnished in my mind and all the folks around me who were looking nervous.
When designing products we often spend an incredible amount of time on the tangible and visible. In the airplane example, I am sure product designers spent lifetimes of effort making sure the seats are comfortable yet safe and space efficient, redesigning the engines in multi-million dollar wind tunnels to make them 5% faster or more fuel efficient. Why do all this again? Oh yeah, to serve your customers better and thus make more money. Sometimes to improve your product you need to get inside the head of your customer and understand the underlying psychology.
To make the product better, start with the customer, find the psychological insight and then go back and tweak the product.
In this example, my customer insight is that people are afraid of flying. In a post-September 11th world where there are crazies trying to blow planes up with their freaking shoes, this fear is even more pronounced in the public psyche. This seems like a fairly intuitive insight and it is, yet I don’t see a single US airline addressing it. The difference between good and great products (and companies) is operationalizing these insights.
Many flights already have personal television displays on every seat with a channel that shows your flight status on a route map. In the short-term, how about another channel that tells you in simple and reassuring terms what is going on and prepares you for it?
“We are 25 miles from the airport and have begun our descent to Midway. In approximately 60 seconds you will hear the plane’s wing flaps start to deploy as the pilot slows the plane down to a safe landing speed…Next, you will hear the plane’s landing gear deploy beneath you…Midway Air Traffic Control has instructed us to circle the airport for 20 minutes. The plane will be banking to the left as we circle. Our approximate planned flight path for the holding pattern is: [map].”
This is just one example of how to address this customer fear. I am sure there are better ones out there. But the point is that if you were to make every person who ever shot a nervous glance around an airplane 25, 50 or 100% more comfortable, you’d probably
boost revenue more than many direct “product” improvements which would likely be more costly. Customers would find flying more relaxing, less taxing and would have better memories stored in association with the brand of airline on which they flew. This increases customer loyalty and turbocharges profitability.
How do you take these lessons and apply them to your startup or company? Perhaps the reason more customers aren’t buying or using your product is not because of the lack of features X, Y and Z (even though they explicitly ask for them!) but because they fear setting it up, figuring out when to use it in their daily life, because your claims seem too good to be true based on their prior experience with crappier products or because they fear they won’t get enough post-sales support. There are a million possibilities for customer FUD. All it takes is some careful research and an open mind to find these barriers to purchase/usage and transform them into competitive advantage.














