IT Service Management Fundamentals
What ITSM is really about
IT Service Management (ITSM) is the set of capabilities, processes, and disciplines an organization uses to deliver services - outcomes customers want, without the customer owning the costs and risks of producing them. Anchor your study on a small vocabulary: a service delivers value by facilitating outcomes; a process is a structured set of activities transforming inputs to outputs; a function is a team with specialized skills; a role is a set of responsibilities assigned to a person or team. Questions frequently blur these - a service desk is a function, incident management is a process, and "incident manager" is a role that can sit in either.
The lifecycle view
Know the broad lifecycle logic: strategy (why and for whom), design (how the service and its controls are built), transition (moving safely into live operation), operation (running it day to day), and continual improvement (making it better). Understand that these are overlapping concerns, not rigid sequential phases - improvement happens during operation, and design feeds back into strategy.
Traps to watch
- Confusing outputs (a delivered change) with outcomes (a business result enabled).
- Treating ITIL-style guidance as a mandatory standard; frameworks are adaptable good practice.
- Assuming processes must map one-to-one to teams.
- Forgetting that the customer, not IT, defines value.
Rule of thumb
Ask "who receives this, and what can they now do that they could not before?" If the answer is a business capability, you are describing a service outcome. If the answer is an internal deliverable, you are describing an output. Use that test on every definitional question.