Designing the type list

The mistake everyone makes is a project type per department, service line or client segment — forty types with identical behaviour and nothing gained. The right question is what BEHAVES differently: does this group of projects burden differently, capitalize, bill differently, or permit different transaction classes? If not, it is not a type; it is a classification or a report attribute. The typical shape is three to eight types, and classifications are the release valve — which is also the answer to the stakeholder who wanted six project units.