Are you confused about the difference between an Incident, Service Request, Problem, and Change in IT Service Management (ITSM)?

In this CGTECH tutorial, we break down these four important ITSM concepts using simple explanations and real-world office examples.

Many beginners think every IT ticket is the same — but in ITSM, each ticket has a different purpose and requires a different approach.

In this video, you will learn:

✅ What is an Incident?
✅ What is a Service Request?
✅ What is a Problem?
✅ What is a Change?
✅ Real-life workplace examples
✅ How IT teams decide which process to use
✅ Why understanding these differences is important for IT support professionals

Simple Memory Guide:

🚨 Incident = Something broke and needs quick restoration
📄 Service Request = Someone needs something standard
🔍 Problem = Find the root cause behind repeated issues
⚙️ Change = A planned improvement or update

Understanding these concepts will help you improve your skills in:

IT Service Management
Service Desk Operations
Helpdesk Support
ITIL Practices
IT Career Development

Whether you are a beginner entering IT, a Service Desk Analyst, or preparing for ITIL certification, this lesson will help you build a strong ITSM foundation.

CGTECH — Learn. Grow. Lead.

Subscribe for more beginner-friendly ITSM tutorials, technology lessons, and career growth content.

#ITIL
#IncidentManagement
#ServiceRequestManagement
#ProblemManagement
#ChangeManagement
#ServiceDesk
#Helpdesk
#ITSupport
#ITCareer
#TechForBeginners
#ITILFoundation
#InformationTechnology
#TechEducation
#ITOperations
#ServiceManagement
#ITProfessional

---

Transcript

0:01 [music]

0:02 >> Welcome to CGTech.

0:04 Learn, grow, lead. In this video, we

0:08 will explain four important ITSM terms.

0:11 Incident, service request, problem, and

0:14 change.

0:15 These are common words in service desk

0:18 and IT support, but many beginners mix

0:20 them up.

0:22 By the end of this lesson, you will know

0:23 how to identify each one using simple

0:26 terms and real office examples.

0:28 Let us get started. First, let us talk

0:31 about an incident. An incident is an

0:33 unplanned interruption to an IT service

0:35 or reduction in service quality. In

0:37 layman's terms, something broke or

0:39 suddenly stopped working.

0:41 For example, your company email suddenly

0:43 goes down, employees cannot send or

0:46 receive messages, the office Wi-Fi stops

0:48 working, or a shared printer stops

0:50 printing unexpectedly. These are

0:52 incidents because the normal service has

0:54 been interrupted. The goal of incident

0:56 management is to restore normal service

0:58 as quickly as possible.

1:00 Quick memory aid, incident means

1:02 something broke.

1:05 Next is service request. A service

1:07 request is a request from a user for

1:09 something they need, such as access,

1:11 information, or a standard service. In

1:14 layman's terms, someone needs something

1:16 normal, expected, or routine. For

1:19 example, an employee asks for a password

1:21 reset, a new staff member requests a

1:24 laptop and email account, a user asks to

1:27 install approved software, or an

1:29 employee needs access to a shared folder

1:31 or Microsoft Teams. Nothing is broken

1:33 here. The user simply needs a standard

1:36 service. The goal of service request

1:38 management is to fulfill user needs

1:40 efficiently, consistently, and through a

1:42 standard process. Quick memory aid,

1:45 service request means someone needs

1:47 something.

1:48 Third is problem. A problem is the

1:50 underlying cause of one or more

1:52 incidents. In layman's terms, it is the

1:55 hidden reason the same issue keeps

1:57 happening. For example, employees keep

1:59 losing Wi-Fi every afternoon, and after

2:02 investigation, the IT team finds that a

2:04 network switch is overheating.

2:06 Another example is repeated login

2:08 failures caused by a directory

2:09 synchronization issue, or a printer

2:11 problem that keeps returning because of

2:13 an outdated driver. These are problems

2:16 because the team is looking for the root

2:18 cause, not just fixing the symptom. The

2:20 goal of problem management is to find

2:22 the root cause and prevent incidents

2:24 from happening again.

2:26 Quick memory aid, problem means the

2:28 hidden cause.

2:30 Fourth is change. A change is an

2:32 addition, modification, or removal of

2:35 anything that could affect IT services.

2:38 In layman's terms, it is a planned

2:40 update, fix, or improvement. For

2:43 example, the IT team schedules a

2:45 software update after office hours,

2:47 upgrades a server during the weekend,

2:50 applies a security patch to protect

2:52 systems from vulnerabilities, or moves

2:54 the company to a new email platform.

2:57 These are changes because they are

2:58 planned and controlled. The goal of

3:00 change management is to implement

3:02 improvements safely with minimal risk

3:04 and disruption.

3:05 Quick memory aid, change means a planned

3:08 improvement.

3:10 Let us summarize the difference.

3:12 Incident is reactive, something broke

3:14 and needs quick restoration. Service

3:16 request is routine, someone needs

3:18 something standard.

3:20 Problem is root cause focused, the team

3:22 investigates why the same issue keeps

3:24 happening. Change is planned, the team

3:27 updates, fixes, or improves IT services

3:30 in a controlled way.

3:32 Knowing the difference is important

3:34 because it improves ticket accuracy,

3:36 speeds up resolution, prevents repeated

3:38 issues, reduces risk, and supports

3:41 better IT decisions. Right request,

3:44 right process, better results.

3:48 If this lesson helped you, subscribe to

3:50 see G Tech for more beginner friendly

3:52 ITSM tutorials, career guides, and

3:55 practical tech lessons.