Anish Kapoor and Ideas for Startups

May 28, 2008

Anish Kapoor\'s Cloud Gate I was at the ICA last night for the opening of a new exhibition by Anish Kapoor. He spoke beforehand about his process as an artist, which was fascinating to hear; he’s a very compelling speaker.

Software builders share with artists share the problem of trying to create something when everything is possible. Anish talked about this issue and how, early in his career, he would not let himself to not work on any object for more than 24 hours. This artificial limit freed him from worrying about creating the perfect object, as well as forcing him to generate a lot of ideas.

Anish was also asked about how he approaches starting a new work, how he first puts chisel to granite, especially in light of so much tradition and history that’s gone on before, and he gave a great response:

Every material, every problem is an old problem. The question is how do you solve it in a new way. -Anish Kapoor

It reminded me of a discussion I had in January on as part of an MIT TechVenture panel for students interested in enterpreneurship. A number of the questions were around how to find that perfect idea for a startup. I proposed that finding an idea for a startups isn’t hard and any student in the room would be able to generate good ideas and, more importantly, good problems, if they sat down and tried. I recommended buying a notebook and simply trying to come up with as many good ideas as they could over the next month, and that they’d be surprised where they ended up.

One Idea Per Page

After the conference, I wanted to prove this to myself, so I did exactly that. I bought a Small Black Notebook and each night would spend about 15 minutes working on some ideas. I added the constraint of putting one idea on each page. This forced me to focus on getting down one good idea, putting aside the 20 related ones. Like Anish’s rule of not working on something for more than 24 hours, I found this freed me to think more creatively.

The first thing I learned very quickly was that sitting down and trying to come up with ideas was a terrible way to do it. I never actually came up with any new ideas while sitting in front of the notebook. They usually came while I was doing something simple like making coffee, walking to the T, or cleaning my house. However, having a notebook and the habit of writing in it each night meant that when ideas came, whenever they came, I’d make it point to remember them and work through the details that night.


Problems Not Answers

A second pattern that emerged in my notebook was that I was able to come up with a lot of ideas that were answers without an established problem. While, in each case, I could create a problem, the problems were ones that either hadn’t been solved before or weren’t recognized as interesting unsolved problems. These were easy to come up with and were usually the worst ideas. It’s hard enough to get customers to buy your solution; also having to first convince them of the problem is real is a Bad Idea.

The better ones were the ones for which I started with an old question, usually one that had been solved, and tried to solve in a much better way. Often these ended up with ideas for companies that don’t make sense for me to be involved with. While playing squash, for example, I had an interesting idea for sneakers. I’m not interested in learning enough about the sneaker industry to make it real, but I found myself obsessed with it for days, searching the web for information about materials and how to find a good supplier (if you’re looking, East Coast-based startup Panjiva is where to start).

After a month of keeping my notebook, I had convinced myself that it’s not that hard to come up with ideas for startups. My notebook was full and while most of them were junk, half a dozen were interesting and two or three were ideas that would make for good companies. But ideas are the easy part.


2010 Does Not Exist: Event Horizons and Software

May 15, 2008

I don’t believe in anything that will happen more than two years from now.

I’ve come to refuse to accept any argument for a technical or product decision that’s based on something “in the long-run”. The long run doesn’t exist. Our industry changes so fast that any decision is meaningless without a time scale. Is porting to the iPhone a good idea ? It’s a useless discussion to have unless it’s grounded in a time frame. Three years from now, the phone market will be completely different. Google will own it, or Yahoo, or maybe phones will die and hip technocrats will all have little, wireless-enabled devices made by ASUS and use Skype to talk to each other. Or maybe it will be shown that cell phones cause brain tumors and everyone will have suddenly ditched them. Who knows.

In addition, even if there aren’t significant technological or market changes, three years from now, your team will have been working away for three years. That’s three years worth of code, three years worth of product thinking and investigation, three years of sales cycles, and three years of team members being hired and leaving. If the product is at all innovative, it will have a different architecture, different marketing strategy, and, it probably does a whole lot more than it used (if it doesn’t, you’ve got much bigger issues).

You can’t predict beyond your event horizon

For every organization, there’s a point beyond which prediction is meaningless. If you’re a newly-formed startup, it might be as few as six months. An enterprise software company with a few dozen customers; probably a year or so. Beyond this point, there are so many unknowns, each of which is interdependent with the others, that it’s impossible to see beyond them. Any discussion of architecture or technology choices or features beyond this point is useless.

This isn’t an excuse to be less rigorous or to ignore strategic thinking in general. As software is built, it’s needs to be well-factored and structured so that, no matter what happens two years from now, you’re in a good position to adapt. You don’t want to be the company whose product takes off and isn’t able to keep up with the tornado (*waves to Friendster *). But there are many fewer cases of companies’ technology not being able to keep up than those that have gone out of business chasing problems that exist only in alternate realities they never got to.

And, focusing on a set period of time, gives you a window in which to adjust. Once there’s a real chance that your product will take off within the next 6 months, you’ve got 6 months to get ready for it, in a real concrete way, and are likely to execute much more effectively as you’re not worried about where you’d like to be 2 years from now; save that for when you’re larger and can actually predict two years out.

You can’t predict, so enjoy the ride

Once you’ve accepted this, technology and product decisions become much easier to make as each one is grounded in a concrete time frame. There’s only so much that can be done in 6 months, so your starting point can be “if the whole team focused on this one thing for 6 months, where would we want to go ?”, which gives any discussion an immediate level of focus and scope.


PowerSet: Nice mustaches, lousy search

May 14, 2008

PowerSet came out of super-secret beta this week with much buzz. As someone who works on search software and thinks about similar problems all day (albeit in a different domain), I have to admit I was excited to try the company that “has Google scared”.

I tried it and I don’t get it. They may be doing some crazy NLP/semantic web voodoo behind-the-scenes, but I can’t see any way it’s actually making the experience for users better.

Their relevance ranking feels worse than Google, Yahoo, et al. And the only additional feature is that, for certain searches, it will display Factz (sic) which are basically articles it’s pulled out of Wikipedia or Freebase. Only a small subset of the searches seem to have any Factz (sic) and they aren’t that helpful.

It ends up being a poorly-implemented version of what others like Exalead or Hakia already do. Or what a hacker could do in a weekend by putting Freebase and Wikipedia into Solr.

However, they do have good facial hair:

Nice stache; lousy search.


East Coast - West Coast

May 1, 2008

With a blog named “Right Coast Tech”, I feel compelled to comment on XConomy’s article Is Boston Venture System is Losing More Ground to the West Coast ?

This is not the first and won’t be last “East Coast Vs. West Coast Venture Scene” article. The problem I have with all of them is that they’re answering the wrong question.

Strawberry is Much Better

They remind me of the Boston-New York arguments that inevitably happen when a New Yorker comes to Boston. New York has much better nightlife, is much bigger, and has better bagels. These are facts, not arguments and miss the point. If you care a lot about bagels, clubbing until 3 am, and being surrounded by 8 million people, then you’re going to like New York. Boston has more history, is a short drive to the suburbs and nature, and is much smaller. If you like walking the Freedom Trail, hiking in the mountains, smaller cities, and not being surrounded by tons of people all of the time, you’ll like Boston. Arguing about which city is “better” is as interesting as arguing over chocolate or vanilla ice cream.

The West Coast VC ecosystem is bigger, which means you’re exposed to many more ideas, people, and VCs. That’s a fact. There’s pros and cons to this. Having access to many more co-founders, employees, and potential investors is a benefit. On the other hand, you’re competing with many more entrepreneurs. Additionally, being exposed to more ideas is not necessarily better. A case can be made for over-stimulation. An entrepreneur only needs one idea. Having 3,000 doesn’t help and, in fact, it’s likely to hurt. Warren Buffet lives in Omaha for a reason. That said, there’s plenty of other great investors who thrive in New York.

It’s Irrelevant as All Ice Cream Is Good

An entrepreneur should use an approach for networking, raising money, and hiring that fits the ecosystem in which she’s operating. But that’s true of a number of variables besides size. Like the economy for example: if times are tough, one should be more conservative in financial projections of burnrate and when to raise capital.

More importantly, a good idea and a good team is going to do great things in any venture ecosystem in any economic time. If Boston’s scene has no growth over the next 5 years, it will still be good for a variety of reasons and still a great place to launch a venture.