This morning on the TwitterBlogosphere (sorry - I agree we need a shorter, sweeter word here. It will come, I'm sure, but for now I'm stuck with TwitterBlogosphere!) there were a number of discussions which really caught my attention. They highlighted for me how a particular choice of words can indicate a poor understanding of the context - ITIL/ITSM, or even just an immature thinking process. I offer (for your delight!) some optimum terminology that I would respectfully suggest we all get into the habit of using in ITSM.
First - "Business/IT Alignment". That's not what it's about. It's "Business/IT Integration"! If IT is "aligned" with the business that means it's separate and is trying to line up. IT is not a separate entity from the business, it's PART of the business. So IT better get itself properly integrated into the business, not aligned. IT needs to be aware of business objectives and then make sure that IT services enable and support those business objectives. Stop saying "Business/IT alignment"!
Secondly - Such-and-such is "compliant" to ITIL. No it can't be! I don't care what it is (usually we talk about tools in this context) but you cannot be compliant to some good ideas and recommendations - which is all ITIL is really. But you can be "compatible" to ITIL. (For a more complete explanation of "compliance" vs. "compatible" see the PinkVERIFY page at our main website.) And for those of you like to churn out the "oh, it's just semantics!" argument and simply refuse to believe that these two words are not synonyms of each other, I'll give you my favourite analogy. When you're looking for a life partner are you looking for someone who'll be compliant, or someone compatible? See - there's a BIG difference!