I have an unusual background; a Bachelor in Business and a Masters in Computer Science. Computers had always been my passion and business my curiosity. I decided to study business in university because at that age I had already gone through much of the curriculum for CS with some gaps that I didn’t care much about at that time, later on I filled these gaps, mostly, through my Masters and reading.

Given this background I tend to understand both worlds pretty well, the inherent psychology of the people involved, and the gaps (or lets say chasms) between them. Lets face it, most of us technologists think the business user is an annoyance to put it mildly. Need evidence? Here’s a typical occurrence:

Hotshot programmer Joe spends a week creating an algorithm that he believes to be living proof of his genius. While showing it to his prospective business users they all agree that the green button is a little too green and that a red button should be placed somewhere on the screen; Joe’s labour falls on deaf ears. Joe, in his inability to convey the genius of his labour concludes that business users are (insert your favorite stereotype here) and vows to defiantly plaster his Dilbert comics all over the wall of his cubical.

The problem here is that business users, at least most of them, cannot think in the same terms software people can. They just cannot imagine and/or extrapolate in the technology domain as us software people can. It’s just not the area of their experties. Plain and simple and has nothing to do with their IQ.

Historically this led to business systems being developed based on IT’s understanding of the business needs which is a disconnected process. Agile software development methodologies address these problems but are inherently limited due to the complexity and cost of prototyping. Of course a Ruby on Rails developer is much more agile and much more capable of cranking prototypes of features than, say, his Java counterpart, but eventually he won’t be able to do everything leaving nothing for his user’s imagination.

I’ve been working with salesforce.com for more than 8 months now and to be very honest, I was very skeptical at the beginning. I’ve been around enough to know that there are no sliver bullets (SOA or SOAP Webservices anyone?), and when I was introduced to salesforce.com my initial reaction was along the lines of “Yeah, cool, nice toy.. Lets see how soon I can make it break under its own weight of unfulfilled promises!.” To my chagrin, at the time, the platform continued to deliver at an alarmingly fast pace.

When I was working for BEA, it was typical for a pre sales cycle to extend for 6 months or even a year. At our local office in Toronto we had a small army of pre sales engineers that spent most of their time creating demos to illustrate how our products can address customer requirements.

These demos usually were very labour intensive, have absolutely nothing to do with the real project, and of very poor code quality (its just a demo! right?). This naturally led to the business users (and sometimes IT users as well), to take very important decisions based solely on their ability to imagine, extrapolate, and fill in the gaps. They had to somehow envision the final outcome. If you’re reading this and came that far then this is an all too familiar process. This almost always led to frustration for business users because what they saw in the demo has nothing to do with the final product, which usually also took 8 months to build and cost an arm and a leg!

With salesforce.com, we almost always engage business people (exclusively) who have business problems they want to solve. We interview them, understand their challenges and requirements, spend no more than a week building a salesforce.com prototype (using their own data!), then go back for a show & tell. In my experience so far, this bedazzles the business users and moves the sales process at velocities I’ve never experienced before.

Why does it work this way? Simple. Because with salesforce.com there’s no need to tell your prospective client to imagine anything. Whatever they want can 90% of the time be implemented and turned around very quickly. This creates confidence in their purchasing decision and makes the value of their investment immediately accessible.

Again, I still believe in the non-existence of Silver Bullets, and salesforce.com is no Silver Bullet too. It has its limitations and oversights like any other product. But right now they are pretty much ahead of the curve and they don’t seem to be slowing down at all. That doesn’t mean that Java, Groovy, Ruby, Rails, Grails, PHP, etc… are useless or dead, far from the truth in my opinion. It just means that certain class of enterprise development isn’t a fit for these paradigms any more. Try “Mashing Up” salesforce.com with any of the above and get the best of both worlds. Add EC2 or Google App Engine into the mix and you’ll begin to realize how the enterprise software development of tomorrow is very different from that of yesterday.

In a world facing a major economic crises, IT will continue to be viewed as a “Cost Center” and the days of multimillion dollar investments in what amounts to data entry and reporting systems are over.

The world is changing. Get over it quick or turn into the COBOL programmer of tomorrow.