Service Strategy — The Master Plan (Without the Corporate Buzzwords)

"Strategy is not just what you do — it's why anyone should care." — Your future annoyed-but-in-love-with-ITIL self

---

Hook: Why does Service Strategy matter (again)?

Imagine your organization is a bakery. You've got amazing croissants, a trendy storefront, and music that says "we care about artisanal butter." But customers keep buying doughnuts across the street. Looks like you have a product problem... or a strategy problem.

You've already covered ITIL basics, common terminology, and why aligning IT with the business matters. Now we zoom in: Service Strategy is the cookbook that tells the bakery which pastries to make, who to sell them to, how to price them, and whether opening a midnight croissant bar is a brilliant idea or a bankruptcy waiting to happen.

This lesson explains what Service Strategy in ITIL is, what it does, and how it links to the previous topics (terminology, alignment, benefits) without rehashing them like a broken record player.

---

What is Service Strategy? (Short version)

Service Strategy is the ITIL lifecycle stage that defines the market, value, customers, and capabilities required to create and maintain services that deliver organizational value. It’s the brain behind the muscle: decisions about which services to offer, to whom, how to fund them, and how to differentiate in the market.

It moves ITIL from “we can do this” to “we should do this” — and then to “here’s how we win.”

---

Core objectives of Service Strategy

• Understand customer needs and the market — who has demand, what patterns do they show? (Yes, demand management is a thing.)
• Define the service portfolio — what to offer, invest in, retire.
• Manage financials — chargeback, budgeting, and costing so services aren’t free-for-all.
• Manage demand and capacity strategically — align resources to business patterns.
• Define provider type and competitive positioning — internal, shared, or external.

---

Key concepts (with the annoying-but-essential precision)

Service Portfolio vs Service Catalog

Thing	Purpose	Audience
Service Portfolio	The full set of services — proposed, live, retired. Strategic view.	Executives, portfolio managers
Service Catalog	A subset of the portfolio: services available to users/customers. Tactical view.	Operational teams, end users

Think: Portfolio = the full bakery menu (including experimental items). Catalog = the board you hang in the shop today.

Value, Utility, and Warranty

• Utility = does the service do something useful? (Does the croissant taste like a croissant?)
• Warranty = can it be delivered consistently? (Is it always fresh when customers show up?)
• Value = Utility + Warranty — this is what the business pays for.

Patterns of Business Activity (PBA)

Identifying when and how customers use services. Example: payroll spikes at month-end; e-learning usage peaks during onboarding seasons.

Types of Service Providers

• Internal — IT serves its own business unit.
• Shared — IT provides services across multiple business units (think: corporate data center shared among departments).
• External — Outsourced/cloud providers selling to external customers.

Each has different strategy needs: internal providers focus on value to the business, external providers focus on market competition and ROI.

---

How Service Strategy connects to earlier learning

• From common ITIL terminology you already know words like "service" and "customer" — now we apply them to market and financial choices.
• From business alignment, you've seen why IT must speak business — Service Strategy is the concrete plan that makes that alignment tangible.
• From benefits of ITIL, remember efficiency and risk reduction? Strategy decides which benefits are prioritized, funded, and timeboxed.

Ask yourself: if ITIL is the language, Service Strategy is the conversation starter that gets the CEO to actually join.

---

Real-world analogies and examples

• Netflix (external provider): Strategy = invest in proprietary content vs. licensing. They analyzed markets, demand patterns, and decided original content = differentiation.
• Internal IT (internal provider): Strategy = improve employee productivity by offering standard desktop images, not bespoke setups. It's a decision to standardize (reduce cost) over extreme customization (increase cost).
• Shared service (shared provider): Centralized HR systems across divisions — strategy decides SLAs across competing business priorities.

Micro-example: Your IT department has too many special-case applications. Strategy choices:

1. Standardize and retire custom apps (save cost).
2. Keep custom apps and invest support (higher cost, closer to certain business needs).
3. Outsource maintenance to specialists (trade cost for capability).

Pick based on value, budget, and strategic fit.

---

Quick strategy toolkit — questions to ask

1. Who is the customer and what outcome do they actually want?
2. What services in our portfolio create the most measurable value?
3. What patterns of demand will impact our capacity and costs?
4. How will we fund, measure, and charge for services?
5. What type of provider are we and what does market competition look like?

Code block (pseudocode for deciding service fate):

if (value_contribution < threshold && cost_to_support > threshold2):
    retire_service()
elif (strategic_importance and limited_internal_capability):
    outsource_or_invest()
else:
    optimize_and_measure()

---

Strategy vs Tactics (Because people mix these up at parties)

• Strategy = decide to be the bakery that sells late-night croissants to students.
• Tactics = how you price the croissants, which ingredients you source, the social media posts you run at 11pm.

Table: Strategy vs Tactics

Level	Question	Example
Strategy	What market and value?	Offer 24/7 late-night snacks to students
Tactics	How to implement?	Hire night bakers, create 11pm promo, low-cost packaging

---

Closing: TL;DR + Power Move

• Service Strategy is the deliberate planning layer that determines what services to offer, who to target, how to fund them, and why they should exist.
• It sits above design, transition, operation and continuous improvement — guiding them with market, financial, and demand insight.

Power move for your next study session: pick a real service (your company network, a SaaS tool you use, the campus Wi-Fi) and sketch a one-page strategy: customers, value proposition, funding model, PBAs, and go/no-go decision. You’ll go from "nice-to-know" to "able-to-argue-smartly-at-the-next meeting."

Final thought: Strategy without action is a daydream. Action without strategy is chaos. The sweet spot? Strategy that creates clear, fundable, measurable steps your teams actually agree to follow.

---

Versioned for the curious and caffeinated: keep reading, keep questioning, and please — never design a service purely because someone in a meeting said " wouldn't it be cool if...".