November, 2008

...now browsing by month

 

An American in India: Reflect and Recommit

Thursday, November 27th, 2008

Indian Economic SummitSince hearing about the terror attacks at the Oberoi and Taj Hotels in Mumbai earlier this evening it reminded me of a note I sent friends and family on my last night at the Oberoi Hotel in Bangalore. Over a twenty month period In 2004-06 I travelled to India four times for extended business trips developing a deeper understanding of the fascinating and smart people, rich culture, and its economic transformation and decided to share some of my experiences and thoughts with friends and family — the full note is below with some minor edits to provide context on certain references.

While this evening some sought to destroy the personal friendship and economic relationship that Americans and Indians have formed over the past two decades I am looking forward to my next visit to India to recommit myself to strengthening this relationship and will hopefully be staying at the Oberoi Hotel (it is a magnificent hotel)

Click to continue »

Managing Consumer vs. Enterprise Products Part I

Monday, November 24th, 2008

After spending four years at Siebel and now approaching my 4.5 year anniversary at Yahoo I am asked relatively frequently how does managing enterprise vs. consumer software products differ.   It was a question I first asked myself when I decided to leave Siebel for Yahoo! and now it’s part of my arsenal of interview questions.  Beyond the obvious points – enterprise customers pay millions while consumers usually pay nothing – there are more interesting answers to this question that deserve exploration.

Let’s start with a simple question – how do you know what to build?

In the enterprise world if you want to know what to build jump on an airplane and visit five or six telecom companies of various sizes from British Telecom (BT) to Bezek Telecom and you will quickly see that the problems that BT and Bezek face in order management, billing, or ticketing are similar.  If you can solve it for Bezek and scale it then you have a product you can sell.  While there is a tremendous amount of work to build, sell, customize, deploy, and scale these enterprise solutions identifying the correct problem to solve should not be the risky part of the endeavor.

On the consumer side determining what to build is the risky. Even the best product managers and designers with adept consumer touch will get it wrong more often than not.  If each new project requires the resources of a reasonably well funded team and only one out of ten are successful then you are operating a business with VC model economics.  Most consumer software companies (even growth companies like a Google) are not in the VC business for good reason — they have shareholders that expect consistent returns. Therefore building out processes and platforms that enable you to experiment quickly and efficiently is vital. 

  • Build: Plant a few seeds with a some features at a reasonably low development cost.  
  • Test: Bucket test these features for a reasonable amount of time to allow a signal to form – patience pays as users often have to discover and learn new features.  
  • Analyze + Decide: Then decide to double-down or dump.  It make take a few iterations before you can make a definitive double-down or dump decision, but each iteration should provide signals that inform that ultimate decision.

The nuts of bolts of getting these experimental systems working is where much of the product magic will come from.  Assuming the product is gaining traction – what features should be prioritized.  As products in the Internet consumer space start gaining traction they generate goldmine data sets.  Coming from the enterprise software where the major software providers (Oracle and SAP) don’t see much of the data their customer generate (albeit this is changing with salesforce.com and NetSuite) there is a temptation to allow these data-sets to drive all product decisions. Falling to this temptation will ultimately lead you to a very stale product.   Incremental features designed to address specific metrics will impress when viewed via a narrow lens but the product will quickly become a series of tactics with no larger vision.

G1 Android: One Month Later & Tad Jealous of iPhone Owners

Sunday, November 23rd, 2008

G1 AndroidEverybody in Silicon Valley seems to have an odd love affair with the iPhone and while it is an impressive product I couldn’t resist the opportunity to be a bit different and buy myself the much derided G1 (aka Google Phone) by T-Mobile. One month later I am a tad jealous of the strange love affair people have with their iPhone.  The instant reviewers of the blogosphere quickly panned the G1 — while at times I felt like jumping I felt like I needed to make the G1 part of my life for more then a few hours or even days. Here is what I found:

G1 Hardware: Overall lacks polish and fit n’ finish I would expect from a $150+ device.

  • Keyboard: Angled section forces right thumb into uncomfortable position.  The keys themselves are
  • Thickness: If you miss phones from 1996 you’ll like the thickness of the G1.
  • Power recharge input : Flimsy plastic cover cap.  Why does the most used input require a plastic cover?
  • Keyboard slider arm: Arm that slides the keyboard open/close position is very flimsy piece of plastic. When expanding/collapsing the arm its snap is anything but gentle, and I am fairly certain that in a matter of months it will fly off its hinges.
  • Battery: Rarely make it through a full day when my usage is relatively intense — multiple phone calls, checking email, and browsing the web. For an enterprise user used to the battery life of a Blackberry battery this will prove unusable for most.
  • Buttons: Too many. I constantly confuse the Home and Back button — especially when I am working in landscape mode.
  • Track ball: Too small and sensitive — when browsing the trackball is the cause of many erroneous clicks and movements.
Android OS: First, impressed by the overall responsiveness of the OS – for a version one that is not easy and it deserves credit.  Yet, the UI experience leaves plenty of room for improvement. Pull Out Tray and Menu button are the biggest culprits, but there are a plethora of small stuff that when combined create a very average experience.
  • Pull-out tray: I suspect many users will never discover all the apps. Opening the tray requires a cumbersome select and pull motion – for all the value that sits within this tray one would expect easier and more natural access.
  • Menu Button: Too many applications require constant use of the Menu button — this is partially poor design on the part of the Apps, but I find myself engaging this button constantly when I am in Browser, Mail, etc.  These actions should appear/disappear when needed.  For example, upon reaching the bottom of a web-page display a “Bookmark” action.
  • Applications: Why do I need to load sixty applications to delete one.  If there is an easier way that somebody is aware of please do tell.
  • Search Apps: Nearly impossible to discover how to search all your apps — with the tray open you just start typing — but it took me a few weeks to discover this feature. After the user has added say 40 apps why not expose a search box that can be easily dismissed by the user or provide a gentle hint once the user has a certain number of apps.
  • Notifications: Little icons appear when an email arrives, app download completes, etc. The icons themselves are usually useless — they don’t convey the type of notification they are supposed to represent.  Additionally, it seems like anytime anything happens a notification appears — I really don’t care that it finished downloading an App.  Finally, opening the notification tray requires very nimble fingers.
  • Clock: Why by default does the home screen include a clock that takes up half the screen real-estate when their a clock in the upper right hand corner that is perfectly fine. I don’t get it.
Core Applications: Each of these deserve their own separate post as they are core to the overall experiencewill save that for another day.  Here is the Twitter version:
  • Browser: One of the bigger disappointments of the device.  Mistakes gestures as simple as scroll and zoom.  Search box and Address Box are distinct entities when they should be tightly integrated (see Chrome for a good start).  Finally, exclusive search provider — in some markets Yahoo! is actually superior to Google and
  • Mail: Gmail should place the Reply and Reply All button in the Menu option as otherwise it forces you to scroll through the entire email to simply hit Reply.
Android Market
  • Early start is disappointing, but withhold judgement until they have broader reach and Google providers a monetization solution.
  • App quality is extremely poor: I have uninstalled 80% of the apps as they were utter crap.
  • Limited selection: I am begging for something interesting— how about the Wall Street Journal Reader (like the one for Blackberry)