Skip to main content

SMB != IBM ?

This hold Lotus Foundation non-announcement has once again have me shaking my head about IBM's understanding and focus on the SMB market. As I said on Christian Tillmanns' blog.

"IBM have some of the best solutions for the SMB market, but never seem to understand the importance of this market not just in the revenue perspective, but the impact it has on the enterprise market. Remember that Microsoft’s and Google’s primary focus initially was in the SMB market. And now look where are they. If you have a good foothold on the SMB market you will gain in the enterprise market. What IBM needs to understand is that every individual consumer is a small business and they grow to become enterprises by number. Good example is what Microsoft did with Outlook. Google has done with Google Docs. IBM still does not get it. For example, if you want people to adopt Lotus Symphony DO NOT, DO NOT require people to fill out a super long form or any form at all. I told a customer to try it, but he decided it was too much trouble to fill out all that information just to download what is amount to Open Office."

But Lotus Protector is another example. There is a huge use of virtualization in the SMB market and many companies uses ESXi since it is free. So when you state that Lotus Protector is available as a Virtual Appliance why not make it easy for customers to install it onto a ESXi virtual partition using the OVF format. Instead you have to use the VMware Center Converter because Lotus Protector is in VMX format. This extra step can cause problems and corrupt your ESX partition if it is interrupted. There is a free tool from VMware out there to convert from VMX to OVF format. Why not just make it available in the naive virtual appliance format? Do you think this helps small businesses accept IBM products? DON'T THINK SO.

The concept from UX Design applies not just for visual interaction, but have huge impacts on the back-end part of the product. Cloud computing's advantage is its low barrier to entry. So you need to apply this same concept to how an IT department views an on-premise product. Lotus Foundations' concept was just that. So now that you have terminated the hardware, please give the Business Partners the ability to create their own DOM USB or CF Card so that they can have this ability using other hardware.

Comments

Henning said…
For me SMB = IBM Business Partner not IBM itself.
Unknown said…
For as much "transparency" as IBM Lotus wants to provide, they have been strangely silent on this topic. I've asked several IBM Lotus Foundations representatives for their take on this, future Business Partner Calls, or even an inkling of future directions with the product line and I have been met with silence. Frankly, that does not make me feel very good about this product line.
Gregg,

It has become very frustrating. It seems as if all activity with Lotus Foundations has stopped. They came up with Smart Business as the small business solution which included Lotus Foundations which is suppose to be IBM Foundation for Smart Business. But there has been no communicate or activity at all. I was told that there was going to be big marketing and push in the small business market with many things happening this year. I have not seen anything. I guess terminating Lotus Foundations hardware was a big thing. It sound like the same old same old.

Popular posts from this blog

Creating Twitter Bootstrap Widgets - Part II - Let's Assemble

Creating Twitter Bootstrap Widgets - Part I - Anatomy of a Widget Creating Twitter Bootstrap Widgets - Part II - Let's Assemble Creating Twitter Bootstrap Widgets - Part IIIA - Using Dojo To Bring It Together This is two part of my five part series "Creating Twitter Bootstrap Widgets".   As I mentioned in part one of this series, Twitter Bootstrap widgets are built from a collection standard HTML elements, styled, and programmed to function as a single unit. The goal of this series is to teach you how to create a Bootstrap widget that utilizes the Bootstrap CSS and Dojo. The use of Dojo with Bootstrap is very limited with the exception of Kevin Armstrong who did an incredible job with his Dojo Bootstrap, http://dojobootstrap.com. Our example is a combo box that we are building to replace the standard Bootstrap combo box. In part one, we built a widget that looks like a combo box but did not have a drop down menu associated with it to allow the user to make a select

The iPhora Journey - Part 8 - Flow-based Programming

After my last post in this series -- way back in September 2022, several things happened that prevented any further installments. First came CollabSphere 2022 and then CollabSphere 2023, and organizing international conferences can easily consume all of one's spare time. Throughout this same time period, our product development efforts continued at full speed and are just now coming to fruition, which means it is finally time to continue our blog series. So let's get started... As developers, most of us create applications through the conscious act of programming, either procedural, as many of us old-timers grew up with, or object-oriented, which we grudgingly had to admit was better. This is true whether we are using Java, LotusScript, C++ or Rust on Domino. (By the way, does anyone remember Pascal? When I was in school, I remember being told it was the language of the future, but for some reason it didn't seem to survive past the MTV era).  But in the last decade, there a

The iPhora Journey - Part 4 - JSON is King - The How

  The iPhora Journey - Part 1 - Reimagining Domino The iPhora Journey - Part 2 - Domino, the Little Engine that Could The iPhora Journey - Part 3 - Creating an Integrated UI Framework The iPhora Journey - Part 4 - JSON is King - The Why The iPhora Journey - Part 4 - JSON is King - The How As we mentioned yesterday, in reimagining Domino, we wanted Domino to be a modern web application server, one that utilized a JSON-based NoSQL database and be more secure compared to other JSON-based NoSQL platforms. A Domino document existing within a Domino database is the foundational data record used in iPhora, just as it is with traditional Domino applications. But instead of just storing data into individual fields, we wanted to store and process the JSON in a Domino document.  However, text fields (AKA summary fields) in Domino documents are limited to only 64 KBytes, and that is a serious limitation. 64 KBytes of JSON data does not even touch what the real world typically transfers back and fo