Skip to main content

Why don't organizations pay more attention to developer experience?

ยท 2 min read
Drew Robson
Consultant

I've done work on projects specifically for DevEx and, in my experience, the single biggest hurdle is simply convincing the powers that be that it's a good way to spend time (and therefore money).

It's odd because in these organisations will boast about how they're big-picture thinkers, and in the end the whole point of building any software is to make something easier to do later at the cost of effort now, yet they're often terrified of spending resources on anything that isn't an end product or that doesn't produce immediate value.

Even if you can get them to agree in principle that ThingX would be worth having, it's rarely seen as expedient to build it now because of the short-term opportunity cost, and the can is kicked ever further down the road.

"We'll allocate some time for ThingX later but right now we can't afford to down tools on ThingY" they say, ad nauseam; six months later, somebody will say "you know, if we'd just done ThingX back then it would have paid for itself by now," and everyone will nod and agree, but somehow that doesn't become "...so perhaps we shouldn't put it off any longer."

The worst part is that when you finally do get the go-ahead to work on making these sorts of improvements, everybody will agree afterwards that it was a great idea and well worth the effort... but not learn from it. "Remember how we built ThingX, and it was great and made everybody's lives a load easier? Well, we've got this idea for something else..." fails to persuade anybody. Previous improvements are taken for granted, and what things were like without them is quickly forgotten, rather than prompting anybody to change their thinking about front-loading effort.

Why don't organizations pay more attention to developer experience?