- Windows HPC hits top 10 among supercomputers
- Ruby on Rails rolls into the enterprise
- Mobile phone chargers are energy vampires
- 10 IT security companies to watch
- Researchers getting the lead out of electronics
Let’s say you have an application or service you have rolled out to hundreds or thousands of people and you discover a serious problem. Not a show stopper that forces you into action, but something that affects how the software performs and potentially complicates life for users.
This is a situation that faces enterprises, software vendors, software-as-a-service purveyors and Web application services providers with monotonous regularity, and one that is unlikely to go away much before the end of the universe. The question is, what do you do when this happens in your organization?
There are two schools of thought: First, you 'fess up, make certain that all users and all tech support know what the problem is, how it will affect the product, what can be done about it, and to the extent you are legally liable and ethically responsible, compensate the users. That’s the sophisticated, big boy approach.
The alternative is to not tell your users or even all of the tech support staff, add the problem to the list of stuff to be fixed and hope that not many users discover the problem. Should they do so, you treat it as if it were a minor problem, minimize the user’s concerns, tell them it will be fixed in the next release and hope they go away. That’s the weenie approach.
I’ve been thinking about this because the latter is far more common and, indeed, just happened to me courtesy of Network Solutions, a company I have chastised in previous Gearhead columns over the problems with its e-commerce offering.
Here’s what happened: My wife’s company, which uses the Netsol shopping cart, decided it needed to provide overseas sales and shipping due to the number of overseas inquiries it was getting for its apparel. For U.S. and Canada orders, the company provides free shipping, but shipping overseas is expensive.
So I changed the shopping cart to charge for foreign shipping, tested it with a couple of addresses in England, and thought nothing more of it. Until the first overseas order came in from a town in Victoria, Australia. The system said the shipping was free when in reality it would have cost $117 via UPS.
I called Netsol support and went through my shipping logic setup with the tech who agreed it looked correct. He put me on hold and then came back five minutes later to tell me it was a known bug. If there was any text in the state field for international orders then the shipping logic behaved as if the order was domestic.
Partner Content
SMART Steps Toward Consolidated Workload Automation
Consolidating job scheduling into a single, comprehensive workload automation solution is a critical first step to effective workload automation (WLA).
White paper on WLA here
A Comprehensive Approach to Practicing ITIL Change Management
Read a compelling whitepaper by EMA, Inc. to learn best practices for integrating workload automation.
Whitepaper here
2 Minutes to IT workload automation
BMC CONTROL-M can put money back into your IT budget and strip the complexity and risk from workload automation.
View video here
Gain a faster, cheaper way to manage workload
BMC CONTROL-M can help you migrate to a workload automation solution to meet your organization’s goals.
Listen here for more info
Comment