Service Strategy and Value Creation
This domain tests how well you connect services to customer outcomes, demand and funding rather than to features. Expect questions on value propositions, service offerings, market spaces, service portfolio management, demand management and business cases.
Core rules and concepts
- Value is perceived by the customer and includes outcomes, costs and risks. A service offering combines goods, access to resources and service actions.
- The service portfolio has three parts: pipeline (in design), catalogue (live or ready) and retired. The catalogue is customer-facing; the portfolio is the full investment view.
- Demand management uses user profiles and personas to understand patterns and influence demand where possible.
- A business case compares benefits, costs, risks and options over a defined period. It is a decision aid, not a one-off approval document.
- Funding models matter: who pays, how consumption is charged and whether cost recovery encourages wasteful demand.
Worked example
A team proposes an internal analytics service. A weak case starts with the technology. A stronger case states target customer outcomes, such as faster month-end reporting; defines utility and warranty; estimates demand volume and variability; compares build, buy and SaaS options; quantifies costs and risks; identifies funding and chargeback; and states how success will be measured. The reasoning is that strategy is a set of choices about which outcomes to serve and what the provider will and will not warrant.
Traps
Building features before defining outcomes; treating the service catalogue as an asset inventory; ignoring demand variability; presenting a business case once and never revisiting assumptions; pricing below cost without a stated strategic reason.