« Finally on my way to level 2 support - I hope | Main| "Customers buy from people they know, like and trust" »

Climbing on the soapbox in defense of discussion databases.

Category Opinion
Ed Brill created an entry today about the power of some of the templates that are delivered with the base Domino product. (link). Most of the comments have pointed out the lack of updates to the UI and the functionality of the templates for the last several years. I started to respond to these comments, but realized that my entry was getting too long and perhaps would ruffle a few feathers, so I'll put it here instead.

I have argued for many years that while Iris/Lotus created what I think is still the greatest software product ever, it has never recognized its full potential for collaboration because of issues around who controls databases and ACLs. In the V1/early V2 timeframe Notes was an marketed and sold as a company wide purchase and was implemented only at a few large organizations. The product really took off when the licensing changed and it became a departmental product and proliferated through organizations in a grassroots method. Typically, IT was only peripherally involved with the implementation and in many cases wanted nothing to do with the product. This all changed when management started recognizing Notes applications as being "mission critical". IT departments became engaged and the implementations became part of the corporate infrastructure. I’d argue that this was the greatest inhibitor to realizing the full value of these templates, and in particular the discussion database. Once Notes became a corporate resource, the lockdown that most organizations imposed on the creation of new databases greatly reduced the usefulness of these templates. In the early days of Notes, Lotus touted the discussion database as one of the main features, and it was the one application that most people seemed to “get” right away. As a result, discussion databases proliferated like wild fire, and soon clients were complaining that they had 10,000 discussion databases 95% of which were unused. The bean counters saw this as a waste of precious disk space and wasted resources. This perception along with other organizational entities that were challenged by the ability of discussions to bypass longstanding hierarchical business methods lobbied for better control of the situation. As a result, IT departments were charged with controlling the creation and management of the databases and within a short time so much bureaucracy was interjected in the process that most customers stopped using discussions databases. While there are probably some examples of discussion databases that have served organizations for many years, the real power of the discussion template was the ability to create a repository for a short lived issue that could be openly debated and vetted. So what if after a month it was no longer being used? – it was real collaboration and it worked. People still do the same things today – it’s just all contained inside of email messages, or IM chats. This is some of the functionality that Groove tried to recreate by moving to a peer-to-peer model, and that the Activity Explorer is attempting to return to WCS. It is no surprise that these templates haven’t been updated since R5. Who really wants to propose using a discussion database when it takes two weeks and a ream of paperwork to get one created? Lotus/IBM certainly recognized this problem and during the R3-R5 timeframe, discussions were a "dirty word" at Lotus - I can remember being chastised by a Lotus sales rep for including a discussion database in a presentation. "Customers no longer see any value in discussion databases - they want to hear about mission critical applications". Ed's entry is the first time I can remember someone from Lotus even admitting that the templates exist in some time. Perhaps with some of the changes to the way pages and applications can be managed in WCS, there is now recognition within IBM that user created and controlled applications can once more be part of the product?

Comments

Gravatar Image1 - No argument from me on this front. Without a doubt admins need to protect the user population from itself. (Buy me a few beers and I can tell you "dumb user" stories for hours.) The problem is that the only current way to protect the users is to remove their ability to be creative. It’s sort of like giving users Excel, but not allowing them to create a new spreadsheet. (Sometimes that might not be a bad idea either) The most cost effective applications of Notes and collaboration were created back in the V2-V3 days (before everything got locked down) by users that had no clue about programming, but realized that they had the power to create an application based on a template that immediately made their role within the organization much more effective. (Of course many of them then tried to create a version 2 and 3 of their application that quickly grew into a Frankenstein and made them much less effective - but that's a different beer conversation)

My belief is that Lotus could have modified/enhanced the product early on to facilitate this creativity without creating a nightmare for admins. You can see that this was the approach that Ray took with Groove and the concept of moving collaboration to the "edge" of the organization. I think he realized that some of the big promise of collaboration couldn't be met with the current Notes product, so he tired to do it with a peer-to-peer model that bypassed the admin. (right objective/wrong approach) Locking Notes down was, and still is, an organizational necessity (even though some of reasons for this have always been wrong). It's still the best product available, but it isn't perfect (IMHO). As the transition (and I'll probably get beat up for calling it a transition) to Hannover occurs, there is an opportunity to fix this and make the product even better. I’m not saying that it would be easy or that I even have a clue about how to do it (lot’s of opinions of course). One of the advantages of being considered something of a lunatic is that when I start ranting about these things most people are just happy to see an opening to run away and never stick around to ask me how?


Gravatar Image2 - Being a developer and administrator, I beg to differ just a little. In my mind, the lack of access for the normal end user was never about control for the sake of control. It was more about keeping the users from screwing up. I have the perfect example to illustrate my point:

If you go to any Domino site with an Admin who knows anything, you will find that users will only have editor or designer level access to their mail files. This is not to keep them from messing with the ACL or design of the database. Rather, it's to keep them from inadvertantly going File-Database-Delete. If you think I am kidding, I am not. This was the first change I made when I became the Admin at my last company. Prior to making the change, IT was having to restore 1-3 databases per week because the users delete them by mistake.

Just as I don't trust users to tell me the truth when I ask if they have loaded anything on their computer lately, I don't trust them to understand the ramifications of database design. Think about how much time IT would spend fixing problems created by users instead of developing more complex solutions to solve business problems.

Just a thought

Sean---

Gravatar Image3 - I didn't mean to imply that IBM/Lotus were leading people in the wrong direction, but rather it was clear that they recognized the problem early on and the model didn't lend itself to an easy solution. I would agree that Quickplace was a valiant attempt to fix some of this, but we all know of organizations that have now locked down their Quickplace environments just as tightly.

But it’s not the admins fault either – their overriding objective is to manage resources. They’re the ones that get called on the carpet when servers run out of disk space etc.

The problem in threefold:

No one gets on the cover of CIO magazine by touting hundreds of different applications developed and managed by stock clerks, librarians and file clerks even if they solve a multitude of problems and have an immediate return on investment. CxOs want to get credited with a killer application that costs millions to build and delivers a ROI in just a few short years.

Even today, in a flattened world, collaboration still scares individuals at all levels of management. I have seen it in every organization I have ever worked with; fiefdoms exist and are often fiercely defended. This group wants applications and communications and gives lip-service to the concept of collaboration but wants applications that either start or end at their level. (i.e. they want to consolidate information from underlings so that they control its dissemination, or they want the opportunity to get more visibility with upper levels of management.

IBM and Lotus have been very hesitant to cannibalize ISV’s business (unlike Microsoft) and have left the advanced customization to others. However, the various IBM/Lotus labs have spent a great deal of time researching how collaboration is best practiced, yet these lessons have never made their way into the base templates. I could be very wrong, but I don’t think there are any ISVs that generate a considerable portion of their business selling updated base templates for Notes. As a result, I don’t think that many, if any, would complain if IBM/Lotus took all of the lessons learned and created a set of base templates that really advanced collaboration out of the box. Adding functions such as the ability to appoint a moderator that could manage a database without being able to edit the individual documents, voting facilities, automatic summarization, timed inactivation etc. would certainly breathe new life into these valuable templates.

Gravatar Image4 - No controversy here. I have to add that the impediment hasn't really been IBM/Lotus leading the parade down the wrong street. It's really about admins who want to control their servers. Allowing users the ability to create applications (even from trusted templates) is difficult to control and manage. I think that's why Quickplace has been a modest success.

Post A Comment

:-D:-o:-p:-x:-(:-):-\:angry::cool::cry::emb::grin::huh::laugh::lips::rolleyes:;-)

Calendar

Calendar