In fashion, the way your clothes fit is more important than whether they are the latest style. If they are too long, too short, too tight or too loose, you can't achieve the comfort and style you seek.
So it is with enterprise software. When we see a request for proposals, it usually contains hundreds of detailed specifications for features, but only a cursory list of requirements for compatibility with enterprise architecture and integration with other systems.
This feature-centric approach leads to poor software choices and increases the long term expense of integration and support. If your organization has adopted standard software services for all departments, you should not keep re-purchasing the same features every time any department needs a new point solution. Your organization can save money by standardizing on a database, reporting tools, email, and other shared services.
The way a solution fits with the rest of your architecture may be more important than many of the features that are enumerated in a typical purchase request.
So it is with enterprise software. When we see a request for proposals, it usually contains hundreds of detailed specifications for features, but only a cursory list of requirements for compatibility with enterprise architecture and integration with other systems.
This feature-centric approach leads to poor software choices and increases the long term expense of integration and support. If your organization has adopted standard software services for all departments, you should not keep re-purchasing the same features every time any department needs a new point solution. Your organization can save money by standardizing on a database, reporting tools, email, and other shared services.
The way a solution fits with the rest of your architecture may be more important than many of the features that are enumerated in a typical purchase request.