Lotus databases are not relational and should not be used in place of systems that need solid relational databases (finance, sales, etc.).

On the other hand, with Lotus, companies can create absolutely wonderful workflow applications that allow almost any paper form floating around your office to turn into an interactive, routable, approval-driven system that is easy to use. These types of systems make the routing and approval process of company information fast, easy and increases accountability because everyone can see where the bottleneck is.

Lotus development is also MUCH faster than any other type of development, which allows the publication of workflow applications in a timely manner.

Instead of trying to justify getting rid of Lotus Notes (which isn’t going to happen since your company just invested big bucks in it), you might want to beg for training so your learning curve is much quicker.

I want to ask for your advice here. I’m working in company where almost whole IT is not satisfied with Lotus notes. Unfortunately, there is one small group of Lotus notes defenders, supported by various incentives of IBM, which is doing everything to keep Lotus notes alive, going against any other platform.

That’s why we are preparing some constructive and pragmatic list of arguments why we should’t develop future applications in Lotus Notes and switch to some other platform instead. Our arguments should be good enough to make company management (consisting of non IT people) to decide that Lotus Notes is not suitable for our company.

Could anyone give us some suggestions for pragmatic arguments why Lotus Notes is wrong platform for database application development and help us to win our battle over Lotus Notes?

thank you in advance for any comment which could prevent us from future pain caused by Lotus Notes

Best Regards
Peter

I will post the best on here somewhere. sometime.