Instead, it was a well-written and, at times, entertaining perspective that revolved around three main points:
- You can’t build one product and have it be right for everyone - accessibility is the Most Important Thing.
- A platform-less product will always be replaced by an equivalent platform-ized product.
- Platforms solve accessibility - a platform is accessibility.
To boil it down, Yegge seemed to be saying with a fair amount of passion and angst that the failure of Google+ was that it continued Google’s emphasis on building products that weren’t service-oriented architectures (SOA). His premise is you can’t be all things to all people so you need to build a platform so that other people can make you all things to all people.
Where was the customer in all of this? I’m sorry, maybe I missed it but it didn’t seem focused on the customer at all. After all, who IS the customer for Google+?
Now, I have nothing against SOA and I think his points about Accessibility are quite valid as he states “When software — or idea-ware for that matter — fails to be accessible to anyone for any reason, it is the fault of the software or of the messaging of the idea. It is an Accessibility failure.” I agree with this point - after all if a customer can’t figure out how to use your software to accomplish a given task, then I’m sorry, the capability in that area doesn’t exist for them.
Where I disagree with him is his premise that we solve for the customer (accessibility) by building a Platform.
Yegge worked at Amazon before Google and drew heavily in his post from this experience. Amazon made a huge push (thanks to Jeff Bezo’s “cultural imperative” to move all development to SOA. And yet, he also jabs at Jeff’s love of his “millions of semantics-packed pixels on the landing page”, emphasizing just how difficult it is to navigate Amazon’s crowded and often confusing site. So where’s the connection between Accessibility and Platform?
I would restate Yegge’s points this way:
- We want to sell to Everyone
- We can’t address Everyone by ourselves
- We need to build a platform that can be extended by 3rd parties to appeal to Everyone
- SOA is the best technical way to do this
And Google+’s problem, in my view is just that. After all, who is the intended customer for Google+? It appears they built it in response to the competitive threat by Facebook, or LinkedIn, or both. And while imitation is the highest form of flattery, it isn’t a path to a clear target market definition. In fact, it’s a clear path to nowhere, for by definition the target audience that you’re building for is already taken!
I’m sure many of you have received an invitation to join Google+. And like myself, you’ve accepted it and done some minimal set up and snooping around. And there certainly are some interesting twists to it, but really, are you going to move from LinkedIn, Facebook or both to Google+? Do you really need another social network?
First of all that’s a pretty rough move, akin to selling your house and moving to a foreign country in the real world. Which a few people do from time to time, but only because there’s clear value in uprooting yourself and family and making such a bold and difficult transition. I don’t personally see any compelling advantage to moving to Google+. Do you? But am I the intended customer? Are you?
Maybe it’s intended for people who haven’t joined the other social networks. Well, what is this group looking for in a social networking site? And what makes Google+ uniquely suited to this group? I currently have two myself - LinkedIn for my “professional” life and Facebook for my personal life. I’m not sure I have time, quite candidly for another virtual “life”.
According to Yegge’s post, there doesn’t seem to be any concern about any of this. Yegge is passionately advocating an internal, SOA revolution within Google. That is classic inside-out thinking that I’ve written about in this blog before.
And that is the message that I think is so important in all of this. Everything we do must be driven by a deep understanding and commitment to delivering a superior experience to our intended customer. And, if SOA does this, then great implement SOA (as painful as that may be).
Are you in the middle of a significant and costly internal improvement initiative? Is it being driven by a clear and uncompromising focus on your intended customer, or is it being driven by internal forces (e.g. cost-reduction, corporate mandates, politics, egos, etc.?)
If it’s the latter, you may want to take a step back and question whether or not it’s worth doing in the first place.