The technical requirements are an important foundation in any product development. Only that which is precisely defined can be accurately assessed and measured later on.
An important consideration during the definition of a product’s specifications is the tug of war between what is desired and what is ultimately feasible to produce. The reality is that not all that is defined in the product’s specifications will actually be feasible to produce, either from a technical or a cost perspective.
It is important that when it comes to defining product specs this is done carefully and with consideration. Often the unfiltered wishes of the Marketing department are included in the definition, without first examining whether this is technically feasible. Therefore it has proven to be highly advantageous to carry out a so-called feasibility study before defining the specification in order to avoid complications down the road.
For complex developments, the specification includes several hundred to thousands of individual points. Obviously not everything can be equally important with such a great number of parts and so it has become common to speak of “must haves” and “nice to haves”.
Once the specifications have been established, they should not be changed anymore! However the reality is that this is not always possible.
So-called change requests are more frequent than the project manager would like and in the end they always cost time and money. So when defining the initial specs it is always important to consider how high the risk is that specifications will change at a later date.
-> Back to overview
-> More information on the methodology behind the 24 design factors