Silver Bullet Syndrome

I've noticed a trend in my current organization which I'm sure is common to many companies. I'm having a hard time defining it, but let's call it "Silver Bullet Syndrome"... where when faced with some business problem, companies immediately look for an off the self (OTS) technology solution - many times without understanding the full scope of the problem. The OTS solution is viewed as a "Silver Bullet" and will immediately solve all of the organization's woes.

Now I'm not saying all off the shelf software is bad, but often times these business problems are not generic enough to be addressed by a general solution. The lack of flexibility of many OTS solutions compounds the problem, forcing companies to modify business processes or requirements to meet the capabilities of the tool instead of the other way around.

Once the tool is in place however, another problem manifests itself. This often starts with a management mandate like, "OK now that we have our shiny new Silver Bullet 2.0 and have paid $$$ for it, let's get the biggest bang for our buck by using it everywhere!". What I've seen is that the limitations and compromises encountered when solving the original problem are now limitations and compromises of multiple business processes - making the entire organization less effective.

In my current situation JCAPS is playing the Silver Bullet role. JCAPS was initially purchased for it's single customer view capabilities. Even though they've had continuous problems with that implementation, the organization moved forward with a JCAPS-based business automation project. Looking at the suite, someone noticed the JCAPS Business Activity Monitoring (eBAM) functionality and now wants to use this for system level reporting on the system.

Some examples to drive home the point on how the company has modified it's business to meet the capabilities of the tool:
  • This organization is traditionally .NET and has a large staff of .NET developers and infrastucture. It has little expertise or experience supporting Java enterprise applications.
  • While some of the EDI messages this organization supports are included in the JCAPS OTDs, some are not. JCAPS does not provide the capability to customize these modules, forcing the company to develop "home grown" solutions anyway (reducing the benefit of the tool).
  • The system reporting that the company wants is a mixture of tables and charts reporting on the performance of the system. The eBAM module only supports specific chart types (bar, pie, light) and no tables. Furthermore, eBam only works with Oracle or an internal proprietary database. Not a good fit for a company which mainly uses Sybase tables.

Currently the project is behind schedule (and I'm guessing over budget). I believe this company would have a better chance for long term success if the organization focused on using it's tech knowledge to create some custom solutions that meet their exact business needs (and they could support), instead of looking for a "Silver Bullet".

Comments

Post a Comment

Popular posts from this blog

I Believe...

A recent reorg at my company left me with a new manager - and a different approach to software development than my team had been previously following.  Our new approach is one that I don’t necessarily agree with, but it led me to think about - and reevaluate -  those tenets of software development that I think are important and that I believe lead to increased quality and productivity. This post will consist of fairly high level discussions about how to organize code, teams, and projects - but contain very little actual code. Many of these ideas will not be my own.  They are mostly ideas I’ve learned from others and their willingness to share their experiences with me.  They are, however, ideas that I’ve practiced and hardened as I’ve worked to build my own ideal environment for delivering value through software . Many of these ideas I now take for granted as commonplace (even though they aren’t).  I felt a need to document them anyway - so people can understand what to expect (a
Read more

Performance Tuning JCAPS - Part 2

It's been close to 2 months since my first Performance Tuning JCAPS post. Since then, we've noticed our servers running out of TCP connections under heavy load. Researching this problem, we learned that the JCAPS' JMS server makes heavy use of TCP in implementing Request/Reply queues . We approached Sun for guidance and they assured us that they've had success implementing high throughput applications using the JMS request reply solution... but how? It appears a multi-step solution is needed. First, running out of TCP connections in a scenario like ours is a JCAPS bug addressed in an ESR (110348) and rolled into JCAPS 5.1.3 Update Release 3 . We installed this update and noticed a marked improvement. Running my simple 75 user simulated test, transactions took 2521 ms to round trip (compared to the previous time of 20128ms). While this is great improvement, an average of 2.5 seconds is still really slow for this simple transaction. We reported our findings to Su
Read more

FRail :include

I really like developing with Rails, but I've been frustrated the last few days by some things Rails should do quite easily, yet doesn't. I've already written here and here about some of my struggles with Rails :include clause. Here's one more... Let's say you have a has-and-belongs-to-many relationship. If you :include this relationship in a find query, Rails will automatically create the join clause including the lookup table! That's cool. Unfortunately, it looks as if only the :include clause provides this piece of functionality. Why isn't the same functionality provided via the :join clause or through a general purpose module? This doesn't make any sense to me! I'm working on a database application where I don't need to display a lot of data, but the data displayed is heavily filtered by it's connections to other information in the database. I need to join a lot of tables to perform the filtering operation and using :include
Read more