The author describes how to make metrics a useful part of the development process. He focuses on metrics for software complexity, which can be used to flag potentially nettlesome problems early in the life cycle, before they become expensive to undo or patch. He looks at metrics in the context of designing interfaces for engineers, managers, and both (i.e. a public, as opposed to private, interface).