How many companies have purchased a new application to support one of their major business processes, only to be disappointed with the return on investment? After completing all the due diligence of building the business case, defining needs, identifying potential vendors, distributing the RFP, conducting demonstrations, and finally selecting and implementing the system, it never seems to play out as expected.
Of course the missing step in the above scenario involves examining the business processes. Most system implementations in my experience leave this key step out—companies adapt their internal processes to work with an application. Or, they spend a fortune customizing the solution to support their processes, and then pay an unreasonable amount in future updates.
WHAT DRIVES WHAT? Should the process drive the technology you select or should the technology drive your business processes?
Of course the missing step in the above scenario involves examining the business processes. Most system implementations in my experience leave this key step out—companies adapt their internal processes to work with an application. Or, they spend a fortune customizing the solution to support their processes, and then pay an unreasonable amount in future updates.
WHAT DRIVES WHAT? Should the process drive the technology you select or should the technology drive your business processes?