← Back to the blog

Blog

Project Contracts: When Incentives Slow Delivery

Project contracts are supposed to speed up performance. A new research paper dated 28 September 2026 arrives at the opposite conclusion in a formal model: if the client cannot observe the contractor’s actual effort, even an optimally designed contract can slow progress, lower the probability of success and narrow the project scope. Permitting costly resets adds further distortions.

The model is no ready-made formula for IT contracts. It does, however, expose a governance error I keep seeing in projects: the contract rewards what is easy to measure, while the behaviour that determines project success stays hidden.

The contract also governs bad news

Three mechanisms in particular deserve attention in the steering committee:

  • Milestones: Paying for formal completion can reward a green status instead of the early disclosure of an integration risk.
  • Control: Empirical research on project alliances suggests that behavioural controls can support cooperation and trust when both parties take part in governance and design.
  • Relationship: Research on IT service contracts also finds that repeated collaboration is linked to hybrid contractual forms. Formal rules and lived cooperation do not replace each other; they complement each other.

In a software project this becomes tangible during test and UAT triage. When a supplier is paid solely for acceptance on schedule, the incentive is there to reclassify defects late or pass them off as change requests. A reliable forecast, transparent defect-age categories and a shared decision log show whether schedule, quality and remuneration still point in the same direction.

A reset is a governance decision

Re-planning or a reset must not simply carry the old incentive mechanism forward. Before approving a re-baseline, clients should ask: Which assumption failed? Who bears the cost of learning? Which metric rewards transparency rather than cosmetic reporting? Which exit rule prevents endless resets?

I judge a contract less by how precisely it describes normal operations than by the behaviour it rewards under pressure.

What project leaders should do now

Build a simple incentive check into the next supplier review: What information can the contractor withhold without suffering a contractual disadvantage? Tie milestones to verifiable quality and transparency criteria as well as deliverables. What matters is whether the contract enables honest project governance, not just whether it demands performance.

← Back to the blog