Free Newsletters

   All InfoWorld Newsletters
Reality Check | Ephraim Schwartz » Gadgets can be dangerous to your corporate health

December 15, 2006 | Comments: (0)

Gadgets can be dangerous to your corporate health

With SOA and Web service APIs on the back end and AJAX on the front end, the age of DiY (do it yourself) software appears to be upon us.

Over the past few days I heard from software companies both big and small, all extolling the amazing DiY capabilities of gadgets, widgets or just plain applets.

The Microsoft gadgets Web site has as good a definition as any so here it is:

"Gadgets are a new category of mini-application designed to provide information, useful lookup, or enhance an application or service on your Windows PC or the Web. Examples might include a weather gadget running on your desktop or on your homepage, an RSS Gadget that pulls in your favorite feeds, or an extension of a business application providing just-in-time status on the pulse of your business."

From startups such as Coghead to the giants like Microsoft and SAP, vendors seem to be falling over themselves to show how hip they are about gadgets.

According to the true believers ordinary users, not programmers, can build out their own special piece of functionality, build their own applications or build extensions to core functionality thanks to the gadget paradigm.

Here's what it says on the Coghead Web site.

"The revolutionary Coghead application delivery service provides an intuitive drag-and-drop development environment with specialized templates for creating a nearly limitless range of applications."

"Limitless range" is what has me scared.

I met with SAP this week and they were all aglow telling me about their latest gadgets that can give you an alert box for an RSS reader that tracks business events rather than just news or blogs.

There's also an SAP gadget that allows a sales manager to track when a sales rep closes a deal, as well as a gadget that sends alerts for KPIs [Key Performance Indicators] and a workflow gadget that shows the purchasing manager the queue for all the requisitions waiting for approval.

Look, I'm all for the idea. I just want to apply the brakes a wee bit.

All of this sounds great and if you’re a weather watcher, go ahead and build a gadget for yourself that tracks the next storm.

But I question the long-term benefits of gadgets if you are part of an enterprise-sized company with thousands of employees that all need to be eating off the same plate.

Where is the quality control in these DiY applications? How do you know you're getting the right information?

What kinds of decisions are you making based on this data? Is it available for e-discovery in case of a law suit?

And finally, can it scale? Can 10,000 employees all ping the warehouse management system simultaneously to see if there are any pink widgets left?

The concept of embedding software in software has its benefits, but what is good for a single user is not necessarily good for thousands of users. Scale changes everything. Just remember that.

Posted by Ephraim Schwartz on December 15, 2006 03:25 PM


RATE THIS ARTICLE:





 

  •  
  • COMMENTS




Ephraim, I have a different point of view. I can remember when spreadsheets first came out. People were saying, "we can't possibly give "users" the ability to create their own financial models! Imagine the chaos! What if someone gets a formula wrong!" In the early 1990s IBM required a special approval process for an employee to get an email address -- fearing the chaos that might result if employees were permitted to issue electronic communication to those outside of the company network. In fact, there was a time when the British Crown had laws preventing people from operating a printing press without a permit (what if they printed something seditious!). Invariably, people benefit from the democratization of information. Empowerment trumps control.

Posted by: Paul McNamara at December 15, 2006 06:14 PM

Paul,
I guess we've come full circle then. Because you remember when people said "we can't possibly give users the ability to create their own financial models," using spreadsheets on their own C: drive.
Well, thanks to compliance, Sarbanes-Oxley, e-discovery, it is true once again.

Companies are realizing there is too great a risk factor in allowing standalone financial models, emails, etc.

Everything is moving back onto the corporate server.
Ephraim

Posted by: Ephraim at December 15, 2006 09:06 PM

I agree with Ephraim; companies have issues with models and data feeds "from the field". I don't disagree with the potential usefulness of these home grown (DIY) tools but the issue truely comes in when you look at the disparity in the results when you have the "same information" from two different people. Would you trust your finances to someone elses spreadsheet that isn't QA'd or audited? How about your healthcare information like tracking blood sugar, weight loss, liver proteins and enzymes, etc? Dang, I guess that calculation on the percentage difference was done wrong by Bob in the lab, I sure hope Mrs. Johnson doesn't find out that we did (insert any bad thing you can think of here) to Mr. Johnson ...

Posted by: Jim at December 15, 2006 09:24 PM

Ephraim, this is the great debate of our day: how to balance the need for solid compliance while maintaining an environment that fosters innovation. Products like Coghead allow companies to innovate faster by letting the people close to a business problem participate in the solution. But, unlike Excel, Filemaker and other PC-based approaches, Coghead's 100% web-based approach centralizes management, backup, disaster recovery, security and transaction logging.

Jim, I think you raise a different (and equally important) issue. Our goal (at Coghead) is to allow domain experts to create a particular class of applications. These applications can be QA'd and audited just like any other app. There will always be a need for programmers to create large, complex apps. But, in nearly every organization, there is a pressing need for smaller, less complex, departmental-level apps. These needs typically don't fit neatly into a packaged application and can't tolerate the time and expense of traditional custom application development. Today, when people have these needs they often resort to innappropriate methods like Filemaker or MS Access. We want to give them a better way.

Posted by: paul mcnamara at December 17, 2006 11:00 AM

Technology White Papers

 

InfoWorld Technology Marketplace

» Technology White Papers Library

Technology White Papers by Topic

Technology White Papers E-mail Alert

Find out when the latest white paper is available:
 
 
» BUY A LINK NOW

Sponsored Technology Links