Providers of systems engineering services and their employees are not always able to be the masters of their own destiny. When working in staff augmentation roles under the auspices of another company, they are typically forced to operate within the corporate culture from which they derive their livelihood, following “foreign” processes and procedures, responding to orders and directives. This situation calls for an alternative maturity model for those that provide systems engineering services. While a client organization might be maturing according to any of several proposed models (SEI 1993, SEI 1995, EPIC 1995, ISO 1990, IEEE 1994), the services contractor cannot necessarily be said to be achieving a similar status.

This should not, however, preclude significant maturation goals on the part of the service provider. The Phoenix Imperative is both a business model and maturity model that has worked effectively in several corporations providing system engineering services. It was developed in the context described above and honed over a period of several years with several customers. It provides not only an alternative to the other organizational maturity models that have been proposed, but also delivers the potential for adoption as a personal maturity model for individuals interested in increasing their effectiveness within the context of employment with a service provider.