Stress-test an outsourcing decision before the next quarter proves the vendor cannot clear the work, cannot exit cleanly, or quietly owns a capability you still claim as core.
Outsourcing decisions fail when scope is fuzzy, when quality bars live only in sales decks, when knowledge transfer is assumed, and when exit costs appear after renewal. A clean RFP scorecard is not evidence that the system can absorb a month of real tickets, handoffs, and staffing gaps without quiet rework inside your team.
What to put on the table
One sentence for what moves out, what stays in, the success metric after ninety days, and the rollback trigger. Attach the scope draft, sample work, SLAs, pricing, and the exit plan. If product, ops, and finance disagree on who owns acceptance criteria, stop and reconcile first.
Name the decision you will make if the stress test finds nothing new, and the delay criteria if training samples or exit terms are not ready.
Attack surfaces
- Scope truth: work the vendor still cannot do without your people as unpaid staff.
- Quality and latency: bars that look fine in a pilot and fail under realistic volume.
- Knowledge risk: docs, tooling, and tribal context that never leave your building.
- Lock-in and exit: data, IP, staffing, and the cost of bringing the work back.
- Finance timing: fixed costs that stay when volume drops, and credits that never clear.
Optional security seat if data leaves your boundary. Optional customer seat if service levels change in ways buyers will feel.
How to run it
Feed Pingpong the RFP pack, sample work, and draft contract. Early passes steelman the move. Later passes attack from ops, finance, security, and skeptic seats. End with a pass that turns surviving objections into a narrower scope, a phased exit clause, or a hold. Delete invented "someone will catch it" reviews and dual-counted savings from headcount that still stays.
When the decision moves customer-facing work, force support and customer seats to map every path that still assumes your old response time. Status pages, SLAs, and sales scripts count. An outsourcing plan that looks clean in a deck while the site still promises same-day human review will fail on the first real week.
Force a day-after narrative: what happens if the vendor misses a sprint, if a key person leaves their side, or if your team invents quiet parallel work. If those stories are stronger than your mitigation plan, fix the package before sign. Related: war-game a vendor selection, stress-test a migration plan, war-game a pilot contract, pretend you are the CFO, and the war-game decisions hub. Process: how to run a Pingpong.