Wednesday, February 28, 2007

Partying Like It's 2001

Startups seem to be sprouting everywhere these days, like mushrooms. Silicon Valley is back! If you feel like you're hearing about more interesting new startups these days than before, you're right. There's money sloshing around as VC investment in 2006 hit $25 billion, its highest level in five years. Silicon Valley got more VC money in 2006 than at any time since 2001. Then there's the more tangible effects for people who work in the valley.

There's jobs for the taking.
The number of jobs in Silicon Valley increased for the first time since 2001, with a net 33,000 increase in 2006.



Incomes are on the rise. Median household income rose 6.5% in 2006, after falling about a percent in the period 2001 - 2004.



If you're interested in exploring statistics about Silicon Valley, take a look at the 2007 Index of Silicon Valley, an excellent statistical summary of the area.

Sunday, February 18, 2007

Diagnosing Startup Problems

One of the classic issues that every startup is faced with is identifying causality in the face of uncertainty and noise. This is true for both positive and negative outcomes. For example:

  • A large bank just bought your software - great news! But can you isolate the specific reasons why they bought and make it repeatable? Or is it a special situation or relationship driven sale?
  • If sales are stalling, what's the issue? Is it the product, the market or sales execution? If the organization is heading towards dysfunction, this often leads to finger pointing and a revolving door among the executive team.
I recently came across one of the best posts I've ever read on the subject. Will Price of Hummer Winblad, has a post called "Isolating Causality: Bad Market or Bad Company." This should be required reading for entrepreneurs and employees in any early-stage startup.

Wednesday, February 14, 2007

Hardwired for the Web

I recently came across the wonderful "Hole in the Wall" project, run by Sugata Mitra, a computer scientist in New Delhi. PBS has an eight minute video segment you can watch here. It's well worth watching. Yes, the sociological implications are significant, but its also just a wonderful, heart-warming story of some impressive young kids realizing their unlimited potential.

Tuesday, February 13, 2007

The case of the missing address book

Tim O'Reilly blogs about the missing Web 2.0 address book. He says:

What really needs to be done is not just to connect the various social networks that do exist in internet network-of-networks style, but also to social-network enable our real social network apps: our IM, our email, our phone. Where, I keep asking vendors, is the Web 2.0 address book?
Spot-on Tim! Why is it that, in spite of all this emphasis on community and collaboration, managing my address book is still painful? The various elements of our communications tools need to be linked together effectively, and the best place for that link is in an address book. My address book is still largely an offline entity, despite some rudimentary efforts at linking it to my online world (e.g. the Outlook Toolbar from LinkedIn). I can import my Outlook contacts into Gmail, but I can't keep them in sync. Plaxo was a promising start to solving this problem, but they became yet another social network, not the linking mechanism between networks.

What should a web 2.0 address book look like? Here are some characteristics I think are key:
  • Always available. It goes without saying - I should have my address book available online and offline, on all my computers and mobile devices, and they should always be in sync. This has been an area of active investment, and solutions are getting better, but its still cumbersome to keep things in sync.
  • Easily portable. I own my address book, and no vendor should use their functionality, no matter how cool, for lock-in. Ideally the address book should store data in a human-readable format to begin with. If not, I should always be able to export into a variety of standard formats.
  • Proactive. Today's model requires my active participation for every contact that gets stored in my address book. A good address book should anticipate some of my needs and act for me. For example, if I've exchanged a couple of emails with someone who is not in my address book, it should try and find that person's contact info (e.g. from LinkedIn, or some other source) and add it to my address book (perhaps asking me for confirmation first). If someone updates an email address on orkut and that person is connected to me, my address book should know about it and act appropriately. Plaxo tried to do some of this, but their fatal flaw was that they were not neutral. Which brings me to my next point.
  • Neutral. The provider of this functionality must be neutral in the areas of social networking and collaboration. If LinkedIn provided this functionality they would attempt to lock my address book to their network. If Yahoo IM provided this functionality, they would likely restrict access to Gmail, and so on. The address book provider must not have a stake in the network, but only in the links between them.

  • Mediate trust relationships. I already have multiple places in which I've placed indications of trust. Anyone linked to me on LinkedIn list is a trusted relationship. Anyone on my Yahoo IM list is probably also a trusted relationship. Ditto for people I've had multiple email exchanges with. How can I aggregate this information in one place and manage trust centrally. One way in which this could be useful, for example, is that recommendation sites could use my trust information to appropriately weight the recommendations I got. Amazon.com would recommend stuff not only based on their collaboration filtering techniques (essentially statistical analysis) but also factor in my trusted relationships. If I was looking for an Italian restaurant in Palo Alto, I'd much rather hear what a few trusted people have to say about it than a mass of strangers.
  • Geo-aware. The contacts in my address book usually have location information stored in the record. Why is this information not used for a visual representation of my address book? For example, if I'm going to Chicago for a weekend trip, wouldn't it be great to map my friends in Chicago, so that I might get in touch with them while I'm there? And wouldn't it be even better if I could find restaurants in the vicinity so that we could meet for dinner at a mutually convenient location.
  • Presence-aware. My address book should have a notion of where I am, and take appropriate action based on my preferences. E.g. point out a good used-book store in the neighborhood (I'm always up for browsing in a good used-book store). Or alert me that a friend is nearby and I might want to get in touch.
How would this ideal address book provider make money? I leave that as an exercise for the reader. :-)

Wednesday, February 7, 2007

First there was HTML...

Evolution of the web in less than five minutes by an anthropologist at Kansas State. This is one for the ages...





(via John Battelle)