Skip to main content

The Meaning of IT

What does the IT in ITIL® stand for? This question may seem easy to answer. The IT stands for “information technology”. But what does that really mean? Is there more than one way to answer the question of what the IT in ITIL® means? I believe there are more than one context or meaning for IT and we must be aware of the distinct meanings. Let’s take a look at some of the ideas or concepts behind IT.

·       IT as “information technology”: This most basic use of IT refers to the physical and technological pieces and components made up of electronics and operating/machine software. E.g. A desktop computer is IT as “information technology”.

·      IT as “management information systems (MIS)”: Computerized components that are used to manage, control and govern information used to run a business or organization. E.g. A customer relationship management system is IT as “MIS”.

·        IT as “collection of applications and infrastructure”: This umbrella use of IT encompasses anything technological or computerized regardless of its usage or its nature. E.g. Cloud computing is IT as “collection of applications and infrastructure”.

·       IT as “place”: This use of IT refers to the location where IT management, control and governance occur. E.g. A data center is IT as “place”.

·        IT as “organization”: This logical use of IT represents the “department” of people who create, deliver, manage, control and govern “information technology” and “management information systems”. The IT folks are IT as “organization”.
Many times I have run across individuals and organizations where the use of the term IT or “information technology” has become confused or misused. This leads to misunderstandings, poor decision making and unclear roles and responsibilities. ITIL® encourages us to clarify our terminology and use it in its proper context.
So let us look at an example. One of the most confused uses of IT is that of IT as “organization”. Unfortunately there is no clear boundary or standard as to what makes up an “IT Department”. Some companies include all IT related work: projects, application development, infrastructure management, support and many other areas. Some companies take a more narrow view and only include the back-end operational activities of supporting infrastructure and operating systems. Business application development, support and management are not included.
This lack of consistency in definition and usage leads to issues when trying to apply ITIL® and other best practices. Does ITIL® cover application development, if that is not part of an “IT Department”? Does ITIL deal with strategies that are related to outside of a narrowly defined “IT Department”? Does requirements gathering and design belong “inside” or “outside” an “IT Department”?
ITIL® itself does not necessarily provide clear answers to these questions. ITIL® does provide guidance that will lead an organization to become more consistent and comprehensive with its usage and definition of terms like “information technology”. If your organization has not undertaken to clarify basic terms like “information technology” it may be interesting to see different definitions based on different perspectives.  The benefits and value will reveal themselves in the long run.

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th

The ITIL Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem