Operations Reference

The RCC Operations Glossary

Clear operating language makes better decisions possible. This glossary defines the terms Ricardo Cruz Consulting uses when diagnosing operational friction, redesigning workflows, reducing founder dependency, and building systems that can support sustainable growth.

B

Blocked capacity

Also called: hidden capacity, trapped capacity, unused operational capacity

Blocked capacity is productive time or service potential that exists inside a business but cannot be used because manual work, waiting, unclear decisions, rework, or coordination consumes it first.
How RCC uses this termRCC uses blocked capacity to distinguish a true staffing shortage from capacity that can be recovered by redesigning how work moves.
Operational Efficiency for Service Businesses →

Business process

Also called: end-to-end process, operating process

A business process is an end-to-end sequence of connected work that produces a defined business or client outcome across people, decisions, systems, data, and controls.
How RCC uses this termRCC treats a process as broader than one task or workflow. Client onboarding, service delivery, billing, and issue resolution are business processes because each crosses several stages and owners.
Business Process Automation for Service Businesses →

Business process automation

Also called: BPA, end-to-end process automation

Business process automation redesigns and coordinates an end-to-end business process across people, workflows, systems, decisions, data, and controls so the complete outcome becomes more consistent and less dependent on manual coordination.
How RCC uses this termRCC uses business process automation when the problem spans several workflows, departments, or systems and cannot be solved by automating one isolated task.
Business Process Automation for Service Businesses →

C

Cycle time

Also called: process cycle time, turnaround time

Cycle time is the elapsed time required for work to move from a defined starting point to a completed outcome, including active work, waiting, review, and handoff delays.
How RCC uses this termRCC measures cycle time to expose where a process is slow even when the amount of active work appears reasonable.
Operational Efficiency for Service Businesses →

D

Decision rights

Also called: decision authority, delegated authority

Decision rights define who may make a decision, within what limits, using which criteria, and when the issue must be escalated.
How RCC uses this termRCC uses decision rights to convert vague delegation into explicit authority so routine decisions stop returning to the founder or senior leader.
Founder Dependency in Service Businesses →

E

Exception path

Also called: exception workflow, escalation path

An exception path is the defined route work follows when the normal workflow cannot continue because information is missing, risk is elevated, a rule does not apply, or human judgment is required.
How RCC uses this termRCC designs exception paths before automation so unusual cases remain visible, owned, and controlled instead of becoming silent failures.
Workflow Automation for Service Businesses →

F

Founder dependency

Also called: owner dependency, key-person dependency on the founder

Founder dependency exists when routine decisions, knowledge, client trust, problem resolution, or coordination still require the founder's direct involvement for the business to operate consistently.
How RCC uses this termRCC treats founder dependency as an operating-design problem that must be reduced through documented knowledge, explicit decision rights, transferable relationships, and owned processes.
Founder Dependency in Service Businesses →

M

Manual handoff

Also called: manual transfer, informal handoff

A manual handoff occurs when one person must remember, communicate, forward, assign, or chase work so another person can begin the next step.
How RCC uses this termRCC evaluates manual handoffs for missing triggers, incomplete information, unclear ownership, and automation opportunities because these transition points often create hidden delay and rework.
Workflow Automation for Service Businesses →

O

Operational debt

Also called: operations debt, process debt, organizational debt

Operational debt is the accumulated cost and risk created when temporary workarounds, undocumented knowledge, unclear decisions, manual coordination, disconnected systems, or outdated controls become permanent parts of how a business operates.
How RCC uses this termRCC identifies operational debt by looking for recurring work or risk that remains unexamined, unowned, and more expensive each time the business grows.
Operational Debt in Service Businesses →

Operational efficiency

Also called: operations efficiency, efficient operations

Operational efficiency is the ability to produce a strong client and business outcome with less avoidable delay, rework, coordination, confusion, and unnecessary effort.
How RCC uses this termRCC evaluates efficiency across flow, quality, capacity, and control rather than treating faster work or lower cost as sufficient on their own.
Operational Efficiency for Service Businesses →

Operational friction

Also called: process friction, operating friction

Operational friction is the avoidable resistance that makes work slower, harder, less consistent, or more dependent on follow-up than the outcome requires.
How RCC uses this termRCC uses operational friction as a diagnostic category covering delays, unclear ownership, repeated questions, duplicate work, excessive approvals, poor handoffs, and manual coordination.
Operational Friction Audit →

P

Process owner

Also called: end-to-end process owner, process accountable owner

A process owner is the person accountable for the performance, clarity, control, and ongoing improvement of an end-to-end business process.
How RCC uses this termRCC separates process ownership from task ownership. Several people may complete steps, but one owner remains accountable for whether the full outcome works.
Business Process Automation for Service Businesses →

R

Rework

Also called: repeat work, correction work

Rework is effort spent correcting, repeating, reconstructing, or reprocessing work because the original output was incomplete, inaccurate, unclear, or unusable downstream.
How RCC uses this termRCC treats rework as a measurable signal of process design, information quality, handoff, or control failure rather than simply an employee-performance issue.
Operational Efficiency for Service Businesses →

S

Shadow system

Also called: shadow spreadsheet, unofficial system, workaround system

A shadow system is an unofficial spreadsheet, document, inbox, message thread, or personal tool used to perform work that the formal process or approved system does not support adequately.
How RCC uses this termRCC does not assume every shadow system should be removed. It first determines which need to be repaired, incorporated, replaced, or intentionally retained with an owner and control.
Operational Debt in Service Businesses →

Single point of failure

Also called: key-person risk, operational concentration risk

A single point of failure is one person, tool, decision, data source, or operating step whose absence or breakdown can stop a critical outcome.
How RCC uses this termRCC evaluates single points of failure by impact, recovery difficulty, and whether knowledge, authority, access, or continuity has been distributed appropriately.
Founder Dependency in Service Businesses →

T

Tribal knowledge

Also called: institutional knowledge in people's heads, undocumented knowledge

Tribal knowledge is important operating information that exists primarily in individual memory, informal conversation, or local habit rather than in an accessible and maintained source of truth.
How RCC uses this termRCC prioritizes tribal knowledge for capture when its loss would interrupt a client outcome, delay decisions, create compliance risk, or make onboarding dependent on repeated explanation.
Founder Dependency in Service Businesses →

W

Workflow

Also called: work sequence, operating workflow

A workflow is the defined sequence through which a specific piece of work moves from trigger to completion, including steps, owners, information, decisions, handoffs, and exceptions.
How RCC uses this termRCC uses workflow as the unit of analysis for repeatable work such as routing a request, approving an expense, following up with a client, or creating a report.
Workflow Automation for Service Businesses →

Workflow automation

Also called: automated workflow, process workflow automation

Workflow automation uses technology to move repeatable work through a defined sequence with fewer manual handoffs while keeping ownership and human judgment clear.
How RCC uses this termRCC automates only after the real workflow is mapped, unnecessary steps are removed, ownership is clear, and the normal and exception paths are defined.
Workflow Automation for Service Businesses →

Find the constraint behind the symptom

The Growth Capacity Assessment helps identify whether founder dependency, unclear ownership, workflow friction, or blocked capacity is creating the greatest constraint in your business.

Take the Growth Capacity Assessment