A project often ends with a handover, a revenue report, or a thank-you meeting. Yet if everyone immediately moves to the next assignment, the most important part can be left behind: the experience just created. A campaign may hit its target while requiring too many approval rounds; a course may receive strong feedback while preparation exhausts the instructor and coordinator. If those lessons are not recorded, the team will have to learn them again next time.
A one-page review is neither a performance report nor a reason for a long meeting. It is a way to learn from work: short enough to write immediately after a project, yet clear enough for someone else to reuse. Its purpose is not to find someone to blame. It is to see which mechanisms helped or hindered the result.
Start with the result worth retaining
Open with three sentences: what the project needed to achieve, what actually happened, and what evidence supports that result. For example, a sales team might write: the goal was to reduce the response time for new leads to below two hours; in the final three weeks, median response time fell from five hours to one hour and forty minutes. This forces the team to separate an observed outcome from the general feeling that “things got better.”
There is no need to list every metric. Select one to three indicators closest to the project objective: completion rate, processing time, repeat rate, rework, cost, or customer feedback. If no numerical data exist, say so and use available evidence such as the number of escalations, documented comments, or delivery progress. Candour makes the review more useful than a polished success story.
Examine the moments that changed the direction of work
The most useful part is usually two or three moments when the project accelerated, slowed down, or changed course. Rather than writing “coordination was weak,” describe the situation: only one person updated the content board, so the design team used the wrong version; after one owner was assigned to update it before 4 p.m. each day, the error stopped recurring. This detail shows that the lesson is not the slogan “coordinate better,” but a clear update rhythm and ownership.
The questions asked also shape what can be learned. Ask: what helped the result emerge; what created delay or rework; which assumption was wrong; and which signal could have been noticed earlier. When answers are tied to a moment, a decision, and evidence, the team can more easily turn them into a specific change for the next project.
End with one change that has an owner
A one-page review becomes useful only when it produces action. The final section should contain no more than three decisions for the next project. Each decision identifies the change, the accountable person, and when it will be applied. For example: “Before the next campaign starts, the project lead will prepare a one-page set of assumptions about the target customer and ask sales and operations to confirm it within 48 hours.” This is a checkable commitment, unlike the general intention to “prepare more carefully.”
The same principle applies to individual projects. After completing a lecture, proposal, or internship, spend 20 minutes recording what you did, what made a difference, and one practice you will change next time. Over time, these short pages become a genuine capability portfolio: they do not merely state what you took part in, but show that you can observe, learn, and improve how work gets done.
A small rhythm that keeps experience from disappearing
Do not wait for a major project to review the work. Schedule 30 minutes within 48 hours of each finishing point, invite the people who did the work directly, and prepare one page with four sections: objective and result, what worked, what needs improvement, and the change for next time. When this becomes a regular rhythm, an organisation does not simply complete more projects. It accumulates better ways of working through every project.
