PM Excellence Academy
Module 10 of 12 · Managing Change & Quality
Both leak out quietly, under deadline pressure, when no one makes them visible. Managing change and protecting quality are one discipline: the refusal to let the important thing happen in silence.
Illustrated module guide · the complete walkthrough · companion to the Quick ReferenceModule 9 taught you to spot when a team is quietly absorbing cost. Two of the most common silent costs in design work are a specific pair. Name them.
The pattern
Big disruptions get attention. The problems that erode a project are small and silent: a “quick” extra option, one more review cycle, a new stakeholder, a coordination check trimmed under a tight deadline. Each feels reasonable in the moment. None gets named as what it is. By the time the cost becomes visible, in eroded margin or a coordination error caught at permit, the inexpensive moment to act has passed.
Unmanaged change is fee the firm gave away for free. A skipped review is risk the firm shipped for free. Both are the same leak.
Strong project managers do not attempt to prevent change, and they do not personally re-check every drawing. They do one thing relentlessly: they refuse to let the important thing happen silently.
Change · the test
A change is any adjustment that alters the project’s original assumptions in scope, deliverables, schedule, level of effort, or fee. The size of the request does not decide whether it is a change. One question does:
Has the boundary of the project moved?
If the boundary moved, it shall be acknowledged and managed, whether it arrives as a formal scope addition or as a polite “could you also…” in a meeting. The common forms:
?Pause & predict.
In a review, the client says “this looks good, could you show one more option?”, then adds “let us pull in our operations team,” then “let us add a working session next week.” None sounds unreasonable. Is this a change?
Change · the cost
Unmanaged change follows a predictable sequence. Caught at step one, it is a conversation. Left to run, it is a write-off.
The team performs the extra work without discussion, and the client assumes it is included.
The team absorbs extra meetings and iterations without understanding why the workload keeps growing.
More work is performed than the fee was built for. Margin disappears, and no one can point to where.
Change is normal, and the fix is not to fight it. The fix is a process that catches the boundary moving and turns it into a decision, every time. That process has five steps, and it starts before the project does.
Change · the model
Effective change management does not start when a change arrives. It starts at the beginning of the project. With these five steps set up front, a mid-project change becomes a routine, fundable decision instead of an awkward, money-losing surprise.
Name the reality of change early: “What is your preferred process for changes to scope, schedule, fee, deliverables, or field conditions?”
Stand up a Change Tracking System, the Project Change Log. Record date, description, reason, cost, and impact. Track every change, asked-for or not.
“Once we pass this review period, it is closed.” Name the milestones (SD, DD, 30/60/90% CD) that, once accepted, become the basis for future work. Rework after that earns compensation.
Settle up front how added scope gets authorized: who can request it (owner, consultant, outside party) and how it is priced.
Document the process and the decision, and share it internally and with the client. The change, and the credit for it, becomes visible to everyone.
Steps 1 to 4 are set at kickoff and in the agreement. Step 5 runs every time the boundary moves. When a change appears, the structure already exists, and the response is simple: log it, check it against a review period, route it through the agreed additional-services process, and document the decision. Address it in real time. Submit the change order before doing the work, not at invoicing. Approved changes adjust the schedule and budget. The sequence of work stays intact even as the dates move.
?Pause & predict.
A project manager logs a client-requested change but does the work first and plans to “sort out the fee at invoicing.” Which steps of the model did they skip, and what does it cost?
Change · get credit
The Change Log exists for one reason: to make sure the firm gets credit for every change, positive or negative, and ties it back to a contract provision. How a project manager pursues that credit depends on the client’s “contracting culture.” Reading that culture correctly is the larger part of the work.
Track all changes, including the ones the firm chooses not to bill, and tie each to a contract provision. A change absorbed and recorded is goodwill the firm can point to. A change absorbed silently is margin lost. When the request is made, lead with a question about how the client wants to proceed, and offer two clear paths forward.
Quality · the system
Quality failures rarely begin with bad engineering. They begin when the review system disappears under schedule pressure. Technical experts produce the work. The project manager’s job is to ensure the review actually happens. It runs in three steps, and the risk appears in the gaps between them.
Before work begins: what needs review, who reviews it (independent of the author), when in the schedule, and what stamps/agency/safety requirements apply.
The firm already has checklists and sign-offs. They fail when skipped under deadline. The project manager confirms reviewers and protects the review time.
Confirm every comment is fully resolved before issue. An open comment that ships is the one that comes back at permit.
?Pause & predict.
A package is due. The drawings look good, but review time is tight, so the coordination check is shortened and final comments are not all closed. It ships. At permit, mechanical conflicts with structural. Which oversight step failed?
The close
The two failures sit side by side. Unmanaged change: the boundary moved and no one said so. Skipped review: a check was due and no one enforced it. Both happen quietly, both under deadline pressure, both when someone chooses comfort over the hard, visible step. And both take the same act of leadership to fix: protect the project’s integrity by refusing to let the important thing happen in silence. The 5-Step Change Model and the 3-step review system are the same instinct, pointed at two different leaks.
This week, on one live project: (1) make sure a Change Log exists and log the next boundary move the moment it appears, with a change order before the work, and (2) confirm the next deliverable’s review is scheduled and owned, with someone closing the comments before issue. One logged change and one protected review are the assignment for the week.
?Challenge · from memory.
From memory: name the five steps of the change model, and the three steps of the oversight system.
The one idea
Unmanaged change is fee the firm gave away for free. Formalizing change and protecting quality are the same discipline.