Service level agreement

From The Jolly Contrarian
Revision as of 17:19, 18 January 2021 by Amwelladmin (talk | contribs)
Jump to navigation Jump to search
Negotiation Anatomy™

A fifteen-year-old with a mop and a bucket, yesterday.
Tell me more
Sign up for our newsletter — or just get in touch: for ½ a weekly 🍺 you get to consult JC. Ask about it here.

A service level agreement (“fondly”[1] known as an SLA — that is an ess-ell-aye, not a “slah”) defines the level of “service” you expect from a vendor, laying out the metrics by which the service is measured, and your remedies and penalties should agreed-on service levels not be achieved.

Conventional wisdom: It is a critical component of any vendor contract.

Thus, in a stroke, the SLA demonstrates the folly of outsourcing: an employee may be expensive, truculent, workshy and in need of holidays and a pension, but (at least in theory) to get a decent job out of her you don’t need an SLA:[2] the better the job she does, the better she’ll get paid. [3]

But once you have outsourced the role to a free agent patrolling the free market, that calculus, however delusional it may in the first place have been, changes.

Now, unless you are a fool, your starting assumption must be that a paid agent will do as little as he humanly can to comply with the most pedantically literal possible reading of your agreement. To do a stroke more is economically irrational (so sayeth the Smiths, Friedmen and Hayeks of economic history). Your service provider has agreed a fixed fee for its services, it is his sole and constant interest to expend as few resources as are humanly possible to earn that fee.

This is no more than an articulation of the agency problem. Yes, it is true: an employee is also an agent, but an outsourced contractor is an agent thrice removed from the best interests of the company seeking the service.

The difference between the fee and those resources is his profit margin. A free agent is exclusively focused on what it does not have to do. This, and only this, is what he turns up for.

Thus, you must have an SLA. You must stipulate in horrific detail exactly how, when, with what implements and at what rate, your service provider must provide the services. You should expect it to do not one micron more than that.

If you outsource a cleaning contract for a five-thousand seat tower block in the CBD, assume your service provider will roll up with one minimum-waged fifteen-year-old, a mop and a plastic bucket UNLESS YOU HAVE AGREED OTHERWISE IN AN SLA.

But yet there is more, for whomsoever your vendor does send along — whom you should assume will be the cheapest-to-deliver unit for whatever level of service you have contracted for — will enjoy precisely the same fundamentally disinterested relationship with her contracting counterparty — your vendor — as it does with you. So you have a human who couldn’t give more than a salutary wave about the performance standard she owes her principal, who is maximally incentivised to do as little as it humanly can to limp over the threshold of your minimum performance standard.

See also

References

  1. Few people who have ever been party to one look upon an SLA with any kind of fondness
  2. This won’t stop middle management trying to impose one, of course.
  3. IN THEORY. OK, folks: I know it doesn’t really work like this (GOD KNOWS I know that) — since either side egregiously welches on that bargain — but the collective is often gripped with a madness a crowdish delusion that it is somehow different.