5.7 Chapter Review

5.7.1 Chapter summary

A useful interim review establishes the current problem definition, evidence, uncertainty, trajectory, and next decisions. It demonstrates progress through validated artifacts and reasoned findings, invites feedback on consequential choices, and records how that feedback changes the project.

5.7.2 Common mistakes

• presenting a chronology of tasks rather than evidence of progress;
• hiding unresolved problems to appear further ahead;
• showing every exploratory graph;
• presenting recommendations before the problem is established;
• claiming the project is on track without schedule evidence;
• asking reviewers for general thoughts instead of specific decisions; and
• failing to update the plan after feedback.

Quality standard: An interim review should make it easier to improve the final project by revealing verified progress, material uncertainty, trajectory, and the decisions needed next.

5.7.3 Interim review checklist

• The current problem, audience, and scope are clear.
• Completed, preliminary, and planned work are distinguished.
• Findings are supported by reproducible evidence.
• Material risks and open questions are visible.
• The schedule includes remaining review and revision cycles.
• Feedback requests are specific.
• Next actions have owners and dates.
• The presentation has a central message and readable visuals.

5.7.4 Exercises

Exercise 1. Given a project with an incomplete data dictionary, several polished graphs, no validation plan, and two weeks remaining, write a five-point recovery plan.

One Possible Answer

1. Pause new analysis until essential variable definitions and units are confirmed.
2. Keep only graphs that directly support the central question.
3. Select a feasible baseline and validation approach before fitting additional models.
4. Narrow the scope so one complete analysis can receive technical and communication review.
5. Assign owners and internal deadlines that preserve time for integration and revision.

Exercise 2. Prepare a five-slide interim review for NVRW after the data-quality assessment but before model development. State what is known, what remains uncertain, and what decisions are needed.

One Possible Answer

A useful sequence is: (1) decision and current project scope; (2) validated datasets, grain, and coverage; (3) material data-quality findings and their analytical consequences; (4) early descriptive evidence and remaining uncertainty; and (5) proposed modelling plan, decisions required, risks, owners, and next milestones.

Exercise 3. Develop three trajectory indicators that would reveal whether the project is likely to finish with integrated evidence rather than disconnected analyses.

One Possible Answer

Three useful indicators are the proportion of priority analytical questions with reviewed evidence, the proportion of key joins and denominators that have been independently validated, and the proportion of proposed recommendations already connected to evidence and limitations in a recommendation-evidence map.

Exercise 4. Convert five pieces of review feedback into a response log containing the issue, decision, owner, deadline, and affected deliverable.

Check Your Work

Each row should preserve the original issue, record whether the team accepted, modified, deferred, or rejected the suggestion, explain the rationale, identify one owner and a real or “To confirm” deadline, and list every affected file or deliverable. Feedback should not be marked resolved until the change has been verified.

5.7.5 Questions for discussion

1. How can a team be transparent about uncertainty without losing reviewer confidence?
2. When is narrowing scope evidence of good judgment rather than failure?
3. Which project decisions should not wait until an interim review?