Midyear Project Review: Decide What Happens Next
- How do you review unfinished projects at midyear?
- What belongs on the project list?
- What evidence should you collect for each project?
- Does the original purpose still justify this version?
- What does a worked project review look like?
- Which decision should you record?
- What can the project teach you about the next attempt?
- What should you leave for your future self?
- Sources
How do you review unfinished projects at midyear?
Review each personal project as a specific piece of unfinished work. Record its intended result, what exists now, the next obstacle and what completion would still require. Then choose to finish, reshape, park or stop it, with a concrete next action. Keep private records private, preserve useful work and agree changes with anyone who shares the commitment before treating a personal decision as final.
A folder can contain months of work and still leave its owner unsure what to do next. This review is designed to produce a usable handoff: enough information to resume deliberately, change the plan or close it. It is an original editorial worksheet, not a validated productivity assessment. The example below is fictional.
For questions about the direction of your year, start with the broader midyear personal review. Here, stay with individual projects and the work actually in front of you.
What belongs on the project list?
The Project Management Institute describes a project as temporary work producing a particular product, service or result. That gives this review a useful boundary: list something that could reach an identifiable end, rather than every continuing responsibility in your life.
“Produce a family photo book” belongs on the list. “Keep family photographs organised” is an ongoing responsibility; you might extract a bounded project from it, such as organising one named collection. Neither is more worthwhile. They simply need different records.
Gather the projects you still consider active from your notes, folders and task lists. Give duplicate references one entry. A project mentioned in a notebook and an app is still one project. Put uncommitted ideas on a separate page rather than quietly adding them to the current workload.
For each entry, name the result and its location: “Photo book, draft in the family-book folder” is more useful than “photos.” Work only with material you own or are authorised to review. Avoid copying other people's private messages or images into a shared review document.
What evidence should you collect for each project?
Create a short project card. Use the same fields for each project so that a polished folder does not receive more attention simply because it is easier to browse.
| Field | What to record |
|---|---|
| Intended result | The specific thing you meant to produce |
| Current artifact | The draft, prototype, list or other work that exists |
| Last completed step | An observable change, with its date if known |
| Open work | Tasks still needed for the current version |
| Blocker | The missing information, decision, permission or resource |
| People involved | Who must agree, contribute or receive the result |
| Proposed decision | Finish, reshape, park or stop |
| Next action | One action you can identify and follow up |
Keep evidence and interpretation apart. “Eight spreads have approved captions” records a state. “Nearly finished” is a judgement that needs more explanation. A draft's existence does not establish that someone has checked it, and a sent request does not establish that permission has arrived.
An unknown is a legitimate entry. If you cannot identify the current version, finding it becomes the immediate task. Do not estimate the remaining work from a file you have not opened.
Does the original purpose still justify this version?
The Association for Project Management's business-case guidance considers benefits, costs, risks and alternative options. It also describes reviewing the case at decision gates as information develops. A personal project does not need a corporate approval pack, but the comparison offers a useful question: given what you know now, which version is worth pursuing?
Write two separate sentences: what you originally intended, and what you still want. They may be identical. If they differ, name the change instead of rewriting the old notes as though the new purpose had always been the plan.
For the fictional photo book, the original aim was a comprehensive account of a family trip. The current wish is a small book to share at a gathering. That change could justify a smaller selection. It does not automatically justify removing photographs other contributors expected to include; that requires a conversation.
Keep money already spent separate from money still required. Record an actual purchase as a past cost, a current quotation as a quotation and an unknown future cost as unknown. This worksheet does not decide whether a financial commitment is appropriate.
What does a worked project review look like?
Suppose the photo-book draft has twelve spreads. Eight have both selected photographs and approved captions. Four still need captions, and two of those also need a decision about which photograph to use. No printing order has been placed.
The project card might say:
Current result: twelve-spread digital draft; eight spreads ready for the contributor's final review, four incomplete. Here, ready means ready for review, not approved for printing; the project remains open until the agreed final checks and handoff are done.
Blocker: two image choices need another contributor's agreement. The remaining caption work is available to do now.
Purpose check: produce a coherent book for the gathering; the group has not yet agreed to reduce its scope.
Next action: send the two specific image choices to the contributor, with a proposed response date, and identify the caption work that does not depend on the reply.
Eight out of twelve spreads is two-thirds, or approximately 66.7%. That is a count of spreads meeting the stated condition, not proof that two-thirds of the effort, time or cost is complete. The four remaining spreads may require quite different amounts of work. Do not turn a count into an effort forecast.
For a separate scheduling illustration, suppose the owner estimates three remaining work sessions of 45 minutes each. That totals 135 minutes, or two hours and fifteen minutes. If only two such sessions are available before the next review, the planned capacity is 90 minutes: one 45-minute session less than the estimate. Those invented figures reveal a planning mismatch; they do not predict this reader's pace.
The owner can change the proposed date, seek help or discuss a smaller scope. Simply entering all three sessions in two available slots would not resolve the mismatch.
Which decision should you record?
Use these as working labels for this worksheet, not as a formal project-management classification.
Finish: the present version still matters and you intend to complete its remaining work. Record the next action and the evidence that will let you close it. In the example, that could mean resolving the outstanding choices before scheduling final review.
Reshape: preserve the purpose while changing the proposed result. Record both versions and who must agree. An eight-spread book is a different scope from a twelve-spread book, even if it uses work already prepared. Do not mark the larger version complete by silently changing its description.
Park: retain a usable restart note while removing the project from the active work plan. State what would trigger reconsideration: a contributor's reply, a named decision or a review date. “Later” provides no such trigger. Parking is not a promise that circumstances will improve.
Stop: decide that you will not pursue the project further. Record what remains useful and what obligations require attention. Tell affected contributors before treating a shared commitment as cancelled. Stopping work does not require deleting files, cancelling services or spending money during the review.
If the decision depends on somebody else, label it “proposed” or “awaiting agreement.” The review can be complete while that decision remains open.
What can the project teach you about the next attempt?
The University of Edinburgh's reflection toolkit presents a sequence of describing an experience, examining its meaning and deciding what to do next. It cautions that short answers to the headline questions may lack depth and encourages concrete action planning. Borrow that sequence for one incident from the project, rather than conducting another review of your whole year.
For example, the fictional book's owner requested “feedback” and received comments about layout when the unresolved need was permission to use two images. The lesson is narrow: the request did not identify the decision needed. The next request can name the two images, explain the intended use and ask the relevant person for a clear response. This is an invented communication example, not a claim about how every stalled project behaves.
Keep the lesson separate from a judgement about character. The record needs a changed action, not a new label for the person doing the work.
What should you leave for your future self?
Save the current artifact, the project card and the decision together, in a location you can find again. Preserve the earlier scope description when you change it. For a parked project, add the unresolved question, the last useful version and the reconsideration trigger; for a stopped project, record the closure decision and any remaining communication.
Read the final card as if returning after a break. Can you identify what exists, what remains uncertain and the first permitted action? If not, clarify that gap before adding more planning detail.
Move only the continuing work into your next-six-months plan. Leave parked projects visible in their own record rather than giving them invented weekly slots. A finished review is a set of explicit decisions and open questions, not a guarantee that every project will be finished.