Given that the key to the reuse program is ``well specified correct, robust and efficient'' designs and code, several safeguards have been put in place which stand to have beneficial side-effects for project teams.
The entrance criteria are strict and uncompromising. This leads to a development approach for reusable code that is more exacting than would otherwise be necessary. If this feeds back into the project teams, the results can only be beneficial to the quality of delivered products. The level of documentation, the use of standard testing mechanisms and adherence to programming guidelines are all strongly monitored for objects in the reuse library. This is necessary in order to ensure consistency within the library. Only by maintaining the consistency and stringent requirements on quality can we hope to achieve effective reuse - to narrow the cognitive distance. If this insistence on quality improves the processes used within the project teams, then it becomes a beneficial side effect.