26.04.2015 Views

Founders at Work.pdf

Founders at Work.pdf

Founders at Work.pdf

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

106 <strong>Founders</strong> <strong>at</strong> <strong>Work</strong><br />

reboot PCs, they restore them from backups, they lose them. It has to be very<br />

resilient. We wanted to make sure the algorithms we were using would scale to<br />

wh<strong>at</strong> we needed.<br />

All those early technology choices were like th<strong>at</strong>. Initially we thought we’d<br />

be using Java, but we ended up not using it because we concluded th<strong>at</strong> there<br />

would never be a stable runtime environment th<strong>at</strong> we could count on on all<br />

desktop PCs. It didn’t seem like Sun, with all due respect, really was on a p<strong>at</strong>h<br />

to having a stable client-side environment. And we needed the thing to work<br />

within several clicks on random PCs worldwide without anybody supporting<br />

them. So we ended up having to do a lot of extra work using C++.<br />

Livingston: Was there an initial customer who was so happy with the product<br />

th<strong>at</strong> you just knew Groove was going to fly?<br />

Ozzie: We launched Groove in beta in October 2000, 3 years to the month<br />

when we first formed the company. We didn’t ship the first commercially available<br />

version of Groove until April 2001. When we did, we announced a 10,000<br />

se<strong>at</strong> deal with GlaxoSmithKline, the major pharmaceutical company. They are a<br />

big Notes customer, but saw the opportunity for Groove to address some of the<br />

cross-boundary collabor<strong>at</strong>ion needs they have in bringing new products to market.<br />

In hindsight, th<strong>at</strong> initial sale may have hurt us more than it helped. We<br />

deluded ourselves into thinking we could sell Groove into enterprises like<br />

GlaxoSmithKline far more quickly and system<strong>at</strong>ically than turned out to be the<br />

case. We really hadn’t paid our dues yet in terms of making Groove “enterprise<br />

ready.” We did th<strong>at</strong> in subsequent releases of the product, but still struggled to<br />

develop a successful, repe<strong>at</strong>able sales model for the enterprise. It was<br />

extremely difficult to sell new technology like Groove into enterprises <strong>at</strong> a time<br />

when their sole focus was on reducing costs and increasing security.<br />

Livingston: Wh<strong>at</strong> else was hard in those 3 “stealth” years?<br />

Ozzie: The thing th<strong>at</strong>’s not really characteristic, th<strong>at</strong> doesn’t really transl<strong>at</strong>e<br />

from both of my startups to wh<strong>at</strong> other entrepreneurs do, is th<strong>at</strong> I think of the<br />

challenges I take on as 10-year challenges, not filling a quick market niche.<br />

There tends to be some time where I’m building up a level of technological<br />

advantage for when we get to market. With technology, there’s no such thing as<br />

a sustainable advantage, but you can get a good running start if you concentr<strong>at</strong>e<br />

on doing something hard really well.<br />

In Notes, it was the d<strong>at</strong>abase and replic<strong>at</strong>ion environment and the security<br />

aspects. In Groove, it was the security aspects again and this transaction synchroniz<strong>at</strong>ion<br />

and the peer-to-peer XML-based communic<strong>at</strong>ions. Most people<br />

find risk and uncertainty very daunting. In both Notes and Groove, there was<br />

both technological uncertainty and market uncertainty. We knew we were<br />

embarking on something th<strong>at</strong> was technologically very difficult and would take<br />

several years. But you know th<strong>at</strong> the market is going to change during those<br />

years, so virtually everything you do, you have to l<strong>at</strong>e-bind the decisions. You<br />

can’t completely predetermine all the user interface or integr<strong>at</strong>ion decisions.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!