Clarity of Requirements -There is a popular misconception that advances in hardware, software, programming languages, and architectures allow companies to deploy technology quickly, easily, and cheaply for almost immediate improvements in productivity, quality, and competitive advantage.
It is true that these advances have made technology more accessible to companies and easier to work with. But unfortunately, the acquisition and mechanics of hardware and software have never been the hard part of deploying technology to the benefit of the business.
The hard part has always been, and continues to be, understanding the problems, understanding what the company must do to solve the problems, and understanding the role that technology plays in the solution. Defining what the technology must do is far harder than figuring out how to do it.
Patience and discipline must be exercised during requirements definition. The key to successfully deploying technology to the benefit of the business is to be absolutely clear on what the technology must do. Sacrificing clarity during the requirements phase with the intention of saving time and money not only results in protracted implementation timelines and excessive costs, but also results in sacrificing the value of the system to the business over its entire life.
How We Do It Page 3 of 5