Q&A: Light the birthday candles for Lotus Notes

Lotus Notes turns 15 on Dec. 7. Iris Associates, the software development company from whence Notes emerged -- on the Lotus dime -- was founded five years earlier to the day. That's reason enough for Network World’s ‘Net Buzz columnist Paul McNamara to get Ray Ozzie on the phone, given Ozzie was the headliner for both productions before leaving Notes Nation in 1997 to start Groove Networks.

Do you ever get tired of talking about Notes?

That's funny … I don't get tired of talking about it depending on the conversation and which way it's spinning. … I get a chance to surf off of it into my current passions and what I'm talking about now and I hope it doesn't sound like the song that nobody wants to hear. I'm passionate about computer-supported cooperative work, writ large. I hope when people are asking about Lotus Notes that that is really what they're talking about.

Take us back to the day when you trotted out Notes 1.0.

At the time Notes was launched, Dec. 7, 1989, we had one customer -- Sheldon Laube from PriceWaterhouse -- who shared our vision. He understood enough about it and he's a great communicator, much better than we were about the value of Notes at the time.

It was a very fortuitous time for Notes to be coming out because people were just using LANs for printer sharing and they could now leverage that simple technology for lightweight processes within the enterprise. By '95 or so the leading-edge companies started to try to use it outside the company, not just inside. We take this for granted now, but it was fairly interesting and it turned out to be difficult because Notes, in particular, was designed for centralized management. It was fairly burdensome from an administrative perspective for good reason: It was the way that you managed the directory, the way that you managed the security was all designed for the data center and for IT, and it was difficult to extend that to an environment of multiple IT organizations.

That was ultimately what led me to leave and start Groove. I thought to myself, if fundamentally the business environment were going to be changing to be more of a mesh than a set of vertically integrated corporations, then this problem that we were seeing was going to occur more and more and more in that these firewalls that we had built around our organizations and the centralized IT groups would increasingly not be reflective of what the business units within the companies needed to do, which was work seamlessly outside the company. Whereas Notes was more about the changing nature of the organization, Groove was about the changing nature of business in general.

When did you know you had something big with Notes?

I'll say something that let's you see a little bit about my personality: I knew we had something before we started the company. The two guys who started Iris with me -- Tim Halvorsen and Len Kawell -- the three of us had been at the University of Illinois in the mid-'70s and had been exposed to a system called Plato, where we first lived the online community experience. We knew what it was like to work with other people at a distance online because we lived it for years.

We lost that when we went into industry. When we graduated from school, they went to DEC and I went to Data General and suddenly we were thrown into this way-back machine of working the old-fashioned way. We had an innate desire to bring back that method of virtual online work that we had experienced before.

In 1989, because of (Lotus founder) Mitch Kapor and a number of other people who believed in us, we finally had the opportunity to start a company and build that vision.

When we came out with the product in '89, we knew what you could do with it and we couldn't understand why we couldn't communicate to others the difference that they could make.

What piece was missing at that point?

People think always in terms of their business problem, their business process, their business pain. You always have to surf off of what you know, and if you are an accountant, you're wrapped up in the accounting procedures that you've dealt with for many years. You might be able to take on incremental things, like a fax machine or a spreadsheet that emulates what you were doing and takes it one notch further, but the concept of going from physical work to virtual work, the concept of processes that cross-cut group boundaries, it required too many things to change.

What really ended up doing it for Notes was nothing that Lotus did, it was the fact that there's a VAR community, a reseller community, which understood their own customers. They understood the context within which collaborative processes would occur. They built solutions on the platform that we built, and then the customers could understand it.

Looking back, were there any aspects of Notes that you had spot-on from the beginning -- or missed?

Absolutely. I'll start with what we missed. We missed -- but I missed clearly -- the immense value in simple publishing. Notes was and is an amazing interactive system around messages and forms and documents and things like that, and in order to use it you have to authenticate yourself to the system so that there's some security and you build these apps and it works really well.

We had a number of people at the time -- early customers like Reuters, who were just trying to get their information out to their customers. They were trying to just publish it to lots of users in an organization.

When I first saw the Web -- Mosaic -- I am ashamed to admit that I said to myself, this is so trivial, it's got no security, you can't authenticate, the server doesn't know who the user is -- so all you can do with this is simple publishing. I should have foreseen earlier on in Notes the value of a simpler, anonymous client/reader that could have been used for a much broader set of applications than it was initially.

One of the things we got right… is the respect for off-line use and mobility. You have to know from day one when you're building a system that you want to treat mobility as a first-class problem. Early on in Notes (we embraced) the concept of putting all of the code that would be on the server on the client so that you could do this replication. Obviously we did that again in Groove, in a different, much more sophisticated way, but it's the same basic idea that you want to empower the user to work whenever, wherever they need to work. I think we got that so right and it amazes me to this day that more people haven't gotten it right.

Why do you think that is?

It's hard. It's hard and you can't add it on, particularly the integration between the storage, communications and security. They all have to be wrapped together from day one in order to get that seamless use between what you do on the client and what you do when you're connected.

Are there milestones through the early years of Notes that you thought particularly important to the development path?

The first big milestone -- and this is not specific to Notes but rather any major commercial end-user software product -- version 3.0 tends to be the first version that hits its mark because it's got a certain level of maturity, a certain level of user feedback plowed back into the product.

The next major milestone -- and this is not widely written about but I think customers understand it -- is there was a thing called "The Nifty 50." It was a set of application templates that were starter apps, so to speak, that were built on top of Notes 3. It bridged a lot of people into understanding and they just started to build more things.

In release 4.5 e-mail and calendaring became world-class. It was concurrent with the release of (Microsoft) Exchange and it suddenly set in motion thousands of companies putting out RFPs for e-mail systems and then picking one, either Exchange or Notes.

The last major event is in '95 when IBM bought Lotus. People don't realize this, but we had shipped about 2.2 million seats of Notes before IBM, and IBM rapidly jacked that up to 100 million-plus. They did so many things right at the start. There was a lot of turmoil because of the Lotus management structure, but they said, 'Do you know what you're doing? If so, we will put resources into it.' They put resources into it and stepped back and let us enable their organization by putting Notes throughout IBM.

What was your reaction when it was first made clear to you that IBM was going to buy Lotus?