Incompatible Mandate
Distinct governance roles merged into one position create structural impossibility.
Distinct governance roles are merged into one position — either by design or by drift. The person holding the merged role faces structural impossibility: the roles require opposing temperaments or create conflicts of interest.
Recognition signals
- One person is both enforcer and relationship owner. They need to hold the vendor accountable AND maintain the trust needed for the next negotiation. These require different temperaments.
- The contract manager is also the PM, or sits in procurement rather than delivery. The contract expertise is separated from the delivery context where it's needed.
- Someone says "that's not my job" about something that IS their mapped responsibility — because the role mapping doesn't match their understanding of the position.
- The same person was deliberately assigned both recommend AND authorise authority. The internal check that recommendation and authorisation should provide is eliminated.
- Enforcing a remediation clause undermines the rapport needed for the next negotiation. The person has to choose which hat to wear, and the choice always costs something.
Structural cause
Why this happens
Organisations conflate roles because it saves headcount. The incompatibility only surfaces under stress — when enforcement and rapport conflict, or when recommendation and authorisation should disagree but can't because they're the same person.
The Incompatible Mandate is invisible in calm waters. When the vendor is performing well and the project is on track, having one person hold enforcement and relationship works fine. The conflict emerges under delivery pressure — when the contract says one thing and the relationship says another.
The structural test is simple: can these two roles disagree with each other? If they're held by the same person, the answer is no. And that's exactly when the governance needs them to disagree.
Risk mapping
| Risk | Description |
|---|---|
| V6 | Role confusion — governance roles don't match position descriptions |
| G1 | Three hats — PM absorbs delivery, technical, and commercial authority |
| G10 | Design gap — governance designed around positions, not authority domains |
Self-assessment
When to worry
- The person enforcing vendor quality is also responsible for maintaining the vendor relationship
- One person holds both recommend and authorise authority for the same decisions
- Contract management sits in procurement, separated from delivery context
- Governance role mapping hasn't been reviewed since the project started
When you're OK
- Enforcement and relationship roles are held by different people
- Recommend and authorise authorities have a structural separation
- Role-to-position mapping has been stress-tested against conflict scenarios
Related reading
- The contract management gap — why contract management and business relationship ownership need structural separation
- Authority Vacuum — the related pattern where roles are missing rather than merged
- Narrative Capture — vendors exploit the conflicted role holder
Structural separation between enforcement, relationship, and recommendation authority needs design, not documentation.
A programme health check stress-tests role-to-position mapping against conflict scenarios. 10fifteen — governance design and assurance.