“Process” Doesn’t Have To Be A Dirty Word

Once again, at potentially the worst possible time for my team, we are being forced to adopt a new company-wide process. My boss is encouraging everyone to participate early and get involved, that way we can provide feedback that will hopefully push this new process in a direction that will work better for everyone involved, but I could see the exhaustion and loss of morale on my coworkers’ faces as what was supposed to be a quick aside turned into an hour-long discussion. To be entirely fair to my coworkers, the only reason I wasn’t having a bad time is because it didn’t impact me and I’m already a heavy user of the tool being forced to fit everyone else. You see, the tool in question is a software development and bug tracking product with a well-built database and plenty of customizability, one that the software developers and testers have been using for over half a decade, to the degree that we barely think about it anymore (I’m not going to name names or get more specific than this for reasons of plausible deniability and keeping my writing away from my work life). What sucks for me specifically, though, is that there is rumor going around that all of the people who HAVE been using the tool in a way that works really well for us are going to be forced to use it this other way, that everyone else is using it, just so everyone uses the tool the same way.

Continue reading