Itil Quick Guide
Now go deliver value, not tickets.
| Term | Meaning | |------|---------| | | "Does it do what it's supposed to?" (Fit for purpose) | | Warranty | "Is it available, secure, reliable?" (Fit for use) | | Service Request | A pre-defined, low-risk user need (e.g., "access to app") | | Workaround | Temporary fix to reduce impact (not root cause) | | Known Error | A problem with a documented root cause & workaround | | SLA | Service Level Agreement (e.g., 99.9% uptime, 4h response) | itil quick guide
In the modern digital landscape, IT is no longer just a support function—it is the core engine of business growth. However, if your IT team is constantly reacting to crises, drowning in tickets, or struggling to align with business goals, you need a framework. Now go deliver value, not tickets
is the world’s most widely adopted framework for IT Service Management (ITSM) . It provides a set of best practices for aligning IT services with the needs of the business. is the world’s most widely adopted framework for
| Type | Risk | Approval | |------|------|----------| | | Low, pre-authorized | Routine (e.g., password reset) | | Normal | Med-High | CAB (Change Advisory Board) | | Emergency | Urgent, high | Emergency CAB (ECAB) |
In ITIL v3, there were roughly 26 processes. ITIL 4 expanded this to , broadening the scope from processes to practices (which include resources, people, and tools). These are categorized into three streams.
| | What it does | Real-world example | | :--- | :--- | :--- | | 1. Plan | Align resources with business vision | Budget for a new CRM rollout | | 2. Improve | Continuously fix problems | Monthly post-mortem on outage | | 3. Engage | Understand customer needs | Taking a feature request call | | 4. Design & Transition | Build/test new solutions | Deploying code to staging server | | 5. Obtain/Build | Acquire or create components | Buying cloud storage or writing code | | 6. Deliver & Support | Run the service & fix issues | The help desk resolving a password lockout |