Here we are in the 21st century and whilst IT technology is moving on, is it possible that the main obstruction to moving forward is that we just dislike change? When I refer to change I mean as part of software / hardware project or implementation. We wrap change up in jargon, methodologies and documentation. We look at all aspects of the change; is it the right thing to do? who else has done it? can we check our thoughts with someone else? does everyone agree? We then document this process and write reports about the documentation. We generally make change quite a difficult and complicated process.
I don’t deny for one second that some changes need a plan to ensure success or chaos would rein. But is it possible that the more popular methodologies are overly complicated? Are they designed this way simply because the more complicated we make things, the better this makes us feel about changing? The core of most methodologies regarding change require documentation, consultation, meetings, follow ups and reviews. All of these generally require time; weeks, months and even years in some cases. Do we need all this extra time? or does it just allow us to adjust to the change? Are we using these methodologies in order to give us time to ‘get our heads around the change’ ? The longer a project takes, the more room there is for failure. The more people involved the more time is spent in meetings and consultation, and the more complicated a methodology the more documentation is required. Are we just making things too complicated for ourselves? If we made ourselves more open to change, and were bolder about change, would we still need complicated methodologies or would things be that bit simpler ?