Summary: The post-implementation review phase of automated information system development work provides a feedback mechanism to management that can measure project results and gather data necessary to analyze what corrective action may be required before beginning another system development effort. The project leader, together with the members of the original development, conversion, and implementation team, performs the post-implementation review. The first step in this process is identifying the project objectives to determine whether they were met. The review team should be provided with the developmental, conversion, and implementation cost estimates; the detailed schedule for developing, converting, and implementing the system; the layout of the proposed system; the quantitative and qualitative benefits expected; and the estimated cost of operating the system. Gathering the data to be used in measuring results against the objectives is the next step. Actual costs through implementation and completion date information should be available from the organization's project control system or financial accounting records. Deviations and danger signals indicating a less than satisfactory system performance need to be identified and their root causes determined. The causes usually fall into the following categories: (1) a lack of clear objectives or clearly delegated responsibility and accountability; (2) inadequately detailed plans, insufficient, undertrained, or poorly motivated staff; and (3) inadequate resources allocated to the project. The final step in the review process is the recommendation of corrective action. Once these recommended corrective actions are developed, the post-implementation review is made final and submitted to management. The action taken by management will generally involve management process improvement, procedural documentation or standardization, or the upgrading of personal skills.