Vendor Management at Enterprise Scale

At my current scale, not all 50+ engineers report to my organization. Some are vendor teams — contracted engineers with different employers, different incentive structures, and different definitions of "good enough."

Vendor management is a skill most PMs learn the hard way.

The Contract Is Not the Relationship

I have seen PMs treat the vendor contract like a shield: "the SOW says X, so they must deliver X." Technically true. Practically useless. Contracts define the floor, not the ceiling. If you manage to the contract, you get contract-minimum work.

The relationship is what drives quality. When vendor teams understand the business context, when they feel like partners rather than hired hands, the quality of their work changes. I invest time in making sure vendor leads understand why we are building what we are building, not just what they need to deliver.

SLAs That Actually Work

Good SLAs are specific, measurable, and tied to outcomes that matter. "99.9% uptime" is a fine SLA for infrastructure. "Respond to critical bugs within 4 hours" is a fine SLA for support. But "deliver high-quality code" is not an SLA — it is a wish.

I define SLAs around cycle time, defect escape rate, and code review turnaround. These are measurable, and they create accountability without micromanagement.

The Escalation Dance

When a vendor underperforms, escalation is an art. Go too early and you damage the relationship. Go too late and you eat the delivery risk. My rule: the first miss is a conversation with the vendor lead. The second miss is a conversation with their manager. The third miss is a conversation with my director and theirs.

Document everything. Not because you are building a case — because clear documentation prevents the "I did not know about this" defense that derails escalation conversations.

Vendor management is program management with an extra layer of organizational complexity.