Services Management (TOC)
Pattern: A named solution to a recurring problem.
The TOC discipline for managing a service organization: prepend two steps to the focusing loop (state the goal, define global performance measures), name the permanent bottlenecks the service flow carries (typically Sales and Marketing on the customer-facing side and IT on the development side), and run identification, exploitation, subordination, and elevation against those bottlenecks under a time-and-flow vocabulary rather than a unit-cost one.
Also known as: Focused Management for Services; the seven-step framework (when paired with the two preliminary steps Pass and Ronen add).
Eighty to ninety-five percent of the global workforce is in services, and the field’s management practice has lagged manufacturing’s by a generation. The TOC literature focused on production, projects, and supply chain because the Drum-Buffer-Rope success stories were dramatic and the work-in-process was physical. Service work-in-process is often invisible (a software ticket, a loan application, an insurance claim, a code review), the bottlenecks are typically permanent (a Sales and Marketing department or an IT development queue that no amount of hiring will turn into a non-bottleneck), and the customer is frequently inside the process rather than at the receiving end of it. The pattern names what transfers from manufacturing TOC and what has to be added for services to be a peer domain rather than a special case.
Context
Services Management anchors the services section because every domain-specific application (customer support, healthcare, education, government, justice systems) is a specialization of the same framework. The pattern presupposes The Goal, Constraint, and Five Focusing Steps; the new material is the diagnostic vocabulary for a service flow, the two preliminary steps that turn the focusing loop into a seven-step framework, and the named permanent bottlenecks the service architecture carries.
The pattern operates at the scale of a service organization rather than at the scale of an individual service transaction. Practitioners running a single help-desk queue or a single approval workflow apply Drum-Buffer-Rope directly, with the service-side adaptations the TOCICO Dictionary names DBR-for-services (controlled release plus the complete-kit discipline). Services Management is the framework that names which queues to look at first, which performance measures to run them against, and how to recognize a service constraint that doesn’t look like a machine. Domains for which the pattern has documented implementations include banks, insurance companies, telecommunications carriers, credit-card companies, hospitals, law courts, professional-services firms, retail chains, government agencies, the hospitality industry, and education.
Problem
A service organization has decided that operational improvement matters, has heard of TOC through The Goal or a consulting engagement, and now faces the question of where to apply the focusing loop. The manufacturing vocabulary (batch size, setup time, raw materials, finished goods, drum schedule) does not transfer cleanly. The work-in-process is non-physical or only intermittently physical. Bottlenecks are hard to spot because there’s no inventory pile to walk past. The goal, especially in government or nonprofit settings, may not reduce to shareholder value. And the cost structure runs heavily fixed: labor is the dominant expense, with no raw-material cost to vary against throughput. Practitioners who have heard “find the bottleneck and focus there” cannot find the bottleneck, can’t name the goal cleanly enough to calibrate exploitation, and can’t separate productive bottleneck time from the activity that fills the day.
What the practitioner needs is a diagnostic frame that names the services-specific permanent bottlenecks before walking the floor, supplies the goal-stating and measure-defining work the focusing loop assumes is already done, and translates exploit/subordinate/elevate into moves that work on flows where the unit is a customer interaction or a development task rather than a machined part.
Forces
• Service work-in-process is often invisible. A patient sitting in an A&E waiting room is countable; a software ticket sitting in a developer’s queue is countable but invisible to anyone not looking at the tracker; a loan application sitting on a credit officer’s desk has no analog of the painted aisle on a shop floor. The practitioner needs diagnostics that surface invisible WIP without depending on the visual cues manufacturing TOC inherited from physical plants.
• Service constraints are frequently permanent. Pass and Ronen’s empirical observation is that most service organizations carry two standing bottlenecks: a Sales and Marketing department that never has enough capacity for all the deals worth pursuing, and an IT development department whose backlog runs 300 to 500 percent of capacity. These aren’t constraints in the sense that elevation removes them; elevation only changes how much of the backlog gets processed. The pattern has to name permanence as a structural property of services rather than as a failure of elevation.
• The customer is inside the process. In manufacturing, the customer is at the back of the flow. In services, the customer is often a co-producer (the patient describing symptoms, the bank customer filling in the form, the litigant testifying). Subordination has to account for the customer’s pace and accuracy, not only the service organization’s.
• Fixed-cost share is higher than in manufacturing. A bank’s cost is mostly people; a hospital’s cost is mostly people; a software organization’s cost is mostly people. Throughput Accounting becomes sharper as a decision lens because most cost variation comes from how the fixed-cost capacity is allocated, not from raw-material flow. Cost accounting’s allocation games are correspondingly more misleading.
• Goals can be plural. For-profit service organizations have shareholder value as a goal in the same form as manufacturers, but nonprofit, governmental, healthcare, and educational organizations frequently carry multi-dimensional goals (medical outcomes, student progression, judicial throughput, public trust) that don’t reduce to money. The focusing loop has to be calibrated against the actual goal, not against a borrowed manufacturing-style profit target.
Solution
Run the service organization through seven steps, in order, with the canonical Five Focusing Steps as Steps 3 through 7 and two preliminary steps prepended to handle the goal-definition and measurement work that manufacturing TOC’s audience usually has already done.
Step 1 — State the goal of the organization. For a for-profit organization the goal is shareholders’ value, defined as discounted cash flow per Ronen and Pass. For a nonprofit, government, or mission-driven organization the goal is a defined set of outcome measures against the organization’s mission, with resource limitations stated explicitly. The step exists because services organizations often haven’t named the goal cleanly enough to calibrate the rest of the loop; manufacturing’s audience usually inherits a P&L target and skips this step without noticing.
Step 2 — Define global performance measures. Beyond the canonical Throughput, Inventory, and Operating Expense, Ronen and Pass add three measures the service environment needs: Lead Time (measured from customer request to delivery), Quality (a composite of customer perception, process quality, and garbage-time share), and Due-Date Performance (adherence to the Service Level Agreement). The added measures are not optional; they’re what makes a services TOC implementation legible to a non-TOC manager and what gives the focusing loop its calibration when the work-in-process is non-physical.
Step 3 — Identify the system constraints. Two standing internal bottlenecks are the default starting point: Sales and Marketing on the customer-facing side and IT development on the internal-capability side. The Cost-Utilization (CUT) diagram is the service-side diagnostic that surfaces them: a histogram in which each bar is a resource or department, the bar’s height is its utilization, and the bar’s width is its cost. A department that stands tall and wide is a permanent bottleneck; a department that’s wide but short is a candidate for offloading work to. The market constraint is identified at the same time and is typically the overall system constraint: most service organizations have excess capacity for the customers they could be serving, with the external constraint binding total Throughput.
Step 4 — Decide how to exploit the system constraints. Exploitation in services runs along two axes: efficiency and effectiveness. Efficiency is the elimination of garbage time — time the bottleneck resource spends on activities nobody should be doing or that a non-bottleneck should be doing. Field measurements put garbage time at 20 to 60 percent of bottleneck hours in IT development and 30 to 50 percent in sales operations, recovered through Pareto analysis of recurring time-wasters and the structural moves (back-office offload, complete-kit discipline, meeting reduction) that eliminate them. Effectiveness is strategic gating: rank tasks competing for bottleneck time by their specific Throughput (value to the organization divided by bottleneck-hours required), execute in priority order, and put non-priority tasks into firm-freeze status rather than a contingency list that quietly re-introduces them under organizational pressure. In one financial-institution case Pass and Ronen document, strategic gating raised effective IT capacity by fifteen percent without hiring by refusing to start the lowest-priority forty percent of the requested portfolio.
Step 5 — Subordinate everything else. Services subordination is double subordination: the whole organization subordinates to the market constraint (everything the customer-facing departments do is calibrated against the demand the market actually expresses), and every non-IT department subordinates to IT development when IT is the standing internal bottleneck. The operational mechanics are the Subordination entry’s two rules — non-constraints deliver exactly what the constraint needs when it needs it, and non-constraints don’t process work the constraint won’t absorb — translated into the service vocabulary by tactical gating: a controlled release mechanism that admits work into the service flow only when it arrives as a complete kit (all the inputs the bottleneck will need, in a single packet, before the bottleneck starts), in small batches, and on the schedule that protects the constraint.
Step 6 — Elevate the system’s constraints. Elevation in services has the usual capacity-addition form (hiring, training, contracting) but Pass and Ronen name a second elevation mechanism that’s especially valuable in services: offload. Offload directs repetitive or non-specialist tasks to non-bottleneck resources, freeing bottleneck capacity for the work only the bottleneck can do. In a medium-sized insurance company Pass and Ronen document, a Pareto analysis found that salespersons spent only thirteen percent of the workday in face-to-face customer meetings; offloading customer retention and administrative tasks to the back office doubled meeting time and produced a twenty-percent sales increase with no headcount change. The cost-per-throughput-unit ratio of offload is typically far better than the cost-per-throughput-unit ratio of hiring.
Step 7 — When a constraint has been broken, return to Step 3. Do not allow inertia to become the system’s constraint. The warning clause is more load-bearing in services than in manufacturing because service organizations carry permanent bottlenecks that survive most elevation moves; the failure mode is treating an elevated bottleneck as removed and quietly de-funding the discipline that kept it running well. The IT department that just got fifteen percent more developers is still the binding internal constraint; subordination doesn’t relax.
The seven steps form a closed cycle. The cycle is the operational definition of the Process of Ongoing Improvement (POOGI) applied to a service organization.
flowchart TD
A["1 — State the goal"] --> B["2 — Define global measures"]
B --> C["3 — Identify the constraints"]
C --> D["4 — Exploit: garbage-time + strategic gating"]
D --> E["5 — Subordinate: market + IT, via tactical gating"]
E --> F["6 — Elevate: hire or offload"]
F --> G{Constraint broken?}
G -->|No| D
G -->|Yes| C
Two operational vocabularies do the heavy lifting across the seven steps: strategic gating (priority-ranking the work for the constraint) and tactical gating (controlled release into the service flow). The two are sister disciplines: strategic gating runs at the planning horizon (which deals will Sales pursue this quarter, which features will IT build this year) and tactical gating runs at the execution horizon (which ticket gets released into the development queue this hour, which customer interaction the agent takes next). Service organizations that adopt one without the other tend to plan well and execute badly, or execute crisply against the wrong priorities.
How It Plays Out
A medium-sized regional bank has stalled at roughly the same volume for three years, despite a marketing department running at full effort and an IT department that’s been hiring continuously. The CEO suspects the system has a constraint and engages a TOC practitioner. The practitioner walks the CUT diagram and finds two permanent bottlenecks: Sales and Marketing is wide and tall (high cost, fully loaded), and IT development is also wide and tall, with a backlog running 420 percent of capacity. Operations and customer service are wide but short, carrying protective capacity exactly as the framework predicts. The bank’s stated goal is shareholder-value growth, which translates cleanly into throughput. Step 1 and Step 2 are quick. Step 3 names both bottlenecks. Step 4 starts with garbage-time elimination at IT: a Pareto analysis of developer time finds that 38 percent of developer hours go to rework caused by incomplete requirements arriving at the team, and another 12 percent to status meetings that could be reduced to a weekly summary. Mandating complete-kit submission of requirements and cutting the meeting load recovers a third of those hours within ninety days. Step 5 (strategic gating of the IT portfolio) refuses the lowest-priority 40 percent of pending feature requests, putting them into firm-freeze status rather than back-of-queue. Within six months, IT throughput (features released, weighted by specific Throughput) is up 35 percent, the marketing team has enough working features to run the campaigns it was waiting on, and revenue tracks accordingly. The pattern produced result without one new hire.
An A&E department at a public hospital is missing the national four-hour-discharge target (patients seen, treated, and discharged or admitted within four hours of arrival) for 40 to 50 percent of patient presentations. The goal is named in legislation (the four-hour standard), the measures are the standard (lead time, due-date performance against the four-hour clock, quality measured by readmission rate and complication rate, throughput measured by patients-presented-and-discharged-or-admitted per day). The practitioner walks the CUT diagram for patient flow and finds the bottleneck is not triage (high utilization but high protective capacity) and not the A&E consultants (busy but able to keep pace with arrival rate); the bottleneck is downstream: specifically, bed availability on the inpatient wards, which delays admission decisions and causes patients to occupy A&E bays they shouldn’t be in. Exploitation rewrites the discharge process on the wards to free beds earlier in the day, with the discharge decision made before the morning round rather than after. Subordination synchronizes the morning ward round, the bed-cleaning rotation, the porter schedule, and the social-work consultation against the discharge clock. Within two months, the four-hour rate has risen to 95 percent. (This is the Oxfordshire Radcliffe Hospital A&E case in compressed form; see the dedicated Oxfordshire Radcliffe Hospital A&E entry for the full record.)
A regional law firm’s partners report that case throughput is bottlenecked by senior partners’ time, that hiring senior partners is impossible at the current revenue level, and that the firm cannot grow. The TOC practitioner runs Steps 1 and 2 (goal: profit per partner, against the conventional partnership measures; performance measures: case throughput, lead time per matter type, due-date performance against client deadlines, garbage time at the senior-partner level). Step 3 identifies senior-partner time as the binding constraint. Step 4 finds that senior partners spend 47 percent of working hours on tasks a senior associate could do (drafting standard motions, reviewing precedent, attending procedural hearings): pure garbage time at the bottleneck. An offload program (the elevation move) restructures the associate-partner relationship so that senior partners review and approve rather than draft and attend, recovering roughly a third of their time within six months. The firm grows case load by 40 percent over the year. Hiring more senior partners would have been Step 6’s first reflex; offload was the cheaper and faster version of the same step.
Consequences
Benefits.
• A diagnostic frame that names the standing service-side bottlenecks (Sales and Marketing, IT) before the practitioner walks the floor, sparing the discovery-by-induction time manufacturing TOC frequently requires.
• A measurement set (throughput, lead time, due-date performance, quality, inventory as WIP, operating expense) calibrated to services rather than to physical production; legible to non-TOC service managers who would not have a vocabulary for buffer penetration.
• The garbage-time discipline is one of the highest-yield exploitation moves in the TOC repertoire — 20 to 60 percent of bottleneck capacity is the typical recoverable share, against the 5 to 15 percent more capital-intensive elevation typically produces.
• Strategic gating gives the organization a defensible refusal of low-priority work, which most service organizations lack and which is the structural cause of the bottleneck’s overload.
• Offload (as an elevation mechanism) typically improves the throughput-per-cost ratio more than hiring does, because the offloaded tasks were always cheaper to perform at non-bottleneck resources.
• The framework transfers across service domains (financial, healthcare, professional services, public sector) without changing the seven steps, which is what lets the rest of the services section build domain specializations on top of it.
Liabilities.
• The two preliminary steps add real work to the start of the engagement. Service organizations whose existing goal definitions are vague (especially nonprofits and public-sector organizations) find Step 1 alone takes weeks, and skipping it produces a focusing loop calibrated against the wrong objective.
• The permanent-bottleneck framing risks a paradigm trap: practitioners who internalize “Sales and IT are the constraints” can stop running Step 3 cleanly and miss a constraint that has moved to a service-delivery resource (operations capacity, customer-facing specialist availability) or to a market segment.
• The garbage-time measurement is intrusive at first and resisted by the bottleneck resources themselves; the implementation needs explicit management air cover before the measurement begins.
• The tactical gating mechanism requires a credible gatekeeper who can refuse work admission against organizational pressure. Service organizations whose culture rewards everyone-doing-everything tend to undermine the gatekeeper role within months unless the gating is supported from the top.
• The framework’s heavy reliance on cost-utilization diagrams and Pareto analysis can read as consultant-speak to a senior service-side audience accustomed to a different vocabulary. The translation work into the host organization’s language is part of the implementation cost.
Related Articles
Complements: Throughput Accounting — Service organizations carry a higher fixed-cost ratio than manufacturers, which makes the T-I-OE frame even sharper as a decision lens than in production; the pattern's pricing, transfer-pricing, and make-or-buy guidance rests on Throughput Accounting.
Contrasts with: Policy Constraint — Service-flow constraints are disproportionately policy constraints (incentive rules, escalation policies, approval-chain structures, professional-licensure scopes), and the pattern names the diagnostic shift from physical-constraint exploitation to policy rewrite.
Corrupted by: Efficiency Trap — Headcount-utilization targets and per-specialist activity quotas keep service non-bottlenecks busy and starve the permanent bottleneck of the protective capacity it needs; the pattern's protective-capacity rule is the corrective.
Depends on: The Goal (concept) — Ronen and Pass's seven-step framework begins with stating the goal because services organizations (particularly nonprofits) frequently lack a clear shareholder-value or analogous goal definition, and the rest of the loop has no anchor without one.
Enforces: Exploitation Without Elevation — The service-side exploitation move is garbage-time elimination (reclaiming the 20-60 percent of bottleneck time spent on rework, unnecessary meetings, and tasks a non-bottleneck should be doing) before any hiring or capacity expansion.
Enforces: Subordination — Subordination in services means two simultaneous subordinations: the whole organization to the market constraint (typically external), and every non-IT department to the IT development queue when IT is the standing internal bottleneck.
Prevents: Local Optimization — Service organizations are especially prone to local-efficiency measurement (utilization of every specialist, call-counts per agent, billable hours per consultant), and the pattern names the move from local efficiency to specific-Throughput-per-bottleneck-hour ranking.
Produces: Throughput — Throughput in services is money generated through delivered service, not service activity completed; the pattern's effectiveness move (strategic gating against specific Throughput) is the service-side discipline that keeps activity from substituting for throughput.
Refines: Drum-Buffer-Rope (DBR) — Service DBR (DBR-for-services) adapts the manufacturing pattern to non-physical work-in-process by combining tactical gating (controlled release into the service flow) with the complete-kit discipline that prevents starting work without the inputs the constraint will need.
Specializes: Five Focusing Steps — Services Management is the service-flow specialization of the Five Focusing Steps, with two preliminary steps prepended for nonprofit and value-driver work (state the goal; define global performance measures) before the canonical identify/exploit/subordinate/elevate/repeat loop.
Uses: Buffer Management — Service buffers are time-based as elsewhere in TOC, but the readings track WIP-aging and due-date-performance against Service-Level-Agreement commitments rather than physical buffer penetration at a shop floor.
Uses: Constraint — Services flows carry permanent bottlenecks (typically Sales and Marketing on the customer-facing side and IT on the development side) that survive elevation; the pattern names those resources as the standing identification target.
Uses: Constraint Type Identification — The pattern depends on naming service constraints as policy or capacity-constrained rather than physical; the Cost-Utilization diagram is the service-side diagnostic that surfaces which department is the standing bottleneck.
Sources
• Cox, TOCICO Dictionary (2nd ed., 2012), entries “DBR for services,” “replenishment for services,” “tactical gating,” “strategic gating,” “garbage time,” “protective capacity” — the certification-grade definitions for the service-side adaptations of the manufacturing vocabulary. The Dictionary is distributed through TOCICO membership and doesn’t carry an Open Library record.
• Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 28 (Ronen and Pass, “Services Management”) — the chapter-length framework from which this entry’s seven-step structure, the CUT diagram, the permanent-bottleneck observation (Sales, IT), the garbage-time and strategic-gating disciplines, and the offload elevation mechanism are drawn. Ch. 29 (Ricketts), Ch. 30 (Klarman and Klapholz), Ch. 31 (Wadhwa), and Ch. 32 (Wright) extend the pattern into professional services, customer support, and healthcare.
• Ronen and Pass, Focused Operations Management: Achieving More with Existing Resources (2008, John Wiley & Sons) — the book-length treatment that supplies the value-driver vocabulary, the complete-kit discipline, the Global Decision-Making methodology, and the field examples behind the Handbook chapter’s empirical claims. Required reading for any practitioner adapting the framework to a specific service-organization engagement.
• Pass and Ronen, “Managing the market constraint in the hi-tech industry,” International Journal of Production Research 41:4 (2003), 713–724 — the peer-reviewed paper that introduces the permanent-bottleneck observation for Sales/Marketing and IT, and that names the seven-step framework as an extension of the canonical Five Focusing Steps.
• Goldratt and Cox, The Goal (1984; revised 1986, 1992) — the originating treatment of the Five Focusing Steps that the services framework specializes; the seven-step framework prepends two steps to Goldratt’s five rather than replacing them.