How to Review a Project That Didn’t Go to Plan

Not every project goes to plan. A deadline slips, a budget grows, or a result falls short of what everyone expected. The temptation is to find someone to blame or to move on quickly and hope the same problem does not return. A short project review offers a better path. It compares the plan with what actually happened, separates known facts from educated guesses, and ends with one change that you can test on the next project. The review should take an hour or less, and it should leave people more willing to speak honestly next time.

A practical example

Planned: The reviewer would receive the proof on Tuesday and authorize printing on Wednesday. Actual: The file was ready Tuesday, the review request went out Friday, and the print slot was lost. Those dates establish a delay. They do not establish why nobody sent the request.

Reconstruct the handoff before explaining it

Bring the brief, file history, and approval message to the review. Ask the person preparing the proof and the person releasing it what each expected to happen next. If one expected an automatic notification and the other expected a manual email, record both accounts. Mark anything you cannot verify as an open question. Also record what worked: the proof was ready on time, so changing the design schedule would not address the observed gap.

Choose a change someone can test. For the next two jobs, the coordinator sends the review request when the proof is marked ready and records the send time in the job file. The project lead compares ready and sent times at the next review. That gives the team a way to see whether the change affected this handoff, even if a later project has an unrelated delay.

End the meeting by naming the owner and putting the review date on the calendar. Keep any private personnel concern out of the shared process notes. The next team needs to know who releases the proof, not who received criticism in the meeting.

Compare the plan with the outcome

Start with the original plan. Pull out the goal, the timeline, the budget, and the main steps you intended to take. Then write down what actually happened for each item. Keep the descriptions factual. “The design round took three weeks instead of one” is a fact. “The designer was slow” is an interpretation, and it belongs in the next section, if it belongs anywhere. Putting the plan and the outcome side by side makes the gap visible without arguing about who was responsible for it.

Separate known causes from guesses

Next, list the factors that may have contributed to the gap. Mark each one as known or suspected. A known cause is supported by evidence, such as a message thread, a timesheet, or a record of a change request. A suspected cause is a reasonable explanation that has not been confirmed. Both are useful, but they should not be treated the same way. Keeping them apart prevents the review from hardening a guess into a conclusion, and it shows the team which claims need checking before anyone acts on them.

Identify a contributing factor, not a culprit

Most project problems have several contributing factors, and they usually involve process, timing, or information rather than one person’s failure. For example, a client may have sent feedback by three different channels, or a dependency may have been unclear at the start. Ask what conditions made the problem likely, and what would have made it easier to notice early. This framing keeps attention on the system. It also helps people speak up, because they are describing how the work was set up rather than defending their own performance.

Plan the meeting in advance

Send the plan and the outcome summary to participants a day before the meeting, along with a short list of questions. This gives people time to check their memories and collect evidence, so the discussion does not depend on whoever remembers most clearly. Invite the people who did the work, not only the manager, and keep the group small enough for everyone to speak. Start by restating the purpose, then move through the sections in order and stop on time.

Agree on what went well

A review that only lists problems can feel discouraging, and it hides the practices worth keeping. Spend a few minutes on what worked. Maybe the weekly check-in caught a risk early, or a shared folder made handoffs easier. Write these down with the same care as the problems. When you change how you work next time, you will know which habits to protect, and the team will see that the review is about improvement rather than punishment.

Keep the review separate from performance reviews

A project review examines the work, not the people doing it. If participants fear that honest answers will be used in performance discussions, they will stop giving them. State the purpose at the start, and keep any notes about individual performance out of the shared record. If a serious concern about someone’s conduct comes up, handle it through the appropriate channel and do not turn the review into a hearing. Clear boundaries make the next review more candid, and candor is what makes the review useful.