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: refuse 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 actually sink projects are small and silent: a “quick” extra option, one more review cycle, a new stakeholder, a coordination check trimmed because the deadline is tight. Each feels reasonable in the moment. None gets named as what it is. And by the time the cost is visible — in eroded margin or a coordination error caught at permit — the cheap moment to act is long gone.
Unmanaged change is just fee you gave away for free. A skipped review is just risk you shipped for free. Same leak, two taps.
Strong PMs don’t try to prevent change, and they don’t 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 doesn’t decide whether it’s a change. One question does:
Has the boundary of the project moved?
If the boundary moved, it must be acknowledged and managed — whether it’s a formal scope addition or a polite “could you also…” in a meeting. The usual suspects:
?Pause & predict.
In a review, the client says “this looks good — could you show one more option?”, then adds “let’s pull in our operations team,” then “let’s add a working session next week.” None sounds unreasonable. Is this a change?
Change · the cost
Unmanaged change follows a predictable sequence. Catch it at step one and it’s a conversation. Let it run and it’s a write-off.
The client assumes the extra work is included — because the team just did it, without discussion.
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.
The fix isn’t to fight change — change is normal. 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. Set these five steps up front and a mid-project change becomes a routine, fundable decision instead of an awkward, money-losing surprise.
Name the reality of change early: “What’s 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 gate, it’s 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’s priced.
Document the process and the decision, and share it internally and with the client — so the change, and the credit for it, is visible to everyone.
Steps 1–4 are set at kickoff and in the agreement; step 5 runs every time the boundary moves. When a change appears, the move is simple because the rails already exist: log it, check it against a gate, 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 PM 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 you pursue that credit depends on the client’s “contracting culture” — and reading it correctly is half the battle.
Track all changes — even ones you choose not to bill — and tie each to a contract provision. A change you absorbed but recorded is goodwill you can point to; a change you absorbed silently is just margin you lost. When you ask, lead with a question to understand 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 PM’s job is to ensure the review actually happens. It runs in three steps — and the risk lives 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 PM 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 aren’t all closed. It ships. At permit, mechanical conflicts with structural. Which oversight step failed?
The close
Look at the two failures 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 because someone chose comfort over the hard, visible step. And both are 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 beat a page of good intentions.
?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 just fee you gave away for free — formalizing change and protecting quality are the same discipline.