The Lords of Vendorbation

L. Jeffrey Zeldman
@zeldman
Published in
3 min readSep 7, 2013

Vendorbation
ven·dor·ba·tion
/ˈvendər-ˈbā-shən/

noun : Unusable web-based intranet software foisted on large populations of users who have no say in the matter. For instance the “dynamic” website for your kid’s school, on which you can never find anything remotely useful — like her classroom or the names and email addresses of her teachers. Merely setting up an account can be a Borgesian ordeal minus the aesthetics.

Tried updating a driver’s license, registering a name change after a marriage, or accomplishing pretty much any task on a local, state, or federal website? Congratulations! You’ve been vendorbated. In ad sales? In publishing? Travel agent? Work in retail? Y’all get vendorbated a hundred times a day.

Terrible food kills a restaurant. Terrible music ends a band’s career. But unspeakably terrible software begets imperial monopolies.

Wholesale contractual vendor lock-in between vendors of artless (but artfully initially priced) web software and the technologically unknowing who are their prey (for instance, your local school board) creates a mafia of mediocrity. Good designers and developers cannot penetrate this de-meritocracy. While they sweat to squeeze through needle’s eye after needle’s eye of baffling paperwork and absurd requirements, the vendorbators, who excel at precisely that paperwork and those requirements, breeze on in and lock ‘er down.

Vendorbation takes no heed of user’s mental model; indeed, the very concept of a user’s mental model (or user’s needs) never enters the minds of those who create vendorbatory software. I say “create” rather than “design,” because design has less than nothing to do with how this genre of software gets slapped together (“developed”) and bloated over time (“updated”).

Vendorbatory product “design” decisions stem purely from contingencies and conveniences in the code framework, which itself is almost always an undocumented archipelago of spaghetti, spit, and duct tape started by one team and continued by others, with no guiding principle other than to “get it done” by an arbitrary deadline, such as the start of a new school year or the business cycle’s next quarter.

Masturbation, or so I have read, can be fun. Not so, vendorbation. It is a nightmare for everyone — from the beleaguered underpaid lumpen developers who toil in high-pressure silos; to the hapless bureaucrats who deserve partners but get predators instead; from the end users (parents, in our example) who can never do what they came to do or find what they want, and who most often feel stupid and blame themselves; to the constituents those users wish to serve — in our example, the children. Will no one think of the children?

Cha-ching! Like a zombie-driven unmerry-go-round spinning faster and faster as the children strapped to its hideous horses scream, the vendorbation cycle rolls on season after season, dollar after dollar, error after error after error.

Think it’s bad now? Wait till the lords of vendorbation start making their monstrosities “mobile.”

Originally published at www.zeldman.com on September 7, 2013.

Designing and blogging since 1995, Jeffrey Zeldman is the publisher of A List Apart Magazine and A Book Apart, co-founder of An Event Apart design conference, and founder and creative director of studio.zeldman. Follow him @zeldman.

--

--

L. Jeffrey Zeldman
@zeldman

A List Apart, A Book Apart, An Event Apart. Designing With Web Standards. Happy Cog. The Big Web Show. Jeffrey Zeldman Presents the Daily Report. Ava’s Dad.