If you’ve worked in the IT industry it’s safe to assume that you’re familiar with ITIL or at least however it’s manage to manifest itself within your organisation. It’s probably one of the longest lasting ideals in IT today having been around for a good 20+ years in its current form, surprising for an industry that considers anything over 3 years archaic. Indeed anyone who’s been involved in implementing, maintaining or attempting to change an ITIL based process will likely call it that anyway and whilst I’m inclined to agree with them I think the problems stem more from the attitudes around these processes rather than the actual processes themselves.
Change management is by far the best example of this. The idea behind it is solid: any major changes to a system have to go through a review process that determines what impacts the change has and demands that certain requirements be met before it can be done. In an ideal world these are the kind of things you would do regardless of whether an external process required you to or not however the nature of IT tends towards many admins starting off in areas where such process aren’t required and thus, when they move onto bigger and better environments, processes like these are required to make sure they don’t unintentionally wreck havoc on larger systems. However change management is routinely seen as a barrier to getting actual work done and in many cases it is.
This is where the attitude problems start to occur. ITIL based processes (no one should be using pure ITIL, that’s crazy talk) should not be a hindrance to getting work done and the second they start becoming so is when they lose their value. Indeed the reason behind implementing an ITIL process like change management is to extract more value out of the process than is currently being derived, not to impede the work is being done. Essentially it should only be an extension of work that would be undertaken in the first place and if it isn’t then you either need to look at your implementation of the change process or why your current IT practices aren’t working with it.
Predominantly I think this comes from being far too strict with these kinds of processes with the prevailing attitudes in industry being that deviation from them will somehow lead to an downward spiral of catastrophes from which there is no escape. If these ITIL process are being routinely circumvented or if the amount of work required to complete the process outweighs the actual work itself then it’s not the people who are to blame, it is the process itself. Realistically instead of trying to mold people to the process, like I’ve seen it done countless times over, the process should be reworked to suit the people. Whilst this is by far more difficult to do than simply sending people on ITIL courses the benefits will far outweigh the costs of doing so and you’ll probably find that more people stick to it rather than attempt to circumvent it.Indeed much of the process revolution that has happened in the past decade has been due to these people rather than process focused ideals.
Whilst ITIL might be getting a little long in the tooth many of the ideals it touches on are fundamental in nature and are things that persist beyond changes in technology. Like many ideas however their application has been less than ideal with the core idea of turning IT in a repeatable, dependable process usurped by laborious processes that add no value. I believe changing the current industry view from focusing on ITIL based processes to people focused ones that utilize ITIL fundamentals would trigger a major shift in the way corporate IT entities do business.
A shift that I believe would be all for the better.
I was never a big fan of writing. I’m a very stereotypical nerd/engineer in that respect as I always struggled to get my thoughts down on paper, especially when I was told I wasn’t elaborating enough. I became frustrated with the arbitrary word counts as everything I needed to say could be summed up in a couple paragraphs and struggled with gathering supporting arguments. It got easier when I started writing documentation professionally, since all you really need there are the facts, but I only really started to enjoy writing about 6 months after I started this blog when I started to force myself to punch out at least 1 post per weekday.
I’ll be honest with you though, I still struggled with the basics for quite a while. Back then inspiration was a lot easier to come across than it was today (thanks to me not having a massive back catalogue of stuff I’ve already written about) but writing anything more than 500 words was a complete chore as the engineer in me yelled continually that anything more was just me waffling on. Over time however I came to realise just how to trigger that part of my brain that knows how to break down a subject into several key points that I can then turn into a paragraph each and now I routinely find myself writing 1000~2000 word posts on things that I’m passionate about.
Of course the small bit of recognition I get amongst my friends and peers for my various musings here go a long way to keeping me coming back to continue writing. It’s why whenever I hear about a friend starting up a blog I’ll link to them, subscribe to their blog and comment on their posts as I know how hard it is when you’re first starting out. I was shouting into the darkness for a good year before I got anything above what I’d classify Internet background noise so I know exactly what it can feel like to do something with seemingly no return. Of course most of the benefits don’t come from page views, but they certainly help to keep you on track to improving your writing (and hopefully other aspects of your life too).
Now I don’t necessarily recommend doing what I do exactly as whilst it’s been immensely helpful for me it’s also had the rather undesirable side effect of giving me a crazy OCD for getting a post out every day. Whilst some of my most complimented bits of writing come from the days when I have to drag inspiration kicking and screaming out of the dark reaches of my brain it would probably be a whole lot better, at least creatively, if I only wrote when the inspiration hit me. Indeed some of the best blogs I read come from those who only write when they really have to. That’s not to say that all my posts are forced out (the majority, thankfully, aren’t) but unless your goal is SEO and page views blogging or writing whenever suits you is probably the best option.
I’d also go out on a limb and say that any sort of online creative expression (whether blogging, vlogging, tweeting or whatever) will help you better yourself in some way. Of course I think some mediums are better for certain things (blogging is best for writing, of course) but giving yourself some sort of creative outlet, even if you think you aren’t that good, will do wonders for you. Sure many people already have these, especially those who make a living off their creativity, but having your own place of expression where only you are in control is definitely something worth having.
I’m not going to say that everyone in the world should blog, more that if you’re looking for a sure fire way to improve your writing and being able focus your thoughts then starting a blog might be the way to go. Plus there’s always the possibility that what you jot down will gain you an audience that will keep coming back for your musings, something that’s extremely gratifying (even the trolls, to a point). Hell if you’re worried about what people might think then just open up notepad every time you want to write something down and save the files off in some random location. Even doing that I think you’d be surprised of the improvements after a while, I know I certainly have.