When the decision isn’t just technical

We’ve all had to find the right technology or framework to solve a problem. For a long time I thought the technical criteria mattered most, things like stability, documentation, the community and maturity. I’m beginning to realize that every decision has social consequences alongside the technical ones, and you ignore them at your peril. Unless, of course, you fancy being thrown out a window.

It gets complicated when technical and social considerations pull in opposite directions, as they often do. Suppose, for example, you have a team that’s spent five years building Java web applications. Tell them their next one will be in Ruby and Ruby on Rails and half the team could easily get angry and leave, even if the switch looks like the best technical choice.

Whatever technology you’re choosing, consider the softer criteria alongside the technical ones. In the words of a classic, “we have to meet luck halfway.” People generally enjoy learning things, but they need to see a deeper purpose. What they most enjoy learning is something that raises their value on the job market. That doesn’t mean you should start writing COBOL because relatively few people know it. In this context, it’s about what’s in demand. Nobody will want to learn the wonderful framework you knocked together yourself. When they get bored working for your company in two years, the experience won’t improve their résumé.

Simple ideas catch on far more easily than complex ones, even when the latter could be useful. If you’re trying to introduce something complicated, have a wow effect ready. It’s a cheap trick, but it works. Always remember that people like to complain about things they don’t fully understand, and it frustrates them. You can’t prevent that. Don’t take it personally, and above all be prepared for it, for example by offering training.