A presenter discusses logistics milestones with colleagues in a boardroom.

A Small Scope Change Can Move Three Other Deliverables

A request to add one interview can sound small because the final video may grow by only a minute. I would assess the work behind that minute before agreeing to it. Arranging the interview, obtaining the material, revising the edit and securing another review can affect commitments that are not visible in the request itself.

Illustrative workflow visual.
  • CategoryProject Management
  • Published
  • AuthorBongiwe Selane
  • Reading time4 min read

A request to add one interview can sound small because the final video may grow by only a minute. I would assess the work behind that minute before agreeing to it. Arranging the interview, obtaining the material, revising the edit and securing another review can affect commitments that are not visible in the request itself.

My example is a fictional construction-project update with a video, a short web article and a presentation. All three use the same approved explanation. I would treat a new interview as a proposed change to that connected package, not merely as an extra clip.

I capture the requested outcome

I would ask what the interview needs to add. Is a decision missing from the current explanation, or does the owner want another person's perspective? The answer determines whether an interview is the appropriate solution and which deliverables need to change.

Two agricultural colleagues discuss an issue register in an orchard office.
Illustrative agricultural coordination.

My change record would retain the requester's wording, the intended audience and the reason for the change. I would keep those separate from my proposed implementation. Otherwise, a production suggestion can quietly become the assumed requirement before the owner has considered alternatives.

I trace the affected work

For the fictional package, I would connect the interview to access, availability, filming, transcription, editing and review. I would then check the article and presentation for statements that depend on the same explanation.

Two colleagues review a compact capacity spreadsheet in an office.
Illustrative capacity planning.

The APM describes change control as capturing and evaluating change requests before approving, rejecting or deferring them. That is the limited framework behind my proposed record. APM change control. The specific production dependencies here are my own illustrative example.

I distinguish known effects from assumptions

I might know that the editor needs the final interview before completing the assembly. I might only assume that the interviewee is available. I would label those differently and name the person who can resolve the uncertainty.

A provisional impact assessment should not look like a firm quotation or a guaranteed schedule. I would state which confirmations are outstanding and when the assessment needs updating. That gives the decision-maker a usable picture without pretending that every detail is settled.

Two women discuss a handover checklist at a meeting table.
Illustrative handover discussion.

I offer options that preserve the purpose

One option could retain the original release and publish the interview later. Another could replace an existing sequence. A third could move the whole package after the necessary review. Each option should explain what the audience receives and which commitment changes.

I would avoid presenting a rushed version as equivalent to a fully reviewed one. If an option removes a review step, that is a substantive difference for the owner to assess, not an invisible efficiency saving. The trade-off belongs in the decision record.

I update the whole plan after the decision

Hands work at a desk with a file-review screen and spreadsheet.
Illustrative approval review.

Once the responsible owner chooses an option, I would update the brief, task dependencies, review windows and affected release records. I would tell the people whose commitments changed and identify the version of the plan now in use.

Approval of a change is not evidence that the changed work is complete. The new tasks still need their own execution and acceptance. I would keep the original decision linked to those tasks so that the team can understand why the extra work exists.

I check whether the intended benefit arrived

Two agricultural colleagues review a calendar on a tablet beside an orchard.
Illustrative availability in the field.

At delivery, I would compare the accepted package with the reason recorded for the change. Did the new interview answer the missing question? If it introduced a different story, that may require another explicit decision rather than a quiet declaration of success.

This is how I would keep a small request from becoming an invisible expansion. The change remains connected to its purpose, consequences and acceptance, while the people doing the work can see which commitments they are now expected to meet.

Research and example note

Prepared for 11 November 2026. The construction engagement is fictional and the article concerns content coordination, not engineering or site operations. The APM reference supports only the general change-control concept; no client outcome or delivery estimate is claimed.

YOUR PRIVACY

Cookie preferences

Optional analytics and advertising cookies help improve this site and support relevant advertising. You can accept or decline each category.

You can change this choice at any time using Cookies in the footer.