ToC in Services
Pattern: A named solution to a recurring problem.
Translate the Theory of Constraints from goods-world assumptions to service work: manage resource buffers instead of inventory buffers, capacity response instead of fixed release control, service deliverables instead of product units, and client value instead of cost-plus service pricing.
Also known as: TOC for Services; TOCS; TOC in Professional, Scientific, and Technical Services.
Services expose the same constraint logic as manufacturing, but they hide the constraint differently. There may be no inventory pile before a machine, no raw material to buffer centrally, and no product unit whose cost can be counted cleanly. The work is a legal matter, a payroll run, an implementation project, a research engagement, a hospital visit, or a technical-support request. The constraint is often expert time, client participation, a service-level commitment, a resource pool, or the provider’s own policy about what work it agrees to start.
Context
ToC in Services sits one level below Services Management. Services Management gives the seven-step operating frame: state the goal, define global measures, then run the Five Focusing Steps. Ricketts’s services work asks the next question: what happens to the standard TOC applications when the system sells service rather than goods?
Ricketts treats professional, scientific, and technical services as the hardest test case because they are customized, expert-heavy, client-facing, and usually light on physical inventory. A law firm, engineering consultancy, systems integrator, research lab, or IT services provider can’t usually apply the manufacturing version of DBR, replenishment, critical chain, or throughput accounting without translation. If the translation works there, it will usually work in the more repeatable service settings downstream: customer support, healthcare, education, government, and justice systems.
Problem
The first generation of TOC success stories made physical operations legible. The plant had work-in-process, the constraint had a queue, the buffer protected the drum, and throughput was tied to saleable product. Service organizations don’t give the practitioner those cues. A consulting firm may be late on client projects because it starts more engagements than its senior architects can absorb. A payroll service may be bound by a service-level agreement whose request volume arrives from the client’s employees, not from a schedule the provider controls. A technical-services provider may have enough people this month and not enough next month because a new contract changes the skill mix overnight.
The practitioner can’t simply tell the service provider to release less work into the system. The provider may not control the arrivals. The practitioner also can’t treat every person as a fixed resource in the manufacturing sense. People return from assignments, learn new skills, shift between projects and processes, and carry expertise that clients are buying directly. The service version of TOC has to preserve the focusing logic while changing the objects the logic acts on.
Forces
• The work-in-process is often intangible. A service request, case file, experiment, code change, or client deliverable can sit in a queue without looking like inventory.
• The client may be inside the flow. Outside counsel works with inside counsel; consultants work with client managers; technical specialists depend on client data, access, and decisions.
• Demand arrives with less provider control. Under a service-level agreement, a provider can’t always delay or deny incoming work without breaking the promise it sold.
• Expert resources are renewable but not interchangeable. A senior tax partner, systems architect, or research scientist returns from one assignment and can be reassigned, but only if the next assignment needs that skill.
• Cost-plus pricing hides value. Standard billing rates can anchor the provider on internal cost instead of the business value the client receives.
• Expert cultures resist outside prescriptions. Professionals, scientists, and technicians are hired for judgment; they won’t accept a mechanical schedule if it ignores the reason clients buy their expertise.
Solution
Translate the standard TOC applications into services by preserving the principle and changing the managed object.
| Goods-world TOC | Service-world translation | What changes |
|---|---|---|
| Replenishment for Goods | Replenishment for Services | Buffer the net change in reusable resources, usually by skill group, rather than the consumption of physical inventory. |
| Critical Chain for Goods | Critical Chain for Services | Protect delivery with project buffers and relay-race work rules, but combine them with resource replenishment when client demand changes the resource mix. |
| Drum-Buffer-Rope for Goods | Drum-Buffer-Rope for Services | Use the constraint to pace the service process, but let the rope trigger capacity adjustment when incoming requests aren’t under provider control. |
| Throughput Accounting for Goods | Throughput Accounting for Services | Measure throughput from project deliverables and process service levels; treat skills, intellectual capital, assets, and proposals as investment-like commitments. |
The most important translation is the resource buffer. Physical inventory leaves when it is shipped; people and skills return from assignment. Resource replenishment therefore tracks net consumption: the difference between resources going out on work and resources returning to the available pool. A professional-services firm that needs one additional data-architecture consultant per month and takes 60 to 90 days to hire or train one does not wait for a signed deal before starting the pipeline. It sizes a resource buffer for that skill group and replenishes when the buffer falls below target.
Critical Chain for Services builds on the same idea. Traditional multi-project critical chain assumes a relatively fixed internal constraint and staggers projects around it. In services, the provider often sells against external demand and then acquires, trains, or reallocates resources to meet it. The resource buffer protects the promise to the client; the project buffer protects the due date. If one is missing, the other is brittle.
Drum-Buffer-Rope for Services keeps the drum and buffer logic but changes the rope. In a factory, release control modulates jobs entering the system so the constraint stays loaded without drowning. In a service process under an SLA, requests may arrive from the client’s customers, employees, or users. The provider may not control release. The rope therefore reads buffer thresholds and changes capacity: add trained capacity when the request buffer climbs above the upper threshold, remove or redeploy capacity when it falls below the lower threshold.
Throughput Accounting for Services makes the financial translation. Services generate throughput from delivered outcomes: a completed engagement, a service level met, a case resolved, a system implemented. Investment is less about plant and physical inventory and more about skills, intellectual capital, service assets, proposal work, and production systems. Operating expense is mostly professional labor, partner or principal time, and SG&A. The rule still holds: don’t allocate operating expense into fake service costs and then decide the service mix from those allocations. Rank work by throughput against the constraint.
Do not import factory cues unexamined: If a service flow has physical inventory or a repeatable process, manufacturing TOC may transfer almost directly. If the service is customized, expert-heavy, and SLA-bound, the practitioner needs the service translation first. Treating every service firm like a factory usually misidentifies the constraint.
How It Plays Out
An engineering consultancy wins more implementation work than its small group of senior integration architects can absorb. The old answer is hire-to-deal: wait until a contract is signed, then start recruiting. Clients won’t wait that long. The firm switches to Replenishment for Services. It defines a resource buffer for integration architects, tracks the net change in available architects as projects start and finish, and begins hiring or cross-training when the buffer falls below target. The constraint is still expert time, but the firm no longer treats expert time as a fixed resource that must ration demand forever.
A payroll service center serves thousands of employees on behalf of multiple client companies. The provider cannot control when employees submit requests, but the SLA requires a response inside a fixed window. Manufacturing DBR would release work to protect a fixed-capacity constraint. DBR for Services reads the request buffer instead. When the buffer crosses the red zone, trained staff shift into payroll processing and non-urgent work pauses; when the buffer shrinks below the lower threshold, staff return to other work. The rope is no longer only a release signal. It is a capacity signal.
A technical-services provider prices every project from a standard rate card. Two engagements that consume the same senior-consultant hours get the same price even when one protects a client’s renewal revenue and the other is routine maintenance. Throughput Accounting for Services changes the bid review. The provider estimates the client’s value, the truly variable costs, and the constraint hours required. Work that produces high throughput per constraint-hour moves forward; work that only looks profitable after allocated overhead is challenged. The sales conversation shifts from “what will our cost-plus rate support?” to “what problem is the client paying to remove?”
Consequences
Benefits.
• Services stop being treated as failed factories. The practitioner keeps TOC’s focusing logic while changing the objects being buffered, scheduled, and measured.
• Resource buffers give service providers a practical middle path between hiring far ahead of demand and waiting until a deal is already late.
• DBR for Services makes SLA-bound processes manageable because buffer status triggers capacity movement rather than pretending the provider controls every arrival.
• Throughput Accounting for Services protects service mix and pricing decisions from the distortions of allocated service cost.
• The pattern creates a bridge from the general services framework to domain entries such as healthcare, customer support, education, government, and justice.
Liabilities.
• The translation work is conceptually expensive. A manager who has only read The Goal may expect one visible constraint and one obvious buffer; the service version asks them to reason about resource pools, skill groups, client coproduction, and value pricing.
• Resource buffers can become disguised slack if the provider doesn’t define the protected skill group and trigger rules precisely.
• Capacity-response ropes need cross-training and management authority. Without them, the signal is real but nobody can act on it fast enough.
• Value-based throughput decisions can collide with professional norms, especially where standard rates, billable-hour expectations, or partner-credit systems carry political weight.
• Expert cultures may reject TOC if the implementation sounds like generic utilization control. The buy-in work is part of the method, not a preface to it.
Related Articles
Refines: Critical Chain — Critical Chain for Services keeps the project-buffer discipline but pairs it with resource replenishment because professional-services firms sell work whose resource demand changes with the client portfolio.
Refines: Drum-Buffer-Rope (DBR) — Drum-Buffer-Rope for Services keeps the constraint-paced flow logic but changes the rope from fixed release control to capacity adjustment when service requests arrive outside the provider's control.
Refines: Services Management (TOC) — ToC in Services takes the services-management frame into Ricketts's service-specific translation layer: resources, projects, operations, and measures are adapted from goods-world TOC to service work.
Refines: Throughput Accounting — Throughput Accounting for Services keeps the T-I-OE decision rule while replacing product cost and physical inventory with service deliverables, intellectual assets, resource buffers, and operating expense.
Upstream of: ToC for Healthcare — Healthcare is one domain specialization of the broader services pattern: patient flow, bed availability, and external care targets are service-flow variants of the same translation problem.
Uses: Buffer Management — Services work still uses time-based buffers, but the buffer is read through service requests, resource availability, service-level commitments, and due-date performance rather than a physical queue before a machine.
Sources
• Ricketts, John Arthur, “Theory of Constraints in Professional, Scientific, and Technical Services,” in Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 29. The chapter this entry primarily follows: the goods-versus-services translation, the professional/scientific/technical-services test case, and the service versions of replenishment, critical chain, DBR, and throughput accounting.
• Ricketts, John Arthur, Reaching The Goal: How Managers Improve a Services Business Using Goldratt’s Theory of Constraints (2007/2008, IBM Press). The book-length treatment behind the Handbook chapter and the source Ricketts points to for the fuller TOC for Services model.
• Cox, James F., TOCICO Dictionary (2nd ed., 2012), entries “strategic gating,” “tactical gating,” and “garbage time (of a bottleneck).” The certification-grade vocabulary for the services-side adaptations that appear across this section.
• Goldratt and Cox, The Goal (1984; later revised editions). The originating goods-world treatment of the focusing logic, DBR discipline, and constraint-centered management that Ricketts translates for service work.