We argue that research in software engineering metrics and measurement has reached a plateau of sorts, and that the time is right to prepare for an undertaking that could greatly benefit the software producing community; the development of software engineering handbooks. The role of engineering handbooks is described, as are two of the ways they might be used: facilitating reuse, and aiding in the identification of tools, methods, and techniques well suited to particular development tasks. Towards this goal, we propose a cooperative undertaking aimed at creating what we call Software Engineering Utility Assessment Models. These would serve to specify sets of related software engineering tasks and their associated attributes in order to allow for both the categorization and comparison of new and existing tools, methods, and techniques. Some initial thoughts regarding the steps to be employed in their development are illustrated by way of a simple example.