We outsource our entire IT and software development department to an external managed service provider. Should outside vendor teams be mapped as seats on our internal Accountability Chart, and who holds single-point accountability for them?

Question

Tyler Smith · Accepted Answer

External vendor names or contractor teams should never appear on your EOS Accountability Chart. The chart exists to govern internal accountability, leadership structure, and decision-making authority. Listing third-party vendors as individual seats confuses reporting lines and weakens internal ownership.

However, the functional capability the vendor provides must exist on your chart. If your business depends on technical infrastructure, cybersecurity, and software development, that functional seat belongs on your Accountability Chart, typically reporting to Operations or directly to the Integrator.

The essential requirement is that an internal employee must occupy that seat and maintain single-point accountability for the business outcome. That internal leader must pass GWC for managing technical deliverables and contractor performance.

The five core roles for this internal seat should include:
- Defining technical requirements and service level agreements (SLAs)
- Managing vendor selection, contracts, and software budgets
- Holding external partners accountable to project milestones and uptime standards
- Auditing code quality, system compliance, and security posture
- Reporting technology Scorecard metrics in the weekly Level 10 Meeting

The outsourced vendor is simply the capacity resource used to deliver the work. If the vendor misses project deadlines or causes system downtime, the internal seat holder is the single person accountable for solving the issue through IDS. Never allow an internal leader to point across the table at an outside vendor to excuse a failed Scorecard metric.