When roles blur: navigating ambiguity and gaps
Units 1 through 3 gave you the framework: outputs, chains, and profiles. In practice, delivery rarely follows the framework cleanly. Roles overlap. Gaps appear. Two people believe they are each waiting on the other. Nobody does something because everyone assumes someone else is.
This unit is about how to navigate that — without stopping the chain, and without creating new problems in the process.
“Ambiguity in a delivery chain is not a design flaw — it’s inevitable. The question is whether you treat it as someone else’s problem or something you help resolve.”
Four ways roles blur — and what to do
These are the most common points of friction in compact delivery. Select each one to read what happens and what the right response looks like.
The Project Management Team assumed Legal would flag the tax exemption procedure in the contract. Legal assumed the Project Management Team had already confirmed it with Finance. Finance wasn’t consulted. Three months into implementation, a payment is blocked because the procedure was wrong.
When you spot a task with no clear owner — especially at a handoff — say so explicitly and early. “Who owns this?” is not a weakness. It is the question that prevents the gap. Raise it before the deadline, not after.
The Project Management Team and Procurement both send separate, sometimes contradictory, comments on a draft contract back to the counterpart at different times. The recipient is confused about what to fix and who to respond to. Two review rounds become four.
Before reviewing, confirm who is reviewing what and in what sequence. Reviews by multiple divisions should be coordinated: consolidated comments, agreed sequence, single point of contact. This saves time — it is coordination, not bureaucracy.
A Project Manager begins informally managing contractor correspondence on variations — because Procurement is slow. The Procurement Agent stops receiving instructions through the correct channel. When a formal claim arises, the contract administration trail is broken.
Filling a gap informally may feel helpful. But when it bypasses a formal process — especially for contract instruments — it creates compliance risk. Escalate the capacity issue rather than absorbing the function. “Procurement needs to act on this and here’s why it’s urgent” is the correct path.
A contractor requests a change to a design specification. The Project Manager thinks it can be approved at team level. Senior management thinks it needs a formal variation order through Procurement. Nobody formally approves or rejects. The contractor makes the change anyway — without written authorization.
When authority level is unclear, the default is to escalate — not to let time pass. Asking “Is this within my authority or does it need to go higher?” takes minutes. An undocumented contractor change that later becomes a dispute can take months to resolve.
How to navigate ambiguity without stopping the chain
Three principles that apply across all four patterns:
When the answer already exists
Before concluding that a situation is genuinely ambiguous, check the PPMM. Many situations that feel ambiguous are actually situations where the answer exists but hasn’t been looked up.
The Practical Project Management Methodology documents the MCA’s procedures, authority levels, and process flows for all major functions. It is your operational reference — the first place to check when you are unsure whether something is your responsibility or what the correct process is.
If the PPMM answers the question — use it. If it doesn’t — escalate. The chain of reasoning is: PPMM first, then ask upward, then resolve in coordination. Never just assume.
Module 6 of this course covers the PPMM in full: what it contains, how it is structured, and how to use it to navigate your specific role’s procedures and checklists.
Ambiguity is normal. How you respond is what matters.
It is worth being direct about something: the ambiguity, gaps, and overlaps described in this unit are not exceptional situations. They are a routine feature of complex, multi-division programs operating under time pressure. You will encounter all four patterns in the course of this compact.
What distinguishes a high-performing MCA from a struggling one is not the absence of these tensions. It is the speed and consistency with which staff recognize them, name them, and move to resolve them.
- ✓When you see a gap: name it early, assign it, don’t let it sit
- ✓When you spot an overlap: coordinate before duplicating effort
- ✓When scope is creeping informally: flag the underlying capacity issue rather than absorbing the function
- ✓When authority is unclear: check the PPMM, then escalate — never assume
What you’ve covered in this unit
- ✓The four most common patterns of role ambiguity: ownership gaps, uncoordinated overlaps, informal scope creep, and unclear authority
- ✓Each pattern has a clear right response — name the gap, coordinate reviews, escalate capacity issues, check authority before acting
- ✓Three navigating principles: name the gap, own outputs not territory, and escalate early rather than late
- ✓The Practical Project Management Methodology (PPMM) is the first reference when a process or authority question is unclear — check it before assuming
A five-question knowledge check on the module, followed by a short role self-assessment — three prompts to apply what you’ve covered directly to your own position.