--- name: itil-service-strategy description: Develop and execute IT service strategy aligned with ITIL 4 framework including service value system, service portfolio management, value stream design, and continuous improvement. Use when defining IT service catalog, designing service value streams, managing service portfolio, aligning IT services with business outcomes, implementing ITIL 4 practices, or establishing service-level strategies. Triggers on phrases like "ITIL service strategy", "service value system", "SVS", "service portfolio", "service catalog", "value stream", "ITIL 4", "service design", "service level strategy", "utility and warranty", "outcome-based IT", "service value chain", "continual improvement". --- # ITIL Service Strategy Design and govern IT services using ITIL 4 framework principles to maximize business value through well-defined service portfolios, value streams, and strategic service management. ## Workflow 1. Define IT service vision: align IT services with organizational strategy; identify key business outcomes IT must enable; establish service management principles and guiding values. 2. Design service value system (SVS): map how value is co-created through service value chain, practices, governing framework, and continual improvement. 3. Build service portfolio: categorize all IT services (service strategy, service transition, service operation, retirement); maintain portfolio documentation and governance. 4. Develop service catalog: publish internal (detailed) and external (customer-facing) catalogs; define service levels, pricing, ordering process, and support contacts. 5. Design service value streams: map end-to-end value delivery for each major service; identify activities, roles, handoffs, and automation opportunities. 6. Define utility and warranty for each service: utility (fitness for purpose — functionality, performance, security); warranty (fitness for use — availability, capacity, continuity, security). 7. Establish service level strategies: SLA definitions by service criticality; reporting and review cadence; escalation procedures; penalty and credit mechanisms. 8. Implement service financial management: cost modeling per service; showback/chargeback; budgeting and forecasting; value demonstration to business. 9. Design continual improvement: improvement registry; Kaizen events; quarterly service reviews; maturity assessment; improvement ROI tracking. 10. Govern and report: service strategy review board; quarterly business reviews (QBRs); service performance dashboards; annual strategy refresh. ## Service Value System (SVS) ``` ITIL 4 SERVICE VALUE SYSTEM ============================== COMPONENTS OF THE SVS: 1. Opportunity / Demand: → Market needs, business requirements, regulatory changes → Customer feedback and pain points → Technology innovations creating new possibilities → Competitive pressures requiring service evolution 2. Service Value Chain (SVC): → Core operating model that transforms demand into value → Six interconnected activities: Plan → Improve → Engage → Design & Transition → Obtain / Build → Deliver & Support → Value streams are configurations of SVC activities for specific services 3. Practices: → 34 ITIL 4 practices (replaced "processes" from ITIL v3) → General management practices (continual improvement, information security, portfolio management) → Service management practices (incident management, service design, change enablement) → Technical management practices (deployment management, infrastructure management) 4. Governing: → Policies, standards, compliance requirements → Risk management framework → Legal and regulatory obligations → Corporate governance structure 5. Continual Improvement: → Improvement embedded at every level of the SVS → Continual improvement model (What is the vision? → Where are we now? → Where do we want to be? → How do we get there? → Take action → Did we get there? → How do we keep the momentum?) → Improvement registry tracking all improvement initiatives VALUE CO-CREATION PRINCIPLES: → It's about the outcome (not just the output): Business cares about outcomes (revenue growth, customer satisfaction), not outputs (number of tickets resolved) Service design starts with desired outcomes → Start where you are (don't reinvent): Assess current services, practices, and capabilities before designing new ones Build on existing strengths; fix gaps incrementally → Progress iteratively with feedback: Small, incremental improvements with regular feedback loops Avoid big-bang transformations → Engage and collaborate: Involve service consumers in design and improvement Co-create services with business stakeholders → Think and work holistically: Consider the full service ecosystem (people, processes, technology, partners) No siloed thinking — services depend on each other SERVICE VALUE CHAIN ACTIVITIES: Plan: → Strategic direction and priorities for all value activities → Transparent view of service portfolio and value system → Alignment of improvement initiatives with organizational strategy → Output: Strategic plan, improvement backlog, service portfolio decisions Improve: → Continual improvement of products, services, and practices → Improvement registry maintenance → Measurement and analysis of current performance → Output: Improvement initiatives, maturity assessments, KPI trends Engage: → Understanding of stakeholder needs through transparent interaction → Feedback collection and analysis → Relationship management with service consumers → Output: Requirements, feedback, stakeholder satisfaction data Design & Transition: → Stakeholder feedback and market trends reflected in components → Meeting expectations for utility, warranty, and cost → Design, development, and transition of new/changed services → Output: Service designs, transition plans, test results, training materials Obtain / Build: → Service components available when and where needed → Meeting specifications for quality, cost, and timelines → Sourcing from suppliers or building in-house → Output: Acquired/built components, supplier contracts, build documentation Deliver & Support: → Services delivered in accordance with specifications → User support and service continuity maintained → Day-to-day operations, incident management, service requests → Output: Service deliveries, incident resolutions, support interactions ``` ## Service Portfolio and Catalog ``` SERVICE PORTFOLIO MANAGEMENT =============================== SERVICE PORTFOLIO CATEGORIES: Service Strategy (Planned / In Pipeline): → Services approved for development but not yet live → Business case documented; funding allocated → Expected launch date and dependencies tracked → Examples: New CRM integration service, AI-powered analytics platform, cloud migration service Service Transition (Being Developed / Tested): → Services in design, build, or testing phase → Transition plan documented; go-live criteria defined → Stakeholders informed of progress → Examples: New HR portal (in UAT), upgraded backup service (being tested) Service Operation (Live / In Production): → Services currently delivered to consumers → SLA monitored; performance tracked → Regular review and improvement applied → Examples: Email service, VPN service, cloud hosting, helpdesk support, application support Service Retirement (Retired / Being Phased Out): → Services no longer delivered → Retirement reason documented (replaced, no longer needed, cost-ineffective) → Data migration or archival completed → Stakeholders notified; alternative services identified → Examples: Legacy file server (migrated to cloud storage), on-prem ERP (migrated to SaaS) SERVICE CATALOG STRUCTURE: External Service Catalog (Customer-Facing): → Simplified view for service consumers → Service name, description, business value → How to order/request the service → Service level commitments (high-level) → Support contact and hours → Pricing (if chargeback model) → Access: Self-service portal, intranet, email Internal Service Catalog (IT-Facing): → Detailed technical view for IT teams → All external catalog information PLUS: Technical specifications and architecture Dependencies on other services and components Capacity and performance metrics Cost breakdown (infrastructure, licensing, labor) Support team and on-call schedule Runbooks and escalation procedures SLA targets and reporting requirements Known errors and workarounds Change history and version information SERVICE CATALOG ENTRY TEMPLATE: Service Name: [Enterprise Email Service] Service ID: SVC-EMAIL-001 Category: Collaboration & Communication Description: Enterprise email service providing secure email, calendar, contacts, and file sharing for all employees. Powered by Microsoft 365 Exchange Online. Business Value: Enables employee communication, scheduling, and collaboration; critical for day-to-day business operations. Service Owner: [Name, Title, Contact] Support Team: Collaboration Services Team Support Hours: 24/7 (P1/P2); Business hours (P3/P4) SLA Tier: Critical (Tier 1) Availability Target: 99.9% (52.6 minutes unplanned downtime allowed per month) Response Times: P1: 15 min; P2: 30 min; P3: 2 hours; P4: 24 hours Ordering: Self-service via IT portal (new user provisioning) Pricing: Included in standard IT allocation (showback: $X/user/month) Dependencies: Azure AD (identity), Microsoft 365 (platform), Internet connectivity Known Issues: [Link to known error database] Last Updated: [Date] ``` ## Service Financial Management ``` IT SERVICE FINANCIAL MANAGEMENT ================================== COST MODELLING PER SERVICE: Cost Components: → Infrastructure: Servers, storage, network, cloud resources → Software: Licenses, subscriptions, SaaS fees → Labor: FTE cost of support team (salaries, benefits, overhead) → Facilities: Data center space, power, cooling (if on-prem) → Support: Third-party support contracts, vendor support → Security: Security tools, compliance costs, audit costs → Depreciation: Hardware depreciation over useful life (3-5 years) → Contingency: 10-15% buffer for unplanned costs Cost Allocation Methods: → Direct allocation: Costs directly attributable to a service (dedicated servers, specific licenses) → Proportional allocation: Shared costs allocated by usage (CPU hours, storage GB, user count) → Fixed allocation: Flat-rate allocation for shared services (helpdesk, security team) → Activity-based costing: Costs allocated based on actual activities consumed (number of incidents, changes, requests) Example Cost Model (Email Service): Component | Monthly Cost | Allocation Method ─────────────────────────────|────────────────|───────────────── Microsoft 365 licenses | $15,000 ($6×2500 users) | Direct (per user) Exchange Online add-on | $3,750 ($1.50×2500) | Direct (per user) Support team (2 FTE) | $16,000 | Fixed (dedicated team) Security tools (proportional)| $2,000 | Proportional (% of total security spend) Contingency (10%) | $3,675 | Fixed percentage ─────────────────────────────|────────────────|───────────────── Total monthly cost | $40,425 | Cost per user per month | $16.17 | SHOWBACK / CHARGEBACK MODELS: Showback (Awareness — No Direct Charge): → Business units receive monthly report of IT costs consumed → No direct financial charge; purpose is awareness and optimization → Report includes: cost breakdown, usage trends, optimization recommendations → Best for: Organizations transitioning to cost awareness; initial phase Chargeback (Direct Allocation): → Business units charged directly for IT services consumed → Charges appear in business unit budgets → Incentivizes cost optimization and efficient usage → Pricing models: Flat rate: Fixed cost per user/per department Usage-based: Cost based on actual consumption (API calls, storage, compute) Tiered pricing: Volume discounts (more usage = lower per-unit cost) Market-based: Price set at market rate (simulates external purchasing) → Best for: Mature IT organizations; cloud environments; organizations with business unit autonomy Budgeting and Forecasting: → Annual IT budget aligned with business strategy → Quarterly budget reviews with business stakeholders → Rolling 12-month forecast updated quarterly → Capital expenditure (CapEx) vs. operational expenditure (OpEx) planning → Cloud cost forecasting: committed spend (RIs, savings plans) + variable spend projections ``` ## Integration Points - **ServiceNow ITSM**: Service portfolio management; service catalog; request fulfillment; SLA management; financial management for IT; continual improvement module; $25K+/year base - **Microsoft Service Management (Azure Arc + Intune)**: Service catalog integration with Microsoft 365; automated service provisioning; service health monitoring; included in E5 - **Jira Service Management**: IT service management; service catalog; SLA tracking; request management; integrates with Atlassian ecosystem; $3-$19/agent/month - **BMC Helix ITSM**: Enterprise ITSM; service portfolio; financial management; AI-driven automation; ITIL-aligned; custom pricing - **Freshservice**: ITSM platform; service catalog; asset management; CMDB; ITIL processes; $19-$59/agent/month - **LeanIX / ServiceNow SDM**: Enterprise architecture and service mapping; service dependencies; business capability mapping; architecture repository - **IT Financial Management Tools (Flexera, Snow Software)**: Software asset management; license optimization; cloud financial management; cost allocation ## Edge Cases - **Startups with no formal service management**: No service catalog, no SLAs, ad-hoc support; solution: start with basic service catalog (top 10 services); define SLAs for critical services only; implement ITSM tool (Freshservice, Jira SM) gradually; grow maturity as organization scales - **Global service delivery across time zones**: 24/7 service coverage required; follow-the-sun model; solution: distributed support teams (Americas, EMEA, APAC); handoff procedures; shared knowledge base; overlapping shift windows for collaboration - **Merged organizations with duplicate services**: Post-merger consolidation needed; different service catalogs, SLAs, tools; solution: service rationalization exercise; standardize on single service catalog; migrate to unified ITSM tool; communicate changes to all stakeholders - **Regulated industry service reporting**: SOC 2, ISO 27001, HIPAA require service-level reporting; solution: automated service reports from ITSM tool; SLA compliance dashboards; audit-ready documentation; quarterly service reviews with evidence - **SaaS-dominated IT landscape**: Most services are SaaS (O365, Salesforce, Slack); limited control over service delivery; solution: manage SaaS portfolio (licensing, usage, contracts); define internal SLAs around SaaS services; monitor SaaS vendor SLAs; escalation procedures with vendors - **Business unit resistance to chargeback**: Business units view IT as a cost center and resist being charged; solution: start with showback; demonstrate value and optimization opportunities; gradual transition to chargeback; align IT costs with business outcomes (not just infrastructure costs)