Thursday, November 13, 2008
Tuesday, October 14, 2008
Two-Pizza Teams
Ron Kohavi (from Microsoft) made a recent visit to eBay. From his description, Amazon has an efficient organization in some aspects and does well evaluating certain metrics and making certain kinds of advancements. Part of this success is driven by their "two-pizza" team culture of 8-person teams with group goals.
However, I think the grass isn't always greener. Amazon is limited in its exploration of spaces which require a breadth of functions and cooperation across teams larger than 8 people. Amazon has limited cross-border trade, and I would expect their attempts to compete with PayPal to be less effective. Teams pushing broad kinds of products have trouble if limited to 8 people, given the diversity of merchants. Amazon's stumbles in auctions and initial attempts at zShops I think reflected a lack of breadth.
Not every project fits in an 8-man box, or is easily sliced into that level of atomic components. Part of eBay's challenges are fitting *some* projects to smaller (narrower) teams. Part of Amazon's challenges are building larger teams for some projects. The Manhattan project in WWII, or the Apollo program, would have taken much longer if only 8 people could communicate amongst themselves. The iPhone, new versions of Microsoft products, and broad visionary products often are better served by less insular teams. Bezos' statement: "You can't do big, clean-sheet invention unless you are willing to invest for long periods of time" shows a subtle limitation in his thinking and in his company. I believe it is possible to do big, clean-sheet invention through shorter term and broader investment. Technology is an amplifier and compresses time, large important clean sheet inventions involve effort, and a *LOT* of imagination.
However, I think the grass isn't always greener. Amazon is limited in its exploration of spaces which require a breadth of functions and cooperation across teams larger than 8 people. Amazon has limited cross-border trade, and I would expect their attempts to compete with PayPal to be less effective. Teams pushing broad kinds of products have trouble if limited to 8 people, given the diversity of merchants. Amazon's stumbles in auctions and initial attempts at zShops I think reflected a lack of breadth.
Not every project fits in an 8-man box, or is easily sliced into that level of atomic components. Part of eBay's challenges are fitting *some* projects to smaller (narrower) teams. Part of Amazon's challenges are building larger teams for some projects. The Manhattan project in WWII, or the Apollo program, would have taken much longer if only 8 people could communicate amongst themselves. The iPhone, new versions of Microsoft products, and broad visionary products often are better served by less insular teams. Bezos' statement: "You can't do big, clean-sheet invention unless you are willing to invest for long periods of time" shows a subtle limitation in his thinking and in his company. I believe it is possible to do big, clean-sheet invention through shorter term and broader investment. Technology is an amplifier and compresses time, large important clean sheet inventions involve effort, and a *LOT* of imagination.
Saturday, October 11, 2008
My Colleague Raghav Gupta Leaves eBay
Raghav was and is a dear professional and personal friend. I enjoyed every conversation and moment I spent with him and the years having him in the cube next to mine only deepened my respect for him. I miss seeing him every day and wish him the best in his continued endeavors.
Monday, October 6, 2008
Peter Norvig, Product Managers and Engineers
Peter Norvig spoke at a panel at eBay ResearchFest 2008 titled "Corporate Research Labs - Challenges and Technologies" on September 29, 2008 - "One very specific part of the problem is how do you get the engineers to talk to the product managers? At Google we solve that by mostly hiring product managers that have computer science degrees."
Engineer or MBA?
Interesting article from Forbes today:
Says Wingo, "eBay needs to drop its obsession with return on investment metrics and think more iteratively and innovatively." He adds: "Engineers should be calling the strategy shots at eBay, not M.B.A.s."
I was unable to independently confirm this attribution from another source, so I hope to confirm this statement at some point.
Says Wingo, "eBay needs to drop its obsession with return on investment metrics and think more iteratively and innovatively." He adds: "Engineers should be calling the strategy shots at eBay, not M.B.A.s."
I was unable to independently confirm this attribution from another source, so I hope to confirm this statement at some point.
Friday, September 19, 2008
Four Changes which Reset Recency Metric for Sort Order
As was mentioned at eBay Live in one of the seller panels: if a seller changes any of these it creates a resetting of the recency metric for preference in sort order:
Title
Category
Price Increase
Item Condition
I have not had a chance to test this in any way, but it seemed quite interesting to me at the time.
Title
Category
Price Increase
Item Condition
I have not had a chance to test this in any way, but it seemed quite interesting to me at the time.
Friday, September 5, 2008
Incremental Changes vs. Large Changes to UI
What is the correct level of granularity for changes to a user interface or policy? A price increase to subscription fees may best be done slowly, and a price decrease done quickly to make it more dramatic. But a UI change can have significant and startling effects. Users habituate their UI behavior. A link with a name change, such as having a link to a subsite with automotive content in 12 point font change to a link for an express general sales format, may divert folks unexpectedly who have habituated clicking on the automotive link.
I saw a site which made a change so that it moved it's "donate money" box and button to the part of the page where the mouse would be on the previous page clicked through. Remarkably effective, I did donate! The box was moved directly, not incrementally.
Users sometimes complain about incremental changes when they can't aggregate because of it. An example is policy changes every few months requiring changes to submitted content. If a change requires a change to user behavior to accommodate it, such as needing to remove email addresses from pages, and then a later policy change to require elimination of JS, then larger, infrequent changes may be more appropriate.
I saw a site which made a change so that it moved it's "donate money" box and button to the part of the page where the mouse would be on the previous page clicked through. Remarkably effective, I did donate! The box was moved directly, not incrementally.
Users sometimes complain about incremental changes when they can't aggregate because of it. An example is policy changes every few months requiring changes to submitted content. If a change requires a change to user behavior to accommodate it, such as needing to remove email addresses from pages, and then a later policy change to require elimination of JS, then larger, infrequent changes may be more appropriate.
Subscribe to:
Posts (Atom)