What's changed: Initial version
6.4Operations design and cost, staffing, and budget management
Covers operations design that builds the operating structure and procedures, the design of shifts and staffing that runs a 24-hour operation seamlessly, cost optimization that balances investment and running cost, KPIs that measure operational quality numerically, and supplier / resource / budget management that governs external suppliers, resources, and budget. The key is building a structure that is neither excessive nor deficient within the SLA-versus-cost trade-off.
Operations is an activity that "creates value only by being kept running," and what governs its quality and sustainability is structure design and the control of cost, staffing, and budget. A service manager must meet the level promised in the SLA with staffing and shifts that are neither excessive nor deficient, optimize running cost (the trade-off between safety and savings), measure operational quality with KPIs and improve, and control outsourcing, resources, and budget in a planned way. Adding people makes the SLA easier to meet but swells cost—designing this balance point is the practice.
6.4.1Operations design and shifts/staffing
- Operations design is the activity of designing—before service starts—the structure, procedures, role division, escalation paths, and monitoring/automation policy for running the service stably. If operations design is weak, it is undecided who judges what during a failure and the initial response lags. Working backward from the SLA's required levels (availability, response time, coverage hours), you prepare the necessary monitoring, structure, and procedures.
- Shift/staffing design decides, for a service requiring seamless coverage such as 24/7/365, how many people to place in which time bands. Excess staff swells labor cost, while too few breaks down response at peaks or during failures and invites an SLA breach. It factors in overnight/holiday first response, reinforcement during busy hours, and multi-skilling (removing dependence on individuals) to cope with leave and attrition. "Work only one person can handle" is a single point of failure, resolved by building runbooks and training.
6.4.2Cost optimization and KPIs
- Cost optimization trims running costs (labor, facilities, licenses, outsourcing, cloud usage, and so on) without waste while maintaining the SLA level. It is not mere cost-cutting; the key is to separate the safety/availability investment that must not be cut from the waste that can be. Typical moves include reducing labor via automation of routine work and right-sizing resources to actual usage (canceling excess capacity). Cutting into the safety margin ends up costing more through SLA breaches and increased incidents.
- KPI (Key Performance Indicator) measures operational quality with objective numbers. Setting indicators such as incident count, mean time to recover (MTTR), SLA attainment rate, first-call resolution rate, and change success rate, you continuously measure actuals against targets and feed them into improvement (PDCA). The purpose of a KPI is not "measuring for its own sake" but "material for improvement decisions," designed in linkage with the level promised to the customer in the SLA.
Most-tested points: "operations design prepares structure/procedures/escalation before service starts," "too much staff raises labor cost, too little breaches the SLA; multi-skilling removes individual dependence," "cost optimization separates waste from safety investment on the premise of maintaining the SLA (do not cut into the safety margin)," "KPIs are numbers for improvement decisions, linked to the SLA," and "govern supplier/resource/budget in a planned way." Questions test choosing a structure that is neither excessive nor deficient in the SLA-versus-cost trade-off.
6.4.3Supplier, resource, budget management, and design judgment
Suppose a service manager designs the operating structure for an online service whose load concentrates at month-end, optimizing cost while meeting the SLA (99.9% availability, 24-hour first-response reception). First, staffing. Meeting 24-hour reception requires overnight/holiday shifts, but pinning the same daytime headcount through the low-load small hours makes labor cost excessive. So the manager allocates staff by time band from the load trend (month-end peak, overnight trough), running normal overnight hours with a small first-response team plus on-call (standby) and reinforcing only at the month-end peak. But "only veteran A can do that task" is individual dependence—a single point of failure that makes the SLA unmeetable during A's leave or departure—so it is resolved by multi-skilling through runbooks and training, letting several people handle first response. Next, cost optimization. Among running costs, routine backup, monitoring, and log collection can be automated to cut labor, but cutting into the staffing headroom (safety margin) for failure judgment and major-incident response would break down response when it matters, costing more through SLA breaches and lost trust—so the manager separates the waste that may be cut (excess standby headcount, unused resources) from the safety investment that must not be. For the outsourced data center and monitoring service, as supplier management (UC/contract), the manager confirms whether the supplier's SLA can meet the company's customer SLA and whether the demarcation of responsibility is clear, revising the contract if needed. Resources are right-sized against demand forecasts (canceling or scaling down excess capacity), and as budget management an annual operating budget is set, with actuals (KPIs: SLA attainment, MTTR, incident count, cost actuals) continuously measured to manage the planned-vs-actual gap and remediated early if an overrun is foreseen. Designing staffing and shifts neither excessively nor deficiently from the SLA target, protecting safety investment while cutting waste, and governing supplier, resource, and budget by KPI is the judgment of operations design.
| What is managed | Aim | Harm of overdoing it |
|---|---|---|
| Staffing/shift | Allocate SLA-meeting structure by time band | Excess = labor cost up; too little = SLA breach |
| Cost optimization | Cut waste while maintaining the SLA | Cutting the safety margin costs more via more failures |
| KPI | Quantify operational quality for improvement | Meaningless if measured but not fed into improvement |
| Supplier/budget | Govern supplier SLA and plan-vs-actual gap | Neglect blurs responsibility and overruns budget |
Trap: "The more staff, the better for meeting the SLA" is wrong—excess staffing swells labor cost, and the practice is to allocate neither too much nor too little by time band in the SLA-versus-cost trade-off. "Cost optimization means cutting cost by any means" is a misconception—cutting into safety/availability investment costs more through increased incidents, so separate the waste that may be cut from the investment to protect. "A KPI achieves its purpose once measured and reported" is wrong too—a KPI has value only when made material for improvement (PDCA). "Work only one person can do is fine as long as it runs" is also wrong—that is individual dependence, a single point of failure, resolved by multi-skilling.
6.4.4Section summary
- Operations design prepares structure/procedures/escalation before service starts; allocate shifts/staffing by time band neither excessively nor deficiently and remove individual dependence (a single point of failure) via multi-skilling
- Cost optimization separates waste from safety investment on the premise of maintaining the SLA (do not cut the safety margin); tie KPIs to the SLA and use them for improvement decisions
- Govern supplier/resource/budget management—supplier SLA, responsibility demarcation, and plan-vs-actual gap—in a planned way (neglect blurs responsibility and overruns budget)
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. For a 24/7/365-reception service, the same headcount as daytime is placed even in the small hours, making labor cost excessive. Which staffing design best optimizes while maintaining the SLA (24-hour first response)?
Q2. Ordered to cut operating cost, in addition to automating routine backup monitoring, you are about to uniformly cut the staffing headroom (safety margin) for major-incident response. Which is the most appropriate view of cost optimization?
Q3. For operational improvement you tally KPIs such as MTTR and SLA attainment monthly and compile them into a report, but you only record the values without connecting them to improvement. Which correction to KPI usage is most appropriate?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.